The “ARIA Required Owned Elements Check” evaluates whether elements with specific ARIA roles include the required child (or ‘owned’) elements defined by the ARIA specification.
Example outcome
I observed that all elements with an explicit semantic role own at least one of their required elements.
Impact
Visual Impairments: Broken or misrepresented widget semantics lead to missing functionality or confusing navigation. For example, a listbox must contain one or more option elements. Without them, screen readers can’t present available choices.
Motor Impairments: Missing expected children can prevent interactive elements (like tab, menuitem, etc.) from being announced correctly or receiving focus as intended, preventing keyboard users from reaching them.
Cognitive Disabilities: Incomplete components (like tabs without tabpanel) reduce clarity and increase cognitive load.
Fixes
To address missing ARIA required owned elements:
Identify the role with missing required owned elements.
Refer to the ARIA specification to find what child roles are required.
Add the missing child elements and ensure their roles are correctly applied.