Webflow has an Audit panel. Why use another checker?

Use both. The Audit panel runs in the Designer and, by Webflow's own documentation, doesn't check color contrast or alt text on CMS-bound and Lightbox images. Perceivly checks the published page and can re-check the whole site on a schedule.

How do I make Webflow form labels accessible?

Give each input a unique ID and add a custom attribute 'for' with that ID to its label. Keep the label visible rather than relying on placeholder text.

Do I need to add code to my Webflow site?

No. Perceivly checks your published pages from the outside, like a visitor. Nothing is added to your project.

Can the checker find every issue on my Webflow site?

No. Automated tests find only part of WCAG issues. Keyboard use, meaningful alt text and screen reader behavior still need a person to review.

All platforms

Webflow accessibility checker

Check any page of your published Webflow site against WCAG 2.2 level AA in about 10 seconds. Free, no sign-up.

The Webflow Audit panel, and what it leaves out

The Webflow Designer has an Audit panel that flags accessibility issues before you publish, such as missing alt text, link text that doesn’t describe the link, skipped heading levels and duplicate element IDs. Use it while you build.

Webflow’s documentation lists its limits: it doesn’t check color contrast, and it doesn’t check alt text on CMS-bound images or images in Lightbox elements. Those are exactly the places where content changes after launch. Perceivly tests the published page in a real browser, with your CMS content and interactions in place.

Typical Webflow issues

Custom components. Webflow gives you full control of the markup. Divs styled as buttons, custom dropdowns and tabs built from scratch need names, roles and keyboard support that a native element would bring on its own. Webflow notes that some of its built-in elements need focus styles added.
Removed focus outlines. Setting an outline to none or to zero width removes the browser’s focus indicator. Keyboard users then can’t see where they are.
Form labels. Webflow says fully accessible forms currently need a custom solution: a label tied to its input with a for attribute. Placeholders are not a replacement for labels.
CMS content. Images and rich text from Collections are filled in by editors after the design is done, and the Audit panel doesn’t check CMS-bound images.

Where to fix common issues in Webflow

Image alt text

Set alt text once per image in the Assets panel, in the image’s settings, as a description or marked as decorative. To change it for one use of the image, select it on the canvas and set Alt text in its element settings; this overrides the asset’s alt text there only.

Color contrast

In the Style panel, the color picker for typography shows a WCAG contrast rating for the text against its background. It can’t judge text on top of images, so check those by eye or with our contrast checker.

Form labels

Give each input a unique ID, then add a custom attribute for with that ID to its Label element. Keep the label visible.

Focus styles

Don’t set outlines to none. Style the Focused (keyboard) state of links and buttons with an outline of at least 2px.

Page language

Webflow sets the page’s lang code from your primary locale in the localization settings. Check it is the language your content is written in.

What Perceivly adds

The Audit panel checks while you design. Perceivly checks the live site on a schedule, with CMS content, embeds and third-party scripts loaded, tracks each issue until it is fixed, and gives agencies white-label reports for their clients. See Perceivly for agencies.

What the scan checks

Automated rules from WCAG 2.0, 2.1 and 2.2, levels A and AA, using the open-source axe-core engine. Among them:

Text and background color contrast
Text alternatives for images
Labels on form fields
Names on buttons and links
Page language and title
Valid ARIA roles and attributes
Keyboard access to scrollable areas
Touch target size (WCAG 2.2)

What needs a person

Automated tests find only part of accessibility issues; published estimates range from about 30% to 57%. These need a person:

Whether alt text actually describes the image
Whether everything works with a keyboard alone, in a sensible order
Captions and audio descriptions that match the media
Clear headings, labels and error messages
How the page behaves with screen readers and zoom

Questions

Webflow has an Audit panel. Why use another checker?: Use both. The Audit panel runs in the Designer and, by Webflow's own documentation, doesn't check color contrast or alt text on CMS-bound and Lightbox images. Perceivly checks the published page and can re-check the whole site on a schedule.
How do I make Webflow form labels accessible?: Give each input a unique ID and add a custom attribute 'for' with that ID to its label. Keep the label visible rather than relying on placeholder text.
Do I need to add code to my Webflow site?: No. Perceivly checks your published pages from the outside, like a visitor. Nothing is added to your project.
Can the checker find every issue on my Webflow site?: No. Automated tests find only part of WCAG issues. Keyboard use, meaningful alt text and screen reader behavior still need a person to review.

Sources

Checked November 4, 2026. Products and prices change; check each source for the current details. Editor menus change between Webflow versions; the help pages above have the current steps.

Other platforms

Perceivly is not affiliated with Webflow. Names are trademarks of their owners. Checked November 4, 2026.