AgentStack
SKILL verified MIT Self-run

Keyboard Review

skill-owl-listener-inclusive-design-skills-keyboard-review · by Owl-Listener

Review keyboard navigation and focus management in an existing interface. Chains: keyboard-navigation, feedback-and-status. Use when testing or reviewing keyboard accessibility specifically, before a release, or when users report keyboard issues.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-owl-listener-inclusive-design-skills-keyboard-review

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Keyboard Review? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Keyboard Review

A focused review of keyboard accessibility — the single most important interaction requirement. If keyboard doesn't work, screen readers don't work, switch devices don't work, and many motor-impaired users are completely blocked.

Process

Step 1: Tab Through Everything

Starting from the browser address bar, press Tab repeatedly through the entire page. Document:

  • Unreachable elements — interactive items that Tab skips
  • Wrong order — focus jumps to unexpected locations
  • Invisible focus — focus moves but you can't see where it is
  • Keyboard traps — focus enters a region and can't leave

Step 2: Test All Components

Using keyboard-navigation, test each component type present:

  • Menus: Tab to open, Arrow keys to navigate, Escape to close
  • Modals: focus trapped inside, Escape to close, focus returns on close
  • Tabs: Arrow keys between tabs, Tab into panel content
  • Forms: Tab between fields, Enter to submit
  • Custom widgets: appropriate keyboard patterns for the role

Step 3: Test Dynamic Content

When content changes on screen:

  • Does focus move to the new content when appropriate?
  • Are screen reader users informed of the change?
  • When content is removed, does focus move to a logical place?
  • Do loading states announce themselves?

Using feedback-and-status, verify all dynamic changes are announced via aria-live regions or focus management.

Step 4: Check Skip Links and Landmarks

  • Is "Skip to main content" present and functional?
  • Are ARIA landmarks present (banner, navigation, main, contentinfo)?
  • Can a keyboard user bypass repeated navigation efficiently?

Output

Deliver a keyboard accessibility report:

  1. Pass/fail summary — can every task be completed by keyboard?
  2. Tab order map — the actual focus sequence with issues marked
  3. Component results — pass/fail for each interactive component
  4. Dynamic content results — focus management for content changes
  5. Fix list — prioritised by severity (blocker, major, minor)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.