- Webflow's Audit panel runs four accessibility checks: missing alt text, non-descriptive links, skipped heading levels and duplicate IDs.
- It does not check inside components, CMS-bound images or colour contrast. Those need other tools or a manual pass.
- Use the colour picker's contrast checker, Vision preview and Text zoom preview in the Designer.
- Style the Focused (keyboard) state and use outline for focus rings. Link each form label to its field with a for attribute.
- Add a reduced motion condition to interactions. This checklist is practical guidance, not legal advice.
The short answer
To make a Webflow site accessible, check seven things, each with a matching tool in the Designer: heading order, alt text, link text, colour contrast, visible keyboard focus, labelled form fields and reduced motion. Webflow's Audit panel catches some of these automatically. The rest need the colour picker's contrast checker, Vision preview, the Focused (keyboard) state, custom attributes on form labels and a reduced motion condition on interactions. Then test with a keyboard and a screen reader.
This is practical guidance for building, not legal advice. If you need to meet a specific law or contract, check its requirements with someone qualified.
What the Audit panel checks, and what it misses
Open the Audit panel from the left toolbar of the Designer. Webflow's help page says it currently runs four accessibility checks:
- Missing alt text
- Non-descriptive link content
- Skipped heading levels
- Duplicate element IDs
It also flags some SEO issues, and marks critical items with a red square and moderate ones with a yellow triangle. Webflow lists its gaps clearly:
- It does not check inside components.
- It does not check alt text on CMS-bound images or images inside Lightbox elements.
- It does not check colour contrast.
A clean Audit panel is a start, not a pass. On a site built from components, most of the page may not be checked at all.
The checklist, with where to fix each item
| Check | Where in Webflow | How to test |
|---|---|---|
| One H1, no skipped levels | Heading tag in element settings | Audit panel, plus components by hand |
| Alt text or decorative | Assets panel, image settings, CMS image fields | Audit panel, plus CMS and Lightbox images by hand |
| Clear link and button text | Link text, or an aria-label custom attribute on icon links | Read the links out of context |
| Text contrast | Colour picker contrast checker | Check each text colour on each background |
| Visible keyboard focus | Focused (keyboard) state, outline | Tab through the page |
| Labelled form fields | Label element, field ID, for attribute | Screen reader announces each field |
| Reduced motion | Interaction conditional playback | Turn on reduce motion in your OS |
| Page language | Site settings, General, Localization | View source, check the html lang attribute |
Headings, alt text and links
Headings. One H1 per page, then H2s for sections and H3s inside them, without skipping a level. Pick the tag for meaning, then style it with a class. Our accessibility basics post explains why this matters for screen reader users.
Alt text. Set it on the asset in the Assets panel, override it per image when the context changes, and mark decorative images as decorative. Bind CMS images to an alt text field, because the Audit panel will not catch them. See our glossary entry on alt text.
Links. Webflow's help says link text should make sense on its own and say where it goes. "Read more" ten times on a page fails that. Icon-only links, such as social icons, need a name; add an aria-label as a custom attribute.
Contrast, Vision preview and text zoom
- Contrast checker. When you edit the colour of text, Webflow's colour picker shows the contrast ratio and the WCAG level it reaches, based on text colour, background, size and weight. It only appears for text colour, so check icons, borders and text on images yourself.
- Vision preview. In the canvas settings, Vision preview simulates red-green, blue-yellow and full colour blindness, and focus impairment. Use it to spot meaning carried by colour alone, such as an error shown only in red.
- Text zoom preview. Also in canvas settings. It shows how the page looks when a visitor has set larger text in their browser. Webflow notes it won't work if custom code sets a font size on the HTML tag.
For the levels themselves, see our glossary entries on WCAG and colour contrast.
Keyboard focus
Press Tab from the top of the page. You should always see where you are, and the order should follow the page.
- Webflow has a Focused (keyboard) state, which maps to
:focus-visible. Styles on it show for keyboard users and not on mouse clicks. - Use the outline property for the focus ring. Webflow added it so the ring does not change the element's size or shift the layout, which a border would.
- Webflow's help says Tabs, Dropdown, Slider and Navbar elements need a focus style on the focused state to be fully keyboard accessible.
- Style the ring once on your shared button and link classes, so every page gets it.
- Check that menus and modals can be opened, used and closed by keyboard, and that hidden items cannot be reached while hidden.
Form labels
Every field needs a visible label, not just placeholder text that disappears when people type. Webflow's help page on form labels says fully accessible forms currently need a small custom step:
- Select the field and give it a unique ID in the Settings panel.
- Select its Label element and add a custom attribute named
for, with the same value as the field's ID. - Group each label and field in a box so you can reuse the pair.
Also write error messages that say what to fix, and keep help text visible.
Motion
Some people get dizzy or sick from movement on screen, and set their device to reduce motion. Webflow lets you respect that:
- In an interaction's settings, add a conditional playback condition for reduced motion, then choose No animation or Skip to end. Webflow University shows this step by step.
- Webflow's smooth scroll for anchor links already turns off when a visitor has reduced motion set.
- Custom code animations, such as GSAP, need their own check for
prefers-reduced-motion.
Keep content readable when motion is off: nothing should stay hidden at its starting state. Our post on fast Webflow interactions has more on motion.
Test with real tools
- Fix everything the Audit panel flags.
- Open each component on its own and check headings, alt text and links inside it.
- Tab through every page template.
- Turn on reduce motion and reload.
- Use a screen reader on the home page, a CMS template and a form: VoiceOver on Mac and iPhone, or NVDA on Windows.
- Zoom the browser to 200% and check nothing is cut off.
Webflow also publishes an accessibility checklist with more items, such as a skip to main link, the site language code and touch target sizes. Use it alongside this one.
What to do next
Start with your templates, not single pages: fix a component once and every page that uses it improves. Then check the CMS fields editors fill in, so new content stays accessible. If you want us to run this checklist on your site, see Webflow development or our care plan, or send us your site. We can tell you what to fix first; we do not give legal advice on accessibility law.



