Skip to main content

​
What are screen readers?

Screen readers are hardware and software technologies that parse the content of any application and read it out loud using text-to-speech. They are essential assistive technologies for users who are blind or have low vision, enabling them to navigate and interact with digital content through audio feedback and keyboard commands.

​
How screen readers work

Screen readers work by:
  1. Parsing the DOM - Reading the HTML structure and semantic elements of a web page
  2. Converting to speech - Using text-to-speech (TTS) engines to vocalize content
  3. Providing navigation - Offering keyboard shortcuts to move through content efficiently
  4. Announcing context - Informing users about element types, states, and relationships

​
Screen readers by operating system

​
Windows

NVDA is a free, open-source screen reader for Windows.
  • Download: nvaccess.org/download
  • Cost: Free
  • Best for: Developers learning accessibility, general users
  • Key features: Active community, frequent updates, highly customizable
JAWS is a commercial screen reader widely used in professional environments.
  • Download: freedomscientific.com
  • Cost: Paid (licensing required)
  • Best for: Professional users, enterprise environments
  • Key features: Extensive features, strong braille support, industry standard
Narrator is Microsoft’s built-in screen reader for Windows.

​
macOS

VoiceOver

VoiceOver is Apple’s built-in screen reader for macOS.
  • Access: Pre-installed on all Macs (Cmd + F5 or triple-press Touch ID)
  • Cost: Free (built-in)
  • Best for: macOS users, iOS development testing
  • Key features: Deep system integration, excellent with Safari

​
Linux

Orca

Orca is an open-source screen reader for Linux environments.
  • Download: orca.gnome.org
  • Cost: Free (open-source)
  • Best for: Linux users, GNOME desktop environments
  • Key features: Integrated with GNOME, supports braille displays

​
Mobile devices

TalkBack (Android)

Google’s screen reader for Android devices.
  • Access: Settings > Accessibility > TalkBack
  • Cost: Free (built-in)
  • Best for: Android app testing, mobile web testing

VoiceOver (iOS)

Apple’s screen reader for iPhone and iPad.
  • Access: Settings > Accessibility > VoiceOver
  • Cost: Free (built-in)
  • Best for: iOS app testing, mobile web testing

​
Getting started with screen readers

1

Download and install

Choose a screen reader compatible with your operating system from the options above. If you’re on Windows, start with NVDA as it’s free and widely used.
2

Learn basic commands

Familiarize yourself with essential keyboard shortcuts. Every screen reader has different commands for navigation, reading, and interaction.
3

Practice on familiar websites

Start by exploring websites you know well. This helps you understand how screen readers announce different types of content and UI elements.
4

Test your own work

Use screen readers to test your web applications. Make note of how they announce different pieces of UI and content.

​
Keyboard commands and cheat sheets

Every screen reader has different keyboard shortcuts and commands it uses to operate.
Learning screen reader commands takes time and practice. Start with basic navigation commands before moving to advanced features.

​
Essential commands to learn

While each screen reader has unique commands, most share similar functionality:
  • Start/Stop reading - Continuous reading from current position
  • Navigate by headings - Jump between heading levels
  • Navigate by landmarks - Move between page regions (header, nav, main, footer)
  • List elements - View all links, headings, or form fields
  • Read current element - Hear information about the focused item
  • Navigate by element type - Move through buttons, links, or form controls

​
Comprehensive cheat sheets

Deque University provides comprehensive keyboard command references for all major screen readers:

Screen reader cheat sheets

Access detailed keyboard shortcuts and commands for NVDA, JAWS, VoiceOver, Narrator, TalkBack, and more.

​
Best practices for testing

Test with at least two different screen readers when possible. Different screen readers may announce the same content differently.
  • Turn off your monitor - This forces you to rely entirely on audio feedback, simulating the real user experience
  • Listen for context - Notice how roles, states, and labels are announced
  • Check navigation efficiency - Can users quickly find and access key features?
  • Test forms thoroughly - Ensure all form fields have proper labels and validation messages
  • Verify error messages - Make sure error announcements are clear and actionable

​
Exercise: Explore with a screen reader

Practice exercise

Download a screen reader compatible with your operating system and explore a website of your choosing.Tasks to complete:
  • Navigate using only the keyboard and screen reader
  • Move between headings to understand page structure
  • Fill out a form and submit it
  • Follow links and return to previous pages
  • Make note of how different UI elements are announced
Questions to consider:
  • Can you easily understand the page structure?
  • Are interactive elements clearly identified?
  • Is the content announced in a logical order?
  • Can you complete tasks efficiently?

​
Additional resources

Build docs developers (and LLMs) love

Get started for freeTalk to us