Inspect hidden page regions for links, buttons, or inputs that still receive keyboard focus. Identify elements that screen readers cannot announce, suggest focus handling changes, and explain how to verify the resulting keyboard behavior.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Remove focusable elements from aria-hidden containers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Check whether regions marked with aria-hidden="true" still contain elements that receive keyboard focus. The skill identifies links, buttons, and input fields, then points out the specific elements and the interaction problems they cause. It suggests changes using tabindex="-1" or inert and explains how to check the results with browser accessibility tools or assistive technology.
Use it when a screen reader falls silent as you press Tab, or when you lose track of your current position while navigating a page. It also helps with reviews of shared UI components and components whose appearance changes with their state. The review starts with native HTML semantics, then examines focus flow and what the screen reader announces.
aria-hidden regions.”Adding aria-hidden does not prevent keyboard navigation to elements inside it. Check the rendered HTML and component states instead of relying only on source files. Where needed, verify the changes with a screen reader.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. 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.
When a keyboard user tabs into an aria-hidden element, the screen reader remains silent, leaving the user with no idea where their focus is or what they can interact with.
aria-hidden="true" must not contain focusable childrentabindex="-1" or inert to properly hide interactive elementsScan aria-hidden="true" containers for focusable elements like links, buttons, or inputs.
Add tabindex="-1" to focusable children inside aria-hidden containers or use the inert attribute.
Explain why focusable elements inside aria-hidden containers cause confusion for keyboard and screen reader users.
Review the rendered markup and interactive states that affect Remove focusable elements from aria-hidden containers. 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-focus
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.