Your website is shut to one in six customers — web accessibility is a market you turn away, not a checkbox you skipped

Pull up your website and it works. The buttons click, the text reads, the form submits — you have proof, because you just did it. That demonstration is also the trap. You tested it the one way you happen to use the web: a mouse, a clear screen, sharp eyes, a steady hand. A large and quiet share of the people trying to buy from you do not arrive that way. They navigate by keyboard because a mouse is not an option. They hear the page through a screen reader instead of seeing it. They need text that scales, contrast that holds, captions on the video. For them your site does not "mostly work." It is a locked door.

This is not a fringe. Roughly 1.3 billion people — about one in six of us — live with a significant disability, and the number is rising as populations age. Add the situational cases everyone meets — a cracked phone screen, glare on a sunny street, a broken wrist, a noisy room with no headphones — and accessibility stops being about a minority and starts being about whether your site holds up in the real conditions people actually use it in. Build only for the ideal user and you are building for a customer who does not exist.

This piece is about treating that as what it is: not a charity feature you add if there is budget, not a compliance panic to paper over, but a market you are turning away, a legal exposure that is now arriving on a fixed clock, and — underneath both — a build decision. Accessibility done right is structural, cheap at design time and brutal as a retrofit. Done wrong it is a widget you paste on top that fixes nothing and, increasingly, paints a target on your back.

Start with the size of who you are excluding, because it is bigger than the word "accessibility" makes it sound. The World Health Organization puts the number at about 1.3 billion people — 16 percent of the global population, one in six of us — living with a significant disability today, a figure growing as the world ages and chronic conditions rise ^[1]. That is not a niche to design around later; it is a sixth of every market you sell into. And it is not a low-value sixth: counting the friends and family whose spending it shapes, disability touches a base controlling on the order of thirteen trillion dollars in annual disposable income worldwide, with roughly 1.9 trillion controlled directly by disabled consumers ^[2]. An inaccessible checkout is not a moral lapse first — it is a sale you declined.

Now the uncomfortable mirror: almost no one is actually doing this. The annual scan of the top million home pages found that 94.8 percent had detectable accessibility failures against the standard, averaging about 51 distinct errors per page ^[3]. Read that as a market signal rather than a scold. If nineteen out of twenty of your competitors ship a site that quietly turns away a sixth of its visitors, the bar to stand out is not heroic — it is to simply not do that. Accessibility is one of the rare places where doing the basic, correct thing is still a competitive edge because so few bother.

It helps to be concrete about what "accessible" even means, because the word sounds like a feeling and it is actually a checklist. The international guidelines — the WCAG standard the laws point to — come down to a handful of plain ideas: structure your page so a machine can read it in order, make every action reachable by keyboard and not just a mouse, keep colour contrast high enough to read and let text scale without breaking, describe your images, caption your video. None of that is exotic, and here is the part operators miss: it overlaps almost completely with things you already want. The same semantic structure that a screen reader needs is the structure search and answer engines parse to understand and cite you. Accessible, fast, and findable are mostly the same build done properly.

Then there is the clock that has started ticking. In the United States, digital accessibility is now one of the most litigated corners of consumer law: more than four thousand web-accessibility lawsuits were filed in 2024, the bulk against e-commerce sites, with a heavy concentration of repeat targets ^[4]. And it is no longer only an American problem. The European Accessibility Act applies as of 28 June 2025 — exactly a year ago — and it reaches any business selling covered digital products or services into the EU regardless of where that business is based, with penalties that run into six figures ^[5]. For a Cairo or Gulf company that exports, sells cross-border, or serves EU customers online, "we are not in Europe" is no longer the shield it sounds like. The legal exposure is structural and it is spreading market to market.

Which is exactly why the most popular shortcut is the most dangerous one. The pitch is irresistible: paste one line of code, install a widget, and a layer drops over your site claiming to make it compliant automatically. It does not work, and the evidence is now blunt. Around a quarter of those 2024 US lawsuits targeted sites that already had an accessibility overlay installed ^[4] — because the overlay sits on top of the page and never fixes the broken markup underneath, so the people it claims to serve hit the same walls. Worse, installing one can demonstrate you knew accessibility was required, weakening any "we did not realise" position. The largest overlay vendor was fined a million dollars by the US trade regulator for claiming its automated tool could make any website compliant — a claim regulators found false ^[6]. The overlay is not a cheaper version of accessibility. It is a more expensive version of inaccessibility.

So where does this leave an operator who just wants to make the right call once? Treat accessibility the way you treat security and performance: a property you build into the structure from the first sketch, not a feature you bolt on when a lawyer or a customer forces it. It is cheap at design time — semantic markup, keyboard order, contrast, alt text cost almost nothing when they are how you build — and brutal as a retrofit once thousands of pages are already wrong. Name it as a requirement before the build starts, the same line in the brief as "must be fast" and "must be secure." Do that and the same work pays you three times: a sixth more of the market can actually buy, the search and answer engines understand you better, and the legal tail simply never grows. Skip it and you are not saving money — you are deferring a bill that arrives with interest, in a courtroom or in the customers who quietly left.