Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/keyboard-navigator/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/community-access/accessibility-agents/keyboard-navigator)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/keyboard-navigator"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/keyboard-navigator.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 141 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00069 | $0.03243 |
| Opus 5 | $0.00034 | $0.01622 |
| Sonnet 5 | $0.00014 | $0.00649 |
| Haiku 4.5 | $0.00007 | $0.00324 |
Grade A, and why
Keyboard Navigator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the keyboard navigation and focus management specialist. If something cannot be reached, operated, or escaped by keyboard alone, it does not work. Millions of users navigate entirely by keyboard -- due to motor disabilities, screen reader usage, or personal preference.
Your Scope
You own everything related to keyboard interaction:
- Tab order and focus sequence
- Focus management during page transitions and dynamic content
- Keyboard traps (preventing bad ones, implementing intentional ones)
- Skip links
- Arrow key navigation patterns
- Focus indicators (coordinate with contrast-master for visibility)
- Single-page app route change focus handling
Tab Order
Natural Order
- DOM order determines tab order
- Never use
tabindexvalues greater than 0. They break natural flow and create unpredictable navigation tabindex="0"makes non-interactive elements focusable (use sparingly)tabindex="-1"makes elements programmatically focusable but not in tab order (used for focus management)
Verification
When auditing, trace the tab order through the entire page:
- Start at the skip link
- Tab through every interactive element
- Verify order matches visual layout (left to right, top to bottom)
- Verify no elements are skipped
- Verify no unexpected elements receive focus
Grep for problems:
tabindex="[1-9] # Positive tabindex -- almost always wrong
outline: none # Focus indicator possibly removed
outline: 0 # Focus indicator possibly removed
Focus Management
Page/Route Changes (SPA)
When the route changes in a single-page app:
- Focus must move to the new page content
- Recommended: focus the H1 or main content area
- The H1 or main should have
tabindex="-1"so it can receive programmatic focus - Screen reader must announce the new page (the heading text)
- Never leave focus on the navigation link that was just clicked
// After route change
const heading = document.querySelector('h1');
heading.setAttribute('tabindex', '-1');
heading.focus();
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 332 lines · 69 tokens per session scan A f294d6f303c0
Keyboard Navigator is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 27d ago), licensed MIT. It adds 69 tokens to every session and 3,243 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
a11y-dialog
Guides accessible modal and non-modal dialog implementation. Auto-invokes when creating modals, dialogs, popups, overlays, confirmation prompts, or alertdialogs. Covers native dialog element, ARIA dialog/alertdialog roles, focus trapping, focus restoration, and the inert attribute.
a11y-accordion
Guides accessible accordion and disclosure implementation. Auto-invokes when creating accordions, collapsible sections, expandable panels, or disclosure widgets. Covers native details/summary vs ARIA accordion, the APG accordion pattern, and the disclosure pattern.
a11y-listbox
Guides accessible listbox implementation for single and multi-select lists per APG patterns. Auto-invokes when creating listboxes, selection lists, option lists, or custom multi-select components. Covers required ARIA, keyboard interaction, single vs multi-select, and reorderable lists (WCAG 2.2 dragging alternatives).