agentleFS
smukhsmukh/a11y-agent-skills/skills/keyboard-navigation-review/SKILL.md

keyboard-navigation-review

Skill8 starsChanged 2 months agoMITView on GitHub

Evaluate a bounded task with real browser key presses. Synthetic keyboard evidence is useful but is not complete assistive-technology evidence. 1. Define the starting URL/state, viewport, task completion condition, and expected focus behavior. 2. Run a11y-agent keyboard <url> --journey <file> or perform the equivalent physical-key review. Journey files must use only the bounded actions in references/journey-review.md; never add arbitrary JavaScript. 3. Check reachability, visible focus, logical sequence, traps, skip links, composite-widget arrow-key behavior, route/state changes, dialog entry, and focus restoration.…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run a11y-agent keyboard <url> --journey <file> or perform the equivalent physical-key review.

    line 21
  2. Distinctive:

    Check reachability, visible focus, logical sequence, traps, skip links, composite-widget arrow-key behavior, route/state changes, dialog …

    line 25
  3. Distinctive:

    Do not infer that a passing scripted journey works with every keyboard layout, switch device, voice input system, browser, or screen reader.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Keyboard navigation review

Evaluate a bounded task with real browser key presses. Synthetic keyboard evidence is useful but is not complete assistive-technology evidence.

Workflow

  1. Define the starting URL/state, viewport, task completion condition, and expected focus behavior.
  2. Run a11y-agent keyboard <url> --journey <file> or perform the equivalent physical-key review. Journey files must use only the bounded actions in references/journey-review.md; never add arbitrary JavaScript.
  3. Check reachability, visible focus, logical sequence, traps, skip links, composite-widget arrow-key behavior, route/state changes, dialog entry, and focus restoration.
  4. Record every action, resulting focused element, accessible name, and failure reason.
  5. Replay any repair from the identical starting state and add a behavior-focused regression journey.

Boundaries

Do not infer that a passing scripted journey works with every keyboard layout, switch device, voice input system, browser, or screen reader. Manual review remains required for visual focus quality and task-level sequence judgment.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.