A Webflow Audit Is Where Interactions Meet Screen Readers

What We Keep Finding

Webflow gives designers real power, and hand-built components carry hand-built risk. A div with a click interaction is a button to the eye and plain text to a screen reader. Custom dropdowns, tabs, and sliders built from interactions rarely carry the names, roles, and keyboard handling their native cousins get free.

Here is the sentence that decides whether this audit is worth buying, and it is Webflow's own. Its Audit panel does not check for accessibility issues inside components. A professional Webflow build is components almost all the way down, and this page's entire subject is custom components, so the built-in checker is silent on precisely the thing that breaks. Two more exclusions land nearby. It does not check alt text on images bound to the CMS, and it does not check alt text inside lightbox media, which between them cover most of the images on a content-driven site.

Two of the four things the panel does check are worth understanding before you treat a clean panel as a clean site. Duplicate element IDs is a real code problem and it stopped being a WCAG failure when the parsing rule was dropped from WCAG 2.2, so clearing it is good hygiene and not a conformance win. A skipped heading level is the same shape, since heading nesting is advice in the standard rather than a requirement. Neither is wasted work. Neither is the thing a report will measure you against either.

Scroll-triggered animation adds the last layer, and the level depends on who started it. Content that arrives on scroll is motion the visitor triggered, which sits at Level AAA. A hero that animates itself on load is Level A. Both can hide content from assistive technology entirely, and content that only exists after an animation has run is content some visitors never get.