Navigate everything by keyboard
Check order, visible focus, menus, modals, accordions, and forms. No trap should prevent users from leaving a component.
Inspect structure and comprehension
Use one main heading, coherent hierarchy, explicit links, semantic regions, and instructions that do not rely on colour alone.
Test forms and errors
Every field has a label, requirements are announced, errors connect to the field, and the message explains how to correct them.
Combine tools with human judgment
Validate contrast and code automatically, then test zoom, mobile, reduced motion, and at least one screen reader. Technical review reduces risk; it is not a legal guarantee.
Keep in mind
This guide provides a general starting point. A diagnosis must account for the actual site, access, data, and constraints before any change.