a11y-keyboard-focus

a11y-keyboard-focus is a skill for Claude Code from RadOrigin-LLC/RAD-Claude-Skills. It costs 118 tokens per session (3,026 once invoked), scanned A, original, Apache-2.0.

Reference guidance for making web interfaces usable with a keyboard, including sensible Tab order and focus behavior. Focus is the element currently receiving keyboard input.

In plain words
What is it for?
Implementing keyboard navigation, focus indicators, skip links, modal focus traps, and returning focus to the right element after a dialog closes.
Why use it?
It helps prevent users from getting stuck, losing their place, or being unable to operate controls without a mouse, including inside dialogs and after they close.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the rad-a11y plugin — 6 skills, 1 agent shipped together

Good fit Implementing keyboard navigation, focus indicators, skip links, modal focus traps, and returning focus to the right element after a dialog closes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/radorigin-llc/rad-claude-skills/a11y-keyboard-focus
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add RadOrigin-LLC/RAD-Claude-Skills --skill a11y-keyboard-focus
Clone the repo
git clone --depth 1 https://github.com/RadOrigin-LLC/RAD-Claude-Skills

Made for: Claude Code.

Or install rad-a11y, the plugin that ships this one along with the rest of its 6 skills, 1 agent.

Wrote 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.

agentmods badge for a11y-keyboard-focus

README.md
[![agentmods](https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/a11y-keyboard-focus/github.svg)](https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/a11y-keyboard-focus)
Your own site
<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/a11y-keyboard-focus"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/a11y-keyboard-focus/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for a11y-keyboard-focus

Your own site · 80×15
<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/a11y-keyboard-focus"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/a11y-keyboard-focus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,026 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00118 $0.03026
Opus 5 $0.00059 $0.01513
Sonnet 5 $0.00024 $0.00605
Haiku 4.5 $0.00012 $0.00303

Measured 12d ago against content hash a9489b994e14, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

a11y-keyboard-focus 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 12d 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.

archive/plugins/rad-a11y/skills/a11y-keyboard-focus/SKILL.md · 419 lines

How it starts

The opening of the file, as written. The whole thing — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Keyboard Navigation and Focus Management

Skill type: Reference. This is teaching/pattern content — it explains keyboard contracts, focus management strategies, and focus-restoration patterns for modals/dialogs. It is not a scanner. Static review (/a11y-review) catches common keyboard/focus source patterns; runtime keyboard feel (Tab order making sense, focus indicator quality) requires browser testing.

Keyboard accessibility is non-negotiable for WCAG 2.1.1 (Keyboard) and required for motor-impaired users, power users, and assistive technology users. Every interactive element must be reachable and operable via keyboard alone.


Focus Fundamentals

What Receives Focus

By default, only natively focusable elements receive keyboard focus:

  • <a href="..."> — links with valid href
  • <button>, <input>, <select>, <textarea> — form controls
  • <summary> — disclosure toggle
  • Elements with tabindex="0" — explicitly focusable
  • Elements with tabindex="-1" — programmatically focusable only (not via Tab)

tabindex values:

Value Effect
0 Element enters natural Tab order at its DOM position
-1 Element is focusable via element.focus() but excluded from Tab order
> 0 Never use. Overrides natural order, causes confusing navigation

Tab Order = DOM Order

Focus follows the DOM order, not the visual layout. CSS reordering (flex-direction: row-reverse, order, grid-template-areas, position: absolute, float) creates a mismatch between what users see and where focus goes.

<!-- Visual order: B A — Tab order: A B (DOM order) -->
<div style="display:flex; flex-direction:row-reverse">
  <button>A</button>  <!-- Tab focuses A first -->
  <button>B</button>  <!-- Then B — opposite of visual order -->
</div>

Always verify DOM order matches visual reading order.


Focus Indicators (WCAG 2.4.7, 2.4.11)

The Rule: Never Remove Without Replacing

/* ❌ FORBIDDEN: Removes focus indicator for keyboard users */
* { outline: none; }
button:focus { outline: 0; }
.btn:focus { outline: none; }

/* ✅ CORRECT: Replace with high-visibility custom indicator */
button:focus-visible {
  outline: 3px solid #005fcc;
  outline-offset: 2px;
}

Read the full file on GitHub · 419 lines

Changes

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.

  1. 12d ago First seen · 419 lines · 118 tokens per session scan A a9489b994e14

Subscribe to this mod's changes

a11y-keyboard-focus is a skill published in the GitHub repository RadOrigin-LLC/RAD-Claude-Skills (5 stars, last pushed 25d ago), licensed Apache-2.0. It adds 118 tokens to every session and 3,026 once invoked, about $0.0006 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-31.

Related

Other skills, from other repositories

light-dark-mode

Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level…

mgifford/accessibility-skills · 69 tokens

tables

Load this skill whenever the project contains HTML data tables ( elements). Under no circumstances use tables for layout purposes. Absolutely always include elements with appropriate scope attributes, a or aria-labelledby, and ensure complex tables have headers associated with data cells. Apply these rules to every…

mgifford/accessibility-skills · 67 tokens

print

Load this skill whenever the project includes print stylesheets, print media queries (@media print), or any content intended for physical printing. Under no circumstances omit print CSS that ensures readable, accessible printed output. Absolutely always hide decorative elements, expand link URLs, and maintain…

mgifford/accessibility-skills · 63 tokens

progressive-enhancement

Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the…

mgifford/accessibility-skills · 73 tokens

wes-bos-sick-picks

Research-first workflow for building frontend UI components (any framework), in the spirit of Wes Bos. Use when designing or implementing a UI component, layout, interaction, or CSS/HTML feature and you want a modern, accessible, best-practice solution rather than a first guess. Researches pitfalls and platform…

boserup/wes-bos-sick-picks · 140 tokens

brand-visual-language

A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…

dembrandt/dembrandt-skills · 68 tokens