Getting Started Testing with VoiceOver

Basics of the Screen Reader

Testing screen reader accessibility is an essential step in reviewing your content. VoiceOver is a screen reader built into Mac devices that reads aloud page content and relevant semantic info (such as headings, lists, and links). Use the following guidance to get started testing with VoiceOver, and to get a more comprehensive picture of accessibility.

Browser Choice:
Screen readers work best with certain browser combinations. For VoiceOver the recommended browser is Safari.

The VoiceOver Key:
VoiceOver uses a modifier key, called the VoiceOver key (or VO), that is combined with other keys for screen reader keyboard commands. It can be set to be either the CAPS LOCK key or the CONTROL+OPTION keys together.

We'll use CAPS LOCK as our VoiceOver key, but feel free to use what key combination you prefer.

Let's Start Testing

When testing, try not to use your mouse. Instead use keyboard controls for navigation. Throughout your assessment, consider:

  • Is any content being skipped that should be read?
  • Is any content being read that's not visible?
  • Are headings, links, and buttons announced? 

Icon of a keyboard.

Turn VoiceOver on or off

Icon of a screen reader.

ON: COMMAND + F5.

OFF:  COMMAND + F5.

Note: Once VoiceOver is turned on, the behavior of your keyboard keys will change.

Change How Fast VoiceOver Talks

Using a slower speaking rate can help with comprehension as you listen during testing.

  1. Use CAPS + Shift + Command and Up or Down Arrows to open settings and adjust speaking rate faster or slower.
  2. Optional: Use Left or Right Arrows to access other speech settings such as Pitch, Volume, Intonation, Braille Table, and Voice.

Read All Content

Caps lock key.

Use CAPS + A to start reading all page content.

  • Is all content read aloud?
  • Is it read in a logical order that follows the visible page structure?
  • Do the names of items that you hear match the names you see?
  • Are images read with their alt text or skipped if decorative?

Navigate Interactive Elements

Interactive elements are things like buttons, links, and form fields. Use TAB to go forward through interactive elements. Use SHIFT + TAB to go backwards.

  • Can you navigate to all interactive elements?
  • As you tab, does the name of elements that you hear matches the name you see?

Select Links or Buttons

return key.

Use RETURN to select or activate links and buttons

  • Can you access (TAB) and activate (RETURN) these elements?
  • Does the visible name on the button match the name that you hear? Is it announced as a button?
  • Is the link text descriptive instead of vague, text like "click here" or "read more"?

Navigate with Arrow Keys

Use ARROW KEYS to navigate options or maneuver content.

  • Can you go backwards and forwards through radio buttons?
  • Can you select and then navigate down through drop-down menus?
  • Can you navigate between tab panels or tree menus?
  • Can you maneuver sliders or select options for auto-complete?

Enhance Your Testing Skills

Open the Rotor

Use CAPS + U to open the Rotor, a menu of elements such as headings, links, and landmarks. Navigate the Rotor with the arrow keys. Use the ESC key to close the rotor, if needed.

  • Are headings and links descriptive?
  • Are landmarks present, unique and being used correctly?
  • Review buttons and form fields, if any.

Testing Forms

form icon.

Uses various keyboard keys.

Check any forms on the page. Are you able to fill out the form using only your keyboard?

  • Are there correct and distinct labels for each field?
  • Can you select checkboxes via the SPACEBAR key?
  • Are you alerted to errors and/or requirements?
  • Do you receive audible confirmation when you submit the form?

Testing Dynamic Content

modal window icon.

Use various keyboard keys.

Test elements like pop-up dialog boxes and modal windows.

  • Can you tab to controls within the pop up window?
  • Can you close the window using the ESC key?
  • When you close the window and navigate away, does the focus move to a logical place?
  • Are status and alert messages announced by the screen reader?

Resources and Testing Practice