Webflow accessibility compliance: what the platform covers and what you must check
Webflow's built-in tools catch four kinds of accessibility problem. WCAG 2.2 Levels A and AA together have 55 criteria. This guide covers what Webflow handles, the gaps it tells you to check yourself, and a short test pass you can run before you publish.
Who is responsible: you, not the platform
Webflow gives you tools. It does not make a published site conform to WCAG. Webflow's own training says accessibility is "both a design responsibility and a technical one" (Accessibility in Webflow, Webflow University). On the legal side, the US Department of Justice's position is that businesses open to the public must ensure the goods and services they offer, including those offered on the web, are accessible (ADA.gov web guidance). The same guidance says there is no DOJ regulation with detailed technical standards for businesses, and points to WCAG as a helpful technical reference.
For a Webflow site, that turns into a short question: which parts did Webflow handle, which parts did your designer handle, and which parts did nobody check?
What Webflow gives you
- Semantic elements. Headings, paragraphs, buttons and links use the matching HTML elements when you use the matching Webflow elements, and links and buttons are keyboard-accessible by default.
- ARIA fields. The element settings panel has fields for roles, labels, and other ARIA attributes.
- The Audit panel. It runs four accessibility checks in the Designer: missing alt text, non-descriptive link content, skipped heading levels, and duplicate element IDs (Intro to the Audit panel, Webflow Help Center).
- A contrast checker in the color picker for text elements, plus a vision preview tool and a text zoom preview tool.
Where Webflow sites usually still fail
These are the gaps the Webflow documentation itself points at, plus the WCAG criterion each one maps to.
| Gap | Why it happens | WCAG 2.2 |
|---|---|---|
| Missing alt text where the Audit panel does not look | The panel does not check components, Lightbox media, or CMS-bound images. Webflow says to check these manually. | 1.1.1 Non-text Content (A) |
| Custom interactive elements | Webflow notes that custom elements built from div blocks and interactions may need extra work to be usable with a keyboard. | 2.1.1 Keyboard (A), 4.1.2 Name, Role, Value (A) |
| Text contrast | The Audit panel has no contrast check. The color picker checker helps, but only for text you test. | 1.4.3 Contrast (Minimum) (AA) |
| Motion and animation | Interactions that auto-play or move continuously need a way to pause, stop, or hide them. | 2.2.2 Pause, Stop, Hide (A) |
| Form labels and error messages | Visible labels and clear error text are a design choice you make in each form. | 3.3.1 Error Identification (A), 3.3.2 Labels or Instructions (A) |
| Third-party embeds and custom code | Chat widgets, cookie banners, booking tools and embedded code are outside Webflow's checks. WCAG conformance applies to the full page, so excluded parts do not count. | Conformance requirement 5.2.2; 2.4.11 Focus Not Obscured (AA) for banners that cover focused elements |
The first three rows come from Webflow's own help article and training video. The last three are common failure points, not Webflow admissions, so test them on your own site.
A 30-minute test pass for a Webflow site
- Run the Audit panel on every page template and clear what it flags. Then check the things it skips: CMS images, Lightbox images, components.
- Run the free accessibility scanner on the published URL, not the Designer preview. It catches rules the Audit panel does not, such as contrast.
- Put the mouse away. Tab through the home page, a form, and any menu or modal. Every control should be reachable, usable, and visibly focused, and focus should never disappear behind a sticky bar or cookie banner.
- Zoom to 200% and check that nothing is cut off or overlapping.
- Pause anything that moves. If an interaction runs without user input, there must be a visible control to stop it.
- Write down what you found. Use the WCAG 2.2 checklist for the record and the remediation plan template for the fixes.
Publish a statement that matches what you tested
A Webflow site needs an accessibility statement that names the standard you test against, what you know is not yet fixed, and how to reach a person. If you embed third-party tools, say so in the statement instead of implying you control them. The free accessibility statement generator gives you a draft, and the WordPress and Shopify guides show the same idea for other platforms.
Document what you tested, not just what you hope
Core Kit ($99) includes the WCAG 2.2 self-audit checklist, accessibility statements for the EU and US, an internal policy, and a remediation plan. They work with any platform, including Webflow.
Get Core — $99 Run the free accessibility scannerFAQ
Does Webflow make my site WCAG compliant?
No. Webflow provides tools such as the Audit panel, ARIA fields and contrast and vision preview tools, and says itself that the Audit panel is not a comprehensive audit. Conformance depends on how you build and what content and third-party code you add.
What does the Webflow Audit panel not check?
It runs four checks: missing alt text, non-descriptive link content, skipped heading levels and duplicate element IDs. It does not check text contrast, and it does not check alt text in components, Lightbox media elements, or CMS-bound images.
Do I need an accessibility statement for a Webflow site?
A statement is not a Webflow feature and not a substitute for testing, but it is the usual place to state your target standard, known gaps and a contact route.
Is this legal advice?
No. This page is general information and professional documentation guidance, not legal advice, and reading it does not create an attorney-client relationship. Have qualified counsel review anything you publish or send to a regulator, buyer, or court, especially if you have received a legal notice.