Guide · reviewed 2026-11-03
What accessibility checks can’t an automated scanner do?
An automated scanner can tell that an image has alt text, a field has a label and a button has a name, but not whether the alt text is right, the label makes sense or the page can actually be used. A person has to check keyboard use, focus order and visible focus, how a screen reader announces the page, zoom and reflow to 400%, the meaning of alt text and link text, captions, error messages, and anything that moves or times out. The 20-minute routine below covers the essentials for one page.
What automated checks cannot judge
Tools such as axe-core, which Raasta, Lighthouse and axe DevTools all use, test rules that have a clear yes or no answer in the code. Many WCAG criteria depend on meaning or behaviour instead: whether the order makes sense, whether a description is accurate, whether a task can be finished. Those need a person.
- Keyboard use. A scanner can spot some focus problems in the code, but not whether you can open the menu, choose a size and reach checkout without a mouse.
- Focus order and visible focus. Whether focus moves in a logical order, never disappears and never lands behind a sticky header or an open dialog.
- Screen reader experience. Whether headings, landmarks, buttons and updates are announced in a way that lets someone follow the page.
- Zoom and reflow. Whether content still works at 400% zoom (a 320 CSS pixel wide view) without sideways scrolling or overlapping text.
- Meaning. Whether alt text describes the image, link text says where it goes, and labels and instructions are clear.
- Media, motion and timing. Whether videos have accurate captions, moving content can be paused, nothing flashes, and time limits can be extended.
A 20-minute routine for one page
- 1. Keyboard (5 minutes). Click the address bar, then press Tab through the whole page. Use Enter and Space on buttons and links, arrow keys in menus and Escape to close dialogs. Note anything you cannot reach, cannot use, or where focus is invisible or jumps around.
- 2. Skip link and focus after actions (2 minutes). Check that the first Tab shows a skip link, and that after opening a dialog, submitting a form or changing a filter, focus goes somewhere sensible.
- 3. Zoom and reflow (3 minutes). On a desktop browser, zoom to 200%, then 400%. Text must stay readable, nothing should overlap or be cut off, and you should only need to scroll in one direction.
- 4. Screen reader (5 minutes). Turn on VoiceOver (Cmd+F5 on a Mac) or NVDA (free on Windows). List the headings and landmarks, move through the main content, and fill in one form. Is everything announced with a sensible name and role?
- 5. Meaning (3 minutes). Read the alt text of the main images, the link and button text out of context, and the form labels. Submit a form with mistakes: does the error say what went wrong and how to fix it, next to the field?
- 6. Media and motion (2 minutes). Play a video with sound off: are captions there and accurate? Is there a pause control for carousels and animations, and does anything flash or time out without warning?
Where automated checks fit
Run an automated check first, such as Raasta’s free quick scan or live-page check, Lighthouse or WAVE, and fix what it finds. It clears the common, mechanical failures quickly, so your manual time goes on the things only a person can judge. Repeat the routine on each page type (home, listing, product or article, form, checkout), not on every page.
See the common failures and their fixes, the WCAG 2.2 guide or the accessibility statement generator.
Questions
How much of WCAG can automated tools check?
A large share of the common failures, but not all criteria, and only partly for many of them. Treat a clean automated result as a good start, not as proof the page is accessible.
Which screen reader should I test with?
Use one that real users rely on: NVDA or JAWS with Chrome or Firefox on Windows, VoiceOver with Safari on Mac and iPhone, or TalkBack on Android. Testing one well beats skimming several.
Do I need to be an expert to do this?
No. Keyboard, zoom and reading for meaning need no special skills. Screen reader testing takes some practice; WebAIM’s guide is a good place to start. For a large or regulated site, add an expert audit.
How often should I repeat the manual checks?
When you add a new page type or component, after a redesign, and before a major release. Automated monitoring can cover the checks in between.