accessibility-review

Audit a web, mobile, desktop, document, or product flow for practical accessibility issues using current WCAG 2.2 AA-oriented checks, code, screenshots, and interaction evidence. Use for accessibility

SKILL.md

GitHub

Accessibility Review

Review the actual experience, not just a checklist.

Evidence-first workflow

  1. Define the surface, users, platforms, assistive technology assumptions, and evidence available.
  2. Review semantic structure, names/roles/states, keyboard path, focus order/visibility, forms/errors, contrast, zoom/reflow, motion, media, dynamic updates, and touch targets as applicable.
  3. Test representative happy, error, empty, loading, and modal/overlay states.
  4. Classify findings by user impact, reproducibility, relevant criterion, evidence, and pragmatic fix direction.
  5. Retest after changes; a screenshot never proves keyboard or screen-reader behavior alone.

Guardrails

  • Use current WCAG 2.2 guidance when standards mapping matters; do not claim certification.
  • Do not rely on automated scans as proof of accessibility.
  • Preserve user preferences such as reduced motion, zoom, contrast, and input method.