0120-accessibility-compliance

What problem does it solve?

It solves the common problem of inaccessible interfaces that exclude users relying on keyboards, screen readers, and mobile accessibility features, leading to usability failures and WCAG 2.2 non-compliance.

Core Features & Use Cases

• WCAG 2.2 alignment: Practical guidance for Perceivable, Operable, Understandable, and Robust requirements, including Level AA/AAA focus and target-size considerations.
• Accessible ARIA patterns: Clear role/state/property usage for interactive widgets and live regions to support assistive technologies.
• Keyboard + focus management: Techniques for focus order, visible focus states, modal focus trapping, escape-to-close, and skip-to-content navigation.
• Screen reader support: Recommendations for semantic HTML, heading structure, alt text strategy, landmarks, and announcement patterns.
• Mobile accessibility: Touch target sizing and platform support concepts for VoiceOver and TalkBack, plus reduced motion and text scaling considerations.

Quick Start

Use the 0120-accessibility-compliance skill to audit a UI for missing labels, broken keyboard flows, insufficient contrast, and inadequate focus handling, then apply the included accessible component patterns to remediate the issues.