Screen readers: how a blind visitor experiences your homepage
A screen reader turns your page into speech in the structure the HTML provides. What a blind visitor hears on a typical homepage, and the fixes.
The short answer
A screen reader turns a web page into speech or braille, reading the structure and text the HTML provides in the order it provides it. It does not see the layout, the colours or the picture of the smiling team. A blind visitor arriving on a typical business homepage hears the page’s name, then navigates by jumping: through the list of headings to find the section they want, through the landmarks to reach the main content, through the links to find the contact page. When the headings are real, the images are described, the buttons are buttons and the forms are labelled, the experience is fast. When they are not, the visitor hears a stream of “link, link, image, clickable” and leaves.
What a blind visitor hears
| On the page | With good structure | With poor structure |
|---|---|---|
| Arrival | Page title, then a skip link to the main content | Page title, then every menu item, one by one, on every page |
| Hero image | A short description of what it shows, or nothing if decorative | ”Image, IMG underscore 4821 dot jpg” |
| Headline | ”Heading level one: what the company does” | Just text, indistinguishable from a paragraph |
| Menu | ”Navigation landmark, button, menu, collapsed” and it opens with Enter | ”Clickable” and nothing happens |
| Call to action | ”Link, get a quote" | "Link, click here” or “link, read more”, six times |
| Contact form | ”Edit text, your name, required" | "Edit text” with no idea what to type |
| Error after submit | Announced: “Email address: enter a valid email, for example name at company dot com” | Silence; the border turned red |
| Testimonials carousel | Paused, with controls, or a simple list | Content changing under them with no announcement |
The fixes, in order of impact
- Real headings in a real outline, so the headings list is a table of contents for the page.
- Landmarks: header, navigation, main, footer, and a skip link, so the visitor can jump to content.
- Descriptions on meaningful images, empty descriptions on decorative ones.
- Links and buttons that say what they do on their own: “Get a quote”, not “click here”.
- Real buttons and links, so they are operable and announced correctly.
- Labelled form fields, announced errors, focus moved to the first error.
- Announcements for content that changes, and no content that changes without the visitor’s action.
- Language declared, so words are pronounced correctly.
Trying it yourself
Turn on the screen reader built into your computer or phone, turn the screen off or close your eyes, and give yourself two tasks: find the phone number, and submit the contact form. Use only the keyboard on the computer, or the standard gestures on the phone. Note where you are lost. Then have the same tasks done by someone who uses a screen reader daily; their speed will show you what a well-built page makes possible.
What this means for you
A blind visitor experiences your site as its structure, and the structure is either there or it is not. Real headings, landmarks, described images, meaningful link text, real buttons, labelled forms and announced changes turn a wall of “clickable” into a page someone can use in seconds. The same fixes serve keyboard users and search engines, they are required by the accessibility standard, and on a well-built site they are the default. Try the two tasks with your eyes closed this week; it is the fastest way to understand what needs to change.
Frequently asked questions
How many of our visitors use a screen reader?
More than the raw count suggests, because they are invisible in most analytics and because the same fixes serve keyboard users, voice control users, people with cognitive impairments and search engines. Accessibility legislation applies regardless of the number. The practical answer is: enough that a site which excludes them is excluding customers and taking a legal risk.
Can we test this ourselves?
Yes. Every major operating system includes a screen reader. Turn it on, close your eyes or turn off the monitor, and try to find your phone number and submit the contact form. Ten minutes teaches more than any checklist. Then have an automated check run on every page, and a proper audit once.
Do accessibility overlay widgets fix this?
No. They add a toolbar and sometimes attempt to guess descriptions; they cannot restore missing structure, label fields that have no labels or make a menu operable. Screen reader users widely report that overlays make sites harder to use. The fixes have to be in the page.
Sources
- W3C WAI: How people with disabilities use the web (accessed 2026-09-11)