Screen Reader Users Can't Buy From You: The Sale You Never See You Lost

A man in Brampton uses a screen reader because of low vision. He wants to book a plumber. He lands on a local trades website, tries to find the "Book Now" button, and the reader just says "clickable" with no label. He gives up and calls the next company on the search results page, the one whose site actually works with his tools.

Nobody at the plumbing company ever finds out this happened. There's no error message, no complaint, no support ticket. The visitor simply leaves, and the analytics dashboard shows a bounce like any other. This is the part of accessibility that most business owners never think about: the damage is invisible from the inside, but it's very visible from the outside, to the exact customers you're losing.

This isn't a niche audience

It's easy to file accessibility under "nice to have for a small group of people." That's a mistake. Vision impairment, colour blindness, motor difficulties, temporary injuries, ageing eyesight, and situational limits like a cracked phone screen or bright sunlight on a screen all fall under the same umbrella. Some of these are permanent, some are temporary, and some hit everyone eventually. The market that benefits from an accessible site is much larger than the market that requires assistive technology full time.

Add to that the people browsing one-handed with a toddler on the other arm, or driving and using voice commands, or sitting in a waiting room with the sound off. Good accessibility practice tends to make a site easier for all of these people, not just the ones who need a screen reader.

What actually goes wrong on most sites

We audit a lot of existing websites before we touch them, and the same handful of problems show up again and again.

• Buttons and links with no readable label, so screen readers announce "button" or "link" with nothing useful attached
• Colour contrast too low to read comfortably, especially light grey text on white backgrounds
• Forms with no proper labels, so a person using a keyboard or reader has no idea what field they're filling in
• Images with no alt text, which also means Google has no idea what the image is either
• Menus and pop-ups that trap keyboard focus, so a user tabbing through the page gets stuck and can't move forward or back

None of these are exotic problems. They're the kind of thing that happens when a site gets built fast, by whoever was cheapest, with nobody checking it against real usage. They're also the kind of thing that gets fixed quickly once someone actually looks for them.

The legal angle is real, but it's not the main point

There is a compliance side to this. Ontario has AODA requirements, and larger organisations have specific obligations under it. In the US, ADA-related web lawsuits have been rising for years. If your business serves the public, ignoring accessibility entirely does carry legal exposure, and that risk grows as your business grows.

But we'd rather talk about the upside than the threat. Treating accessibility purely as a legal liability to manage is how you end up with a bolt-on "accessibility statement" page and nothing actually fixed. Treating it as a growth lever changes how the whole project gets approached, because now you're asking "how do we let more people use this" instead of "how do we avoid getting sued."

What good accessibility actually buys you

A site built with accessibility in mind tends to load faster, because clean semantic markup is lighter than div-soup with a dozen scripts trying to fake basic functionality. It tends to rank better, because a lot of accessibility practice, like proper headings, alt text, and readable link text, overlaps directly with what search engines look for. It tends to convert better, because clearer forms and buttons help every visitor, not just the ones using assistive tools.

There's also a reputation angle that's easy to underestimate. A business that visibly works for people with disabilities gets word-of-mouth referrals from a community that talks to each other and remembers who made things easy. That's not charity, it's just how referral networks work in any tight community.

Fixing it doesn't mean rebuilding everything

Business owners often assume accessibility work means tearing down the site and starting over. Usually it doesn't. Most of the fixes are targeted: proper labels on form fields, better colour contrast in the design system, alt text written for real images instead of left blank, keyboard navigation that actually works through menus and modals, and headings that follow a logical order instead of being chosen for font size.

We run these audits using both automated tools and manual keyboard and screen reader testing, because automated scanners catch maybe half the real problems. The other half only show up when a person actually tries to use the site the way a real visitor would, tabbing through forms, listening to how a screen reader announces the navigation, checking whether a modal window can be closed without a mouse.

For a webapp or a CRM built for internal staff, the same logic applies, just with a different audience. If someone on your team has a repetitive strain injury and can't use a mouse for hours, or a new hire has colour blindness and can't tell your red and green status indicators apart, that's lost productivity you're paying for without noticing.

Where to start

If you've never had your site looked at from this angle, the honest first step is a proper audit, not a guess. We go through a site's structure, forms, navigation, and content, test it with a keyboard and a screen reader, and come back with a prioritised list. Some fixes take an afternoon. Others need to be built into the next redesign. Either way, you end up with a clear picture instead of a vague worry.

If you want that picture for your own site, get in touch through /contact or start a project at /start. We'll tell you plainly what's working, what isn't, and what it would take to fix it.