How to fix aria valid attr on Wix

Steps for Wix

1. Open your site in the Wix Editor. ARIA attributes set by Wix's built-in components are managed through each element's Settings or Accessibility panel — click the element, then click Settings (gear icon) → Accessibility.
2. For custom HTML or embed widgets (Insert → Embed → Custom Code or HTML iframe), click the element → Settings → open the HTML code panel and search for the misspelled ARIA attribute, then correct it.
3. If the misspelling is in a Wix App (e.g. Wix Forms, Wix Stores product widgets), it is controlled by Wix's platform code; submit feedback via Wix Support because you cannot directly edit app-generated markup.
4. For Velo (Wix's coding environment), open the relevant page code or public/backend file in the Velo editor and search for the misspelled attribute.
5. Publish your changes and verify with axe DevTools.

<!-- ❌ WRONG — misspelled attribute; screen readers ignore it entirely -->
<input type="text" id="email" aria-labeledby="email-label">

<!-- ✅ CORRECT — double 'l' in labelledby -->
<input type="text" id="email" aria-labelledby="email-label">

<!-- Other common misspellings to watch for: -->
<!-- aria-descrribedby  →  aria-describedby  -->
<!-- aria-reqired       →  aria-required      -->
<!-- aria-expaned       →  aria-expanded      -->
<!-- aria-valuenow      →  aria-valuenow  (this one IS correct) -->

What is aria valid attr?

ARIA (Accessible Rich Internet Applications) attributes are special HTML attributes like `aria-label`, `aria-labelledby`, and `aria-describedby` that tell screen readers and other assistive technologies what your page elements are and how they work. Every valid ARIA attribute has a precisely defined name — even a single missing or transposed letter (such as writing `aria-labeledby` instead of `aria-labelledby`) makes the attribute completely meaningless to assistive technology. Browsers silently ignore unrecognised ARIA attributes, so the intended accessibility information is simply never conveyed. This rule (WCAG 4.1.2, "Name, Role, Value") requires that all interface components have properly programmatically determinable names and roles.

Screen-reader users — people who are blind, have low vision, or have motor disabilities — rely on ARIA attributes to understand and interact with buttons, forms, dialogs, and navigation. When an ARIA attribute name is misspelled, the assistive technology receives no information at all, as if the attribute were never there. This can make critical controls completely unusable for those users, creating a real accessibility barrier and potential legal liability under laws such as the ADA (US), the European Accessibility Act, and the UK Equality Act. Beyond legal risk, accessible sites consistently earn higher user trust, lower bounce rates, and broader audience reach — all of which support organic rankings and conversions.

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