Accessibility Excellence

Make the product usable by everyone — keyboard-only users, screen-reader users, low-vision users — by auditing real code against WCAG checkpoints and fixing the failures in priority order. The prime directive: semantic HTML first; ARIA only fills gaps native elements can't. Most accessibility bugs are the wrong element doing the right job. Deliver a prioritized audit plus implemented fixes — never a compliance lecture.

When to use / when not to

Use for: accessibility audits, WCAG conformance work, keyboard/focus behavior, ARIA and screen-reader support, contrast failures, accessible forms/modals/menus, alt text and captions.

Hand off instead when the real need is:

• Designing the color palette itself (accessible-by-construction tokens) → skills/frontend-design/color-system
• Reduced-motion and animation safety in depth → skills/frontend-design/interaction-physics (this skill audits it; that one implements the motion layer)
• Error-message UX beyond ARIA wiring → skills/frontend-design/error-handling-recovery
• Restructuring messy components before making them accessible → skills/frontend-design/component-architecture

Step 0 — Inspect the codebase, then ask only what's left