Key takeaways
- Accessibility means people with visual, hearing, motor and cognitive disabilities can use the product. The usual standard is WCAG, level AA.
- Automated tools find some problems quickly. Keyboard, screen reader and zoom checks by a person are needed for the rest.
- It's increasingly a legal requirement too: in the EU, the European Accessibility Act applies to many products and services from 28 June 2025.
Where this picks up
You've seen that accessibility is a non-functional quality that decides whether some people can use a product at all. This article is about testing it in practice.
Who you're testing for
- People who are blind or have low vision: screen readers, magnification, high contrast.
- People who are deaf or hard of hearing: captions and transcripts.
- People with motor disabilities: keyboard only, switch devices, voice control.
- People with cognitive disabilities: clear language, predictable layouts, enough time.
And many others benefit: someone with a broken arm, bright sunlight on a phone screen, a noisy train, an older user.
The standard: WCAG
The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the reference most laws and companies use. The current version is WCAG 2.2. They're organised under four principles, often remembered as POUR:
| Principle | Means | Example requirement |
|---|---|---|
| Perceivable | Users can perceive the content | Images have text alternatives; text has enough contrast |
| Operable | Users can operate the interface | Everything works with a keyboard; no keyboard traps |
| Understandable | Users can understand content and controls | Form errors are identified and explained |
| Robust | Works with assistive technologies | Elements have correct names and roles for screen readers |
Each requirement has a level: A, AA or AAA. Most organisations and regulations target AA. In the EU, the harmonised standard EN 301 549 builds on WCAG.
The checks every tester can do
Keyboard only
Put the mouse away and complete a key journey with Tab, Shift+Tab, Enter, Space and the arrow keys.
- Can you reach and use every control?
- Is the focus always visible?
- Is the order logical?
- Can you get out of every menu, dialog and widget?
Screen reader
Turn on NVDA (free, Windows), VoiceOver (macOS and iOS) or TalkBack (Android) and listen:
- Do buttons and links have meaningful names ("Add to cart", not "button" or "click here")?
- Do form fields announce their labels and errors?
- Do images have useful alternative text, and decorative ones none?
- Can you navigate by headings?
Zoom and reflow
Zoom the browser to 200%, then make the window narrow. Content should reflow without being cut off or needing horizontal scrolling for normal text.
Colour and contrast
- Normal text needs a contrast ratio of at least 4.5:1 against its background at level AA; large text at least 3:1.
- Information must never rely on colour alone: "fields in red are required" fails for colour-blind users.
Media and motion
Videos need captions; audio needs a transcript. Animations should respect the system's "reduce motion" setting.
Tools: helpful, but not enough
Automated checkers like axe, WAVE and Lighthouse find issues such as missing labels, low contrast and missing alternative text in seconds. Add them to the pipeline.
But they can't judge whether alternative text is meaningful, whether the focus order makes sense or whether a journey is usable with a screen reader. A page can pass every automated check and still be impossible to use.
Every year, the non-profit WebAIM runs automated accessibility checks on the home pages of the top one million websites.
In its 2025 report, 94.8% of home pages had detected WCAG failures, with an average of about 51 errors per page. The most common problem, low-contrast text, appeared on 79.1% of home pages.
These are only the issues an automated tool can detect. The real number of barriers is higher.
Lesson: most of these errors, like missing labels, low contrast and missing alternative text, are simple to find and fix. A few automated and manual checks in everyday testing would remove most of them.
Building it into the process
- Add accessibility to the Definition of Done for UI changes.
- Run an automated checker in the pipeline on key pages.
- Do a keyboard pass on every new screen.
- Do a screen reader pass on key journeys before major releases.
- Involve real users with disabilities for important products. They find what checklists miss.
Do
Report accessibility bugs with the user impact: "Screen reader users can't complete checkout: the Pay button has no accessible name and is announced only as 'button'."
Don't
Treat accessibility as polish for the end of the project. Fixing it then means redesigning components; building it in from the start costs far less.
Check yourself
A form shows required fields with a red border only, and a pop-up error that disappears after 3 seconds. Which accessibility problems can you spot?
Show answer
Several: information relies on colour alone (red border); the error disappears too fast for many users, including screen reader users who may not hear it at all; and it's likely not linked to the field, so assistive technology can't tell users which field is wrong. Fix: visible text like "(required)", errors that stay until fixed, announced to screen readers and connected to each field.
