accessibility-rules
Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.
When & Why to Use This Skill
This Claude skill provides a comprehensive accessibility checklist and implementation guide for UI components, ensuring full compliance with WCAG 2.1 AA standards. It streamlines the development process by offering actionable practices for keyboard navigation, screen reader compatibility, and focus management, helping teams build inclusive digital experiences.
Use Cases
- Building New Components: Use the skill to implement accessible keyboard interactions and ARIA attributes from the initial development phase.
- Refactoring Legacy UI: Audit and update existing repository components to fix accessibility debt, such as missing focus indicators or incorrect semantic HTML.
- WCAG Compliance Auditing: Conduct systematic reviews of UI elements to ensure they meet international accessibility standards for screen reader and keyboard-only users.
- Code Reviews: Integrate accessibility checks into the PR process to maintain high-quality, inclusive code standards across the team.
| name | accessibility-rules |
|---|---|
| description | Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics. |
| license | MIT |
| author | AI Agents |
| version | "1.0" |
When to use this skill
Use this skill when building new components, refactoring existing ones, or auditing for accessibility. Use this skill when implementing UI to ensure keyboard, screen reader, and focus semantics are preserved. Covers WCAG 2.1 AA principles and practical implementation patterns.
For complete checklist, testing procedures and examples, see references/REFERENCE.md.