What automated checks don't catch
Automated scanners such as axe-core, which TestingBot's scheduled scans and the tb:accessibility command use, check what can be decided from the page's code: a missing label, an image without an alt attribute, text whose colours do not have enough contrast.
Many WCAG success criteria need a person to judge them. Is the alt text accurate? Can a keyboard user finish the checkout? Does the error message say how to fix the error?
A scan without violations therefore means no automated violations were found, not that the page is accessible. Use this checklist next to your automated scans. Each item names the WCAG success criterion it relates to.
Keyboard
Put the mouse away and use only Tab, Shift+Tab, Enter, Space, the arrow keys and Esc.
- Every link, button, form field and custom control can be reached and used (2.1.1 Keyboard).
- Focus never gets stuck in a widget, an embedded video or a dialog you cannot leave (2.1.2 No Keyboard Trap).
- The order focus moves in matches the visual and reading order (2.4.3 Focus Order).
- You can always see where focus is (2.4.7 Focus Visible), and it is not hidden behind a sticky header, cookie banner or chat button (2.4.11 Focus Not Obscured, WCAG 2.2).
- Opening a dialog moves focus into it, and closing it returns focus to the control that opened it.
- A "Skip to content" link or landmarks let you bypass repeated navigation (2.4.1 Bypass Blocks).
- Single-key shortcuts can be turned off or remapped (2.1.4 Character Key Shortcuts).
Screen reader
Listen to the page with a screen reader: VoiceOver on macOS and iOS, NVDA on Windows, TalkBack on Android. You can turn these on during a TestingBot Live session, see Screen Reader Testing.
- Each control is announced with a name that matches its visible label, its role (button, link, checkbox) and its state (expanded, selected, checked) (4.1.2 Name, Role, Value; 2.5.3 Label in Name).
- Headings describe the section that follows and their levels make an outline of the page (1.3.1 Info and Relationships; 2.4.6 Headings and Labels).
- Content that appears without a page load, such as "Added to cart" or a search result count, is announced (4.1.3 Status Messages).
- The reading order makes sense when the layout is ignored (1.3.2 Meaningful Sequence).
- Link text makes sense on its own or with its sentence: no row of "Read more" links that all sound the same (2.4.4 Link Purpose).
Content and meaning
- Alt text describes what the image means in its context. A scanner only checks that the attribute exists; decorative images should have an empty
alt=""(1.1.1 Non-text Content). - Information is not given by colour alone, for example a required field shown only in red or a chart whose lines differ only in colour (1.4.1 Use of Color).
- Instructions do not rely only on shape, size or position, such as "click the round button on the right" (1.3.3 Sensory Characteristics).
- Text over images, gradients and videos has enough contrast everywhere it appears. Scanners often report these as "needs review" because they cannot measure the background (1.4.3 Contrast (Minimum)).
- Icons, focus outlines and the borders of form fields have at least 3:1 contrast against their background (1.4.11 Non-text Contrast).
- Page titles say what the page is, and pages that work the same way are named and laid out the same way (2.4.2 Page Titled; 3.2.3 Consistent Navigation; 3.2.4 Consistent Identification).
Zoom, reflow and spacing
- At 200% browser zoom no text is cut off or overlaps (1.4.4 Resize Text).
- At a 320 CSS pixel wide viewport (400% zoom on a 1280 pixel screen) the page needs no horizontal scrolling, apart from content such as tables and maps (1.4.10 Reflow).
- Increasing line height, letter and word spacing does not hide or clip text (1.4.12 Text Spacing).
- The page works in both portrait and landscape orientation (1.3.4 Orientation).
- Content that appears on hover or focus, such as tooltips, can be dismissed without moving the pointer, can be hovered itself, and stays until dismissed (1.4.13 Content on Hover or Focus).
- Touch targets are large enough or far enough apart (2.5.8 Target Size (Minimum), WCAG 2.2).
Motion, time and media
- Carousels and animations that start automatically and last more than five seconds can be paused or stopped (2.2.2 Pause, Stop, Hide).
- Nothing flashes more than three times a second (2.3.1 Three Flashes or Below Threshold).
- Session timeouts warn the user and let them extend the time (2.2.1 Timing Adjustable).
- Videos have accurate captions and audio description where needed, and audio-only content has a transcript (1.2.1 to 1.2.5). Scanners can detect a missing caption track, not wrong captions.
- Gestures such as swipes, pinches and drags have a single-pointer alternative (2.5.1 Pointer Gestures; 2.5.7 Dragging Movements, WCAG 2.2).
Forms and errors
- Errors are described in text, next to the field, and say how to fix them (3.3.1 Error Identification; 3.3.3 Error Suggestion).
- Labels and instructions are visible before the user starts typing, not only as placeholder text (3.3.2 Labels or Instructions).
- Legal, financial and data-deleting submissions can be reviewed, corrected or undone (3.3.4 Error Prevention).
- Changing a field or a select does not unexpectedly submit the form or move to another page (3.2.2 On Input).
- Users are not asked to enter the same information twice in one process, and login does not depend on a memory or puzzle test (3.3.7 Redundant Entry; 3.3.8 Accessible Authentication, WCAG 2.2).
- Personal data fields such as name, email and address have the right
autocompletevalue (1.3.5 Identify Input Purpose).
Needs review items
The report of a scheduled scan has a Needs review tab with the elements axe-core could not decide, for example text on a background image. They never fail a scan, but each one is a place where a person should look. Work through them with the checks above.