aria-required-parent
Web validation
Some ARIA “child” roles such as listitem, menuitem, or option only make sense when they sit inside their required parent roles (list, menu, or listbox, respectively). If the required relationship is missing, assistive technology users lose crucial structural context, which can cause confusion and navigation failures.
Pass Patterns
listitem elements sit inside an ARIA list
Each listitem is a direct child of the list.
<div role="list">
<div role="listitem">First item</div>
<div role="listitem">Second item</div>
</div>menuitem elements sit inside an ARIA menu
Each menuitem is a direct child of the menu.
<div role="menu">
<button role="menuitem">A</button>
<button role="menuitem">B</button>
<button role="menuitem">C</button>
</div>A listitem linked to its list with aria-owns
When the DOM structure can't be changed, aria-owns on the parent tells assistive technologies which elements belong to it.
<div role="list" aria-owns="item-1 item-2"></div>
<!-- Elsewhere in the page -->
<div role="listitem" id="item-1">First item</div>
<div role="listitem" id="item-2">Second item</div>Note: aria-owns is not widely supported across browsers and screen readers. Prefer placing child elements inside their required parent in the DOM, and use aria-owns only when that is not possible.
Fail Patterns
A listitem element sits outside a list parent
The listitem elements have no list parent.
<div role="listitem">Alpha</div>
<div role="listitem">Beta</div>A menuitem element sits outside a menu element
The menuitem element has no menu parent.
<div role="menuitem">Settings</div>Try It Yourself
Using a screen reader
New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers
- Load the page and open a screen reader.
- Move the screen reader focus to the element using screen reader navigation keys.
- Listen for how the screen reader describes the element and its context.
Expected results: The screen reader announces something like “List, two items… list item 1 of 2.”
Actual results: The screen reader announces “List item” with no list context or ignores the list item completely.
FAQ
How does this issue relate to 1.3.1 Info and Relationships?
SC 1.3.1 requires that relationships conveyed visually are also programmatically determinable. Placing ARIA child roles inside their required parents ensures that assistive technologies can expose those relationships.
Why is this issue marked as Critical?
When the required parent relationship is missing, assistive technology users may receive incomplete or misleading information, making interactive controls unusable and blocking core tasks. Because the defect directly prevents successful operation, it carries critical severity.
Where can I find the required parent for a role?
To find the required parent element, go to the ARIA specification at https://www.w3.org/TR/wai-aria-1.3/#[role-name] (replace the square brackets and their content with the element’s role).
In the role ’s details table, find the role’s “Required Accessibility Parent Roles”.
Standards and Regulations
| Standard | Success Criterion | Reference |
|---|---|---|
| WCAG 2.2 | 1.3.1 Info and Relationships (A) | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. |
| EN 301 549 | 9.1.3.1 Info and Relationships | Same as the WCAG text. |