Screen Reader Compatibility Audit for Business Websites: A Plain-English Guide
A no-jargon walkthrough for small business owners on auditing and fixing screen reader compatibility issues that quietly block real customers from buying today.
# Screen Reader Compatibility Audit for Business Websites: A Plain-English Guide
If a customer can't read your website, they can't buy from you. That's obvious for sighted visitors, but a surprising number of small business sites are effectively invisible to anyone using a screen reader — the software that reads web pages aloud for people who are blind, have low vision, or have certain cognitive or motor conditions.
This guide is for small business owners and operators who aren't developers. It walks through what a screen reader compatibility audit is, what to check, how to run one yourself in under an hour, and what to fix first.

What a Screen Reader Actually Does (and Why You Should Care)
A screen reader takes the HTML on your page and announces it out loud, in order. The popular ones are NVDA and JAWS on Windows, VoiceOver on Mac and iPhone, and TalkBack on Android.
Users navigate by jumping between headings, links, buttons, form fields, and landmarks (like "main", "navigation", "footer"). If your site doesn't expose those things properly in the code, the user gets a confusing audio mess — or silence where a button should be.
Three reasons this matters for a small business:
- Real customers can't reach you. WebAIM's annual analysis of the top million homepages consistently finds detectable accessibility failures on the vast majority of them. That's revenue walking past your door.
- Legal exposure. Lawsuits over inaccessible business websites have been filed in every US state, and small businesses are common targets because they're easier ones.
- It overlaps with SEO. Many of the same fixes — proper headings, alt text, clear link text — also help Google understand your page. Google's guidance on creating helpful content emphasizes clear structure and meaningful labels, which is exactly what screen readers need.
The Plain-English Checklist
A full WCAG audit has hundreds of checks. You don't need to do all of them today. Start with this short list, which catches the issues that cause the worst real-world failures.
1. Page title
Every page needs a unique, descriptive . Screen readers announce it the moment a page loads.
- Bad: "Home" or "Untitled"
- Good: "Wedding Cakes & Custom Desserts — Bluebird Bakery, Austin TX"
2. Headings in order
Headings are how screen reader users skim. They press a single key to jump from heading to heading. If your "headings" are just bold text, or if you skip from H1 to H4, that navigation breaks.
- One
per page (the page's main subject). for major sections,for subsections under those.- Pick heading levels based on hierarchy, not font size.
3. Alt text on meaningful images
Every needs an alt attribute. The content depends on what the image is doing.
- Product photo of a navy hoodie:
alt="Navy cotton hoodie, front view" - Pure decoration (a background swoosh):
alt=""(intentionally empty) - A logo that's also a home link:
alt="Bluebird Bakery, home" - An infographic with numbers: describe the data, not "infographic"
If you're unsure, ask: "If I removed this image, what would the user lose?" That's your alt text.
4. Buttons that say what they do
A screen reader announces "button" plus its label. If the label is "click" or just an icon with no text, the user has no idea what the button does.
- Bad: an icon-only trash button with no aria-label
- Good: a button labeled "Remove item from cart"
- Bad: "Click here" or "Read more" (especially when six of these are on the page)
- Good: "Read our pricing guide"
5. Form labels
Every input — name, email, address, search — needs a visible label wired to the input using for and id, or by wrapping the input inside the . Placeholder text is not a label; it disappears the moment someone starts typing.
6. Link text that makes sense out of context
Screen reader users often pull up a list of every link on the page. If 12 of them all say "Learn more", that list is useless.
7. Focus order and visible focus
Press Tab on your keyboard, starting from the address bar. Watch where the highlight goes. It should travel through the page in a sensible order, and every focused element should have a clearly visible outline. If the outline is invisible or focus jumps around erratically, screen reader and keyboard users are lost.
8. Landmarks
Modern HTML has tags like , , , and . Use them. Screen readers let users jump straight to "main content," skipping the menu they've already heard ten times today.

How to Actually Run the Audit (45 Minutes, No Code)
Here's the workflow for a non-technical owner. You'll need a laptop and about an hour.
Step 1: Run an automated scan first (5 minutes)
Automated tools catch the obvious failures fast — missing alt text, missing labels, low color contrast, broken heading order. They won't catch everything, but they'll find the long pole in the tent.
Use a free site audit (you can run one with FreeSiteAudit) to get a baseline report across your pages. Save it. You'll come back to it.
Step 2: Turn on a screen reader and use your site (20 minutes)
This is the step most owners skip. It's also the one that teaches the most.
On Mac: Press Cmd + F5 to toggle VoiceOver. Run Apple's VoiceOver tutorial first if you've never tried it.
On Windows: Download NVDA (free). Start it. Press Insert + N to open the menu and toggle speech.
On iPhone: Settings → Accessibility → VoiceOver. Once on, swipe right to move forward and double-tap to activate. Set the Accessibility Shortcut so you can triple-click the side button to toggle it.
Now look away from the screen and try to do these tasks on your site using only the screen reader and the keyboard:
- Find your phone number or contact info.
- Find your most important product or service page.
- Add an item to the cart, or fill out and submit your contact form.
- Read your homepage hero section.
Note every place you get stuck, hear something confusing, or hit a dead end. Those are your real bugs.
Step 3: Cross-reference (10 minutes)
Take your notes from Step 2 and the automated report from Step 1. Anything appearing in both is top priority. Anything that only showed up in Step 2 — like a checkout flow that doesn't work without a mouse — is also top priority, even if the scanner missed it.
Step 4: Make a ranked fix list (10 minutes)
Group your issues into three buckets:
- Blocks a purchase or contact: broken forms, unreachable buttons, modal dialogs that trap focus, "Add to cart" that doesn't announce. Fix this week.
- Confuses navigation: missing headings, no landmarks, vague link text. Fix this month.
- Polish: decorative images with verbose alt text, slightly low contrast on secondary text, missing skip-link. Fix this quarter.
A Real Walkthrough: Fixing a Florist's Product Page
Let's make this concrete. Imagine a small florist site, "Petalwise."
The owner runs an audit and listens to her own product page in VoiceOver. Here's what she hears, in order:
> "Petalwise dot com. Image. Image. Image. Heading level one, Spring Bouquet. Button. Button. Twenty-five dollars. Edit text."
That's the entire experience. The problems:
- "Image. Image. Image." Three product photos with no alt text. Fix: give each a short, specific alt —
"Spring bouquet with pink peonies and white roses, top view". - "Button. Button." Two icon-only buttons (probably a heart for "save" and a share icon). Fix: add an accessible name to each —
aria-label="Save to wishlist"andaria-label="Share this bouquet". - "Twenty-five dollars." Good — price is announced. But notice it didn't say "price." Fix: place it inside semantic markup so it's clearly associated with the product.
- "Edit text." That's an unlabeled input — probably the quantity field. Fix: add a visible
tied to the input. - Missing entirely: the "Add to Cart" button. It exists visually, but in code it's a with a click handler, not a real button. Fix: change it to a real
element.After the fixes, the same page reads:
> "Petalwise. Link, home. Main. Heading level one, Spring Bouquet. Image, spring bouquet with pink peonies and white roses, top view. Button, save to wishlist. Button, share this bouquet. Price, twenty-five dollars. Quantity, edit text, one. Button, add to cart."
That's a customer who can actually buy.

Split-screen workspace showing a marketer running NVDA on a Windows laptop with the speech viewer open, listing aloud "button, button, button" for an unlabeled navigation, next to a printed audit checklist with items like "alt text", "form labels", "heading order" being ticked off with a pencil Common Mistakes Small Business Sites Make
A few patterns show up over and over. Fix these before anything else:
- Modal popups that trap or lose focus. Newsletter pop-ups, age gates, and cookie banners are the worst offenders. The popup should pull focus to itself when it opens, restore focus when it closes, and be dismissible with Escape.
- Carousels with no controls. Auto-rotating sliders are a usability disaster for everyone. Replace with a static hero if you can. If you can't, make sure it can be paused and each slide is reachable by keyboard.
- PDF-only menus, schedules, or price lists. Restaurants and clinics often post a PDF and nothing else. PDFs are frequently inaccessible. Always have an HTML version of the same information.
- Decorative icons treated as content. Tiny social media icons with
alt="facebook icon"get read aloud repeatedly. If the link text is "Facebook", the icon's alt should be empty. - Inaccessible video. Captions are mandatory for embedded product videos or testimonials. A transcript is even better.
- Color-only signals. Red text saying "out of stock" is invisible to a screen reader unless the words "out of stock" are actually there. Don't rely on color alone.
What "Done" Looks Like
You'll never reach 100% on every accessibility check on every page, and you don't need to. A good target for a small business site is:
- Every page has a unique title and an H1.
- Every image either has meaningful alt text or is explicitly marked decorative.
- Every form field has a label.
- Every button and link has a clear, unique purpose announced.
- The full purchase or contact flow can be completed using only the keyboard.
- A screen reader can read the page top to bottom without saying anything bare like "image" or "button" with no further information.
Once that's true, re-run the audit every quarter, after any major design change, and after you launch a new product page or campaign landing page. Regressions are easy to introduce when a designer adds a new section without thinking about labels.

A florist owner happily packing an online order in her shop, with her phone open to a confirmation screen reading "Order placed successfully," and a small printout taped to the wall showing a screen reader audit scoring 96/100 with green checkmarks next to "labels," "landmarks," and "focus order" The SEO Bonus
Almost every fix on this list also helps Google. Search engines parse the same HTML that screen readers do. Clear headings, descriptive link text, real button elements, alt text on images, and a logical landmark structure all feed into how well a crawler understands and ranks your content. Google's Core Web Vitals work on web.dev is complementary — together with accessibility hygiene, it covers most of what makes a small business site both findable and usable.
The time you spend making your site work for a screen reader user isn't charity time. It's the same work that helps every other visitor and the search engine that brings them to you.
Quick-Start Action Plan
If you only have an hour this week, do this:
- Run a free audit on your homepage and your top-converting page. Start here.
- Fix every missing alt text and every missing form label first. These are usually one-line changes.
- Turn on VoiceOver or NVDA and try to complete a purchase on your own site. Note every place you fail.
- Hand the audit report and your notes to whoever maintains your site, with the three-bucket priority list above.
- Re-audit in 30 days.
Accessibility isn't a one-time project; it's a hygiene practice. But the first pass — the one that catches the worst blockers — is genuinely doable in an afternoon. Most of the customers you're losing to this issue right now are losing you to a competitor whose site they can actually use. Fix that, and you get them back.
Ready to find out where your site stands? Run a free accessibility-aware site audit with FreeSiteAudit and get a prioritized report you can hand straight to your developer — or work through yourself.
Sources
- Web Content Accessibility Guidelines (WCAG) — https://www.w3.org/WAI/standards-guidelines/wcag/
- WebAIM Million annual accessibility report — https://webaim.org/projects/million/
- Google Search Central: Creating helpful, reliable, people-first content — https://developers.google.com/search/docs/fundamentals/creating-helpful-content
- web.dev Core Web Vitals — https://web.dev/articles/vitals
Check your website for free
Get an instant score and your top 3 critical issues in under 60 seconds.
Get Your Free Audit →