What the audit covers
Eight areas, each tested on desktop and on a phone. Every finding names the WCAG 2.2 success criterion it fails, so your developer can look it up.
Automated scan
Every agreed page template run through automated rule checks for what machines can find: missing alternative text, empty links and buttons, contrast failures, ARIA misuse.
Keyboard
Every menu, form, dialog and carousel used without a mouse: no traps (2.1.2), logical focus order (2.4.3), a visible focus (2.4.7) that is not hidden by sticky bars (2.4.11).
Screen readers
Landmarks, headings, labels, live messages and error text tested for sense, not only presence, with NVDA on Windows and VoiceOver on macOS and iOS.
Forms and checkout
Labels and instructions (3.3.2), clear errors (3.3.1), no re-typing what you already entered (3.3.7) and log-in without memory puzzles (3.3.8).
Colour, zoom and reflow
Text contrast 4.5:1 (1.4.3), controls 3:1 (1.4.11), reflow at 320 CSS px wide, the same as 400% zoom (1.4.10), and custom text spacing (1.4.12).
Touch and pointer
Targets at least 24 by 24 CSS px or well spaced (2.5.8), and a single-pointer alternative to every drag, such as sliders and map pins (2.5.7).
Media and documents
Captions for video (1.2.2), text alternatives for audio, and the PDFs your customers must read: tags, reading order and form fields.
Statement draft
A draft public accessibility statement: what conforms, what does not yet, the fix plan and how people can report a problem. You publish it; see this site's own.