Accessibility testing
What accessibility means, the WCAG principles, a fast manual check anyone can do and the tools that help.
Accessibility means that people with disabilities can use a product: people who are blind and use screen readers, people who can't use a mouse, people with low vision, colour blindness, hearing loss or cognitive differences. It also helps everyone else — captions in a noisy train, big buttons on a small phone, clear text for non-native speakers. In many countries it is also a legal requirement.
WCAG in four words
The Web Content Accessibility Guidelines (WCAG) are organised around four principles. Content must be:
| Principle | Meaning | Examples |
|---|---|---|
| Perceivable | Users can see or hear it in some form | Text alternatives for images, captions, enough colour contrast |
| Operable | Users can operate it | Everything works with a keyboard, no time traps, no flashing content |
| Understandable | Users understand it | Clear labels and errors, predictable navigation, page language set |
| Robust | Works with assistive technology | Valid, semantic HTML; correct roles and names for controls |
Most teams aim for WCAG level AA, which covers the most important requirements without extreme effort.
A 15-minute manual check
- Keyboard only: unplug the mouse. Can you reach every link, button and field with Tab, see where focus is, open menus and close dialogs with Esc?
- Zoom to 200%: does the layout still work without horizontal scrolling or hidden text?
- Images: do informative images have meaningful alternative text, and decorative ones empty alt?
- Forms: does every field have a visible label? Are errors described in text, not only by red colour?
- Headings: is there one H1 and a logical heading structure?
- Contrast: is body text readable against its background (at least 4.5:1)?
- Screen reader: with NVDA (Windows), VoiceOver (macOS/iOS) or TalkBack (Android), can you complete the main task?
Common bugs
- Icon buttons with no accessible name (“button, button, button”)
- Custom dropdowns and sliders that can't be used from the keyboard
- Focus lost or trapped after opening a dialog
- Placeholder text used instead of labels
- Status messages (“Added to cart”) that screen readers never announce
- Light grey text on white
- Captcha with no accessible alternative
Tools
| Tool | Use |
|---|---|
| axe DevTools, Lighthouse | Automatic checks in the browser |
| WAVE | Visual overlay of issues on the page |
| Colour contrast analysers | Check text and background combinations |
| NVDA, VoiceOver, TalkBack | Real screen reader testing |
| axe-core / Playwright | Automated accessibility checks in CI |
Automatic tools find roughly a third of accessibility problems. The rest — whether alt text makes sense, whether the flow is understandable — needs a human.


