Accessibility
WCAG 2.2 & ADA: Does Your Small Business Website Need to Be Accessible?
Yes — and the legal exposure isn’t limited to large companies. Federal courts have repeatedly ruled that business websites count as places of public accommodation under the ADA, and WCAG 2.1 Level AA is the standard courts and demand letters reference. Building to WCAG 2.2 AA is the smarter target, since it’s backward-compatible with 2.1 and covers where enforcement is heading next.
A small retail-shop owner gets a demand letter: her site’s color contrast is too low for a screen reader user, fix it in thirty days or face a federal claim. Eight employees. Site built by a freelancer years ago and never touched since. That’s not a hypothetical — it’s the exact shape of thousands of real cases filed every year, and small businesses aren’t the exception. They’re increasingly the target, precisely because they tend to have more gaps and smaller legal budgets than the retailers everyone assumes get sued instead.
The numbers most small business owners haven’t seen
This isn’t a fringe risk. Federal website-accessibility lawsuits hit 3,117 filings in 2025 — a 27% jump from 2,452 the year before, according to Seyfarth Shaw’s litigation tracking. And the target profile isn’t who most owners picture:
E-commerce and retail account for roughly 70% of filings, food and beverage another 21% — so if you run a shop, restaurant, or online store, this is squarely aimed at businesses like yours, not just national chains.
What WCAG actually asks for
WCAG (Web Content Accessibility Guidelines) is published by the W3C and organised around four principles: content has to be perceivable, operable, understandable, and robust — POUR, for short. WCAG 2.1 Level AA is the version consistently cited in settlement agreements and consent decrees today. WCAG 2.2, published in October 2023, adds nine further success criteria, mostly around cognitive accessibility and touch-target sizing.
The practical guidance is simple: treat 2.1 AA as your legal floor and 2.2 AA as your actual target. Because 2.2 is backward-compatible, building to it gives you full coverage of the standard courts reference with no downside.
Does the ADA legally require this for a private business?
The ADA doesn’t mention websites by name — it was written in 1990. But multiple federal courts have filled that gap through case law. The 9th Circuit’s ruling in Robles v. Domino’s Pizza established that a business’s website falls under Title III as a place of public accommodation. A circuit split exists — the 11th Circuit ruled differently in Gil v. Winn-Dixie — which is part of why the legal picture feels murky. What isn’t murky: plaintiffs keep filing, and WCAG 2.1 AA keeps showing up as the reference standard regardless of which circuit a case lands in.
Separately, the DOJ’s Title II rule requires state and local government websites to meet WCAG 2.1 AA, with compliance deadlines recently extended to April 2027-2028 for larger and smaller public entities. That rule applies to government sites, not private business directly — but it reinforces WCAG 2.1 AA as the standard regulators and courts keep converging on.
If you sell to customers in the EU
Worth flagging for any business trading internationally, not just US-based ones: the European Accessibility Act applies to businesses selling products or services to EU customers, and it references WCAG 2.1 Level AA as its technical standard too. If your website reaches European buyers, this isn’t a US-only conversation.
Why fixing it now costs less than fixing it after a lawsuit
| Typical cost | |
|---|---|
| Professional manual accessibility audit | $2,500-$10,000 |
| Settlement + legal defense after a claim | $60,000-$200,000+ |
| Fashion Nova’s 2025 web accessibility settlement | $5.15 million |
One widely-used shortcut is worth naming directly: accessibility overlay widgets that promise a one-line fix. They can mask some issues visually, but they don’t touch your underlying code, and several overlay vendors have themselves been named in lawsuits for failing to deliver genuine accessibility. A real fix touches your actual HTML — semantic structure, contrast, keyboard navigation, form labels — not a script layered on top.
The market you’re accidentally excluding
Set the legal risk aside for a moment and there’s a plainer business case: an estimated 26% of US adults live with a disability. An inaccessible site isn’t just a legal liability — it’s a quarter of your potential customers hitting a barrier before they can even read your pricing page.
The most common failures on real websites
Across the sites that get flagged, a small handful of issues keep showing up: text with too little contrast against its background, images with no alt text describing what they show, form fields with no proper label attached, buttons or links with no accessible name, interactive elements that can’t be reached or operated with a keyboard alone, and pages missing a declared language attribute. None of these require a redesign to fix — they’re implementation details, not visual overhauls, which is exactly why they’re so often overlooked rather than genuinely hard to solve.
Where to start
- Run an automated scan first — it won’t catch everything, but it flags the obvious gaps fast.
- Fix color contrast and missing alt text — the two most common failures on real sites.
- Check every interactive element works with a keyboard alone, no mouse.
- Label every form field properly, not just with a placeholder.
- Get a manual audit before you rely on an automated tool’s “all clear.”
This is exactly what our accessibility service covers — a real audit against WCAG 2.2 AA, structural fixes to your actual code, not an overlay bolted on top. It pairs naturally with a full technical SEO audit, since clean semantic markup tends to help both at once.
Not sure where your site currently stands?
I’ll tell you honestly how exposed your site is and what it actually takes to fix it — no scare tactics, just a real answer.
Start a projectFrequently asked questions
Is website accessibility legally required for small businesses?
The ADA doesn’t name websites explicitly, but multiple federal courts, including the 9th Circuit in Robles v. Domino’s Pizza, have ruled that a business’s website counts as a place of public accommodation under Title III. In practice, this means small business websites face real legal exposure, and WCAG 2.1 Level AA is the standard courts and settlement agreements consistently reference.
What’s the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2, published by the W3C in October 2023, adds nine additional success criteria on top of 2.1, mostly around cognitive accessibility and touch-target size. It’s backward-compatible, so meeting WCAG 2.2 AA automatically satisfies WCAG 2.1 AA, the version most legal standards still reference directly.
Do accessibility overlay widgets actually protect my business?
A one-line overlay script can mask some issues visually but doesn’t fix the underlying code, and several have themselves been the subject of lawsuits for failing to deliver genuine accessibility. Structural fixes to your actual HTML, semantic markup, contrast and keyboard navigation are what hold up in a real audit or a courtroom.
Does the European Accessibility Act affect my website?
If you sell products or services to customers in the EU, the European Accessibility Act applies and references WCAG 2.1 Level AA as its technical standard, similar to the US legal landscape. This matters for any small business trading internationally, not just companies physically based in Europe.
How much does it cost to make a website accessible?
A professional manual accessibility audit typically runs $2,500-$10,000 depending on site size, with remediation cost on top depending on how many issues are found. That’s consistently far less than the $60,000-$200,000+ in settlement and legal defense costs reported for businesses that get sued after ignoring it.