reviewing-accessibility
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
divorspanwithrole="button"when a native<button>would work - Heading hierarchy is logical (single
h1per page, no skipped levels) - Lists use
ul/ol/dlfor related items, not styled divs - Data tables have
th,captionoraria-label
WCAG: 1.3.1 Info and Relationships, 2.4.6 Headings and Labels
More from mattobee/skills
designing-agent-teams
Use this skill to design or refine a multi-agent coding team with model-to-role assignments. Triggers when creating an agent team for a codebase, adding agents to an existing team, reviewing an agent team configuration, choosing which AI model to assign to each role, or optimising cost/quality/speed tradeoffs across agents.
10suggesting-next-steps
Use this skill to suggest prioritised next steps for a project. Triggers when the user asks what to work on next, wants to resume after a break, or needs help prioritising a backlog.
7prioritising-accessibility-fixes
Use this skill to prioritise a set of accessibility issues for remediation based on severity, user impact, and effort. Triggers when triaging an accessibility backlog, deciding what to fix first after an audit, planning an accessibility sprint, or asking which accessibility issues matter most.
7estimating-accessibility-effort
Use this skill to estimate the effort required to remediate accessibility issues. Triggers when sizing accessibility work for a sprint, estimating how long a WCAG fix will take, scoping remediation work, or planning accessibility improvements.
7predicting-accessibility-risks
Use this skill to identify accessibility risks in a proposed feature, design, or technical plan before implementation begins. Triggers when planning a new feature, reviewing a design, assessing a technical approach for accessibility impact, or asking what could go wrong for disabled users.
7writing-accessibility-tests
Use this skill to write Playwright accessibility tests using the two-layer strategy (axe-core scans + targeted assertions). Triggers when adding accessibility test coverage, reviewing test gaps, writing axe scans, or creating Playwright assertions for accessible names, landmarks, ARIA states, focus management, or contrast.
7