What problem does it solve?
Accessibility gaps that exclude people who use screen readers, keyboard navigation, assistive tech, or who experience cognitive, motor, or situational impairment.
Core Features & Use Cases
- WCAG 2.2 guidance for designers: Practical design rules for perceivable, operable, understandable, and robust experiences (contrast, labels, reflow, semantics, ARIA misuse avoidance).
- Screen reader & keyboard experience design: Reading order, landmarks, heading hierarchy, live regions, focus management, and keyboard interaction patterns.
- Accessibility testing methodology and remediation planning: Automated vs manual testing, and a structured remediation approach (P0–P3) to make audits actionable.
- Use cases: Accessibility audits, inclusive design reviews, WCAG compliance checks, form and navigation design, and “is this accessible?” guidance for product UX.
Quick Start
Use the include skill to turn an accessibility concern in a design or UI into a clear, testable audit and remediation plan for all users, including screen reader and keyboard users.