A beginner's guide to testing your website with screen readers: how to turn on NVDA, VoiceOver and TalkBack, what to check and which WCAG 2.2 criteria apply.
Why test your website with a screen reader
A screen reader is a program that converts what appears on screen into speech (or into braille, with a braille display). It is used mainly by blind people or people with low vision, and it lets them move through a website by headings, links, forms or page regions without seeing it.
Automated tools detect many problems, but they do not tell you how your website “sounds”. A button may technically have a name and still be announced as “button, button” without explaining what it does. A pop-up window may open without the screen reader noticing. Listening to your website with a screen reader helps you discover this kind of barrier and understand why it matters.
The good news is that there are free screen readers, or ones built into the operating system, and a handful of keys or gestures is enough to get started. In this guide we explain which one to choose, how to turn it on, what to check and, above all, which conclusions you can draw (and which you cannot) from your own tests.
What you can check yourself and what you cannot
Before you start, it is worth setting expectations. If you do not use a screen reader every day, the way you navigate will differ from that of an expert user: slower, with fewer shortcuts and more doubts about whether a failure lies with the website or with you. The W3C Web Accessibility Initiative (WAI) takes this into account in its guidance on involving users in evaluation:
• An initial review carried out by the team itself helps to detect and fix major barriers before testing with users. And testing with users is not enough on its own either: it needs to be combined with a WCAG conformance review.
• Care is needed when drawing conclusions from limited evaluations: the results from a few people cannot be generalised.
• Sometimes the problem is not the website, but that the tester is not familiar with the browser or with the keyboard shortcuts of their assistive technology.
So treat your tests as a quick filter for spotting obvious failures, not as a verdict. They are very good for checking whether images have alternative text, whether headings reflect the structure, whether form fields announce their label or whether buttons say what they do. To assess the real experience, the W3C recommends combining a conformance review with the involvement of people with disabilities.
Which screen reader to choose
You do not need to try them all from day one. Start with the one that matches your computer and expand later. This table summarises the three easiest to get hold of to start with:
| Screen reader | Platform | Cost | How to turn it on | Base key or gesture |
|---|---|---|---|---|
| NVDA | Windows | Free and open source | Download and install it from the NV Access website | NVDA key: Insert by default |
| VoiceOver | macOS | Built into the system | Command + F5; on computers with Touch ID, hold Command and press Touch ID three times | VO key: Control + Option, or Caps Lock |
| TalkBack | Android | Built into the system | Press and hold both volume buttons for a few seconds, or go to Settings, Accessibility, TalkBack | Swipe right or left with one finger and double-tap |
A practical tip: if your audience mainly uses mobile, do not stop at desktop. And remember that the result also depends on the browser. The W3C ARIA Authoring Practices Guide advises testing with every combination of browser and assistive technology relevant to your audience, because support varies.
Getting started with NVDA on Windows
NVDA is free and open source. Once installed, it starts speaking. The first thing worth learning is how to make it stop: the Control key silences speech instantly.
Browse mode and focus mode
According to the NVDA user guide, web pages are navigated in browse mode: you move with the arrow keys as if it were a text document and you can jump between types of element with a single letter. When you enter a field to type, NVDA switches to focus mode, in which almost all keys go to the control. NVDA + Space toggles between the two modes and, if NVDA has switched to focus mode on its own, Esc takes you back to browse mode.
Quick navigation keys you will use in every test
• H: next heading; the number keys jump to headings of a specific level (1 for level 1, 2 for level 2…).
• K: next link.
• F: next form field; B: next button.
• D: next region or landmark.
• T: next table; L: next list; G: next graphic or image.
• Shift + the letter: the previous element of the same type.
• NVDA + F7: elements list (links, headings, form fields, buttons or landmarks), very useful for seeing at a glance how the page is structured.
• NVDA + Down Arrow: read everything from the current position.
If you work as a team, turn on the Speech Viewer from NVDA’s Tools menu: it shows the text NVDA is speaking in a window, which makes it easier to take notes or show the test to other people.
Getting started with VoiceOver on Mac and TalkBack on Android
VoiceOver on Mac
Turn on VoiceOver with Command + F5. Almost all of its commands are combined with the VO key, which by default is Control + Option or Caps Lock. Two commands are enough to get started:
• VO + U opens the rotor. Use the Right and Left Arrow keys to choose a category (for example, headings or links) and Up and Down to move through its items. It serves a similar purpose to NVDA’s elements list.
• VO + A reads from the current position to the end of the page.
Which categories appear in the rotor on web pages can be configured in VoiceOver Utility, in the Web Rotor tab.
TalkBack on Android
With TalkBack turned on, the touchscreen works differently, so first learn how to turn it on and off: the shortcut of pressing and holding both volume buttons for a few seconds. Then learn the basic gestures, as described in Google’s help:
• Swipe right with one finger: next item. Swipe left: previous item.
• Double-tap: activate the selected item.
• Swipe with two fingers: scroll through the page.
• Reading controls: by swiping up or down with three fingers (or, on devices without multi-finger gestures, swiping up then down with one finger) you choose how to move: by headings, links, controls, words or characters, among others.
TalkBack includes a tutorial for practising the gestures. Spend a few minutes on it before your first test: it will save you a lot of frustration.
Step-by-step test script
Choose a representative page (the home page, a service page and another with a form) and follow this route. Each step is linked to one or more success criteria of the Web Content Accessibility Guidelines (WCAG) 2.2, shown with their official names:
| Step | What you do | What should be announced | WCAG 2.2 criterion (level) |
|---|---|---|---|
| 1 | Load the page and listen to the start | A page title that describes its topic and the correct reading language | 2.4.2 Page Titled (A); 3.1.1 Language of Page (A) |
| 2 | Move through the headings (H in NVDA, rotor in VoiceOver) | Headings that summarise the content, with consistent levels | 1.3.1 Info and Relationships (A); 2.4.6 Headings and Labels (AA) |
| 3 | Jump between regions (D in NVDA) | Regions such as navigation, main content and footer | 1.3.1 (A); 2.4.1 Bypass Blocks (A) |
| 4 | Move through the images (G in NVDA) | Useful alternative text on informative images and silence on decorative ones | 1.1.1 Non-text Content (A) |
| 5 | Open the links list | Links that make sense from their text or context, with no repeated “click here” | 2.4.4 Link Purpose (In Context) (A) |
| 6 | Fill in a form and submit it with errors | Each field’s label, whether it is required and the error that has occurred | 3.3.2 Labels or Instructions (A); 3.3.1 Error Identification (A) |
| 7 | Use menus, tabs, accordions and pop-up windows | The name, role and state of each control (for example, “expanded” or “collapsed”) | 4.1.2 Name, Role, Value (A) |
| 8 | Add something to the basket, search or submit a form | Status messages (“product added”, “3 results”) without you having to look for them | 4.1.3 Status Messages (AA) |
| 9 | Read the page from start to finish and then move through it with Tab | A meaningful reading order that matches the visual one; when tabbing, a logical focus order | 1.3.2 Meaningful Sequence (A); 2.4.3 Focus Order (A) |
It will take longer at first; with practice you will get faster. Do it first with the screen visible to understand what is happening and, once you are more confident, try some tasks without looking.
How to document what you find
A poorly described failure is hard to fix. To make your notes useful for the technical team, always follow the same structure:
1. Where: the page address and the specific element (for example, “magnifying glass button in the header”).
2. With what: screen reader, browser, operating system and, if you know them, their versions.
3. What you did: the key or gesture used and the task you were trying to complete.
4. What you heard: the exact phrase the screen reader announced (NVDA’s Speech Viewer helps a lot here).
5. What you expected: what should have been announced, for example “Search button”.
6. Related criterion: the WCAG criterion that is probably not met, if you are sure of it.
If you are unsure whether a behaviour is a failure of the website or of how you are using the screen reader, note it down anyway and mark it as “to be confirmed”. It is better to review it later than to accept it as fine.
Common mistakes when starting out
These are common stumbling blocks when a team starts testing with screen readers, and how to avoid them:
• Using only the Tab key. Screen reader users do not navigate only with Tab: they jump between headings, links or regions and read the content with the arrow keys. If you only tab, you will miss the text, the images and the structure.
• Fixing everything with ARIA. The W3C ARIA Authoring Practices Guide warns that incorrect ARIA distorts the experience of screen reader users, and that ARIA roles do not provide keyboard behaviour on their own. Before adding attributes, check whether a native HTML element (a button, a link, a form label) solves the problem.
• Accepting a single combination. Something working with NVDA in one browser does not guarantee it will work with VoiceOver in another. Test at least the combinations your audience uses most.
• Mistaking your own difficulty for a failure. As the W3C points out, sometimes the problem is unfamiliarity with the assistive technology’s shortcuts. Practise before drawing conclusions.
• Replacing users. Your tests do not replace the experience of people who use screen readers every day. Use them so that you reach those tests with the obvious failures already fixed.
From first tests to a full evaluation
Testing with screen readers is one of the most effective ways for design, content and development teams to understand accessibility. But the criteria required by the regulations go far beyond what can be reviewed in a quick walkthrough. According to the W3C, the European standard EN 301 549 incorporates, for web content, WCAG 2.1 level AA as it stands, and that level covers dozens of criteria that require systematic technical and manual testing.
If you want to know precisely where your website stands, our digital accessibility audit combines automated tools and expert manual review, including navigation with screen readers. And once you have the list of failures, the accessibility remediation team can help you fix them in the code and check that they are announced as they should be.
Sources
• Web Content Accessibility Guidelines (WCAG) 2.2 (W3C) (https://www.w3.org/TR/WCAG22/)
• Involving Users in Evaluating Web Accessibility (W3C WAI) (https://www.w3.org/WAI/test-evaluate/involving-users/)
• ARIA Authoring Practices Guide: Read Me First (W3C WAI) (https://www.w3.org/WAI/ARIA/apg/practices/read-me-first/)
• European Union accessibility policies (W3C WAI) (https://www.w3.org/WAI/policies/european-union/)
• NVDA User Guide (NV Access) (https://download.nvaccess.org/documentation/userGuide.html)
• VoiceOver User Guide: getting started (Apple) (https://support.apple.com/guide/voiceover/vo4be8816d70/mac)
• Turn on TalkBack (Android Accessibility Help, Google) (https://support.google.com/accessibility/answer/6007100)
• Use TalkBack gestures (Android Accessibility Help, Google) (https://support.google.com/accessibility/android/answer/6151827)
• TalkBack menu and reading controls (Android Accessibility Help, Google) (https://support.google.com/accessibility/android/answer/6007066)