ARIA & keyboard
ARIA role is outside its required parent
WCAG 2.2 success criterion 1.3.1 Info and Relationships (Level A)
- WCAG 2.2
- 1.3.1 Info and Relationships
- Level
- A
- Default severity
- Needs review
- Available in
- Free
Updated for Lumtera 1.3.0 and Lumtera Pro 1.2.0.
Why does it matter?
WCAG 1.3.1 asks that structure reaches assistive technology; WAI-ARIA says this role must sit inside a particular parent role, as a tab sits in a tab list, and without it screen readers cannot say how many items there are or which one this is.
Who it affects: Screen reader and keyboard users, who depend on ARIA and focus order being correct to understand and operate the page.
What does Lumtera flag?
A role outside the parent role it needs, such as a tab with no tab list around it. For review; aria-owns is taken into account.
Check ID aria-required-context — use it to filter the content report or with wp lumtera issues --rule.
How do I fix it in WordPress?
Wrap the element in the parent role the message names, or use native HTML: list items in <ul>, table cells in <table>. If the parent is elsewhere on the page, point to this element from it with aria-owns.
Example
<div role="tab">Details</div>
<div role="tablist"><button role="tab">Details</button></div>
How do I check the fix?
- Update the post. The issue disappears from the Lumtera Accessibility sidebar on the next check, and from the site report on the next scan.
- Press Tab from the top of the page. Focus should move in reading order and never land on something invisible or silent.
Find this issue across your whole site
Lumtera runs this check in the block editor sidebar as you write, in the Elementor panel, in Review mode on the live page, and across the whole site in the content report and with wp lumtera scan. You can change its severity or turn it off in Lumtera → Settings.
Related checks
-
WCAG 1.3.1 · AError
Heading is empty
-
WCAG 1.3.1 · ANeeds review
Heading level is skipped
-
WCAG 1.3.1 · ATip
Content uses an H1 heading
-
WCAG 1.3.1 · ATip
Bold text may be a heading
-
WCAG 1.3.1 · ATip
Heading is very long
-
WCAG 4.1.2 · AError
Form field has no label
Start with the free plugin today
All 88 content checks and 38 whole-page checks, fixes you approve with undo, and the site report — free, with no account and no page limits.