Section 1
The market case: buyers you cannot count because they never get in
Inaccessible sites do not generate complaint emails; they generate silence. A visitor using a screen reader hits an unlabeled form and leaves. A buyer with low vision meets gray-on-white text and squints once, then closes the tab. An older customer, and every market is aging, fights a tiny tap target and gives up. None of this appears in analytics as anything but another bounce. The W3C's business case for accessibility documents the upside in plain commercial terms: extended market reach, stronger brand, and innovation spillover, against a global disability market of more than one billion people plus their families and friends. For a local service business, the practical math is simpler: some percentage of your addressable customers cannot currently buy from you, and your competitors are mostly just as closed. Opening the door is differentiation. For the step that usually comes next, see [The Technical Foundations of a Website That Sells: Speed, Accessibility, and Trust](/blog/technical-foundations-website-that-sells).
Section 2
The five failures that block most buyers
Accessibility sounds vast, but the damage is concentrated. WebAIM's 2026 analysis of the top one million home pages found WCAG 2 failures on 95.9% of them, averaging 56.1 detectable errors per page, and the same handful of issues dominate year after year. The table below lists the big five. Notice two things. First, every one of them also hurts buyers without disabilities: low contrast is hard to read in sunlight, unlabeled forms confuse everyone, vague link text wastes attention. Accessibility fixes are usability fixes with a legal benefit attached. Second, none requires a rebuild; most are content and markup corrections a competent developer handles in days. Run the free WAVE tool on your homepage and you will likely meet this exact list.
Section 3
The legal case: the direction of travel is one-way
On the risk side, the trendline matters more than any single statute. The Department of Justice's published guidance states plainly that the ADA's requirements apply to the websites of businesses open to the public, and points to WCAG as a helpful standard. In April 2024, the DOJ went further for the public sector, issuing a formal rule requiring state and local government websites to meet WCAG 2.1 AA on fixed deadlines. Private-sector demand letters and lawsuits over inaccessible websites have become a steady industry, typically targeting exactly the failures in the table above because automated scans find them in seconds. An operator should read this the way they read any compliance curve: standards formalize, enforcement spreads, and early movers pay less. Fixing accessibility now is cheaper than fixing it under a deadline set by someone else's lawyer. A useful companion to this piece is [AI-Generated Web Design: What It Actually Changes for Service Businesses](/blog/ai-generated-web-design-service-businesses).
Section 4
Where to start without boiling the ocean
Aim for WCAG 2.1 AA as your working standard, it is what the DOJ rule references and what most legal settlements specify. Sequence it like an operator: first, scan your five highest-traffic pages with WAVE and fix the automated findings, which catches the contrast, alt-text, and label issues that dominate WebAIM's data. Second, unplug your mouse and try to book a call on your own site using only the keyboard; whatever stops you is priority one. Third, bake the standard into your process, every new page ships accessible, so the debt stops growing. This is how ConvertOS handles it inside LeverageOS: accessibility is a build standard, not a retrofit project. If you want your exposure and opportunity assessed in one pass, a strategy call is the fast route. If you are turning this into practice, [The Discovery Call Is a Qualification Tool, Not a Pitch: How to Run It](/blog/discovery-call-as-qualification-tool) maps the adjacent system.