Accessibility

This skill makes interfaces usable by everyone — keyboard-only users, screen-reader users, low-vision users — and meets the legal bar (the EU Accessibility Act and ADA Title II both reference WCAG). Accessibility is not a nice-to-have; it's increasingly a legal requirement and always a larger addressable market.

Analogy: a curb cut was built for wheelchairs, but everyone with a stroller, suitcase, or bike uses it. Accessible UI is the same — built for those who need it, better for everyone.

Dependencies

This skill is stronger when Vercel's web-design-guidelines skill (part of vercel-labs/agent-skills, ~27k⭐) is installed — it ships the ARIA/focus/keyboard checklist. Delegate the checklist to it when present; always pair with the axe-core test step below, which catches runtime violations a static checklist can't. Never block on a missing dependency — the rules below are the embedded fallback.

The target

WCAG 2.2 Level AA — the bar referenced by the EU EAA, ADA Title II, and Section 508. Automated tools catch only ~30-40% of issues, so combine automated tests with manual checks.

Discovery (max 3 questions, only if unknown)

1. Are you building new components or auditing existing UI?
2. Any specific complaint (keyboard trap, unreadable contrast, screen reader silent)?
3. Is there a CI pipeline where an a11y test could run?