Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/accesskeys
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure accesskey values are unique. 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 18 of 22 without it.
3 fixed18 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 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
A single-page application renders views dynamically without full page reloads. When switching from View A (which has `accesskey="k"`) to View B, View B mounts a component that also declares `accesskey="k"` while View A elements remain rendered in a background DOM branch. What accessibility bug occurs here?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that background DOM elements with matching accesskeys create duplicate shortcut conflicts | Passed | Passed |
| Recommends ensuring active DOM trees contain strictly unique accesskey values | Missed | Passed |
The instructions your model reads when the skill loads.
Duplicate access keys cause conflicts where only one element (usually the first) is reachable via the shortcut, making other elements inaccessible to keyboard users.
accesskey attribute value must be unique on the pageCheck for duplicate accesskey attributes across the document to ensure each shortcut is unique.
Assign unique values to each accesskey attribute or remove redundant ones to prevent shortcut conflicts.
Explain how duplicate access keys affect keyboard accessibility and browser shortcut handling.
Review the rendered markup and interactive states that affect Ensure accesskey values are unique. 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/accesskeys
test cases passed, vs 18 / 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.