How to fix aria required parent on Wix

Steps for Wix

1. In the Wix Editor, select the menu or component that contains the flagged element.
2. Open Wix's Accessibility Settings panel (if available for that widget) and check for ARIA role options.
3. For components that don't expose ARIA controls, use Wix's 'Custom Code' feature (Settings → Custom Code → Add Code → Head or Body) to inject a small JavaScript snippet that wraps the elements in the correct parent role after the DOM is ready.
4. Alternatively, switch to Wix Studio (which offers more control over HTML/ARIA attributes) and use a Custom Element or HTML Component to rebuild the affected widget with correct ARIA structure.
5. Test with the axe DevTools browser extension after publishing.

<ul role="menubar">
  <li role="none"><a href="/shop" role="menuitem">Shop</a></li>
  <li role="none"><a href="/about" role="menuitem">About</a></li>
</ul>

What is aria required parent?

ARIA (Accessible Rich Internet Applications) roles come in pairs: a "child" role must always live inside a specific "parent" role for screen readers to make sense of the relationship. For example, a `menuitem` must be inside a `menu` or `menubar`, an `option` must be inside a `listbox`, and a `row` must be inside a `grid` or `rowgroup`. When the required parent wrapper is missing, screen readers either skip the element entirely or announce it with confusing, broken context. The `aria-required-parent` rule flags every place where a child ARIA role exists without its mandatory parent container role.

Screen reader users — including many people with visual impairments or motor disabilities — rely on these structural relationships to understand and navigate menus, dropdowns, product option lists, and navigation bars. A broken parent-child ARIA structure means those users cannot operate your navigation or select product options, which directly reduces conversions and creates a real legal accessibility risk under laws such as the ADA (US), EAA (EU), and the Equality Act (UK). Failing WCAG 2.1 Success Criterion 1.3.1 (Info and Relationships) can expose your store to accessibility lawsuits, which have surged in recent years against ecommerce sites. Fixing this also signals structural HTML quality to search engines, supporting your overall SEO health.

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