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
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Scope, Findings by criterion, User impact, Automated evidence, Manual evidence, Untested areas, and Remediation priority. Grade each finding none, note, warning, or error, and order the list with the most severe first. When a pinned change is under review, mark each finding new, unchanged, updated, or absent against the state before the change; otherwise report severity alone.
Example
Synthetic example; not an observed client result.
Input: The checkout dialog opens, but Tab moves behind it.
Output: warning: focus escapes the active dialog. Keyboard users can reach obscured controls; verify focus containment and return focus after close.
1---2name: review-accessibility3description: "Reviews accessibility when asked to check keyboard access, screen-reader behavior, focus, contrast, or WCAG requirements; incomplete testing cannot establish conformance."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/review-accessibility7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Accessibility Review1617Use 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/).1819## Workflow20211. Identify supported surfaces, technologies, content types, user journeys, and stated conformance target if any.222. Inspect semantics, names, roles, values, headings, landmarks, labels, errors, status messages, and focus management.233. Test keyboard order, traps, shortcuts, pointer alternatives, motion, timing, and input assistance.244. Review contrast, text scaling, reflow, zoom, orientation, target size, spacing, and non-text alternatives.255. Map each finding to an exact WCAG 2.2 success criterion and level when supported.266. Separate automated findings from keyboard, screen-reader, magnification, cognitive, and user testing needs.277. Record environment, browser, assistive technology, viewport, zoom, and evidence limitations.2829## Boundaries3031- Do not claim WCAG conformance from automated scans or partial surface testing.32- Do not treat overlay widgets as substitutes for accessible product behavior.33- Do not include sensitive user data in screenshots or test evidence.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return Scope, Findings by criterion, User impact, Automated evidence, Manual evidence, Untested areas, and Remediation priority. Grade each finding `none`, `note`, `warning`, or `error`, and order the list with the most severe first. When a pinned change is under review, mark each finding `new`, `unchanged`, `updated`, or `absent` against the state before the change; otherwise report severity alone.4041## Example4243Synthetic example; not an observed client result.4445Input: The checkout dialog opens, but Tab moves behind it.4647Output: warning: focus escapes the active dialog. Keyboard users can reach obscured controls; verify focus containment and return focus after close.