accessibility-operable

Review user interfaces for keyboard operability and focus management.

6|3|Updated May 3, 2026
One-click install
npx skills add https://github.com/HDeibler/universal-design-principles --skill accessibility-operable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-operable
Source: https://github.com/HDeibler/universal-design-principles/tree/main/plugins/process-and-robustness-principles/skills/accessibility-operable
Command: npx skills add https://github.com/HDeibler/universal-design-principles --skill accessibility-operable

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you ensure users can operate your UI reliably using keyboard and other input modalities, while preventing accessibility failures like keyboard traps, missing focus states, and timeouts they cannot manage.

Core Features & Use Cases

  • Keyboard access and visible focus: Ensures every interactive element is reachable, focus is clearly shown, and focus order matches logical reading order.
  • Overlay and navigation operability: Provides correct behavior for modals, dialogs, popovers, menus, and similar components, including focus trapping and restoring focus on close.
  • Timing, motion, and input modality alternatives: Covers warning/adjustable timeouts, reduced-motion compliance, and keyboard/single-pointer alternatives for gesture-heavy interactions.

Quick Start

Apply accessibility-operable when reviewing a keyboard-only flow by tabbing through the interface, verifying focus is visible, and checking that every overlay can be closed (for example with Esc) without trapping the user.

Frequently Asked Questions about accessibility-operable

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

FAQPage Schema
How do I fix keyboard traps and missing focus in modal dialogs?

To fix keyboard traps and missing focus in modal dialogs, enforce standard keyboard interactions, trap focus within the overlay, and restore focus to the triggering element on close to ensure keyboard and assistive technology users can navigate reliably.

What is keyboard operability and visible focus management for WCAG 2.1 compliance?

Keyboard operability and visible focus management for WCAG 2.1 compliance means every interactive element is reachable via tab, focus order matches logical reading order, and a clear focus indicator is always displayed during keyboard navigation.

How do I provide keyboard alternatives for gesture-heavy pointer interactions?

To provide keyboard alternatives for gesture-heavy pointer interactions, implement single-pointer and keyboard alternatives alongside reduced-motion support, ensuring users can complete timing-sensitive flows without relying solely on complex gestures.

Does this accessibility review cover adjustable timeouts and reduced motion?

Yes, this accessibility review covers adjustable timeouts and reduced motion compliance by verifying timing-sensitive flows provide warnings and adjustable limits, and motion-dependent interactions respect reduced-motion preferences.

What's the best way to test UI overlays for keyboard navigation and escape behavior?

The best way to test UI overlays for keyboard navigation and escape behavior is to tab through the interface, verify visible focus, and confirm every modal, popover, and menu can be closed with Esc without trapping the user.