Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/aria-hidden-focus
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.
Passed 21 of 22 test cases with the skill, and 15 of 22 without it.
and 4 more in the full report
6 fixed15 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I built a custom slide-out menu that gets hidden off-screen with `aria-hidden="true"`, but keyboard users can still tab into the links inside it. Could you conduct an accessibility review on this code, flag any elements violating keyboard or screen reader rules, and show me how to properly handle focus for those child elements?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that focusable links inside aria-hidden containers create silent ghost focus for screen readers. | Passed | Passed |
| Recommends applying tabindex="-1" to child links inside the hidden container. | Missed | Passed |
| Instructs how to verify the fix using browser DevTools Accessibility Tree. | Missed | Passed |
The instructions your model reads when the skill loads.
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
test cases passed, vs 15 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.