A screen reader’s first fifteen minutes
Nothing teaches accessibility faster than hearing your own page through a screen readerScreen readerAssistive technology that speaks the page aloud (VoiceOver, NVDA, JAWS), navigating by the semantics in the markup — the reason markup quality is something you can hear. — and nothing gets postponed harder. This sheet is the on-ramp: the handful of keystrokes that matter, and a plan for the first fifteen minutes.
Two rules before you start
Learn the stop key before anything else. Speech you can’t silence is why most first attempts end inside a minute. It’s Control — on both.
Don’t arrow through the page word by word. That’s the tourist’s walk. People who use screen readers daily pull up the list of headings and jump — WebAIM’s surveys have found heading navigation the most common way to find information for over a decade. Your job isn’t to narrate the page; it’s to check the shortcuts have somewhere to land.
VoiceOver, already on your Mac
Ships with macOS. Pair it with Safari — that’s the combination Apple builds and tests together.
- ⌘F5
- Turn VoiceOver on or off. On a Touch ID Mac, hold ⌘ and press Touch ID three times.
- Control
- Stop speech, immediately. Learn this one first.
- ControlOption
- The VO keys, held at the start of every command below — written as VO. Caps Lock works too.
- VO→
- Move to the next item; ← moves back.
- VOSpace
- Press the thing you are on.
- VOU
- Open the rotor — lists of headings, landmarks, links, and form controls. Switch lists with ← and →.
- VO⌘H
- Jump to the next heading.
- VOA
- Read continuously from here.
NVDA, free on Windows
Download it from nvaccess.org; it pairs well with both Chrome and Firefox. On web pages it runs in browse mode, which is why single letters below work as jumps — the page is treated as a document, not a text field.
- CtrlAltN
- Start NVDA.
- Control
- Stop speech — same reflex, same key.
- Insert
- The NVDA key, for commands that need it. Caps Lock can stand in if you chose that at setup.
- H
- Jump to the next heading; Shift + H goes back.
- 1–6
- Jump to the next heading of exactly that level.
- D
- Jump to the next landmark.
- K
- Jump to the next link.
- F
- Jump to the next form field.
- InsertF7
- The elements list — every heading, link, and landmark on the page in one searchable dialog.
- Insert↓
- Read continuously from here.
The phone in your pocket
In WebAIM’s tenth screen-reader survey (2024), 91.3% of screen reader users reported using one on a mobile device — the phone pass is the majority experience, not extra credit. On an iPhone: Settings → Accessibility → VoiceOver, and set the side-button triple-press shortcut while you’re there. On Android the same job is TalkBack.
- Swipe →
- Move to the next item; swipe ← moves back.
- Double-tap
- Press the item you just heard.
- Two-finger tap
- Stop speech.
- Two-finger twist
- The rotor — choose what swiping up and down steps through, headings included.
Spend the fifteen minutes like this
- Minutes 0–3, somewhere you didn’t build. Turn the screen reader on, on a page you have no stake in, and practice the stop key until it’s a reflex. You can’t think while it talks; everyone silences it constantly.
- 3–6, the outline. On your own page, pull up the heading list — the rotor on VoiceOver, the elements list on NVDA — and read only that. Does it tell the page’s story in order? That list is your page’s table of contents, and it’s often the first bug report.
- 6–9, the landmarks. Jump by landmark. Is there a main? Do repeated navs have names that tell them apart? Then press Tab once from the top of the page: does a skip link surface?
- 9–12, the controls. Tab through everything interactive. Each stop should announce a name, a role, and a state. Silence, “clickable”, or “button” with no name are your bugs. Submit a form empty: does focus land somewhere that explains what went wrong?
- 12–15, one real task. Pick the page’s main job and finish it with your eyes off the screen. Slow is fine — stuck is a finding.
What fifteen minutes doesn’t prove
It doesn’t make you a screen reader user. People who rely on this software are far faster than you’ll be today and lean on shortcuts you haven’t met — your slowness is yours, not theirs. And passing your own ear test is not the same as being accessible: this catches the loud failures. The quiet ones still need the layered model — and, eventually, feedback from people who use this software every day.
To spend the plan on a page built for it, the listening room is where you can hear all of this: eleven barriers a scanner passes over, every one of them audible before it is visible, answers included.