We'd like to set Google Analytics cookies to learn how people use the Knowledge Base, so we can improve it. We set them only if you accept.

Skip to main content
Digital Accessibility Knowledge Base

Practical guides for using screen readers

If an issue entry sent you here, you're in the right place. This article explains what screen readers are and how they work, and points you to a hands-on guide for the screen reader already installed on your computer or phone. No prior experience with assistive technology is needed.

What a screen reader is?

A screen reader is software that reads what's on the screen aloud, or sends it to a braille display. People who are blind or have low vision use screen readers to operate computers and browse the web, working entirely from the keyboard on a computer, or with touch gestures on a phone, rather than with a mouse or by sight. Common screen readers include VoiceOver (built into every Mac and iPhone), NVDA and JAWS (Windows), Narrator (built into Windows), and TalkBack (Android).

How screen readers work

Screen readers don't read the pixels on the screen. They read the accessibility tree, a structured version of the page that the browser builds from your code. For each element, the tree exposes three things: its role (button, heading, link), its accessible name (the text announced for it), and its state (checked, expanded, disabled).

This is why a page can look perfect and still fail: an icon button with no accessible name looks fine on screen, but a screen reader announces it as just a "button." The visual layer and the accessibility tree are two different views of the same page, and screen reader users only get the second one.

Why testing with one matters

Automated tools like Evinced detect issues by analyzing the code, but hearing the result for yourself is the most reliable way to confirm an issue and understand its real effect on users. Ten minutes with a screen reader is usually enough to confirm or rule out a reported issue and it's the fastest way to build intuition for why these issues matter.

Pick your guide

The guides below are written for beginners: setup, staying in control, core concepts, and a scripted first test you can follow step by step.

They share the same concepts, so whichever matches your device is the right choice.

Before you start

The first minutes with a screen reader can feel disorienting, it talks fast, and it's not obvious how to make it stop. That's a normal part of learning, and each guide opens with the two or three keys or gestures that keep you in control. Expect basic comfort after one short session, not mastery; confirming issues doesn't require expert skills.