How to fix aria required children on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Identify the PHTML or Knockout JS template rendering the broken widget. Common locations: app/design/frontend/<Vendor>/<theme>/Magento_Catalog/templates/ (product options), app/design/frontend/<Vendor>/<theme>/Magento_LayeredNavigation/templates/ (filters), app/code/<Vendor>/<Module>/view/frontend/templates/.
2. Open the relevant .phtml or .html (Knockout) template file and locate the container element with the ARIA container role.
3. Add the required child roles to the child elements in the template markup (e.g. role="option" and aria-selected="false" on each filter item <li>).
4. Run bin/magento cache:clean and bin/magento setup:static-content:deploy after editing templates.
5. If the widget is generated by a third-party module, create a template override in your custom theme rather than editing the module directly.
6. Test on your staging environment with the axe browser extension and a screen reader before deploying to production.

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.