How to fix aria allowed attr on Webflow

Steps for Webflow

1. Open your project in the Webflow Designer.
2. Select the flagged element on the canvas. Open the Element Settings panel (gear icon, ⚙) and scroll to the 'Custom Attributes' section.
3. Find the mismatched aria-* attribute listed there. Either delete it, change the attribute name to one that is valid for the element's role, or change the element's role attribute to one that supports the aria-* attribute.
4. If the attribute is being set by custom JavaScript in the project's Custom Code section (Project Settings → Custom Code or page-level Embed), find and correct it there.
5. Publish the site and verify with the axe DevTools browser extension.

What is aria allowed attr?

ARIA (Accessible Rich Internet Applications) is a set of special HTML attributes — like `aria-checked`, `aria-expanded`, `aria-required` — that tell screen readers and other assistive technologies what a page element is and how it behaves. Each HTML element has a "role" (either its native role, such as `button` or `checkbox`, or one you assign with `role="…"`), and only certain ARIA attributes are valid for each role. The `aria-allowed-attr` rule flags situations where an ARIA attribute is applied to an element whose role does not support it — for example, putting `aria-checked` on a plain `<div>` with no appropriate role, or adding `aria-expanded` to an element whose role never has an expandable state. These mismatches are recognised by automated accessibility scanners and flagged against WCAG 4.1.2 (Name, Role, Value).

Screen readers like JAWS, NVDA, and VoiceOver rely on ARIA attributes to announce the correct state and purpose of interactive controls to blind and low-vision shoppers. When an ARIA attribute is mismatched to its element's role, the screen reader either ignores it silently or announces confusing, incorrect information — causing those customers to misunderstand your navigation, forms, filters, and checkout controls. This directly reduces conversions among users with disabilities and exposes your store to legal risk under accessibility laws (ADA Title III in the US, EN 301 549 in the EU, and equivalent legislation elsewhere) that increasingly require WCAG 2.1 AA compliance. Search engines also use ARIA signals to better understand page structure, so clean, valid markup supports long-term SEO health as well.

See the complete Aria allowed attr guide for every platform and the full background.