How to fix aria required attr on Wix

Steps for Wix

1. Open the Wix Editor for your site. Click the element flagged (e.g., a text box or custom widget) to select it.
2. Open Wix's Accessibility Settings panel: click the element → Settings (gear icon) → Accessibility.
3. For custom-coded sections (Wix Velo / Corvid), open the Developer Tools panel, navigate to the relevant page code or public file, and locate the HTML/JSX where the ARIA role is set — add the missing attribute there.
4. If the element is a native Wix component (e.g., a text element used as a heading), use the Design/Text panel to set it as a proper heading tag (H1–H6) instead of relying on a custom `role="heading"` — this removes the need for `aria-level` entirely.
5. Publish the site and re-test with the axe browser extension.

<div role="heading" aria-level="2">Featured Products</div>

<!-- Better: use native HTML which never needs aria-level -->
<h2>Featured Products</h2>

<!-- Slider example: all three value attributes required -->
<div role="slider"
     aria-valuenow="50"
     aria-valuemin="0"
     aria-valuemax="100"
     aria-label="Price range">
</div>

What is aria required attr?

ARIA (Accessible Rich Internet Applications) roles tell screen readers and assistive technologies what a piece of content is — for example, a heading, a slider, or a tree item. Many ARIA roles come with required attributes that must be present for the role to make sense. For instance, any element with `role="heading"` must also have `aria-level` (a number from 1–6) so assistive technology knows whether it's a top-level heading or a sub-heading. When a required attribute is missing, the ARIA role is effectively broken — like labelling a shelf "Aisle 3" but leaving out the aisle number.

Screen reader users — who are often unable to use a mouse and rely entirely on assistive technology — receive garbled or meaningless announcements when required ARIA attributes are absent. This directly blocks those users from understanding your page structure, navigating your store, or completing a purchase. Under WCAG 2.1 Success Criterion 4.1.2 (Name, Role, Value), all user interface components must expose correct role information to assistive technology; failing this criterion creates legal accessibility risk in the US (ADA), UK (Equality Act), EU (EAA), and beyond. Search engines also parse page structure using semantic signals — broken heading hierarchies and malformed ARIA can weaken how Googlebot understands and ranks your content.

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