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="true" must not be present on the document <body>
Document content is not accessible to assistive technology if
<body aria-hidden="true", content is not accessible to assistive technology.
aria-hidden="true"to otherwise accessible objects: A web page is designed to be fully accessible, and it would be accessible if elements do not contain the
aria-hidden="true"attribute value. Screen readers do not read content marked with the
aria-hidden="true"attribute value. Users can still tab to focusable elements in the hidden objects, but screen readers remain silent.
Any content or interface elements intentionally hidden from users — e.g., inactive dialogs, collapsed menus — must also be hidden from screen reader users. When items are available to sighted users — such as when they activate a button or expand a menu item — the same items must be available to screen reader users. The goal is to provide screen reader users an equivalent user experience to sighted users. If there is a compelling reason to hide content from sighted users, there is usually a compelling reason also to hide that content from blind users. Further, when content is made available to sighted users, it makes sense to make it available to blind users as well.