No-code

WCAG accessibility audit for Webflow sites

Why Webflow causes accessibility issues

Webflow is the reference no-code platform for web designers, but its visual approach to page building creates structural accessibility problems. Webflow generates HTML based on nested divs — a 'div soup' where every visual element is a div with custom CSS classes. Semantic tags (nav, main, article, aside, section) are rarely used because the designer thinks in terms of visual layout rather than document structure. Webflow interactions (scroll animations, hover effects, modals, sliders) are built with the proprietary interaction system that does not generate necessary ARIA attributes. Webflow forms have basic accessibility support (labels present) but error handling is limited. CMS components (dynamic collections) generate repetitive HTML without ARIA landmarks. Focus management is absent: modals open without receiving focus, hamburger menus do not trap focus, tabs do not support arrow navigation.

Common issues on Webflow

'Div soup' HTML structure without semantics

WCAG 1.3.1

Webflow generates its HTML from the designer's visual structure. Every element is a div with CSS classes. Semantic tags (header, nav, main, section, article, aside, footer) are not used by default. Screen readers cannot identify page regions (navigation, main content, footer). Landmark navigation is impossible, forcing the user to traverse every element linearly.

Interactions and animations without ARIA

WCAG 4.1.2

Webflow's interaction system allows creating complex animations (modals, accordions, menus, tabs) visually. But these interactions do not generate required ARIA attributes: tabs do not have role=tablist/tab/tabpanel, accordions do not have aria-expanded, modals do not have role=dialog. The visual result is convincing, but components are unusable for assistive technologies.

Focus not managed on interactive components

WCAG 2.1.1

Webflow interactive components (modals, hamburger menus, lightboxes, sliders) do not manage keyboard focus. Modals open without receiving focus, allowing tabbing behind the panel. Hamburger menus do not trap focus within the open menu. On closing, focus is not restored to the trigger element. Sliders are not keyboard navigable (arrows, Tab).

Dynamic CMS content without accessible structure

WCAG 1.3.1

Webflow CMS collections (blog, portfolio, products) generate dynamic content lists. Each collection item is a div containing divs. Lists are not ul/ol tags. Article titles are not h2/h3. Links surround entire blocks without clear descriptive text. The whole thing is a series of clickable divs without semantic structure.

Test your Webflow site

Discover the WCAG non-conformities of your Webflow site in 5 minutes. Free, no commitment.

Run the free audit

What Scrutia detects on Webflow

Scrutia analyzes the HTML generated by Webflow in a real browser. Our engine detects div soup structures without semantic tags, interactions without ARIA attributes, components without focus management, and CMS collections without accessible structure. We test each interactive component with keyboard (modals, accordions, tabs, sliders) and verify that ARIA landmarks are present. Corrections are provided in HTML/CSS/JS with instructions for applying them in the Webflow editor or via custom code embed.

Frequently Asked Questions — Webflow

Can accessibility problems be fixed directly in Webflow?

Partially. Webflow allows adding custom attributes (role, aria-label, aria-expanded) via the interface. Semantic tags (nav, main, section) can be assigned in each element's settings. For more complex corrections (focus trap, aria-live, keyboard navigation), you need to use Webflow's Custom Code feature to add JavaScript.

Does the free Webflow plan allow applying corrections?

The free Webflow plan does not allow adding custom code (JavaScript). You can fix ARIA attributes and semantic tags in the interface, but corrections requiring JavaScript (focus management, aria-live) require a paid plan with Custom Code or site export.

Webflow says its sites are accessible, is that true?

Webflow has made progress (custom attribute support, assignable semantic roles), but a Webflow site's accessibility depends entirely on how the designer builds it. The tool does not enforce best practices: it is possible to create an accessible Webflow site, but it requires specific expertise that most designers do not have.

Audit your Webflow site now

106 RGAA criteria tested in 5 minutes. Free score, full report with code fixes for €49.

Test my Webflow site