Rocket Validator looks for accesibility violations on your pages using the axe-core accessibility engine, hosted on our own servers and integrated into our web crawler. You don't need to buy an additional license, everything's already included in your Pro account at Rocket Validator.
WCAG: 4.1.2: aria-hidden elements do not contain focusable elements
This rule checks
aria-hiddenelements do not contain focusable elements.
aria-hidden="true"attribute on an element removes the element and ALL of its child nodes from the accessibility API making it completely inaccessible to screen readers and other assistive technologies. Aria-hidden may be used with extreme caution to hide visibly rendered content from assistive technologies only if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. If aria-hidden is used to hide visible content from screen readers, the identical or equivalent meaning and functionality must be exposed to assistive technologies.
aria-hidden="false"on content that is a descendent of an element that is hidden using
aria-hidden="true"will NOT expose that content to the accessibility API and it will not be accessible to screen readers or other assistive technologies.
The rule applies to any element with an
aria-hidden="true"to an element, content authors ensure that assistive technologies will ignore the element. This can be used to hide decorative parts of a web page, such as icon fonts - that are not meant to be read by assistive technologies.
A focusable element with
aria-hidden="true"is ignored as part of the reading order, but still part of the focus order, making it’s state of visible or hidden unclear.