Accessibility Inclusive Design

Core Workflow

1. Identify the product surface, audience, platform, assistive technologies, input methods, legal/compliance context, and risk level.
2. Use semantic structure first. Add ARIA only when native semantics cannot express the interaction correctly.
3. Check the experience across keyboard, pointer/touch, screen reader, zoom/reflow, color/contrast, motion, captions/audio alternatives, and error recovery.
4. Separate automated checks from human judgment. Automated tools catch some issues; they do not prove accessibility.
5. Prioritize blockers that prevent task completion, then issues that create confusion, fatigue, or exclusion.
6. Verify fixes in the actual interface and target states.

Freshness Rule

Verify current W3C/WAI WCAG guidance and platform accessibility documentation before giving compliance-sensitive advice. WCAG 2.2 is the current W3C recommendation for maximizing future applicability, but legal requirements vary by jurisdiction and this skill is not legal advice.

Accessibility Priorities