accessibility
Accessibility WCAG 2.1 AA: keyboard, screen reader, semantics, focus, contrast, reduced motion, touch targets, labeled forms, error announcements.
SKILL.mdskills/frontend/accessibility/SKILL.md
GitHubaccessibility
Accessible by construction, verified by testing — not audited in at the end.
Inspection
Keyboard-walk the flow; inspect semantics (landmarks, headings, names/roles/values), focus order/visibility, contrast, motion, form labeling.
Decision rules
Native elements first, ARIA to fill gaps only; every async update announced; errors tied to fields; reduced-motion honored; AA contrast minimum.
Activate when
- Any UI work: new screens, components, forms, navigation, media, animations.
Do NOT activate for
- Non-UI code (nothing here applies).
Procedure
- Semantics: native elements and landmarks first; ARIA only to fill genuine gaps; headings in order; skip links on content pages.
- Keyboard: all functionality reachable and operable, visible focus, logical order, focus trapped/restored in dialogs, no keyboard traps.
- Screen reader: names/roles/values on controls, live regions for async updates, error announcements tied to fields, images alted (decorative empty).
- Visual: contrast AA, 44px-class touch targets, focus visible,
prefers-reduced-motionhonored, content usable at 200% zoom. - Forms: programmatic labels, grouped related controls, inline errors with suggestions.
- Verify: keyboard-only walkthrough, screen-reader pass on changed flows, automated checks (axe/lighthouse) green, findings tracked as defects not suggestions.
Failure modes
Div-soup with click handlers; placeholder-as-label; focus lost in dialogs; carousels auto-advancing without pause; color-only meaning.
Escalation
Component fixes → frontend/component-design; verification probes → frontend/ui-verification.