Accessibility as a Business Advantage: Compliance Isn't the Point, Revenue Is

A business owner we spoke with last year had just been threatened with an accessibility lawsuit. Nothing had come of it in the end, a demand letter, a scramble to fix a few things, a cheque to a lawyer, and everyone moved on. But the conversation that followed was telling. Their question wasn't "how do we fix this properly." It was "what's the minimum we need to do so this doesn't happen again."

That's how most businesses think about accessibility, if they think about it at all. It's a legal exposure to manage, not an opportunity to pursue. We think that's backwards, and not for sentimental reasons. It's backwards because it leaves money on the table.

The Market You're Not Counting

Every business owner can tell you their target customer's age, income bracket, and rough location. Almost none can tell you how many of those customers have a vision impairment, use a screen reader, navigate by keyboard because a motor condition makes a mouse difficult, or simply rely on captions because they're watching your video with the sound off on a train.

These aren't fringe cases. Vision changes with age, and your customer base is ageing whether you've noticed or not. Temporary impairments count too, a broken arm, a migraine, bright sunlight on a phone screen. Accessibility isn't a niche feature for a small group. It's the difference between a site that works for people under ideal conditions and one that works for people as they actually are, on a given Tuesday, with whatever they're dealing with that day.

When your site doesn't work for these visitors, they don't file a complaint. They leave. Quietly, permanently, and often for a competitor whose site happened to work. You never see that loss on a report. It just looks like a slightly lower conversion rate that nobody can quite explain.

What Poor Accessibility Actually Looks Like

It's rarely one dramatic failure. It's a collection of small frictions that compound.

Buttons that only work with a mouse click and ignore keyboard navigation entirely. Colour contrast so low that text disappears in bright light or for anyone with reduced vision. Forms with no labels, so a screen reader just announces "edit text" with no context about what's being asked. Images with no alt text, meaning a blind visitor gets no idea what's actually being shown, including the products you're trying to sell them. Videos with no captions. Popups that trap keyboard focus so a user literally cannot tab their way out.

None of these are exotic problems. They're default outcomes of building fast and not checking. Most agencies don't check, because checking takes longer than shipping, and clients rarely ask.

Why This Is Different From "Being Nice"

We want to be clear about something. This isn't a charity pitch. Accessible design tends to be better design, full stop, for everyone.

Clear contrast helps a tired user at 11pm as much as it helps someone with low vision. Logical heading structure helps search engines understand your page as much as it helps a screen reader. Larger touch targets help anyone using a phone one-handed on a crowded bus, not just someone with limited dexterity. Well-written alt text often doubles as decent SEO copy. Captions help someone in a noisy warehouse watch your product demo just as much as they help someone who's deaf.

The overlap between "accessible" and "just genuinely well built" is enormous. When we hear "the accessible version will be a slower, uglier version," that tells us the person hasn't seen it done properly.

Where This Actually Gets Fixed

Retrofitting accessibility onto a finished site is possible but painful, a bit like trying to add a wheelchair ramp after the building's already poured. It's much easier and cheaper when it's part of the build from the start.

That means:

• Semantic HTML structure, so headings, lists, and landmarks are actually marked up correctly rather than faked with styled divs
• Keyboard navigation tested properly, not assumed to work because the mouse version does
• Colour contrast checked against WCAG guidelines before a design gets signed off, not after a complaint
• Forms with real labels, clear error messages, and sensible tab order
• Alt text written with intent, describing what matters rather than stuffing keywords

This is standard practice in how we build sites and webapps at Redenn, not an upsell. It costs a bit more attention during the build. It costs a lot more time and money to bolt on afterwards, and it costs you customers indefinitely if you never do it at all.

The Legal Angle Is Real, But It's Not the Reason

Yes, accessibility lawsuits and complaints have become more common, and yes, in some jurisdictions there are real legal standards your site should meet. We handle that side of things properly. But we'd rather a client build for accessibility because it grows their business, not just because it protects them from a letter.

A business that's easy to use for a customer with low vision is usually also faster, clearer, and less frustrating for every other customer too. That's not a compliance win. That's a business advantage that your competitors, still treating this as legal paperwork, aren't bothering to capture.

A Practical Starting Point

You don't need to overhaul everything this quarter. Start by having your current site actually tested, not glanced at, tested, with a screen reader and a keyboard alone, no mouse. Most business owners who do this for the first time are visibly uncomfortable within about thirty seconds. That discomfort is useful information. It's showing you exactly what a real customer is experiencing right now.

If you want that audit done properly, or you're planning a new build and want accessibility handled from day one rather than tacked on later, get in touch through /contact or start a project at /start. It's a smaller conversation than most people expect, and it tends to pay for itself.