What problem does it solve? Accessibility issues are often discovered late, when retrofitting fixes is far more expensive than building them in. This Skill guides both the implementation of accessible UI components and the auditing of existing interfaces, so keyboard users and assistive-technology users are not blocked by missing labels, broken focus, or incorrect ARIA. ## Core Features & Use Cases - Accessible Implementation Guidance: Choose semantic elements first, then add keyboard support, focus management, labels, error handling, and reduced-motion behavior while writing components, forms, dialogs, and menus. - Structured Audits: Test keyboard-only interaction, inspect focus behavior and ARIA usage via browser tools or code review, and report findings with severity levels (critical, high, medium, low) and concrete fixes. - Evidence-Matched Reporting: Distinguish verified results from partial code reviews, avoid unmeasured color-contrast claims, and list testing gaps explicitly. - Use Case: While building a checkout form, use this Skill to ensure every input has a proper label, errors are announced to screen readers, and the entire flow works without a mouse. ## Quick Start Ask the AI to audit the current page or component for accessibility issues, including keyboard navigation and focus behavior, and report findings by severity.
