# Aria Hidden Body

> 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.

- Skill: `thedaviddias/aria-hidden-body` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add thedaviddias/aria-hidden-body`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedaviddias/aria-hidden-body/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: thedaviddias (https://skillmd.com/u/thedaviddias)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/thedaviddias/aria-hidden-body

---


# Do not use aria-hidden on the document body

Setting `aria-hidden="true"` on the body effectively silences the entire application for screen reader users, rendering the site completely unusable.

## Quick Reference

- The `<body>` element should never have `aria-hidden="true"`
- Hiding the body makes the entire page invisible to assistive technologies
- Often happens accidentally when managing modal states

## Check

Check if the `<body>` element has `aria-hidden="true"` applied at any point in the lifecycle.

## Fix

Remove `aria-hidden="true"` from the `<body>` and use it only on specific background containers when modals are open.

## Explain

Explain the catastrophic impact of hiding the body element from assistive technologies.

## Code Review

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/en/rules/accessibility/aria-hidden-body

