Webflow accessibility: the Audit panel and its limits

The Audit panel is the quickest way to catch obvious problems while you build in Webflow, and it is worth keeping clear. It also has documented blind spots, and a clear panel is easy to mistake for a finished job. This page lists what the panel checks, what it does not, how to set alt text and ARIA attributes in the Designer, and what to test on the live site afterward.

Every Webflow product statement here comes from Webflow's own documentation, read on October 11, 2026: the Help Center article Intro to the Audit panel (updated March 26, 2026), the article Include alt text on images (updated January 30, 2026), Webflow's accessibility checklist, and Webflow's accessibility page. Help Center pages are revised over time, so check the current article if a label differs.

What the Audit panel checks

Open it with the Audit panel icon in the left toolbar of the Designer. Webflow's article says it currently includes four high-impact accessibility checks:

• Missing alt text. Images with no descriptive alt text that are not marked decorative.
• Non-descriptive link content. Webflow defines the problem as empty links: links with no meaningful text or image alt text.
• Skipped heading level. For example an H2 section whose subheadings are H4, with no H3 between.
• Duplicate element IDs. The same ID on more than one element on a page.

Critical errors carry a red square and moderate ones a yellow triangle. Pressing Alt or Option plus U expands or collapses every item. The panel groups images with missing alt text into two kinds, Asset (the canvas image references an asset that has no alt text) and Rich text (an image inside a rich text element), and a Find it for me button in the Missing alt text modal jumps to the right setting. For duplicate IDs, the panel lists all elements and component instances that share the ID. That sits oddly beside the component limit below, which Webflow words as covering accessibility and SEO issues within components; treat the ID list as a convenience, not as proof that components were checked. The panel also runs SEO checks for missing image alt text, meta titles, meta descriptions and schema markup.

Two details are easy to miss. First, Webflow's article defines the flagged problem as empty links, links with no meaningful text or image alt text, and says the panel does not provide guidance on generic terms such as "read more" or "click here". Do not expect it to flag weak wording; check by reading the links. Our link text checker flags those phrases. Second, Webflow's marketing page for accessibility, read on October 11, 2026, describes the panel as checking "some common issues like missing alt text, empty links, and out-of-sequence heading elements", which names three. We use the Help Center article and its count of four, because it is the more recent and specific source.

What the Audit panel does not check

One more limit follows from how the check is described. Webflow defines missing alt text as images included without descriptive alt text and not marked decorative. Nothing in the article says the panel compares the text with the picture, so a description that is present but wrong should not be expected to trigger it. Hovering over an issue and pressing the silenced bell icon ignores it. Ignored items are moved out of the active list, and Webflow's article says you can bring one back with the disclosure arrow beside it, so review them before you call the panel clear.

Webflow lists these exceptions in the same article. "No issues in the Audit panel" and "no accessibility issues" are different statements.

Set alt text in the Designer

Webflow gives you four places to set alt text, and they interact. The steps below follow the Include alt text on images article.

On the image asset, so every use inherits it

1. Open the Assets panel (press J).
2. Hover over the image and click the settings cog.
3. Write a description in the Descriptive field, or click Decorative if the image adds nothing.

Whenever the image is used on the site, it inherits this text. That is convenient and also the risk: one sentence now appears wherever the asset appears, whether or not it fits that page. If a new copy of the same image is dragged into a design, it defaults to the Assets panel text again.

On one image, overriding the asset

1. Select the image element on the canvas and click the settings cog.
2. Open the Alt text dropdown and choose Custom description, or choose Decorative.

On images inside a rich text element

1. Select the image inside the rich text element and click the wrench icon.
2. Open the Alt text dropdown and choose Custom description or Decorative.

If the rich text element pulls its text and images from a rich text field, update the alt text in that field on the Collection item instead.

On CMS-bound images, where the Audit panel is blind

1. Open the CMS panel, open the Collection's settings, click Add new field and choose Plain text. Label it, for example, "Alt text for blog image", and save.
2. Open each Collection item and write a description in the new field. Save.
3. Back on the canvas, select an image bound to the Collection, open the Element settings panel and click the purple dot in the Alt text dropdown.
4. Choose the text field you created.

Each item now carries its own text. Because the Audit panel does not check these images, a blank field on item 40 will not be flagged in the Designer.

In bulk with Webflow AI

In the Audit panel, choose Sitewide from the dropdown, click Add alt text, then Generate alt text. Review and edit each result and accept it with the checkmark, or click Accept to save them all. Webflow says generation works for JPG, PNG, GIF, WEBP and AVIF, and not SVG. Read every suggestion against the picture before accepting; AI alt text accuracy explains why a fluent sentence can still be wrong.

Set ARIA attributes, landmarks and language in the Designer

Webflow's checklist gives specific places for the code-level tasks.

• ARIA attributes. Select the element on the canvas and open Custom Attributes in the Element Settings panel. To hide a decorative element that is not an image from assistive technology while keeping it visible, add the name aria-hidden with the value true. (Webflow checklist task, read October 11, 2026.)
• Landmarks. In the Element Settings panel, use nav for the navigation, main for the primary content (with the ID main if you add a skip link), section for page divisions, aside for sidebars and footer for the footer. (Webflow checklist task.)
• Language. Go to Site settings, General, Localization, enter the two-letter language code, save and publish. (Webflow checklist task.)
• Page titles. Use Pages panel, Page Settings, SEO Settings, and use dynamic fields for CMS pages. (Webflow checklist task.)

The published element then carries aria-hidden="true". That is our rule, not Webflow's: GotAlt flags aria-hidden on a focusable element as a serious issue under WCAG 4.1.2 (see the methodology), so keep the attribute off anything a keyboard user can reach.

Webflow's own accessibility checklist

Webflow publishes a living checklist maintained by its brand studio web team (Webflow checklist, read October 11, 2026). We counted it on October 11, 2026: 48 tasks in 14 categories (Animation, Appearance, Code, Color, Content, Controls, Forms, Headings, Images, Interactions, Keyboard, Lists, Media and Tables). Webflow says some tasks are inspired by WCAG 2.1 AA and others are best practices its team follows, and that addressing them will make a site more accessible but does not guarantee it is fully accessible. For the standard behind the list, see our WCAG 2.2 checklist and which WCAG version applies.

The "Where" label on each task shows how little of it the Audit panel touches:

Only two tasks, finding empty links and keeping a logical heading order, list the Audit panel as where they are done. The other 46 are done elsewhere in the Designer, and the panel covers at most a few of them in part, alt text being one. Webflow also labels each task Design, Development or Review (16, 24 and 8 tasks respectively), which is a handy way to split the work between a designer and a developer.

What GotAlt checks on the published Webflow site

The Audit panel works inside the Designer on the page you are building. GotAlt works on the live URL, the page as an ordinary visitor's browser receives it, with no Webflow login and nothing installed. The two overlap on a few items and differ on the rest.

Three differences matter most for a Webflow build. GotAlt reads the published HTML regardless of how it was produced, so a component instance or a CMS-rendered image is read like any other markup. It can catch a wrong sentence inherited from the Assets panel, because the deep audit compares the text with the file (up to six images per page). And it confirms that what you set in the Designer is what the page now says.

What it cannot see matches the methodology page: anything a script adds after load, pages a visitor cannot open (an unpublished or password-protected page), computed contrast, keyboard traps and screen reader announcements. If an image appears only when a script runs, check it manually. The guide to testing website accessibility covers those manual checks.

A review loop for a Webflow build

1. Clear the Audit panel

   Fix each flagged item, and review any you have ignored, before publishing.

2. Do the manual items

   Work through the checklist tasks the panel cannot see, and the components and Lightbox images it skips.

3. Publish and scan the live URL

   Run the free scan and the alt text checker on the pages that matter most.

4. Test with a keyboard

   Tab through the page, check the focus outline, and zoom to 200 percent.

5. Repeat after CMS changes

   New Collection items and swapped assets are where blank or inherited descriptions come back.

No tool, GotAlt or Webflow's included, can make a site conform to WCAG on its own. If you serve US or EU customers, our ADA website guide and EAA guide explain which rules may apply; they are general information, not legal advice. Our guides for Shopify, WordPress, Wix and Squarespace cover the same ground for other builders.