How to fix aria required children on Wix

Steps for Wix

1. Open the Wix Editor and click on the element that contains the flagged ARIA structure (e.g. a menu, gallery, or repeater).
2. Wix generates most ARIA markup automatically; if the violation comes from a Wix-native widget (e.g. Wix Menu, Wix Pro Gallery), you cannot edit the underlying HTML directly. File a bug report via Wix Support so Wix's engineering team can fix the widget.
3. If you are using Wix Blocks or a custom widget built with Velo (Wix's JavaScript API): open the Dev Mode panel, locate the relevant component, and update the role and tabindex attributes in the component's HTML/CSS settings or in the Velo $w() event code.
4. For Velo-generated elements, use $w('#myElement').setAttribute('role', 'menuitem') and remove tabindex with .removeAttribute('tabindex') as needed.
5. Preview the site and test with axe DevTools to confirm the fix.

<!-- ❌ WRONG: img with tabindex is not a valid child of role="list" -->
<ul role="list">
  <img src="product.jpg" alt="Blue Widget" tabindex="0">
</ul>

<!-- ✅ CORRECT: wrap the image in a proper listitem -->
<ul>
  <li>
    <a href="/products/blue-widget">
      <img src="product.jpg" alt="Blue Widget">
    </a>
  </li>
</ul>

<!-- ❌ WRONG: a[tabindex] as direct child of role="menu" -->
<div role="menu">
  <a href="/sale" tabindex="0">Sale</a>
</div>

<!-- ✅ CORRECT: give the child the required menuitem role -->
<div role="menu">
  <a href="/sale" role="menuitem">Sale</a>
</div>

What is aria required children?

ARIA (Accessible Rich Internet Applications) roles tell screen readers and other assistive technologies what a piece of your page is — a list, a menu, a tab panel, etc. Each parent role has a strict set of child roles it is allowed to contain. For example, a `list` role must contain `listitem` children; a `menu` must contain `menuitem` children. When you nest elements that don't belong — such as a plain image or link with a `tabindex` attribute — directly inside a parent ARIA role, assistive technologies get confused and may skip content, announce it incorrectly, or break keyboard navigation entirely. The WCAG 1.3.1 criterion ("Info and Relationships") requires that the structure you see visually is faithfully conveyed in code so every user, regardless of ability, gets the same information.

Screen-reader users — roughly 7–8 million people in the US alone — rely on correct ARIA structure to navigate your store. A broken ARIA parent/child relationship can cause product listings, navigation menus, carousels, or tab panels to become completely invisible or unreadable to assistive technology, directly costing you sales from customers with disabilities. Beyond lost revenue, WCAG 1.3.1 failures are frequently cited in ADA Title III accessibility lawsuits against online retailers; a documented violation increases your legal exposure. Google also uses accessibility signals as a quality indicator, so persistent structural errors can subtly suppress your organic rankings over time.

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