Screen Reader
A screen reader is assistive technology that presents digital content through synthesized speech, braille, or both.
It allows someone to navigate and interact with interfaces without relying on the visual presentation of the page.
What It Uses
Screen readers work with accessibility information provided by the browser and operating system.
That information is influenced by things such as:
- Semantic HTML
- Accessible names
- Headings
- Landmarks
- Alt text
- ARIA
- Form labels
- Interface states
A screen reader does not simply read every visible word from top to bottom.
How It Works
Users can navigate by more than individual characters or lines.
Depending on the software and interface, they may move between headings, links, landmarks, form controls, tables, or other structural elements.
That makes good page structure particularly important.
Why It Matters
A page can look completely understandable visually while providing very little usable information to a screen reader.
Poor semantics, missing labels, incorrect ARIA, or confusing document structure can turn a visually polished interface into a difficult one to navigate.
Common Problems
Common problems include:
- Controls announced without meaningful names
- Incorrect heading structure
- Missing image alternatives
- Custom components with incomplete semantics
- Dynamic content that is not communicated
- Page regions that are difficult to navigate
How to Improve
Start with semantic HTML and accessible names.
Use screen-reader testing as part of manual accessibility testing, particularly for important user flows and custom components.