Accessibility Review
Use current primary guidance as a review baseline, then report only what the available evidence supports. Primary authority: official reference.
Workflow
- Identify supported surfaces, technologies, content types, user journeys, and stated conformance target if any.
- Inspect semantics, names, roles, values, headings, landmarks, labels, errors, status messages, and focus management.
- Test keyboard order, traps, shortcuts, pointer alternatives, motion, timing, and input assistance.
- Review contrast, text scaling, reflow, zoom, orientation, target size, spacing, and non-text alternatives.
- Map each finding to an exact WCAG 2.2 success criterion and level when supported.
- Separate automated findings from keyboard, screen-reader, magnification, cognitive, and user testing needs.
- Record environment, browser, assistive technology, viewport, zoom, and evidence limitations.
Boundaries
- Do not claim WCAG conformance from automated scans or partial surface testing.
- Do not treat overlay widgets as substitutes for accessible product behavior.
- Do not include sensitive user data in screenshots or test evidence.
Output
Return Scope, Findings by criterion, User impact, Automated evidence, Manual evidence, Untested areas, and Remediation priority.
1---2name: accessibility-review3description: Review web or application accessibility using WCAG 2.2 success criteria, semantic structure, keyboard behavior, assistive-technology needs, visual presentation, and user impact. Use for evidence-based findings without claiming conformance from incomplete testing.4license: MIT5---67# Accessibility Review89Use current primary guidance as a review baseline, then report only what the available evidence supports. Primary authority: [official reference](https://www.w3.org/TR/WCAG22/).1011## Workflow12131. Identify supported surfaces, technologies, content types, user journeys, and stated conformance target if any.142. Inspect semantics, names, roles, values, headings, landmarks, labels, errors, status messages, and focus management.153. Test keyboard order, traps, shortcuts, pointer alternatives, motion, timing, and input assistance.164. Review contrast, text scaling, reflow, zoom, orientation, target size, spacing, and non-text alternatives.175. Map each finding to an exact WCAG 2.2 success criterion and level when supported.186. Separate automated findings from keyboard, screen-reader, magnification, cognitive, and user testing needs.197. Record environment, browser, assistive technology, viewport, zoom, and evidence limitations.2021## Boundaries2223- Do not claim WCAG conformance from automated scans or partial surface testing.24- Do not treat overlay widgets as substitutes for accessible product behavior.25- Do not include sensitive user data in screenshots or test evidence.2627## Output2829Return Scope, Findings by criterion, User impact, Automated evidence, Manual evidence, Untested areas, and Remediation priority.30
JovaniPink