This is practical accessibility guidance for first-pass triage. It is not legal advice, a formal audit, WCAG certification, or a conformance guarantee.
What this means
A container hidden from assistive technology appears to include focusable controls.
Why it matters
Keyboard users may reach something that screen readers cannot announce properly.
How to fix it
- Do not place focusable controls inside aria-hidden="true".
- Remove the content from the tab order when it is hidden.
- Use proper modal, disclosure, and inactive-state patterns.
What automated checks can detect
A checker can find focusable descendants inside aria-hidden containers.
What still needs manual review
Test focus order and screen reader announcements through the relevant interaction state.
Automation cannot fully validate dynamic focus management across all app states.