Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 38 ยท Testing Tools and Audits

Testing with Screen Readers

Learn the basics of testing with NVDA, VoiceOver, JAWS and TalkBack: starting up, essential commands, a test script, and how to read what you hear.

A screen reader reads the page aloud (or to a braille display) using the accessibility tree, not the pixels. Testing with one is the only way to hear what your markup really says. It feels strange at first, but a few commands are enough to do useful tests. You do not have to become an expert user; you are checking that names, roles, states and order make sense.

Experienced screen reader users navigate far faster and differently than a developer doing a spot check. Use your own testing to catch obvious problems, and involve disabled users in research for real usability feedback.

Which screen reader and browser

Screen reader Platform Cost Pair with
NVDA Windows Free Firefox or Chrome
JAWS Windows Paid Chrome or Edge
Narrator Windows Built in Edge
VoiceOver macOS, iOS Built in Safari
TalkBack Android Built in Chrome
Orca Linux Free Firefox

The WebAIM survey of screen reader users has regularly shown JAWS and NVDA as the most used on desktop, and VoiceOver and TalkBack on mobile. A sensible minimum test set: NVDA with Firefox or Chrome, VoiceOver with Safari on a Mac or iPhone, and TalkBack when you have an Android app or mobile site.

Support differs between combinations, so a pattern that works in one may not in another. Prefer native HTML to reduce that variation.

Turning them on

  • NVDA: install, press Ctrl+Alt+N. Stop speech with Ctrl. Quit with NVDA+Q. The NVDA key is Insert or Caps Lock.
  • VoiceOver on Mac: Cmd+F5. The VO key is Ctrl+Option. In Safari, enable "Press Tab to highlight each item" for normal tabbing.
  • VoiceOver on iPhone: Settings > Accessibility > VoiceOver. Swipe right/left to move, double-tap to activate.
  • TalkBack: Settings > Accessibility > TalkBack, with the same swipe/double-tap idea.

Tip: turn on a speech viewer (NVDA: Tools > Speech Viewer; VoiceOver: Caption Panel) so you see the text, and lower the speech rate until you are comfortable.

Essential commands (NVDA and VoiceOver)

Task NVDA VoiceOver (Mac)
Read next / previous item Down / Up arrow VO+Right / VO+Left
Read all from here NVDA+Down VO+A
Next heading H (Shift+H back) VO+Cmd+H
Next landmark D VO+U, rotor
Next link, button, form field K, B, F Rotor (VO+U), choose type
List of elements NVDA+F7 Rotor (VO+U)
Next interactive element Tab Tab
Stop speech Ctrl Ctrl

NVDA "browse mode" uses single letters (H for headings) when you are in page text, and switches to "focus mode" inside form fields so typing works. Notice the mode sounds.

A simple test script

  1. Page title and language: load the page; does it announce a meaningful title? Is pronunciation right (a wrong lang makes English text sound foreign)?
  2. Headings: list headings (NVDA+F7 or H key). Do they outline the page?
  3. Landmarks: jump with D. Are main, nav and others present, and labeled when repeated?
  4. Links and buttons: listen to the link list. Does each link make sense alone? Are there "click here" or "read more" lists?
  5. Images: arrow through content. Are meaningful images described and decorative ones skipped?
  6. Forms: tab through each field. Does it say the label, type, required state and hint? Submit with errors: are errors announced?
  7. Widgets: operate tabs, accordions, menus and dialogs. Is the state announced ("collapsed", "selected")? Does focus move correctly?
  8. Dynamic updates: trigger status messages and loading states. Are they announced politely?
  9. Tables: arrow into a data table; does it announce headers as you move across cells?

Reading what you hear

A well-built control announces name, role, state, value. For a checkbox: "Subscribe to newsletter, checkbox, not checked". For a collapsed menu button: "Products, button, collapsed". When you hear only "button" or "link", the name is missing. When you hear "clickable", you probably have a div with an event handler and no role.

The demo below deliberately mixes good and bad markup. Use a screen reader (or the DevTools accessibility tree) to compare what each control announces.

Good and bad accessible names

Mobile screen readers

On phones, touch exploration replaces keyboard navigation. Check that touch targets are big enough, that swipe order matches reading order, that custom gestures have simple alternatives (single tap), and that headings and landmarks are reachable from the rotor (iOS) or reading controls (Android).

Common mistakes in testing

  • Testing only with the mouse and the screen reader at the same time; the mouse hides problems.
  • Assuming a pass in one screen reader means a pass everywhere.
  • Using ARIA to patch what native HTML would do right.
  • Not testing the unhappy paths: errors, empty states, timeouts.
  • Skipping language: a Spanish quote inside an English page needs lang="es" on that element.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a screen reader read from?

    Browsers expose names, roles, states and values through the accessibility tree, and screen readers read that.
  2. 2. Which NVDA key jumps to the next heading in browse mode?

    H moves to the next heading, D to the next landmark, K to the next link and F to the next form field.
  3. 3. A screen reader announces only 'button' for an icon control. What is missing?

    An icon-only button needs a name, for example from aria-label or visually hidden text.
  4. 4. Which pairing is a sensible minimum for desktop testing?

    NVDA is free and widely used on Windows; VoiceOver with Safari covers Apple devices.

Summary

  • Screen readers use the accessibility tree: check name, role, state and value.
  • Test with at least NVDA (Windows) and VoiceOver (Apple); add TalkBack for mobile.
  • Learn a few commands: headings, landmarks, links, form fields, element lists.
  • Follow a script that covers title, structure, links, images, forms, widgets and updates.

Next: Accessibility Laws and Standards