A screen reader is assistive technology that converts digital content into synthetic speech or braille output. Blind and low-vision users rely on screen readers to use websites, applications and documents. NVDA, JAWS, VoiceOver and TalkBack are the most common examples. Whether a site works well with a screen reader depends on correct HTML structure and text alternatives.
A screen reader reads the accessibility tree of a page through the operating system's accessibility interface and converts the content into speech or braille. Instead of scanning the page visually, the user navigates between headings, links and form fields with keyboard shortcuts, for example jumping to the next heading with a single key. NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android are the most widely used screen readers. NVDA is free and open source; VoiceOver and TalkBack are built into their operating systems.
How well a screen reader can present a page depends entirely on how the page is coded. A meaningful heading hierarchy, correctly labeled form fields, alt texts and, where needed, ARIA attributes define the experience. Elements built only with div and span that look like buttons but carry no semantic information can be invisible or meaningless to a screen reader. The most instructive test for a site owner is to try the site with a screen reader personally, using only the keyboard for critical flows such as sign-up or checkout. Automated scans report missing labels and structural issues; fixes belong in the source code. Combining an automated scan with a short manual test gives remediation a concrete starting point.
Frequently asked questions
What are the most widely used screen readers?
On Windows, NVDA (free, open source) and JAWS (commercial) are the most common pair. VoiceOver ships built into Apple devices and TalkBack into Android devices. For testing, NVDA is usually the recommended starting point: it is free, easy to install and gives a picture close to real user experience. The mobile experience should additionally be tested with VoiceOver or TalkBack.
How do I know if my site works with a screen reader?
Combine two methods. First run an automated scan: missing alt texts, unlabeled form fields and heading structure problems are listed quickly. Then do a short manual test: with NVDA running, navigate your site using only the keyboard, try to complete critical flows and listen to whether the announced content makes sense. Together they give a realistic picture of compatibility.
This content is for information only and is not legal advice.