Reviewed October 15, 2026

How to screen reader test a Shopify product page in 30 minutes

Set up like a shopper, not a developer

Install a free screen reader, NVDA on Windows or VoiceOver on a Mac or phone, and open your best selling product page. Resist reaching for the screen. The test only teaches you something when you navigate by sound and keyboard the way a blind shopper does, using heading navigation to survey the page before linear reading, exactly as experienced users do.

Note the first minute carefully. Can you tell what store you are in, what the product is, and what it costs, in that order, without hunting? Those three facts are the page working. If the screen reader opens with a long run of navigation, announcements, and promotional banners before any product information, your page order needs work regardless of what follows.

Walk the buying path by ear

Move through headings, then links and buttons, listening for names that make sense out of context. Add to cart is clear; button, link, or a product image announced as a string of numbers is not. Choose a variant by listening: are options labeled as a group, is the selected size announced, and does the price update get spoken when the variant changes the cost?

Add the item to the cart and follow what happens. A cart drawer that opens without announcing itself strands screen reader users on a page that, to them, did nothing. Listen for a confirmation, a cart count update, and a reachable path to checkout. Every silent state change on the path is a place a real shopper gives up.

Listen for the classic failures

Unlabeled icon buttons, image links with file name alt text, sale badges announced repeatedly, review stars read as long symbol strings, and size charts trapped in images are the failures this test surfaces again and again. So are popups for email capture that grab focus without announcement and cannot be dismissed by keyboard, which end the session entirely.

Write down failures in the order a shopper meets them, with the exact announcement you heard. That transcript is a better brief for a developer or theme fix than a general statement that the page is not accessible, and it lets you verify the fix by hearing the same passage read correctly on the retest.

Fix, retest, and schedule the next pass

Most product page screen reader fixes are template level: real button labels, proper heading order, labeled variant groups, live announcements for cart changes, and text alternatives for chart images. One theme edit repairs every product at once, which makes this test the highest leverage half hour in store accessibility.

Retest the same product after fixes, then spot check a second product with different options, because variant types differ. Put the pass on a quarterly rhythm and after any theme or app change affecting the product page, and rotate which team member runs it, since fresh ears hear problems that familiarity has taught the regular tester to skip.

Frequently asked questions

Which screen reader should a Shopify merchant test with?

NVDA with Chrome or Firefox on Windows is free and widely used, and VoiceOver is built into Apple devices. Either finds the major problems. Testing with one real screen reader beats reading about ten, and testing on a phone with VoiceOver or TalkBack covers the mobile experience where most traffic now arrives.

I am sighted. Can I run this test meaningfully?

Yes, if you navigate by sound and keyboard and keep your eyes off the screen during the pass. The goal is to hear what a blind shopper hears: order, names, and announcements. Many experienced auditors are sighted. Take notes from what you heard, not what you saw, and the test stays honest.

What is the single most common product page failure?

Silent state changes: adding to cart, changing a variant, or opening a cart drawer without any announcement. The page visibly changes and audibly says nothing, so a screen reader user cannot tell anything happened. Proper live region announcements fix this class of failure across the whole template at once.

How often should I screen reader test my store?

Quarterly at minimum, and after any theme update, product page redesign, or new app that touches the buying path. The test is short and template fixes scale, so frequency is cheap. A store that tests quarterly rarely faces a large accessibility surprise; a store that never tests accumulates one.