Check whether aria-hidden on the document body hides an entire page from screen readers, tools that read content aloud. Identify problematic states and suggest limiting hiding to specific background containers.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Do not use aria-hidden on the document body. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Run score Not tested
See how to installChecks settings on <body> that can hide an entire page from screen readers. The attribute aria-hidden="true" tells assistive technologies to ignore an element. When it is applied to <body>, it affects the whole page. The skill checks for this setting both when the page first appears and during state changes triggered by user actions.
Use it to investigate a modal that stops screen reader output when opened, or content that remains visible on screen but is not recognized by a screen reader. It also helps when reviewing interface components or design systems and checking how background content is hidden and how focus moves.
aria-hidden="true" to <body>.”Applying this setting to <body> hides the whole page from assistive technologies, so temporary states during use are also part of the review. The stated approach is to verify fixes with browser accessibility tools or assistive technologies.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Setting aria-hidden="true" on the body effectively silences the entire application for screen reader users, rendering the site completely unusable.
<body> element should never have aria-hidden="true"Check if the <body> element has aria-hidden="true" applied at any point in the lifecycle.
Remove aria-hidden="true" from the <body> and use it only on specific background containers when modals are open.
Explain the catastrophic impact of hiding the body element from assistive technologies.
Review the rendered markup and interactive states that affect Do not use aria-hidden on the document body. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/aria-hidden-body
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.