How to fix aria valid attr on Webflow

Steps for Webflow

1. Open your project in the Webflow Designer.
2. Select the element that has the invalid ARIA attribute (use the Navigator panel to locate it).
3. In the right-hand Settings panel (gear icon), scroll down to 'Custom Attributes'. Find the misspelled attribute entry (e.g. `aria-labeledby`) and correct the Name field to the proper spelling (e.g. `aria-labelledby`). Do not change the Value.
4. If the attribute appears in a Symbol or Component, open the Symbol/Component in edit mode and apply the same correction there so all instances are updated.
5. For custom code embeds (HTML Embed elements), click the element → Settings → open the embed code editor and correct the attribute name in the raw HTML.
6. Publish the site and verify using axe DevTools in the browser.

What is aria valid attr?

ARIA (Accessible Rich Internet Applications) attributes are special HTML attributes — like `aria-label`, `aria-labelledby`, or `aria-hidden` — that tell screen readers and other assistive technologies what an element is and how it behaves. Every valid ARIA attribute has an exact, officially defined name. An "invalid ARIA attribute name" means your HTML contains an ARIA attribute that doesn't exist in the official specification — most commonly a typo like `aria-labeledby` (one 'l' instead of two) instead of `aria-labelledby`. Because the attribute name is wrong, the browser and assistive technology silently ignore it entirely, as if it were never there.

When an ARIA attribute name is misspelled, screen readers receive no accessibility information from it — the element appears unlabelled or unidentifiable to blind and low-vision shoppers. This directly harms the shopping experience for millions of people with disabilities and puts your store at legal risk under laws like the ADA (US), AODA (Canada), EAA (EU), and Equality Act (UK), all of which reference WCAG 2.x conformance. Accessibility lawsuits targeting online stores have increased sharply year over year, and a simple typo is exactly the kind of findable, actionable violation that appears in demand letters. Fixing it is quick and meaningfully improves usability for customers using assistive technology, which can also improve conversion rates in that segment.

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