
Accesskey Uniqueness Checker
Reviews HTML pages to catch duplicate accesskey shortcuts that block keyboard users.
- Repository
- thedaviddias/Front-End-Checklist
- Stars
- 74,632
- Licence
- MIT
- Files
- 2 files
What it does
This skill teaches an AI agent to review web page markup for duplicate accesskey attributes, which are keyboard shortcuts defined in HTML. When two elements share the same accesskey, only one is typically reachable, leaving others hard or impossible to use from the keyboard. Once installed, the agent checks rendered HTML and interactive components for this problem, explains the impact, and suggests unique values or removing redundant ones, with notes on how to verify the fix using accessibility tools.
Great for
- Front-end developers auditing a website for accessibility issues
- Teams reviewing components or design-system patterns before release
- Accessibility reviewers who want a quick check on keyboard shortcuts
Skip it if
- Sites that do not use accesskey attributes, since the rule has nothing to check (it is a narrow check, not a full accessibility audit)
- Situations needing a guaranteed compliance certification, because the skill gives guidance rather than a formal test
Try asking
- “Check this HTML page for duplicate accesskey values and tell me which elements conflict.”
- “Review our navigation component and suggest unique accesskey assignments.”
- “Explain why two buttons with the same accesskey break keyboard access and how to fix it.”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 2 original files, the MIT licence and an attribution note.
accesskeys.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip accesskeys.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip accesskeys.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Paste the rendered HTML (after JavaScript runs) rather than source templates, since components may add accesskey values dynamically.
- Ask the agent to also check native semantics and focus order, as the skill recommends, not only the attribute values.
- Verify fixes with a browser accessibility tool or by testing keyboard navigation yourself.
What's inside
- references/rule.md
- SKILL.md
Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.