What should a website accessibility monitor check after every release?

Start with page structure and keyboard use, then test the forms and flows that matter most.

Run a fast automated pass

Check new and changed pages for missing names, invalid relationships, contrast failures, duplicate IDs, and structural errors. Treat results as leads, not proof.

Use only the keyboard

Confirm every interactive control can be reached, focus is visible, the order makes sense, and no dialog or menu traps focus.

Test one real task

Complete the most important flow with realistic data. Verify labels, instructions, errors, status updates, and recovery steps are clear.

Review at zoom

At 200% and 400% zoom, content should reflow without losing controls or forcing two-dimensional scrolling except where it is essential.

Keep human checks in the loop

Automation cannot judge whether alternative text fits the context or whether a task is understandable. Schedule manual review around high-impact changes.

Sources

WCAG 2.2 Quick Reference and W3C guidance on evaluating web accessibility. Reviewed Sep 22, 2026.