By platform · Webflow
In Webflow, Everything Is a Design Decision
Webflow outputs clean HTML and leaves the meaning of it entirely to you. That is the good news and the warning, and the built-in checker is quieter than most people assume.
Last reviewed August 30, 2026
For designers and agencies building client sites in Webflow who want them to hold up under review.
Webflow is unusual among visual builders. It outputs clean, standards-based HTML rather than a nest of wrapper divs, so the raw material is good. Whether that HTML means anything is settled by the person moving elements around the canvas. That is you.
Webflow does ship real semantic elements, so a heading you drag on is a heading. The trouble is the scaffolding around it. Div blocks, containers and anything you assemble yourself carry no meaning at all until you set the tag, and the whole accessibility story here is what you change those defaults into, and which of those choices the Audit panel will and will not mention.
What breaks on Webflow
The failures we find most often on this platform, and the rule each one breaks.
Everything defaulting to a div
A heading that looks like a heading but is a div block gives a screen reader user nothing to navigate by, and heading navigation is how most of them move around a page. The tag is set in element settings and it takes four seconds.
1.3.1 Info and Relationships
Link blocks used as buttons
An action that submits, opens or toggles should be a button. Links and buttons behave differently under the keyboard, are announced differently, and set a different expectation about what happens next.
4.1.2 Name, Role, Value
Interactions that break focus
A Webflow interaction can hide an element visually while leaving it in the tab order, so a keyboard user's focus disappears into a menu nobody can see and the page appears to stop responding.
2.4.7 Focus Visible
Custom dropdowns and tabs built from frames
The built-in components handle state properly. The same pattern rebuilt from div blocks and interactions looks identical and exposes nothing, so a screen reader never learns whether a panel is open or which tab is selected.
4.1.2 Name, Role, Value
Missing alt text on CMS images
Collection images pull their alt text from a field. If that field is empty or was never bound, every item on the page publishes with nothing, and the Audit panel is one of the places that will not tell you, because it does not check CMS-bound images.
1.1.1 Non-text Content
Removed focus outlines
Designers remove the browser's default outline because it clashes with everything. If nothing replaces it, a keyboard user has no way to see where they are on the page, which makes every other fix on this list irrelevant to them.
2.4.7 Focus Visible
The plugin question, answered
Webflow has an apps marketplace that installs inside the Designer, with hundreds of listings in it. Not one of them retrofits structure, because structure is a decision you make while building rather than a layer you add afterwards.
What you actually have for accessibility is the Audit panel, a contrast readout inside the color picker, and whatever you write into custom code. The Audit panel is worth running and worth understanding, because the list of what it stays quiet about is longer than the list of what it checks.
The Webflow Audit panel
A checker built into the Designer running four accessibility checks. Missing alt text, non-descriptive link content, skipped heading levels, and duplicate element IDs.
- What it does
- It catches mechanical failures while you are still building, grades each one critical or moderate, and groups missing alt text by where to go and fix it. Alt or Option plus U opens and closes the whole panel.
- What it cannot
- Webflow publishes what it misses, and that list is the more useful half. It does not look inside components, which is how every professional Webflow build is assembled. It does not check alt text on CMS-bound images or inside Lightbox elements. And it does not measure text contrast at all. Its fourth check, duplicate element IDs, is a hygiene warning rather than a conformance failure, because WCAG 2.2 removed the criterion that used to cover it.
The contrast readout in the color picker
A ratio measurement built into Webflow's own color picker for text elements.
- What it does
- It measures while you are choosing the color, which is a far cheaper moment than measuring after that color is used across sixty pages.
- What it cannot
- It measures a flat pair of colors. Text sitting over a photograph or a gradient has to be measured against the worst region of the image, and no picker does that for you. Use our contrast checker for those and sample the lightest part.
Custom code focus styles
A snippet in site-wide custom code that restores a visible keyboard focus style everywhere.
- What it does
- One block of CSS using :focus-visible restores an indicator across the whole site without showing it on every mouse click, and it is the single highest-value change on most Webflow builds. At Level AA the indicator needs 3:1 against the color next to it.
- What it cannot
- It does not fix elements that should not be focusable in the first place. And 3:1 against the background is not the only measurement in the standard. The stricter rule compares the focused and unfocused states on the same pixels, so an indicator can satisfy one and fail the other.
Overlay widgets (accessiBe, UserWay, AudioEye and the rest)
A script you paste into your template that draws a toolbar for visitors and claims to repair your pages automatically as they load.
- What it does
- The toolbar half is real. Bigger text, higher contrast, adjusted spacing and a reading guide are preferences some visitors use, and the field's own reference document on overlays says a non-trivial array of accessibility problems can genuinely be repaired this way.
- What it cannot
- It does not change the markup your server sends, and the categories it handles worst are the ones that decide whether a site works at all. Text alternatives, form labels and error handling, and keyboard access. More than 5,000 US digital accessibility lawsuits were filed in 2025, and the firm that compiles that dataset reads the filings the same way every year, which is that widgets do not materially reduce legal risk. Our overlays page has the documented record.
What to actually do
- Go through your elements and set real tags. H1 to H6 for headings, paragraph for body copy, button for buttons, nav for navigation.
- Add a visible :focus-visible style in custom code, at 3:1 against whatever sits next to it.
- Map the alt text field in every CMS collection, then open a published collection page and check it arrived, because the Audit panel will not.
- Test every interaction with the keyboard. Anything hidden visually has to leave the tab order too, or focus vanishes into it.
- Run the Audit panel, then run the free 10-page scan on the published site for the contrast and structure the panel never looks at.
- Check your color styles before they get used across sixty pages, using the picker's own readout for flat colors and ours for text over images.
On themes and templates
Webflow templates vary as widely as WordPress themes, though there is a published bar. Webflow's submission requirements carry an accessibility section, and a template has to meet those requirements and pass a quality review before it reaches the Marketplace. Read what the bar actually asks for, because much of it is heading hierarchy, contrast and alt text rather than the whole standard, and some of it is Webflow house style rather than WCAG's minimum. A template built by a designer who set real tags gives you a head start on every page. One built mostly from div blocks means retagging elements across every page, which is a week nobody quoted for. Open the element tree before you buy, and look at the headings first.
One honest limit
Webflow gives you enough control to build something genuinely accessible and exactly as much control to build something that passes the Audit panel and still fails a real person. Four checks is four checks. Most of WCAG is a judgment about whether the structure you chose reflects what your content actually means, and no panel in any tool can make that call for you.
Keep reading
Other platforms
Webflow
We test all 55 WCAG 2.2 A and AA rules on your Webflow site, with an expert review and a real blind screen-reader user on your key journeys. Every finding screenshotted and mapped to its fix. $499, report in 5 business days.