Screen reader

What is a screen reader?

A screen reader is assistive technology that converts the text, images, and interface elements on a computer screen into speech or braille output. It lets blind and visually impaired users navigate websites and other digital content using keyboard commands instead of a mouse. Screen readers run on desktop and mobile devices, reading on-screen content aloud or sending it to a refreshable braille display.

Why is a screen reader important when it comes to accessibility?

Millions of people rely on screen readers to access digital content every day. For blind and visually impaired users, there's no way to see the screen directly, so a screen reader is often the only way to read a web page, fill out a form, open a document, or use an app. That access breaks down without properly coded pages.

Screen readers also open up education and employment to people with visual impairments who'd otherwise be shut out of digital tools. Laws like the ADA and Section 508 require a large proportion of websites and workplace software to work with assistive technology, making screen reader compatibility a question of compliance as well as accessibility.

People with limited vision, low vision, or certain cognitive disabilities often use screen readers alongside magnification or a browser's built-in accessibility settings, so the benefit reaches a wider group than blind users alone.

How does a screen reader work?

A screen reader sits on top of your computer's operating system and listens for what's happening on screen.

When you open an app or a web page, the operating system builds an accessibility tree: a structured map of every button, heading, image, and form label on the page.

The screen reader reads that tree instead of reading pixels, which means that a page needs properly coded headings and alt text for the screen reader to be able to read it.

You control a screen reader almost entirely through keyboard commands, as the computer's cursor and the mouse aren't part of the workflow. You send commands to jump between headings, links, and form fields, or to move line by line through a document.

As you move, the screen reader speaks the focused item aloud, whether that's a paragraph, a heading, a button label, or an image's alt text. Some screen readers can send that same text to a refreshable braille display instead of, or alongside, speech output.

Behind the voice is a speech synthesizer, a software program that turns text into spoken audio at an adjustable speed and pitch.

Screen readers also offer more advanced functions beyond reading top to bottom: you can jump straight to a heading, skip to a table, have the software spell out a word flagged by a spell checker, or read only the highlighted text on a page.

Mobile screen readers on Android devices and Apple products use touch gestures instead of a keyboard, and swiping and tapping replace most keyboard commands.

An example of how you can use a screen reader

Picture a screen reader user filling out a signup form on a website. They press Tab to move to the first field, and the screen reader announces "Email address, edit text" because the field has a form label tied to the input. If a developer skipped that label, the screen reader would only announce "edit text," leaving the user to guess what to type.

Popular screen readers

Here are the screen readers users will be most familiar with:

• NVDA (NonVisual Desktop Access) – A free, open-source screen reader for Windows computers, popular because it's actively maintained and costs nothing.
• JAWS (Job Access With Speech) – A long-standing desktop screen reader for Windows, common in workplaces that need advanced functions such as scripting for specific software programs.
• VoiceOver – Built into every Apple product, including Mac, iPhone, iPad, and Apple Watch, with no separate download required.
• TalkBack – Google's screen reader for Android devices, built into the operating system.
• Narrator – Microsoft's screen reader bundled with Windows computers, useful for quick tasks though less full-featured than NVDA or JAWS.

Each works differently, but all of them read the same underlying accessibility tree, so a web page built with clean markup and alt text usually works across different screen readers. However, there are some key differences, so don’t assume a screen reader will give you exactly the same output as another.

Screen reader vs. screen magnifier

A screen reader and a screen magnifier both help people with visual impairments, but they solve different problems.

Some users combine both tools, magnifying part of the screen while letting the screen reader handle anything too small or too far off-screen to see comfortably.

Common mistakes or misconceptions

• One screen reader is not the same as another. NVDA, JAWS, VoiceOver, and TalkBack interpret ARIA attributes and custom components differently, so a page that works with one may fail silently with another. Screen reader testing across different combinations of browser and screen reader catches issues a single test misses.
• Visual order and reading order aren't the same thing. A screen reader reads content in the order it appears in the underlying HTML, not the order it appears on screen. CSS positioning that reorders elements visually can leave the reading order scrambled even when the page looks fine.
• Screen readers aren't only for blind users. People with low vision, certain cognitive disabilities, dyslexia, and some motor impairments use screen readers too, often paired with magnification or other accessibility settings.
• Decorative images still need attention. An image that adds nothing to the content should get an empty alt attribute, not a missing one, or the screen reader announces the filename instead of staying silent.