A screen reader is assistive software that converts digital content into spoken audio or braille output. It helps people who are blind or have low vision navigate websites, apps, and documents using keyboard commands or touch gestures. Screen readers rely on accessible information, such as text, headings, labels, and image descriptions, to communicate what's on the screen.
Screen readers use information provided by websites and applications to explain what's on the screen. Here's how they work:
The screen reader identifies content: It accesses information about text, headings, links, buttons, and other elements.
The information is communicated: It reads the content aloud using a synthesized voice or sends it to a compatible braille display.
The user navigates: Keyboard shortcuts or touch gestures allow the person to move between headings, links, forms, and other content.
For example, when someone reaches a properly labeled button, the screen reader can announce its name and purpose.
Several screen readers are available, including:
JAWS: A paid screen reader for Windows.
NVDA: A free, open-source screen reader for Windows.
VoiceOver: Built into Apple devices, including Macs, iPhones, and iPads.
Narrator: Built into Windows.
TalkBack: Built into most Android devices.
A screen reader helps someone navigate and interact with digital content, while text-to-speech converts written text into spoken audio.
Screen reader | Text-to-speech | |
|---|---|---|
Main purpose | Navigate and interact with websites, apps, and documents | Listen to written text |
Navigation | Supports keyboard shortcuts and gestures | Usually focuses on reading selected content |
Output | Speech or braille | Speech |
Screen readers often use text-to-speech to communicate information, but they also provide navigation and interaction features.
Screen readers rely on accessible website content. When buttons, images, forms or other elements aren't properly labeled or structured, people using screen readers may struggle to navigate a website or complete tasks.
Common problems include:
Images without alternative text.
Form fields without clear labels.
Headings that don't follow a logical structure.
Buttons or menus that can't be used with a keyboard.
Error messages that aren't announced by screen readers.
The Web Content Accessibility Guidelines (WCAG) address many of these issues. Automated accessibility scans can identify some problems, while manual testing with a screen reader helps reveal barriers that automated tools may miss.
Assistive technology: The broader category of tools, including screen readers, that help people with disabilities use digital content.
Alternative text: The image description a screen reader announces to the user.
ARIA: Code attributes that give screen readers extra information about complex interface elements.
Braille display: A device that shows screen reader output as raised braille characters.
Are Accessibility Barriers Going Unnoticed?
Find common website accessibility issues with Clym's free Scanner.
People who are blind or have low vision primarily use screen readers. People with other disabilities may also use them, as may developers or accessibility testers evaluating how websites work with assistive technology.
Many are. VoiceOver, Narrator, and TalkBack come built into their operating systems, and NVDA is a free download for Windows. JAWS is a paid product.
You can test your website using a screen reader such as NVDA or VoiceOver. Try navigating menus, completing forms, and interacting with buttons using keyboard commands or gestures. Screen reader testing can reveal accessibility barriers that automated tools may not detect. Read more about automated vs. manual accessibility testing.
Screen readers typically rely on alternative text to describe images. Some tools can also generate image descriptions automatically. For PDFs, proper document structure and tags help screen readers interpret the content. Scanned PDFs may require text recognition before their content can be read.
First, turn on the screen reader built into your device or install one. Examples include VoiceOver on Apple devices, Narrator or NVDA on Windows, and TalkBack on Android. You then use keyboard shortcuts or touch gestures instead of a mouse to hear content read aloud and move between headings, links, buttons and form fields. Most screen readers include a tutorial or help mode for learning the basic commands.
Compliance Content Manager | CIPP/E (IAPP) | CPACC (IAAP)
Alex is a Compliance Content Manager at Clym, where he researches and writes about everything related to data privacy and web accessibility compliance for businesses, helping them stay informed on their compliance needs and spreading awareness about making the web safer and more inclusive. When he's not writing about compliance, Alex has his nose in a book or is hiking in the great outdoors.
