What Is a Screen Reader? Definition, Examples, Testing

What is a screen reader?

A screen reader is software that turns what is on a screen into speech or braille so that people who are blind or have low vision can use computers and phones. It reads text aloud, announces headings, links, buttons and form fields, and lets the user move around with keyboard commands or touch gestures instead of a mouse. It is one kind of assistive technology.

How a screen reader works

A screen reader does not look at pixels. It asks the browser or operating system for each element's name, role and state, then speaks them: "Subscribe, button" or "Email, edit text, required". Pages that use real HTML elements give it this information for free. Custom widgets need ARIA to supply it, which is exactly what WCAG success criterion 4.1.2 (Name, Role, Value, level A) requires.

Users rarely read a page top to bottom. According to WebAIM's screen reader guide, they jump between headings to get an outline, pull up a list of links, move by landmarks such as main and nav, and skip repeated navigation with skip links. Good structure is the interface.

Common screen readers

Who uses which: the WebAIM survey

The WebAIM Screen Reader User Survey #11 (July to August 2026, 1,780 valid responses) asked which screen reader people use most on a desktop or laptop: JAWS 55.0%, NVDA 32.9%, VoiceOver 6.5%. On mobile, respondents could pick several: VoiceOver 72.2% and TalkBack 29.5%. WebAIM notes the sample was not controlled and may not represent all screen reader users, so treat the numbers as a guide to what to test first, not as market share.

How to test with a screen reader

• Pair a reader with its usual browser. WebAIM suggests NVDA with Firefox, JAWS with Chrome, VoiceOver with Safari and Narrator with Edge.
• Use default settings and basic navigation first. That shows the baseline a typical user gets.
• Walk through the key flows: sign up, search, checkout, error messages. Listen for unnamed controls and links that make no sense out of context.
• Check headings, landmarks and keyboard navigation order before anything else; most problems are structural.
• Expect a learning curve. WebAIM warns that unfamiliarity with the tool is easily mistaken for an inaccessible page.

Common mistakes that break screen reader use

• Images without alternative text, which are skipped silently or read as a file name. See accessible images.
• Clickable div elements with no role or name, so the reader cannot say what they do.
• Links labelled "click here" or "read more", and pages with no headings.
• Form fields without labels, and errors that appear visually but are never announced.
• Content that changes after load with no announcement to the user.

Screen readers, WCAG and monitoring

Screen reader support is a core test for WCAG conformance. Automated tools cannot hear a page, so they miss many problems; they do catch regressions cheaply. LoadFocus page speed monitoring records the Lighthouse Accessibility score on every scheduled audit, which flags a drop after a release. Manual screen reader passes still decide whether the page is usable. For the bigger picture, read why performance testing should include accessibility and the best tools for website accessibility testing.

FAQ about screen readers

Is a screen reader the same as a screen magnifier?

No. A screen reader outputs speech or braille. A screen magnifier enlarges what is shown for people with low vision. Some users run both together.

Which screen reader should I test with?

Start with NVDA, which is free, and VoiceOver on a Mac or iPhone. JAWS is the most used desktop reader in the WebAIM survey, so test with it if you can. On Android, use TalkBack.

Do screen reader users use a mouse?

Mostly not. They navigate with the keyboard on a computer or with touch gestures on a phone, which is why headings, focus order and labels matter more than visual layout.

Can automated accessibility tools replace screen reader testing?

No. Automated tools find missing labels, contrast and some ARIA errors, but they cannot judge whether the spoken experience makes sense. Use them for regression checks and keep manual passes for key journeys.

Is a screen reader the same as text-to-speech?

No. Text-to-speech only reads text aloud. A screen reader also announces roles and states, lets users navigate by structure and works with controls, forms and applications.