Manual checks recur when a change can affect their result. A successful check applies to the tested commit, environment, and scope; it is not permanent accessibility or visual approval. Run the automated suites first. Unchecked items have not been verified.
| Trigger | Manual work |
|---|---|
| First setup of this suite | Review the initial CI-generated screenshots and run the full accessibility checklist to establish a recorded starting point. |
| Navigation, content structure, form, code-copy, CSS, or layout changes | Repeat the affected keyboard, screen-reader, contrast, zoom, and no-JavaScript checks on the changed page types. |
| Release candidate | Run a representative keyboard and screen-reader smoke test across home, list, single, terms, taxonomy, and 404 pages; review unresolved findings before release. |
| Browser or assistive-technology changes that affect supported users | Repeat representative navigation, reading-order, and form checks in the changed environment. |
| Intended visual change, browser upgrade, font change, or capture-environment change | Review the screenshot differences and approve replacement baselines generated in CI. |
| A new page type or viewport enters the visual suite | Review its first CI-generated baseline. |
Initial baseline approval is a one-time setup step for that baseline set. Screenshot comparisons run automatically in CI after that. Human review recurs when a difference is intentional or when the capture environment changes; an unchanged screenshot does not need a fresh manual review on every run.
Generate baseline images with the workflow described in the visual baseline guide. Check page content, navigation, responsive layout, clipping, overlap, focus appearance where captured, and unexpected missing elements at each viewport. Record the CI run and reviewed commit. Review the actual differences before accepting replacement images; do not update baselines only to silence a failure.
Use the checks below for the affected scope. A release smoke test covers representative pages and interactions; a substantial navigation or layout change warrants the full checklist.
The automated suite now requires zero violations, including contrast and form labels. This does not mean these manual checks have passed. Record any manual defects separately.
Put results in the pull request or release record, and link any defects. Keep the checklist as the procedure rather than checking it off permanently. Use this template:
Date:
Tested commit:
Tester:
Scope and page types:
Browser and version:
Operating system and version:
Screen reader or other assistive technology and version:
Viewport and zoom:
Checks completed:
Result: passed / failed / not run
Findings and issue links:
Screenshots or CI run:
Axe results and accessible-name assertions do not replace a person using a screen reader. Leave manual checks marked as not run until that work is done.