skills.rest
hulusi-tunc
hulusi-tuncCOMMUNITY
Explore all skills by this author →
GitHub

keyboard-review

Identify keyboard navigation and focus-management issues across UI interfaces.

3|Updated Mar 28, 2026
Search Tags:#testing#accessibility#a11y#navigation#keyboard#ui-review#focus-management
One-click install
npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill keyboard-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keyboard-review
Source: https://github.com/hulusi-tunc/unicorn-skills/tree/main/.claude/skills-archive/inclusive-interaction--keyboard-review
Command: npx skills add https://github.com/hulusi-tunc/unicorn-skills --skill keyboard-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps QA and design teams identify keyboard navigation and focus-management issues in interfaces, ensuring accessible and frictionless use for keyboard-only users.

Core Features & Use Cases

  • Step-through focus flow audit to verify tab order, visible focus indicators, and avoidance of keyboard traps.
  • Focus management validation across dynamic content and modal dialogs, including trap checks and return focus behavior.
  • Regression and accessibility reporting by compiling a comprehensive keyboard accessibility report with findings and priors for fixes.
  • Use Case: When releasing a new UI component, run this skill to surface focus order problems and accessibility blockers before deployment.

Quick Start

Run a keyboard-review on the target UI to generate a focused accessibility assessment.

Frequently Asked Questions about keyboard-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit keyboard navigation and focus management across a UI?▼

To audit keyboard navigation, you step through the UI to verify tab order, check visible focus indicators, test for keyboard traps, and compile findings into an accessibility report.

What is focus trapping and when do I need to test for it in dynamic content?▼

Focus trapping occurs when keyboard focus cannot escape a specific UI element. You need to test for it during dynamic content observation and modal dialog validation to ensure return focus behavior works correctly.

Can I use this keyboard accessibility audit for regression testing during UI releases?▼

Yes, you can run a keyboard accessibility audit during regression testing before UI releases to surface focus order problems and accessibility blockers across web and app interfaces.

Does keyboard accessibility testing work for both web and app interfaces?▼

Keyboard accessibility testing applies to both web and app interfaces, allowing QA and design teams to validate end-to-end navigation and frictionless use for keyboard-only users.

What's the best way to document keyboard accessibility findings for design teams?▼

The best way to document keyboard accessibility findings is to compile a comprehensive report detailing focus management issues, tab order problems, and priors for fixes to guide remediation.

Why does focus disappear when navigating dynamic content with a keyboard?▼

Focus disappears in dynamic content when focus management fails to return focus properly after a modal closes or content updates, requiring validation of return focus behavior during keyboard audits.

Related Skills

Explore More Design & Creative Skills→
tsuji-tomonoritsuji-tomonori

a11y-keyboard-focus

Audit keyboard operability and focus management for WCAG 2.2 compliance.

Community
Advanced
exceptionlessexceptionless
2.5k

accessibility

Enforce WCAG 2.2 AA compliance for frontend components with semantic HTML and ARIA.

Official
Intermediate
RepairYourTechRepairYourTech
6

accessibility

Audit web accessibility against WCAG 2.1 guidelines and provide code examples.

Community
Intermediate
JhabbigJhabbig

wcag-audit-patterns

Audit web interfaces for WCAG 2.2 accessibility violations.

Community
Advanced