Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Screen Reader

Software that announces a page's text, headings, labels and messages to people who cannot see the screen, and reports what the page provides.
StrategytechnologyUpdated

Definition

A screen reader is software that announces a page to a person who cannot see the screen. The site's guides use the word without stopping to define it, so the sense here is the one the glossary already relies on. The alt text page says that someone with a screen reader hears an image's alternative text, because assistive technology announces an image by reading that text out. The WCAG page names people relying on a screen reader among those the guidelines serve, and files a page that works with assistive technology, screen readers among it, under the robust principle. This page restates those two and adds nothing the guides do not teach.

The standards stay with the WCAG page, and how each product behaves is a matter for its own platform's accessibility documentation. What follows is limited to what the site's guides say a screen reader does.

What it can and cannot report

The guides describe both what a screen reader carries from a page and what it drops.

It announces what the page provides:

  • Headings, which listeners use to move around the page, so a correct hierarchy helps them navigate.
  • Labels on form fields and names on buttons, and error messages written in text.
  • Alt text on images that carry meaning, while an empty alt on a decorative image tells it to skip the image.
  • Messages the page announces, such as a confirmation after the final click.
  • A close control that carries a label made for it.

It cannot report what the page leaves out:

  • Text drawn inside an image, unless the same words are also written out in the alt text or the surrounding page.
  • A message shown only visually, which leaves the listener with nothing announced.
  • A control without a label, or a custom one the screen reader announces as nothing.
  • An image with no alt attribute, which leaves a gap, and in some cases the file name is spoken instead.

In practice: forms, confirmations, headings, images and in-app messages

The accessibility guide treats a delivery-slot picker that only a mouse can use as ending the journey for anyone who relies on a keyboard or a screen reader.

The confirmation pages guide repeats the accessibility guide's note: a success message that exists only visually leaves nothing announced once the visitor has made the final click.

The headings and content structure guide says listeners move through a page by its headings, so skipped levels, empty headings and headings picked for their look break that route.

The image SEO guide covers a further gap: words inside a picture, such as a chart's labels or a banner's line, are invisible to a listener unless the alt text or the page repeats them.

The in-app messages guide asks for a close control labelled for screen readers and for messages to be tested with one on, because a message announced only as an unlabelled image fails some of its intended audience.

Illustrative example — not a real result

A tile retailer listens to its own homepage

Rovolux Tiles, an invented tile retailer, asks a marketer to listen to its homepage with a screen reader switched on. The offer line is drawn inside the hero image, so the software announces the picture and says nothing of the offer, and the 3 category buttons beneath it are read out with no names. The team puts the offer line in the page text, writes alt text that says what the picture shows and gives each button a label. They listen again the next day, hear all 3 changes and add a listening pass to the checks that run before any page change goes live.

WCAG is the reference the page is built and checked against; its robust principle is the one that asks a page to work with assistive technology such as a screen reader. Alt Text is what the software reads in place of an image, and an empty one tells it to move on. Closed captions turn a video's sound into text on screen for viewers who cannot hear it, a different need from the screen reader's, which serves viewers who cannot see the screen. A consent management platform supplies the banner a visitor can meet on the first screen, and the accessibility guide calls a banner that traps keyboard focus worse still, since a visitor who cannot dismiss it cannot use the site at all.

Common confusions

  • It is an accessibility checker. A scan tests what software can detect. A screen reader is assistive software, and judging what it announces falls to a person.
  • It shows what a visitor sees. It announces what the page provides; text inside images, visual-only messages and unlabelled controls go unannounced.
  • The keyboard check covers it. The guides list the keyboard alone and a screen reader as separate checks.
  • It concerns a separate audience. The accessibility guide counts its users as part of the ordinary audience, not a group apart.
  • Fixing it is left to developers. The accessibility guide asks for the screen reader check to be designed into briefs and templates, so the headings, link text and alt text it announces are settled before any code is written.

More terms to look up

Where this term is used

Related