accessibility
Achieve and maintain WCAG compliance through inclusive design practices, proper ARIA usage, and comprehensive testing methodologies.
Profile →npx skills add cosmicstack-labs/mercury-agent-skills --skill accessibility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill guides the agent to pursue WCAG compliance via inclusive design, proper ARIA usage, and comprehensive testing methodologies. It emphasizes early accessibility consideration, human-in-the-loop testing, and a maturity model for integrating accessibility into processes.
How it works
- Encourages treating accessibility as a human right and integrating it from the wireframe stage.
- Promotes testing with real users of assistive technologies in addition to automated checks.
- Outlines WCAG POUR principles (Perceivable, Operable, Understandable, Robust) and provides concrete examples for text alternatives, keyboard navigation, screen reader support, color contrast, and motion preferences.
- Includes guidance on ARIA usage: use ARIA only when native HTML semantics are insufficient; demonstrates common ARIA patterns for modals and tab panels.
- Describes automated testing tools (axe-core, WAVE, Lighthouse, Pa11y, Accessibility Insights) and how they fit into CI/CD, plus a manual testing checklist and screen reader testing expectations.
- Presents an accessibility testing methodology with both automated and manual components and a practical CI example using axe-core with Playwright.
When to use it
Use when scanning or implementing accessibility practices across design and development work, especially in projects aiming for Level AA WCAG compliance and inclusive design practices. It is intended for teams integrating accessibility into design critiques, sprint planning, and definition of done.
What it can touch
- Tools: axe-core, axe DevTools, WAVE, Lighthouse, Pa11y, Accessibility Insights
- Code patterns: ARIA usage examples, semantic HTML guidance, keyboard interaction patterns, focus management snippets
- Testing artifacts: automated test examples, manual testing checklists, screen reader testing scenarios
Caveats
- The skill notes that automated tools catch about 30-40% of accessibility issues; manual testing is essential to cover remaining gaps. It also advises that Level AAA may be aspirational and Level AA is the practical target.
- Licenses and authorship information indicate MIT license and the author is cosmicstack-labs. These are stated facts; no policy or legal assurances beyond what's described are provided.
# Accessibility Skill ## Core Principles ### 1. Accessibility Is a Human Right Digital accessibility is not a compliance checkbox — it's about ensuring everyone can use the web regardless of ability. Approximately 15% of the world's population experiences some form of disability. Building accessible products is the ethical choice, not just a legal requirement. ### 2. Start Early, Not as an Audit Accessibility must be considered from the first wireframe, not discovered in a last-minute audit before launch. Retrofitting accessibility costs significantly more than building it in from the start. Include a11y in design critiques, sprint planning, and definition of done. ### 3. Nothing About Us Without Us Design with, not for, people with disabilities. Test with real users who rely on assistive technologies. Automated tools catch only 30-40% of accessibility issues — human testing catches the rest. Include disabled people in your user research and usability testing. ### 4. Accessibility Improves UX for Everyone Curb cuts benefit everyone, not just wheelchair users. Captions help people in noisy environments. High contrast helps on sunny days. Keyboard navigation helps power users. Access
- Core Principles
- 1. Accessibility Is a Human Right
- 2. Start Early, Not as an Audit
- 3. Nothing About Us Without Us
- 4. Accessibility Improves UX for Everyone
- 5. Progress Over Perfection
- Accessibility Maturity Model
- Level 1: Unaware
- Level 2: Reactive
- Level 3: Proactive
- Level 4: Embedded
- Level 5: Culture
- WCAG Guidelines — The POUR Principles
- Perceivable — "Can users perceive the content?"
What does the accessibility skill do?
Achieve and maintain WCAG compliance through inclusive design practices, proper ARIA usage, and comprehensive testing methodologies.
How do I install it?
Run `npx skills add cosmicstack-labs/mercury-agent-skills --skill accessibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From cosmicstack-labs/mercury-agent-skills, a repository with 364 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.