How to fix aria required children on Wix Studio

Add the required child ARIA roles (e.g. `role="option"` inside `role="listbox"`, or `role="group"`/`role="option"` inside `role="combobox"`) so every composite ARIA widget contains the child roles the ARIA specification demands.

Steps for Wix Studio

  1. In Wix Studio, open the page containing the broken widget in the editor.
  2. If the widget is a custom component, open the Components panel, select the component, and use the Dev Mode panel to add or correct ARIA attributes via JavaScript (same Velo API as standard Wix).
  3. For Studio-native 'blocks' that output incorrect ARIA, use the Settings → Accessibility panel (where available) or file a bug with Wix Studio support.
  4. For full control, insert a Custom Embed block containing hand-authored HTML with the correct role hierarchy.
  5. Verify with axe DevTools after publishing.
Official Wix Studio documentation ↗

What is aria required children?

ARIA (Accessible Rich Internet Applications) is a set of attributes that tells screen readers and other assistive technologies what a piece of your page does. Some ARIA roles are "composite widgets" — they are containers that only make sense when they hold specific child roles inside them. For example, a `role="listbox"` must contain items marked with `role="option"`, and a `role="combobox"` must own a `role="listbox"` (or similar) that in turn contains `role="option"` children. When those required children are missing, the widget is structurally broken from an accessibility standpoint. The scanner flagged WCAG Success Criterion 1.3.1 ("Info and Relationships"), which requires that the structure you communicate visually is also communicated to assistive technology — and a role hierarchy missing its required children fails that test.

Screen readers used by blind or low-vision shoppers rely entirely on correct ARIA role relationships to announce and navigate interactive controls like drop-down lists, autocomplete fields, product filters, and size/colour selectors. When required child roles are absent, the screen reader either announces the container as empty, skips it entirely, or narrates meaningless raw text — making the control unusable. This directly blocks those customers from completing purchases, which is both a lost conversion and a legal accessibility risk: WCAG 2.1 Level AA is the benchmark cited in ADA, EAA (Europe), and similar legislation, and regulators and plaintiffs increasingly target ecommerce stores. Fixing this also signals to Google that your pages are well-structured, which can contribute to crawl quality and Core Web Vitals signals over time.

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

Not sure if your Wix Studio store has this?

Run a free SEOLZ scan — we’ll find aria required children and every other issue across your whole site.

Scan my site free

Fix aria required children on another platform