Skip to main content

Getting started with VoiceOver on macOS

Posted in Accessibility and Apple

An understanding of how screen readers work is an important part of the journey for anyone who works on digital products. It gives us an appreciation for the many ways people use the web, and there are two solid things you can do:

  1. Observe people who use screen readers using the web
  2. Use a screen reader yourself

The first involves some research and planning, which can be huge barriers, unless you work for an organisation that has access to a panel of volunteers, or know someone personally who uses a screen reader and doesn’t mind giving you a demo.

The second might seem daunting, but, thinking back, it only took me around an hour of fumbling to get to grips with VoiceOver on my Mac.

Open Safari

If you don’t use Safari, the temptation might be to use your preferred browser; I urge you not to do this.

While Chrome shares a common root with Safari, and it’s usable with VoiceOver, I’ve found some quirky behaviour that isn’t there in Safari. Opera, Edge, Brave, Vivaldi and all the rest piggy back on the Chromium project, so they suffer from the same downsides as Chrome.

Firefox used to be impossible to use with VoiceOver, but Mozilla began to change that. Problem is, it’s not perfect and is unlikely to improve any time soon, since Mozilla now have fewer people working on Firefox.

So if you’re looking to experience the same thing as almost all actual VoiceOver users, Safari is what you should test with.

Make the tab key useful

Highlighting all controls on a web page is really useful. It isn’t something every user will have switched on, but it makes a page more usable, and can uncover some extra issues if you’re a software tester.

Activate VoiceOver

FIrst you need to turn VoiceOver on. The default keyboard shortcut is (Command) + F5, but, unfortunately, F5 can be a bit tricky:

  • If your keyboard doesn’t have a Touch Bar, you need to use the fn (Function) key too: + fn + F5
  • If your keyboard does have a Touch Bar, getting access to the Function keys might be more difficult. In System Preferences → Keyboard → Keyboard, you need to ensure either ‘Touch Bar shows’ or ‘Press and hold Fn key to’ (or ‘Press Fn key to’ if you’re on macOS Catalina or earlier) is set to ‘F1, F2, etc. keys’. If this configuration doesn’t work for you (it doesn’t for me), it’s probably best to remap the shortcut to activate VoiceOver.

Remapping the VoiceOver shortcut

To remap the VoiceOver shortcut, head to System Preferences → Keyboard → Shortcuts → Accessibility → Turn VoiceOver on or off. I change the shortcut to + §.

Alternatively, you can forget the keyboard shortcut and navigate to System Preferences → Accessibility → VoiceOver → Enable VoiceOver any time you want to use it.

The same method you used to turn VoiceOver on will turn it off.

The VoiceOver modifier

Keyboard navigation works as normal when VoiceOver is turned on, so tabbing will jump from one interactive element (links, buttons, form inputs) to the next, and so on. But users that can’t see the screen need more than just the keyboard basics to read and navigate web content, which is where the VoiceOver modifier (VO) comes in.

The VoiceOver modifier is two keys: (Control) + (Option). By itself, VO doesn’t do anything, but if you combine it with another key or keys you access the VoiceOver commands.

It’s worth mentioning you can change the VoiceOver key to (Caps Lock) instead of (or in addition to) + in VoiceOver Utility → General → Keys to use as the VoiceOver modifier.

Commands to get started

The good news is you can get around a web page with only a handful of commands:

VO + (the right arrow key)
Go to next thing (heading, paragraph, list item, etc.)
VO + (the left arrow key)
Go to previous thing (heading, paragraph, list item, etc.)
VO + (shift) + (the down arrow key)
Go into area
VO + + (the up arrow key)
Go out of area

Getting into Safari’s web content

Since VoiceOver is a way to use your whole operating system, when you open Safari it focusses on the browser as a whole; you can navigate the toolbar, check your bookmarks, cycle through your tabs, or view the web content (VO + or to move between them).

You’re looking to dig into the web content, so you need to put VoiceOver’s focus on the web content (the focus will be here by default when you open or switch to Safari) and hit VO + + .

If you want to come out of the web content and back up to that top level, use VO + + and choose a different area.

Interacting with the web content

Once you’re in the web content, read through the page with VO + or . You can fall back on your normal keyboard behaviour for everything else:

  • (Return) to follow a link
  • or Space to press a button
  • Numbers, letters and other characters to type in a <textarea> or text <input>
  • Arrow keys and Space to choose from a group of radio buttons
  • (Tab) and Space to choose options from a group of checkboxes
  • Arrow keys and to navigate and choose from form controls like <select>

You get the idea.

Getting used to a screen reader like VoiceOver is really pretty straightforward, with a little effort, and, most importantly, it’s a great way to build empathy with users who use the web in a different way to you!

Accessibility in your inbox

I send an accessibility-centric newsletter on the last day of every month, containing:

  • A roundup of the articles I’ve posted
  • A hot pick from my archives
  • Some interesting posts from around the web

I don’t collect any data on when, where or if people open the emails I send them. Your email will only be used to send you newsletters and will never be passed on. You can unsubscribe at any time.

More posts

Here are a couple more posts for you to enjoy. If that’s not enough, have a look at the full list.

  1. Alt text for CSS generated content

    There’s an interesting feature in Safari 17.4 that allows content added with CSS to have ‘alt’ text. I’m not sure how I feel about this.

  2. The accessibility conversations you want to be having

    In most companies, accessibility conversations centre around WCAG compliance, but that’s just the start. Thinking beyond that is where you want to be!