Skip to main content
Guide

Screen readers and your website, what owners should understand

You do not need to master every screen reader. You do need a logical heading tree, named controls, and pages that work without vision.

07/14/20261 min read

Screen readers turn the structure of a page into speech or braille. They do not "see" your layout the way a sighted user does. They jump by headings, links, buttons, and landmarks. When those are missing or fake, the page becomes a flat wall of text.

What a screen reader user does on your site

  • Skim headings to find the right section
  • Pull a list of links to jump to contact or pricing
  • Tab through interactive controls
  • Hear image alternatives and form names

Structure mistakes that hurt most

Multiple empty headings, a single giant paragraph, clickable cards with no accessible name, and carousels that never announce slide changes.

A minimal owner test

  1. Turn on VoiceOver or NVDA
  2. Navigate by headings on the homepage
  3. Open the contact form and listen to each field
  4. Activate the main call-to-action without looking at the screen

Where widgets help and do not help

A widget can increase font size or contrast for some visitors. It does not invent a heading hierarchy or name unlabeled icons for a screen reader.

Frequently asked questions

Which screen reader should I test with?
On Windows, NVDA is free and widely used. On Apple devices, VoiceOver is built in. Testing one path thoroughly beats installing five tools and learning none.
Does ARIA fix a messy page?
No. Prefer correct HTML first. ARIA helps when native elements are not enough, and wrong ARIA makes things worse.
Is PDF the same as a web page for screen readers?
No. PDFs need their own tagging. A site can be decent while linked files remain unreadable.

Sources

Related articles