Screen Readers Explained for Website Owners
A screen reader is software that reads out what is on a screen, or sends it to a braille display. It's used mainly by people who are blind or have low vision, but also by some people with cognitive or learning disabilities. Understanding how screen readers work shows why certain accessibility practices matter.
Common screen readers
- NVDA: a free screen reader for Windows
- JAWS: a widely used commercial screen reader for Windows
- VoiceOver: built into Apple's macOS and iOS
- TalkBack: built into Android
- Narrator: built into Windows
People use different combinations of screen reader, browser, and device, so no single test covers everyone.
What a screen reader actually reads
A screen reader doesn't read the visual layout. It reads the page's underlying structure, which the browser exposes as an accessibility tree. That's why the code behind your page matters as much as how it looks.
It announces:
- Text content
- Headings, with their levels
- Links and buttons, with their names
- Form fields, with their labels
- Images, through their alt text
- Lists and tables, with counts and positions
- Landmark regions such as navigation and main content
How people navigate
People rarely listen to a whole page from top to bottom. Instead they jump around:
- By headings. Users often pull up a list of headings or skip from one to the next to scan a page. Clear, logical headings are essential. See how to use headings for SEO
- By landmarks. Jumping to navigation, main content, or footer. See skip links and landmarks
- By links and form fields. Listing links out of context means "click here" is useless. Use descriptive link text
- By tabbing through interactive elements. See keyboard navigation and focus
What breaks the experience
- Images without alt text, or with unhelpful alt text. See alt text best practices
- Buttons and links with no readable name, such as icon-only controls without labels
- Form fields without proper labels. See accessible forms
- Headings chosen for appearance rather than structure
- Popups and menus that can't be reached or closed with a keyboard. See accessible modals and popups
- Content that updates without announcement
- Unlabeled or poorly built tables. See accessible tables
- Videos without captions or transcripts. See video captions and transcripts
What helps most
- Use semantic HTML: real headings, lists, buttons, links, and landmarks
- Write meaningful text: descriptive links, clear labels, helpful alt text
- Keep a logical reading order, matching visual order
- Use ARIA only when needed, and correctly. See ARIA basics
- Test. See how to test with a screen reader
Why it benefits everyone
The same structure that serves screen readers helps search engines understand your page, and helps voice assistants, reading modes, and other tools. See website accessibility basics.
The bottom line
Screen readers depend on well-structured, clearly labeled pages. Build with proper HTML and meaningful text, and you'll serve these users and many others.