skills/accessibility-compliance/SKILL.md
Use when implementing or reviewing accessibility - WCAG compliance, screen reader support, keyboard navigation, a11y testing
npx skillsauth add kienbui1995/magic-powers accessibility-complianceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Accessibility isn't optional — it's a legal requirement in many jurisdictions and affects ~15% of users. Build it in from the start, not as an afterthought.
alt="" for decorative)outline: none without replacement)<label><html lang="en"> set correctly<button>, <nav>, <main>, not <div onclick>aria-label, aria-expanded, role for custom widgets# Automated
npx axe-core # or browser extension
npx pa11y http://localhost:3000
# Manual
- Tab through entire page — can you reach everything?
- Screen reader test (VoiceOver/NVDA) — does it make sense?
- Zoom to 200% — does layout break?
- Disable CSS — is content still readable?
| Issue | Fix |
|-------|-----|
| Missing alt text | Add descriptive alt attribute |
| Low contrast | Increase to 4.5:1 ratio minimum |
| No focus styles | Add :focus-visible styles |
| Click-only interactions | Add keyboard handlers (onKeyDown) |
| <div> as button | Replace with <button> |
| Missing form labels | Add <label htmlFor="..."> |
content-media
Use when designing for XR (AR/VR/MR), choosing interaction modes, or adapting 2D UI patterns for spatial computing
testing
Use when creating new skills, editing existing skills, or verifying skills work before deployment
development
Use when you have a spec or requirements for a multi-step task, before touching code
development
Use when executing a structured workflow — select and run a feature, bugfix, refactor, research, or incident template with correct agent and model assignments per phase.