WebsightRun the automated scan first. It will find the missing alt attributes, the low-contrast text, the unlabelled fields and the empty links in seconds, and there is no point doing those by hand. Then do this list. It covers what the engine cannot judge: whether things make sense, whether they work with a keyboard, and how the page behaves for someone who cannot see it.
Each item names the WCAG 2.2 success criterion it relates to so you can trace it, and gives the test in plain words. Mark each one Looks fine, Problem found or Not applicable, and write a line about any problem you find. For a report, do the list on the main templates: home, a content page, a form, and any sign-in or checkout.
What this is not. This is not every WCAG 2.2 success criterion, and ticking every box does not make a site compliant with WCAG or any law. It is the set of checks most often missed after an automated scan. A conformance claim needs a full evaluation by a qualified person.
Before you start
- A keyboard and the discipline to leave the mouse alone for ten minutes.
- A screen reader: VoiceOver is built into macOS (Cmd+F5) and iOS; NVDA is free for Windows. You do not need to be expert; you need to listen to one page.
- Browser zoom at 200 percent and at 400 percent, which is how WCAG tests reflow on a desktop browser.
- A colour picker or contrast checker for text over images, which the scanner cannot decide.
Perceivable 9 checks
Can everyone perceive the content, whatever senses they use?
Image text alternatives are meaningful WCAG 1.1.1
Check that alt text describes the purpose of each image, not just the file name, and decorative images are empty.
Video has captions and audio has a transcript WCAG 1.2.2
Play any video or audio. Captions should be accurate and cover speech and key sounds.
Controls and icons have enough contrast WCAG 1.4.11
Check borders of form fields, icon-only buttons and focus rings have at least 3 to 1 contrast with their surroundings.
Text over images or gradients is readable WCAG 1.4.3
Automated checks often cannot decide this. Check text over photos, banners and gradients by eye or with a colour picker.
Text can be enlarged to 200 percent WCAG 1.4.4
Zoom the browser to 200 percent. Nothing should be cut off or overlap.
Content reflows at 320 pixels wide WCAG 1.4.10
Zoom to 400 percent on a desktop browser. You should not need to scroll in two directions to read.
Colour is not the only signal WCAG 1.4.1
Check errors, required fields, charts and status are also shown with text, icons or patterns.
Headings and lists describe the structure WCAG 1.3.1
Check headings form a sensible outline and that real lists and tables use proper markup.
Reading order makes sense WCAG 1.3.2
With CSS layout aside, the order content is read by a screen reader should still make sense.
Operable 9 checks
Can everyone operate the page, with a keyboard, a switch, a screen reader or a finger?
Everything works with a keyboard WCAG 2.1.1
Put the mouse away. Use Tab, Shift+Tab, Enter, Space and the arrow keys to reach and use every link, button, menu and form control.
No keyboard traps WCAG 2.1.2
Tab into and out of menus, modals, embedded players and widgets. You must always be able to leave with the keyboard.
Focus is always visible WCAG 2.4.7
Tab through the page and check you can always see which element has focus.
Focus order is logical WCAG 2.4.3
Tab order should follow the visual order and meaning of the page, including after opening dialogs and menus.
Focus is not hidden behind sticky content WCAG 2.4.11
Tab through the page with sticky headers, cookie banners or chat widgets showing. The focused item should not be fully covered.
A way to skip repeated blocks WCAG 2.4.1
On first Tab, look for a skip link, or check that landmarks and headings let people jump to the main content.
Links and buttons make sense WCAG 2.4.4
Read the link text on its own. Avoid 'click here' and 'read more' with no context.
Touch and click targets are big enough WCAG 2.5.8
Check small icons, close buttons and links in dense lists are about 24 by 24 CSS pixels or have space around them.
Moving content can be paused WCAG 2.2.2
Carousels, auto-playing video and animations lasting over 5 seconds need a pause, stop or hide control.
Understandable 5 checks
Can everyone understand the content and how to use the controls?
Form fields have clear labels and instructions WCAG 3.3.2
Check every field has a visible label, and required formats or limits are explained before the user submits.
Errors are identified and explained WCAG 3.3.1
Submit a form with mistakes. Errors should be described in text, linked to the field, and announced.
Language changes are marked up WCAG 3.1.2
Passages in another language should have their own lang attribute.
Sign-in does not rely on a cognitive test WCAG 3.3.8
Check that logging in allows paste and password managers and does not need puzzles or transcribing codes.
Robust 2 checks
Does assistive technology get the right name, role and state for everything?
Screen reader announces name, role and state WCAG 4.1.2
With VoiceOver, NVDA or similar, check custom controls such as tabs, menus and toggles announce what they are and their state.
Status messages are announced WCAG 4.1.3
Check that search results counts, success messages and loading states are announced without moving focus.
Recording the result
In a report, this list sits after the automated findings as its own section, with the status of each item and a sentence on anything found. It tells the client two things that the scan alone cannot: that a person looked, and what still needs a person. If you use Websight, the Pro report prints this list with tick boxes on every audit, and the report template guide shows where it fits.
Questions
Why do I need a manual checklist if I have an automated scanner?
Because automated tools find only part of the accessibility problems. An engine can tell that an image has no alt attribute, but not whether the alt text it has is meaningful. It cannot use a keyboard, listen to a screen reader or judge whether an error message makes sense. Those checks need a person, and this list is the set a person should do after the scan.
How long does the manual checklist take?
For a typical small site, 45 to 90 minutes for the first pass on the main templates: home, a content page, a form and any checkout or sign-in. The keyboard and zoom checks are quick; the screen reader spot check takes the longest if you are new to it.
Does completing this checklist make a site WCAG 2.2 compliant?
No. It covers the most common things people miss after an automated scan, not every success criterion, and a conformance claim needs a full evaluation by a qualified person. Use it to find and fix problems and to show a client what was checked by hand.
The other half
The checks this list leaves out, the ones a machine does well, are what the Websight Chrome extension runs for free: a scan of the page you are on, a score out of 100, every issue explained with a suggested fix. Pro, a paid upgrade with a free trial, puts both halves into one branded PDF for the client.