Screen Reader
A screen reader is a software application that converts digital text and interface elements into synthesised speech or braille output. It is the primary assistive technology used by people who are blind or have low vision to navigate computers, websites, and mobile devices. Popular screen readers include JAWS, NVDA, VoiceOver (Apple), and TalkBack (Android).
§ 1 Definition
A screen reader is an assistive technology that interprets the graphical user interface of an operating system, website, or application and renders it as non-visual output through text-to-speech or a refreshable braille display. Screen readers work by accessing the accessibility tree that browsers and operating systems build from the underlying code. When web developers use proper semantic HTML, ARIA attributes, and text alternatives, the accessibility tree contains rich information that screen readers can present meaningfully. When the code is incorrect or incomplete, the screen reader either fails to announce the element or announces it in a confusing way. Testing with actual screen readers is the only reliable way to evaluate an experience, because no automated tool can simulate the sequential, audio-based navigation that screen reader users rely on.
§ 2 How screen readers interact with web content
Screen readers do not read a page visually. They parse the accessibility tree that the browser builds from the DOM and present elements sequentially: line by line, element by element. Users typically navigate via keyboard shortcuts, moving by headings (H key), landmarks (D key), links (Tab or K), form fields, tables, and lists. A screen reader user experiencing an unstructured page with missing headings, unlabeled forms, and no landmarks must listen to every word on the page to find what they need. That is exhausting and, for many users, prohibitive. Proper semantic HTML and ARIA make efficient screen reader navigation possible.
§ 3 Popular screen readers and market share
JAWS (Job Access With Speech) by Freedom Scientific is the most widely used screen reader in enterprise environments, particularly in US government and corporate settings. NVDA (NonVisual Desktop Access) is a free, open-source screen reader popular among developers and individuals. VoiceOver is built into macOS and iOS at no additional cost and is the most common screen reader on Apple devices. TalkBack is Google's built-in screen reader for Android. According to WebAIM's annual screen reader surveys, JAWS and NVDA have roughly equal desktop market share, with NVDA adoption growing. VoiceOver dominates on mobile. Each has its own behaviour, quirks, and level of HTML standard support. Testing with at least two is best practice.
§ 4 Common questions
- Q. Do I need to install a screen reader to test accessibility?
- A. Yes. You cannot evaluate screen reader accessibility with automated tools alone. NVDA is free and runs on Windows. VoiceOver is built into every Mac and iPhone at no cost. Learn the basic keystrokes (arrow keys for reading, H for headings, Tab for links) and navigate your site with your monitor turned off. That experience will teach you more about accessibility than any checklist.
- Q. Does a screen reader announce CSS content?
- A. Screen readers generally do not announce CSS-generated content (content property from ::before or ::after pseudo-elements). Do not use CSS content to convey meaning that is not present in the HTML. If the information is important, put it in the HTML and hide it visually with CSS if needed.
- Screen readers convert digital content to speech or braille for blind and low-vision users.
- They rely on the accessibility tree, which is built from semantic HTML and ARIA.
- Users navigate by headings, landmarks, links, and form fields, not by scanning visually.
- Test with real screen readers (NVDA, VoiceOver). Automated tools cannot substitute.
- CSS-generated content is invisible to most screen readers.
Atomic Glue includes screen reader testing with NVDA and VoiceOver in our QA process. We do not rely on automated checks alone. Our Web Development services ensure your site works for screen reader users. Get in touch for a testing session.
Get in touchA screen reader is a software application that converts digital text and interface elements into synthesised speech or braille output. It is the primary assistive technology used by people who are blind or have low vision to navigate computers, websites, and mobile devices. Popular screen readers include JAWS, NVDA, VoiceOver (Apple), and TalkBack (Android).
Category: Accessibility
Author: Atomic Glue Team
## Definition
A screen reader is an assistive technology that interprets the graphical user interface of an operating system, website, or application and renders it as non-visual output through text-to-speech or a refreshable braille display. Screen readers work by accessing the accessibility tree that browsers and operating systems build from the underlying code. When web developers use proper semantic HTML, ARIA attributes, and text alternatives, the accessibility tree contains rich information that screen readers can present meaningfully. When the code is incorrect or incomplete, the screen reader either fails to announce the element or announces it in a confusing way. Testing with actual screen readers is the only reliable way to evaluate an experience, because no automated tool can simulate the sequential, audio-based navigation that screen reader users rely on.
## How screen readers interact with web content
Screen readers do not read a page visually. They parse the accessibility tree that the browser builds from the DOM and present elements sequentially: line by line, element by element. Users typically navigate via keyboard shortcuts, moving by headings (H key), landmarks (D key), links (Tab or K), form fields, tables, and lists. A screen reader user experiencing an unstructured page with missing headings, unlabeled forms, and no landmarks must listen to every word on the page to find what they need. That is exhausting and, for many users, prohibitive. Proper semantic HTML and ARIA make efficient screen reader navigation possible.
## Popular screen readers and market share
JAWS (Job Access With Speech) by Freedom Scientific is the most widely used screen reader in enterprise environments, particularly in US government and corporate settings. NVDA (NonVisual Desktop Access) is a free, open-source screen reader popular among developers and individuals. VoiceOver is built into macOS and iOS at no additional cost and is the most common screen reader on Apple devices. TalkBack is Google's built-in screen reader for Android. According to WebAIM's annual screen reader surveys, JAWS and NVDA have roughly equal desktop market share, with NVDA adoption growing. VoiceOver dominates on mobile. Each has its own behaviour, quirks, and level of HTML standard support. Testing with at least two is best practice.
## Common questions
Q: Do I need to install a screen reader to test accessibility?
A: Yes. You cannot evaluate screen reader accessibility with automated tools alone. NVDA is free and runs on Windows. VoiceOver is built into every Mac and iPhone at no cost. Learn the basic keystrokes (arrow keys for reading, H for headings, Tab for links) and navigate your site with your monitor turned off. That experience will teach you more about accessibility than any checklist.
Q: Does a screen reader announce CSS content?
A: Screen readers generally do not announce CSS-generated content (content property from ::before or ::after pseudo-elements). Do not use CSS content to convey meaning that is not present in the HTML. If the information is important, put it in the HTML and hide it visually with CSS if needed.
## Key takeaways
- Screen readers convert digital content to speech or braille for blind and low-vision users.
- They rely on the accessibility tree, which is built from semantic HTML and ARIA.
- Users navigate by headings, landmarks, links, and form fields, not by scanning visually.
- Test with real screen readers (NVDA, VoiceOver). Automated tools cannot substitute.
- CSS-generated content is invisible to most screen readers.
## Related entries
- [ARIA](atomicglue.co/glossary/aria)
- [Semantic HTML](atomicglue.co/glossary/semantic-html-website-development)
- [Heading Hierarchy](atomicglue.co/glossary/heading-hierarchy)
- [Landmark Elements](atomicglue.co/glossary/landmark-elements)
- [Accessible Forms](atomicglue.co/glossary/accessible-forms)
Last updated July 2026. Permalink: atomicglue.co/glossary/screen-reader