/qa-a11y

Phase: 3 - Design
Domain: Accessibility
Command: /qa-a11y
Prerequisite: /qa-ui must have run first (or standalone mode)
Allowed tools: Bash, Read, Write

---

What it does

Adds WCAG accessibility audit steps to the UI interaction script generated by /qa-ui. When executed, a11y-cli runs axe-core against every page visited during the UI flow and reports violations by WCAG criterion, impact level, and affected element.

Can also run as a standalone audit on a URL without a UI interaction script.

---

How it works

Integrated mode (default)

1. Reads qa-plan.md for accessibility scope
2. Reads dq-qa.config.json for accessibility.jurisdiction and accessibility.level
3. Reads qa-reports/ui/ui-test.yaml (generated by /qa-ui)
4. Appends a11y: true audit markers to each navigate step in the YAML

The modified YAML becomes the combined UI + accessibility test script.

Standalone mode

If no ui-test.yaml exists:

a11y-cli audit https://app.example.com \
  --level AA \
  --output ./qa-reports/a11y/

Reports are written directly without a UI interaction script.

---

WCAG levels supported

Config value	Standard
WCAG2.1 A	WCAG 2.1 Level A (minimum)
WCAG2.1 AA	WCAG 2.1 Level AA (most common legal requirement)
WCAG2.1 AAA	WCAG 2.1 Level AAA
WCAG2.2 AA	WCAG 2.2 Level AA
WCAG2.2 AAA	WCAG 2.2 Level AAA

---

Output

qa-reports/a11y/
  a11y-report.html        ← human-readable violations report
  a11y-report.json        ← machine-readable violations

---

Violation severity levels

axe-core reports violations at four impact levels, which map to triage priorities:

Impact	Triage priority
critical	P0
serious	P1
moderate	P2
minor	P3