The pattern
What breaks in most Webflow builds
Webflow produces clean markup, which means its failures are design decisions rather than platform limits. That is good news: nearly all of it is fixable inside Designer.
1. Headings chosen for size, not structure
Designer makes it easy to pick H2 because it looks right, then H4 because H3 is too big. The result is a heading outline that skips levels and reads as nonsense to anyone navigating by headings, which is how most screen reader users move around a page.
The fix: choose heading level by structure and set the size with a class. One H1 per page, no skipped levels.
2. Divs styled to look like buttons
A div block with a click interaction looks and behaves like a button for mouse users and is completely invisible to a keyboard. This is the single most common blocking failure I find in Webflow projects.
The fix: use a real button or link element. Where a div is unavoidable, add role, tabindex and keyboard handling, but the native element is nearly always available.
3. Interactions with no keyboard path
Webflow Interactions trigger on click, hover and scroll. Accordions, tabs, dropdowns and modals built this way frequently cannot be opened from a keyboard, never announce whether they are expanded, and do not trap focus when they should.
The fix: use the native Webflow components where they exist, add the expanded and controls attributes, and test every interaction with the mouse unplugged.
4. Link blocks wrapping whole cards
Wrapping an entire card in a link block gives the link an accessible name made of every word inside it: heading, body copy, date, tag and the word “image”. A screen reader user hears a paragraph where they expected a link name.
The fix: link the heading, and extend the clickable area with CSS rather than wrapping everything.
5. Focus states left at the default, or removed
Designer has no visible focus state by default on many elements, and some templates remove outlines for appearance. Keyboard users then have no idea where they are.
The fix: define a focus-visible style on every interactive element, with at least 3 to 1 contrast against the background.
6. CMS alt text left empty
Collection images pull alt text from a field. If the field is optional and nobody fills it, every item in the collection publishes with no alternative text at once.
The fix: make the alt field required, write a short rule for editors, and mark genuinely decorative images as decorative rather than leaving them blank by accident.
Scope
What the audit covers
Every page template
Home, service or product pages, CMS collection lists and item templates, blog, contact, search, 404 and any gated pages.
Every interaction
Navigation and dropdowns, tabs, accordions, sliders, lightboxes, modals, forms and any custom Interaction you have built.
Forms end to end
Labels, required fields, error handling, success messages and anything embedded from a third party.
Across all of it
Keyboard only, JAWS and NVDA on Windows 11, VoiceOver on macOS and iOS, TalkBack on Android, 200 and 400 percent zoom, and Windows forced colours.
Process
How a Webflow audit runs
Scope in writing
You send the published site address. I confirm the templates and interactions in scope, the cost and the timeline, in writing, within one working day.
Manual testing on the published site
Testing what visitors get, not the Designer preview, because interactions and CMS output behave differently once published.
Report split by where the fix lives
Each barrier records the WCAG 2.2 criterion, the page and element, and whether the fix is a Designer setting, a CMS field, a custom attribute or embedded code. That split is what makes the report quick for a Webflow team to work through.
Remediation and re-test
Your team applies the fixes, or I work in the project directly. Then the site is tested again and the report reissued showing before and after.
FAQ
Webflow accessibility – frequently asked questions
Is Webflow accessible by default?
Webflow gives you clean output and good control over semantics, which is more than most builders offer. But the defaults do not enforce anything: a div can be styled to look like a button, interactions can be built with no keyboard equivalent, and the component library does not guarantee correct roles. A Webflow site is as accessible as the person who built it made it.
What breaks most often in Webflow builds?
Interactions and components. Custom dropdowns, tabs, sliders and modals built from Webflow elements frequently have no keyboard support and no announced state. Beyond that, heading levels chosen for size rather than structure, and link blocks wrapping whole cards with no accessible name.
Can you fix it inside Webflow, or do we need code?
Most of it is fixable inside Designer: correct element tags, real headings, visible focus states, alt text, and using the native components properly. Some fixes need small custom attributes or a little embedded code, which Webflow supports. I state clearly which is which.
Do you work in our Webflow project directly?
I can, if you add me to the workspace, or I can deliver a report your own team applies. Many clients prefer the report because it doubles as training for the designers who will build the next page.
What about the Webflow CMS?
CMS collections are where alt text and heading structure usually drift, because content editors work in fields rather than on the page. Part of the audit is a short content rule for your editors so new items do not reintroduce the same barriers.
How long does a Webflow audit take?
One to two weeks for a typical marketing site. Fixes are often faster than on other platforms, because so much is a matter of settings and tags rather than rewriting code.
Next step
Get your Webflow site tested
Send the published address and I will reply in writing within one working day with what fails, what it covers and what it costs.