← QA Library
Chapter 13 / 19 · 7 min read

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:

PrincipleMeaningExamples
PerceivableUsers can see or hear it in some formText alternatives for images, captions, enough colour contrast
OperableUsers can operate itEverything works with a keyboard, no time traps, no flashing content
UnderstandableUsers understand itClear labels and errors, predictable navigation, page language set
RobustWorks with assistive technologyValid, 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

  1. 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?
  2. Zoom to 200%: does the layout still work without horizontal scrolling or hidden text?
  3. Images: do informative images have meaningful alternative text, and decorative ones empty alt?
  4. Forms: does every field have a visible label? Are errors described in text, not only by red colour?
  5. Headings: is there one H1 and a logical heading structure?
  6. Contrast: is body text readable against its background (at least 4.5:1)?
  7. 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

ToolUse
axe DevTools, LighthouseAutomatic checks in the browser
WAVEVisual overlay of issues on the page
Colour contrast analysersCheck text and background combinations
NVDA, VoiceOver, TalkBackReal screen reader testing
axe-core / PlaywrightAutomated 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.

Build accessibility in from the design stage. Fixing a finished product is much more expensive than choosing semantic HTML and readable colours from the start.