How to fix aria allowed attr on Wix

Steps for Wix

1. Open the Wix Editor for your site.
2. Click the element flagged in your audit. In the element's settings panel, look for an 'Accessibility' section — some Wix elements expose aria role and label fields here.
3. If the ARIA attribute was added via Wix Velo (Dev Mode), open the Velo code panel: the relevant file is usually the page's .js file or a public/private module. Locate the $w() selector for the element and remove or correct the aria-* property being set programmatically.
4. If the bad attribute comes from a Wix App Market widget, report it to the app developer via the app's support channel — you cannot edit third-party app markup directly.
5. Preview the page and re-run axe DevTools to confirm the violation is gone.

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.