Skip to main content
SupportDashboard
Qa

A11y


SUB-PHASE D: ACCESSIBILITY

Run axe-core accessibility checks on every page touched by this feature.

Applicability: This sub-phase requires Playwright + @axe-core/playwright (JS/TS stacks only). For non-JS stacks, mark this sub-phase skip with reason "axe-core not applicable to {stackProfile}" and do the manual spot-checks in Step D2 only. The A11Y_APPLICABLE flag in the prompt header tells you whether the automated scan is available — @axe-core/playwright is pre-installed by qa-ralph.sh before the loop starts when applicable.

Step D1: Run automated accessibility scan

If the configured stack supports Playwright + @axe-core/playwright, write a temporary accessibility test in the stack's E2E test directory, run it, then clean it up. If the stack uses a different browser runner, use the nearest equivalent accessibility tooling described by BUILD_GUIDE.md. Prefer make test-e2e or the documented stack-specific E2E command where possible.

Step D2: Manual accessibility spot-checks (Ever CLI)

  • ever snapshot and check: are interactive elements keyboard-navigable?
  • Do form inputs have visible labels?
  • Are error messages associated with their inputs (aria)?
  • Is color contrast sufficient for text on colored backgrounds?

Step D3: Record accessibility results

List any WCAG 2.1 AA violations found. Fix critical violations. Log serious/moderate as known issues.

Was this page helpful?