What your website sounds like: a visit with a screen reader

Imagine closing your eyes and having your home page read aloud to you. Not as flowing text, but the way a screen reader presents it: element by element, link by link. Many site owners hear for the first time what their website actually says. And where it says nothing at all.

Published 15 November 2026 · Libration editorial team · 9 min read
In short A screen reader doesn’t read what is on the screen. It reads what is in the code. If a name, a label or a heading is missing there, that part of the page goes silent or becomes meaningless. Screen reader users usually skim pages by their headings: two out of three survey respondents look for information that way first. The good news: the most common mistakes are small, and you can listen to your own site today, for free.

1. Who uses a screen reader

A screen reader is software that turns the content of a page into speech or sends it to a braille display. Every major operating system includes one: VoiceOver on iPhone, iPad and Mac, TalkBack on Android, Narrator on Windows. On top of that there is the free screen reader NVDA and the commercial JAWS.

The largest regular survey on the subject is run by WebAIM at Utah State University. For its eleventh round in July and August 2026, 1,780 people responded, just over a quarter of them from Europe. Some of the findings:

  • 83 per cent of respondents are blind and 18 per cent have low vision. Some also use a screen reader because of a learning disability or to listen to text while doing something else.
  • 91.8 per cent also use a screen reader on their phone, about three quarters of them on an iPhone. Your mobile layout is not a side issue.
  • In Europe, JAWS and NVDA are almost level, each named by around 42 per cent as their main desktop screen reader.
  • Only just under a third felt the web had become more accessible over the past year. Almost a quarter felt it had become worse.

The European Blind Union estimates that more than 30 million people in geographical Europe are blind or partially sighted, about one in 30 Europeans. Because sight loss becomes more common with age, that number is growing.

2. One home page, read aloud twice

Take an ordinary home page: logo, menu, a large image with the current offer, three tiles saying “Learn more” and a search box. A sighted visitor takes it in within two seconds. This is roughly how the same page sounds in a screen reader, once built without care and once with it. The announcements are simplified; each program words them slightly differently.

On screenBuilt without careBuilt with care
Logo, linked to the home page“Link, graphic, logo-final-2.png”“Link, Sunrise Bakery, home”
Menu icon with three lines“Button”“Button, Menu, collapsed”
Large image with the words “Autumn offer: 20% off all cakes”“Graphic, hero_1920x1080.jpg”“Heading level 1, Autumn offer: 20 per cent off all cakes”
Three tiles saying “Learn more”“Link, Learn more. Link, Learn more. Link, Learn more.”“Link, Our cakes. Link, Order breakfast. Link, Opening hours.”
Search box with a magnifying glass“Edit text. Button.”“Search, edit text. Button, Start search.”
“Add to basket” clicked, a small notice appears top right(nothing)“Black Forest gâteau has been added to your basket.”

Visually, both versions are identical. The difference lies entirely in the code: an alternative text here, a label there, a link that says where it goes. The left-hand column is not an extreme example. These are exactly the most common errors on the web.

3. How experienced users skim a page

Hardly anyone listens to a page from top to bottom. That would be like reading every word of a newspaper to find the sports section. Experienced users jump. Asked how they first look for information on a long page, WebAIM’s respondents said:

  • 67.8 per cent: jump from heading to heading. In NVDA, that’s the H key.
  • 12.5 per cent: use the browser’s find feature.
  • 9.7 per cent: read through the page.
  • 6.7 per cent: go through the links.
  • 3.4 per cent: jump between page regions such as navigation and main content.

88 per cent find different heading levels useful. Headings are the table of contents of your page. If they are missing, or a heading is only styled big and bold but not marked up as a heading, that table of contents is gone. According to the WebAIM Million 2026, 7.5 per cent of the most visited home pages have no headings at all, and 41.8 per cent skip levels, for example from H2 straight to H4.

A second tool is the “Skip to content” link at the very top of the page. It saves users from hearing the whole menu again on every page. 37.7 per cent of respondents use it always or often, more than five years ago.

4. Where websites go silent

For the WebAIM Million, the home pages of the one million most visited websites are tested automatically every year. In February 2026 there were 56.1 detectable errors per home page on average. These errors hit screen reader users particularly hard:

  • Image without alternative text53.1 %
  • Form field without a label51.0 %
  • Link without text46.3 %
  • Skipped heading level41.8 %
  • Button without text30.6 %
  • Page language not declared13.5 %
Share of home pages with this error. Source: WebAIM Million, February 2026, one million home pages.

Images without alternative text

When the alternative text is missing, the screen reader often reads out the file name or just says “graphic”. This is especially frustrating with linked images: according to WebAIM, 45 per cent of images without alternative text were links. Then nobody knows where the link goes. What good alternative text looks like is explained in Writing good alt text.

Links and buttons without a name

Icons without text are fashionable: a heart for the wish list, an X to close, an arrow for “next”. Sighted users understand them; the screen reader just says “button”. A row of identical links such as “Learn more” doesn’t help either, because anyone who opens the list of links hears them without context.

Form fields without a label

According to WebAIM, home pages have 6.9 form fields on average, a third of them without a proper label. Placeholder text inside the field is no substitute: it disappears as soon as you type and is not read reliably by every program. On contact, order and donation forms, this decides whether someone can finish at all.

The wrong language

If the code doesn’t say which language the page is written in, the screen reader guesses. Then a German voice may read English text, and the result is gibberish. A single attribute fixes this.

More code is not more accessibility

There is a set of attributes developers can use to give screen readers extra information, known as ARIA. Used correctly, they help, for example with expandable menus. Used wrongly, they do harm. WebAIM found 59.1 errors on average on home pages with ARIA and 42 on pages without it. That doesn’t prove ARIA causes the errors, but it shows that anyone adding a lot of ARIA also needs to test with a screen reader.

By the way: English-language home pages averaged 46.0 errors in the analysis, below the overall average. That still isn’t good.

5. What about AI?

Screen reader users are among the keenest users of AI. 60.1 per cent of respondents use AI to describe images, half of them for complex graphics too, and 40 per cent get help with online tasks. Only 8.2 per cent use AI in none of these ways.

That doesn’t mean websites can stop caring. Asked what would do more to improve web accessibility, 83.9 per cent answered: better websites, not better assistive technology. An AI can describe a photo. But it cannot know where an unnamed link leads, what an unlabelled field asks for, or that something on the page has changed after a click. That information has to be in the code.

6. Listen for yourself: the 15-minute test

You don’t need training to listen to your site once. You will be slower than someone who works with a screen reader every day. For the obvious mistakes, that’s enough.

Turn on a screen reader

  • iPhone: Settings › Accessibility › VoiceOver. Swipe right and left to move, double-tap to open. Tip: a triple tap with three fingers turns the screen dark, so you really have to rely on your ears.
  • Mac: Command and F5 turn VoiceOver on and off. Control, Option and U open the rotor, a list of all headings, links and form fields.
  • Windows: download NVDA for free. H jumps to the next heading, Tab to the next link or field, and the NVDA key plus F7 lists all elements.
  • Android: Settings › Accessibility › TalkBack.

Three tasks

  1. Hear the table of contents: open the list of headings. Does it give an understandable outline of your page?
  2. Find something: using only your ears, find your opening hours or phone number. How long does it take?
  3. Get something done: submit your contact form with a deliberate mistake. Is every field announced? Do you find out what went wrong?

Listen for three warning signs: file names instead of image descriptions, “button” with nothing after it, and long silence after a click. How to test accessibility beyond that is covered in Testing accessibility.

7. What these errors have to do with the law

Since 28 June 2025, the European Accessibility Act has applied across the EU to online shops, booking platforms and many other services for consumers. The technical benchmark is WCAG, the Web Content Accessibility Guidelines, via the European standard EN 301 549. Almost everything in this article is at the basic level A, the minimum requirements:

What you hearWCAG criterion
File name or “graphic” instead of an image description1.1.1 Non-text Content (A)
“Button” or “link” without a name2.4.4 Link Purpose (A), 4.1.2 Name, Role, Value (A)
“Edit text” without a label1.3.1 Info and Relationships (A), 3.3.2 Labels or Instructions (A)
No headings, or illogical ones1.3.1 Info and Relationships (A), 2.4.6 Headings and Labels (AA)
The whole menu first, on every page2.4.1 Bypass Blocks (A)
The whole page mispronounced3.1.1 Language of Page (A)
Silence after “Add to basket”4.1.3 Status Messages (AA)

Who the law covers and what it requires is explained in The European Accessibility Act. The individual criteria are listed in our WCAG 2.2 overview.

Scan first, then listen The website scan finds, in a few seconds, exactly the errors that go silent in a screen reader: missing alternative text, links and buttons without names, unlabelled fields, a missing language declaration. Free of charge. Afterwards you’ll know where to listen first.

Sources and notes

This article is an overview and is not legal advice.