The Letter That Ruins a Tuesday
The owner of a boutique furniture retailer opens a certified letter she almost didn't sign for. It cites the Americans with Disabilities Act. It says a customer using a screen reader couldn't complete a purchase on her site. It threatens litigation. It gives her 30 days.
She calls her web developer, the same guy who built the site three years ago and has kept it running fine ever since. His answer: "We don't really do that."
Now she's Googling "ADA website compliance" at 11 p.m., and the search results are a mess of contradictory blog posts, vendors selling "ADA certification" badges, and legal disclaimers. She wants one straight answer: what does she actually have to do?
Here it is.
There Is No Website ADA Law — And That's the Problem
The ADA was signed in 1990. Title III of the ADA bars discrimination in "places of public accommodation" — think restaurants, retail stores, hotels, theaters. It was written for physical space, decades before most businesses had a website at all.
Because of that timing, the ADA itself contains no technical standard for websites. No section says "your site must have alt text" or "your buttons must be keyboard-operable." That gap is exactly why so much confusing content exists online — people are trying to answer a legal question with a technical spec that, on paper, doesn't exist.
But "no explicit standard" doesn't mean "no risk" and it doesn't mean "no expectation." It means the standard got established a different way: through enforcement outcomes rather than a published rule.
So What's the Actual Benchmark? WCAG 2.1 Level AA
The Department of Justice has never issued a formal Title III regulation spelling out a website technical standard for private businesses. But it doesn't need to, in practice, because two other things have done the job:
- DOJ's own long-standing guidance, reaffirmed over time, points businesses toward the Web Content Accessibility Guidelines (WCAG) as the way to meet Title III's nondiscrimination requirement online.
- The great majority of settlements and court decisions in private ADA website lawsuits land on the same answer: WCAG 2.1 Level AA.
Put those together and you get a de facto standard. Not a law with that exact wording — a pattern so consistent that treating it as the standard is the only defensible business decision. If you conform to WCAG 2.1 AA (and increasingly, WCAG 2.2 AA, the current version), you're aligned with what regulators, plaintiffs' attorneys, and judges have converged on. If you don't, you're gambling on a technicality that hasn't held up well for other businesses.
WCAG 2.1 AA isn't vague. It's a published set of testable success criteria, things like:
- 1.1.1 Non-text Content — images need meaningful alternative text (not the "IMG_04821.jpg" scenario)
- 1.4.3 Contrast (Minimum) — text needs a 4.5:1 contrast ratio against its background (3:1 for large text)
- 2.1.1 Keyboard — every interactive element (menus, forms, the "Add to Cart" button) must be operable without a mouse
- 2.4.7 Focus Visible — keyboard users need to see where they are on the page
- 4.1.2 Name, Role, Value — custom widgets need to expose their state to assistive technology, like screen readers
The furniture retailer's checkout problem was likely a 2.1.1 or 4.1.2 failure: a screen reader user hit a form element or button that either couldn't be reached by keyboard or didn't announce what it was. That's not a vague "accessibility vibe" issue — it's a specific, fixable, testable failure against a specific criterion.
One Case Where "Guidance" Is Now a Hard Rule
There's an important carve-out worth knowing, because it's often where the confusion starts. For state and local government entities, this is no longer just informal guidance — it's a binding federal rule.
DOJ's April 2024 Title II final rule requires state and local government websites and mobile apps to conform to WCAG 2.1 Level AA, with hard deadlines:
- April 24, 2026 for entities serving populations of 50,000 or more
- April 26, 2027 for smaller entities and special districts
If you run a city, county, school district, or other public-sector site, that deadline isn't a suggestion — it's a compliance date with legal teeth attached. Private businesses like the furniture retailer aren't covered by this specific rule (that's Title II, for government; her exposure is Title III, for public accommodations), but the rule is a strong signal about where enforcement is headed generally, and it locks in WCAG 2.1 AA as the standard beyond any doubt for one whole category of website.
What "ADA Compliant" Does NOT Mean
This is the part vendors love to skip over: there is no government "ADA compliant" certification, seal, or checkbox. No federal agency issues a certificate of compliance for a website. None.
So when a plugin or overlay vendor tells you they'll make your site "certified ADA compliant" for a flat fee, be skeptical. What they're usually selling is:
- A widget that adjusts font size, contrast, or adds an accessibility menu — cosmetic layers that don't fix underlying code problems
- A badge or seal with no legal standing whatsoever
- A false sense of "we handled it" that leaves the actual WCAG failures — broken keyboard traps, missing form labels, unlabeled buttons — untouched
Buying a badge doesn't buy you a legal safe harbor. If a screen reader still can't complete checkout, the badge on the corner of the screen won't matter to a court.
Where the Real Legal Exposure Comes From
For private businesses, exposure comes from two directions:
- DOJ enforcement action — historically rare against individual private businesses, but not impossible, and DOJ's guidance clearly signals its expectations.
- Private civil lawsuits under Title III — far more common in practice, and frequently resolved through settlement rather than going to trial. This is almost certainly the track the furniture retailer's letter is on.
Separately, if you sell products or services to the federal government, Section 508 — an older, distinct law applying to federal agencies and federal contractors — uses a standard aligned with WCAG 2.0/2.1 AA. If a VPAT (Voluntary Product Accessibility Template) has ever come up in a sales conversation, that's Section 508 territory, not Title III.
What Actually Fixes This
There's no one-time fix, because websites change constantly — new pages, new checkout flows, new marketing widgets, all capable of introducing new failures. Practical compliance looks like an ongoing program, not a single sprint:
- Conform to WCAG 2.1 AA (moving toward 2.2 AA) across the whole site — not just the homepage
- Get a real technical audit, not just an automated scanner scan (automated tools catch roughly a third of issues; the rest need human testing with a keyboard and a screen reader)
- Publish an accessibility statement documenting your commitment and how users can report barriers
- Prepare a VPAT if you sell to government or enterprise buyers who require one
- Remediate continuously — every redesign, every new plugin, every marketing landing page needs the same scrutiny as the original build
The Straight Answer
"Is my website ADA compliant?" doesn't have a checkbox answer, and anyone selling you one is selling you a marketing label, not a legal outcome. The real answer is a spectrum: how closely does your site conform to WCAG 2.1 AA, documented and maintained over time?
That's a genuinely hard thing to get exactly right — the criteria are specific, the interactions between them are subtle, and "close enough" is exactly the gap plaintiffs' attorneys and DOJ guidance both point to. It's also exactly the work we do for clients every day: real audits against real WCAG success criteria, real remediation, and an ongoing program so a redesign six months from now doesn't undo the work.
If a letter like that one just landed on your desk — or you'd rather never receive one — talk to WCAG.World now. We'll tell you exactly where your site stands and what it takes to close the gap.