Accessibility is a business decision, not a checkbox
- 5 min read
Accessibility has one of the worst marketing departments in the history of software.
Mention it in a meeting and you’ll hear words like compliance, regulations, WCAG, lawsuits, or requirements. Nobody leans back in their chair and says, “Now that’s exciting.” Accessibility has somehow become the vegetables of product design. Everyone agrees it’s good for you, but they’re hoping someone else orders it first.
Somewhere along the way, we convinced ourselves that accessibility is something you do at the end of a project. Right after fixing the obvious bugs, updating the footer links, and changing the CEO’s profile picture because apparently that’s urgent again.
The problem is, accessibility was never supposed to be a checkbox.
It’s a business decision.
And businesses that don’t understand that usually end up paying for it anyway.
Assumptions
Every product is built on assumptions.
We assume people can see perfectly. We assume they have steady hands, a fast internet connection, perfect hearing, unlimited patience, and enough free time to decipher whatever clever interface we came up with after three design critiques and four rounds of stakeholder feedback.
It’s fascinating, really. We spend months researching users, creating personas, and mapping customer journeys, only to design for someone who barely exists.
Real people are distracted.
They’re holding a coffee while trying to pay a parking ticket. They’re standing in direct sunlight trying to read your low-contrast interface. They’re on a crowded train with one hand occupied, recovering from surgery, or simply getting older. None of these situations are unusual. They’re life.
Accessibility isn’t about designing for a minority.
It’s about admitting that the “average user” is probably the greatest work of fiction our industry has ever produced.
Revenue
Businesses love growth.
Growth teams. Growth experiments. Growth strategies. Growth dashboards. If breathing could be tracked as a KPI, somebody would eventually schedule a Growth Breathing Workshop.
Yet accessibility somehow gets labeled as a cost.
That’s like opening a new restaurant and deciding the front door only needs to work for most people. Sure, you’ve technically opened for business, but you’ve also decided that some customers simply aren’t worth the effort.
Every inaccessible interaction quietly narrows your audience. A checkout form that can’t be navigated with a keyboard. Tiny touch targets that frustrate older users. Videos without captions. Error messages that explain absolutely nothing beyond “Something went wrong.”
Who exactly benefits from those experiences?
Certainly not your customers.
And definitely not your revenue.
Companies spend millions acquiring users, then lose them because someone decided that 12-pixel light gray text on a white background looked “clean.”
Minimalism is wonderful.
Illegibility isn’t.
Experience
Here’s something designers don’t always like hearing.
Accessibility isn’t separate from user experience.
It is user experience.
Think about the last time you used a product that made you feel confident. You knew what would happen before clicking a button. Error messages actually explained the problem. Forms didn’t punish you for formatting a phone number differently than the developer expected. Navigation made sense without requiring a treasure map.
None of those things feel extraordinary.
They feel respectful.
That’s what accessibility really is: reducing unnecessary effort.
The irony is that companies often obsess over reducing friction in their sales funnel while happily adding friction everywhere else. They’ll spend six months improving a conversion rate by two percent, then ship an interface where half their users can’t read the text comfortably.
It’s a strange definition of optimization.
Culture
The biggest accessibility problem usually isn’t technical.
It’s cultural.
Ask most teams who’s responsible for accessibility and you’ll get an interesting collection of answers.
“The designers.”
“No, engineering.”
“QA should catch that.”
“Didn’t Product mention it?”
It’s amazing how quickly responsibility disappears once everyone owns it.
The best products don’t become accessible because one passionate designer fought for it. They become accessible because leadership decided it mattered before the first wireframe was ever drawn.
Culture always beats checklists.
If accessibility only enters the conversation a week before launch, you’ve already lost. At that point you’re not designing inclusively; you’re patching holes in decisions that should’ve been questioned months earlier.
Good accessibility isn’t something you sprinkle on top.
It’s baked into the way a team thinks.
Responsibility
For years, accessibility has been sold as an ethical responsibility.
And it is.
But if that’s the only argument you’re making, you’re missing an even bigger one.
It’s also a competitive advantage.
Products that are easier to use keep customers longer. They generate fewer support tickets, build stronger trust, and reach more people without spending another euro on marketing. They simply remove obstacles that never needed to exist in the first place.
The funny thing is, businesses are obsessed with solving problems.
Accessibility just happens to solve problems before customers complain about them.
That’s a remarkably efficient investment.
Conclusion
Some companies still see accessibility as insurance. Something you buy because you’re afraid of what might happen if you don’t.
The smarter companies see it differently.
They understand that every decision either widens their audience or narrows it. Every button, every form, every sentence, every interaction sends a message about who the product was designed for.
Accessibility isn’t about making products usable for some people.
It’s about making products usable, full stop.
Everything else is just paperwork pretending to be strategy.