Accessibility

Testing Your WordPress Site With a Screen Reader: A Beginner’s Walkthrough

Testing Your WordPress Site With a Screen Reader: A Beginner's Walkthrough

Automated accessibility checkers are useful. They find missing alt text, low colour contrast, empty links and missing form labels in seconds. But they can only detect a portion of real accessibility problems. They can’t tell you whether alt text makes sense, whether a page’s structure is logical when heard rather than seen, or whether a custom dropdown is usable without sight. Screen reader testing shows you what those tools miss.

A screen reader can. Screen readers convert what’s on the page into speech or braille, and blind and low-vision people use them to browse the web. Spending even thirty minutes listening to your own website with a screen reader is one of the most eye-opening exercises in web development. I recommend every developer and site owner try it at least once.

This guide gets you started, even if you’ve never used a screen reader before.

Which screen reader to use

The main screen readers are:

  • NVDA on Windows: free, open source and widely used. A great choice for testing.
  • JAWS on Windows: commercial and popular in workplaces. Similar to NVDA in many respects.
  • VoiceOver on macOS and iOS: built in, free and the most common screen reader on mobile in many markets.
  • TalkBack on Android: built in and important for testing on Android phones.
  • Narrator on Windows: built in, improving, but less used.

For desktop testing, NVDA with Firefox or Chrome, or VoiceOver with Safari, are good starting points. For mobile, test with VoiceOver on an iPhone or TalkBack on Android.

Getting started with NVDA

Download NVDA from its official website and install it. When it starts, it begins speaking. A few essential commands, where the NVDA key is Insert by default:

  • Ctrl: stop speaking
  • Tab: move to the next focusable element
  • Down arrow: read the next line or item
  • H: jump to the next heading
  • 1 to 6: jump to the next heading of that level
  • D: jump to the next landmark region
  • K: jump to the next link
  • F: jump to the next form field
  • NVDA + F7: open the elements list, showing all headings, links and landmarks
  • NVDA + Q: quit NVDA

NVDA has two main modes. Browse mode lets you read the page with single-letter shortcuts. Focus mode passes keystrokes to form fields, so you can type. NVDA switches automatically when you enter a form field, usually with a sound.

Getting started with VoiceOver on Mac

Press Command + F5 to turn VoiceOver on and off. The VoiceOver modifier, called VO, is Control + Option by default.

  • VO + right arrow: move to the next item
  • VO + Command + H: next heading
  • VO + U: open the rotor, a menu listing headings, links, landmarks and form controls; use left and right arrows to switch lists
  • Tab: next focusable element
  • Control: stop speaking

The rotor is the most useful tool for testing. It shows you the page the way a screen reader user often explores it, as lists of headings and links.

What to test

Don’t try to read every word of every page. Instead, focus on the structures screen reader users rely on.

Headings

Open the headings list with NVDA + F7 or the VoiceOver rotor. Screen reader users frequently navigate by headings to skim a page, just as sighted users scan visually.

Check:

  • Is there exactly one H1, describing the page?
  • Do headings follow a logical hierarchy, H2 for sections and H3 for subsections, without skipping levels?
  • Do the headings alone give a good outline of the page?
  • Is any text that looks like a heading actually just bold paragraph text? If so, it won’t appear in the list.
  • Are headings used just for visual size? Decorative text styled as H4 to make it small confuses the structure.

In WordPress, the block editor makes headings easy to set correctly, but themes sometimes use the wrong levels in headers, footers and widgets.

Landmarks

Landmarks are regions like header, navigation, main content and footer. Screen reader users jump between them. Check the landmarks list:

  • Is there a main landmark containing the page content?
  • Is the navigation marked as a navigation landmark?
  • If there are several navigation areas, do they have distinct labels, such as “Main” and “Footer”?

Block themes generate landmarks from semantic template parts, using header, main and footer elements. Classic themes vary.

Links

Open the links list. Each link should make sense out of context, because that’s how it appears in the list.

Common problems:

  • Multiple “Read more” or “Click here” links with no indication of where they go
  • Links that are just URLs, read aloud character by character
  • Icon links, like social media icons, with no accessible name, announced as “link” or the URL

Fixes include descriptive link text, visually hidden text added to “Read more” links, and aria-label on icon links.

Images

Move through the page and listen to how images are announced:

  • Informative images should have alt text that conveys their meaning.
  • Decorative images should have empty alt text, so they’re skipped.
  • Images of text should have the text as their alt.
  • Logos linking to the homepage should have alt text like “Company name home”, not “logo”.

You’ll quickly notice alt text that’s unhelpful, like “IMG_4523.jpg” or “image”, and alt text that’s too long, repeating captions that are already on the page.

Forms

Tab through each form and listen:

  • Does each field announce its label?
  • Are required fields identified?
  • Are instructions and hints announced?
  • Are radio buttons and checkboxes grouped with a legend that explains the question?
  • When you submit with errors, are the errors announced, and can you find them?

Placeholder text alone isn’t a label. Fields with only placeholders are often announced poorly or not at all once the user starts typing.

Menus and interactive widgets

Test the main navigation, dropdowns, accordions, tabs, sliders and modal dialogs:

  • Is the menu button announced as a button with its state, collapsed or expanded?
  • When a dropdown or modal opens, does the screen reader know?
  • Can you operate the widget and understand what happened?
  • When a modal closes, does focus return somewhere sensible?

Dynamic content

Content that changes without a page reload, like add-to-cart confirmations, form success messages, live search results and filter updates, should be announced. That usually requires an ARIA live region.

Add a product to the cart and listen. If nothing is announced, a screen reader user won’t know whether it worked.

Common WordPress issues I find

From screen reader testing on many WordPress sites, these issues come up most often:

  • Theme headers using H1 for the site title on every page, plus another H1 for the page title
  • Social icon links with no accessible names
  • Sliders that auto-advance and are announced constantly
  • Cookie banners that aren’t announced and can’t be dismissed easily
  • Page builder “buttons” made from divs
  • Contact forms with placeholder-only labels
  • “Read more” links repeated dozens of times on archive pages
  • Decorative images with filename alt text

Most are quick to fix once you know they’re there.

Mobile screen readers

On phones, screen reader interaction uses gestures. With VoiceOver on iPhone, swiping right moves to the next item, double tapping activates and the rotor works by twisting two fingers. TalkBack on Android uses similar gestures.

Test your mobile menu, forms and key journeys on a phone with the screen reader on. Mobile layouts sometimes hide or reorder content in ways that only cause problems with a screen reader.

Be humble about results

Using a screen reader occasionally doesn’t make you an expert user. Experienced screen reader users navigate far faster and use techniques you won’t learn in an afternoon. Your testing will find many real problems, but it won’t find everything, and some things that feel awkward to you may be fine for experienced users.

For important projects, include testing by people who use screen readers daily. Their feedback is invaluable. Screen reader testing becomes quicker and more natural every time you do it.

Frequently asked questions

Do I need to test with every screen reader?

No. Testing with one desktop screen reader and one mobile screen reader catches most issues. NVDA on Windows and VoiceOver on iPhone are a good combination.

Will screen reader testing slow my development down?

The first few sessions take time while you learn the commands. After that, a quick check of headings, links and forms on a template takes ten to fifteen minutes.

Can ARIA fix accessibility issues?

Sometimes, but native HTML elements are usually better. The first rule of ARIA is to use a native element when one exists, such as a real button instead of a div with role=”button”.

Are accessibility overlays a substitute for testing?

No. Overlays don’t fix underlying markup reliably and are criticised by many screen reader users. Testing and fixing the site itself is the dependable approach.