Names, roles and values · WCAG 2.0 Level A
ARIA hidden element must not be focusable or contain focusable elements
Ensure aria-hidden elements are not focusable nor contain focusable elements.
What it means
The aria-hidden-focus rule flags elements that fail this check. It maps to WCAG success criterion 4.1.2.
Who it affects
Screen reader and voice control users, who need every control to announce a name and role.
How to fix it
Elements inside aria-hidden="true" must not be focusable. Remove aria-hidden, or remove the content from the tab order with tabindex="-1" or the inert attribute.
<div aria-hidden="true" inert>…</div>Check it on your site
Run a free scan. If this rule fails, the results list the affected elements. Deque, which maintains axe-core, also documents this rule in detail: Deque University: aria-hidden-focus.
Quick answers
What does the axe rule "aria-hidden-focus" check?
Ensure aria-hidden elements are not focusable nor contain focusable elements.
How do I fix "ARIA hidden element must not be focusable or contain focusable elements"?
Elements inside aria-hidden="true" must not be focusable. Remove aria-hidden, or remove the content from the tab order with tabindex="-1" or the inert attribute.
Who is affected by aria-hidden-focus failures?
Screen reader and voice control users, who need every control to announce a name and role.
Automated accessibility scan. Results are informational and may not identify every accessibility issue. This service is not legal advice, a compliance certification, or a substitute for comprehensive manual accessibility testing.