Keyboard Navigation Testing

Verify full keyboard operability of interactive UI elements per WCAG 2.1 SC 2.1.1. Use when testing web or desktop applications for accessibility compliance.

48 stars 10 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill keyboard-navigation-testing
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/qa-engineer/accessibility-testing/skills/keyboard-navigation-testing ~/.claude/skills/keyboard-navigation-testing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Keyboard Navigation Testing

Systematically verify that all interactive functionality is operable via keyboard alone, with visible focus indicators, logical tab order, and no keyboard traps — a foundational requirement for accessibility.

## Context

You are a senior QA engineer testing keyboard accessibility for $ARGUMENTS. Keyboard operability is a Level A WCAG requirement and a legal obligation in most jurisdictions.

## Domain Context

- **WCAG 2.2 Success Criterion 2.1.1 (Keyboard)**: All functionality must be operable through a keyboard interface without requiring specific timings for individual keystrokes (Level A)
- **WCAG 2.2 SC 2.1.2 (No Keyboard Trap)**: If keyboard focus can be moved to a component, focus can be moved away using only the keyboard (Level A)
- **WCAG 2.2 SC 2.4.3 (Focus Order)**: Focusable components receive focus in an order that preserves meaning and operability (Level A)
- **WCAG 2.2 SC 2.4.7 (Focus Visible)**: Any keyboard operable UI has a mode of operation where the keyboard focus indicator is visible (Level AA)
- **WAI-ARIA Authoring Practices 1.2**: Defines expected keyboard interaction patterns for common widgets (tabs, menus, dialogs, trees, grids, comboboxes)
- **Section 508 / EN 301 549**: Legal standards requiring keyboard accessibility for government and public sector applications

## Instructions
Read the full skill on GitHub

Details

Skill name
keyboard-navigation-testing
Path
qa-engineer/accessibility-testing/skills/keyboard-navigation-testing/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Keyboard Navigation Testing skill do?

Verify full keyboard operability of interactive UI elements per WCAG 2.1 SC 2.1.1. Use when testing web or desktop applications for accessibility compliance.

How do I install the Keyboard Navigation Testing skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Keyboard Navigation Testing popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.