Keyboard Navigation — Inclusive Design Skills

When to use it

Use while specifying interactive components and keyboard-only task flows. This is design guidance, not an automated audit or compliance certificate. Upstream Tab and menu rules are simplified: distinguish ordinary navigation from ARIA composite widgets, follow the applicable authoring pattern, and validate focus placement and assistive-technology behavior in the actual build. Source reviewed only; not installed or runtime-tested. GitHub stars are repository-wide.

Compatible agents

Claude CodeCodexGemini CLICursor

Installation

In Claude Code, run /plugin marketplace add Owl-Listener/inclusive-design-skills, then run /plugin, open Discover, and select inclusive-interaction. Ask the assistant to use keyboard-navigation. This installs the containing plugin, not only this skill. For other supported agents, copy the inclusive-interaction/skills/keyboard-navigation folder from the repository into the agent's documented skills directory, as described in the upstream README.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 14, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.