Reviewing Accessibility

Review implemented UI code against WCAG Level AA criteria. This skill reviews code that already exists — components, pages, templates, or markup. It does not write code; findings are reported for a developer or coder agent to act on.

For pre-implementation risk assessment of plans or proposals, use predicting-accessibility-risks instead.

Review process

Review the implemented code against the checklist below. Reference specific WCAG success criteria when flagging violations. Read the actual source files — do not review from memory or assumptions.

Semantic HTML

• Correct elements used (button, nav, main, article, h1-h6, etc.)
• No div or span with role="button" when a native <button> would work
• Heading hierarchy is logical (single h1 per page, no skipped levels)
• Lists use ul/ol/dl for related items, not styled divs
• Data tables have th, caption or aria-label

WCAG: 1.3.1 Info and Relationships, 2.4.6 Headings and Labels