Does my website need to be ADA compliant?
Every vendor selling compliance has a scarier answer than the law does. Here is what the ADA actually says about your website and the work that settles it.
Does my website need to be ADA compliant?
The ADA applies to your website.
And no official government checklist exists for a private business website to pass.
Those two sentences are the whole answer, and almost nobody selling compliance will give you both.
The Department of Justice has said for years that the ADA covers the goods and services a business offers through the web.
It has never published a technical standard for private business websites. It said so in writing in its 2022 guidance.
Instead it points businesses to WCAG, the international web accessibility standard, as helpful guidance.
So the real question is not whether the law can reach your website. It can.
The real question is what standard your site is built to, because the government names one without requiring it.
Search the question and the ads answer it before the law does.
Compliance vendors earn their living on the scary version, so the scary version is the one your search results serve first.
The scary version sells a deadline you do not have and a certificate that does not exist.
The rest of this article is the version with sources, written so you can check every claim yourself.
This article is not legal advice. A question about your own situation belongs with a lawyer.
What the ADA actually says about websites
The ADA is a civil rights law from 1990 that bans discrimination against people with disabilities.
It reaches organizations through two of its titles, and only one of them is yours.
Title II covers state and local governments. Think city hall and the county permit office.
Title III covers businesses open to the public, and a company that serves homeowners sits squarely under it.
The DOJ’s position is that the ADA’s requirements apply to everything such a business offers, including what it offers through the web.
For private businesses it has published guidance rather than a regulation. No rule tells your plumbing company which technical boxes to check. There is no permit to pull and no inspection to schedule.
The guidance points to WCAG as a helpful guide instead. That word helpful is doing quiet work, because guidance is not a mandate.
Courts still lean on WCAG when they weigh these cases, because it is the only detailed bar anyone has written down.
Here is who each rule binds and what it names:
| The rule | Who it binds | Named standard | Where you stand |
|---|---|---|---|
| ADA Title III | businesses open to the public | no standard named | your row |
| Title II web rule | state and local governments | WCAG 2.1 AA | not your row |
| Federal agency rule | federal government technology | WCAG | not your row |
| WCAG itself | binds no one on its own | it is the yardstick | how sites get measured |
Read the last column of that table first. The one row that binds your business names no standard at all.
That gap is not a loophole. It is the reason this law gets enforced against businesses through private lawsuits instead of inspections.
A government inspector never shows up to grade your website. A plaintiff’s firm with a scanner does.
The deadlines you may have heard about
There are real government deadlines in circulation, and none of them are yours.
In 2024 the DOJ finalized a web accessibility rule under Title II.
It requires state and local governments to bring websites and mobile apps to WCAG 2.1 AA.
The dates land in two waves:
| Deadline | Who must comply | Your business |
|---|---|---|
| April 26 2027 | governments serving larger populations | not on this clock |
| April 26 2028 | smaller governments and special districts | not on this clock |
The dates have already moved once. A federal interim rule published in April 2026 pushed each deadline back a year.
If a salesperson quotes you an older date, they are working from a version of the rule that no longer exists.
Your business is not on that clock, because the rule does not cover private businesses at all.
The rule still matters to you for one reason. It is the clearest statement yet of what the government considers an accessible website, and the bar it picked is WCAG AA.
That tells you which standard a serious builder should already be working to.
WCAG is the checklist everyone actually uses
WCAG stands for Web Content Accessibility Guidelines, the testable standard written by the W3C, the body that writes web standards.
It is not a law. It is the checklist the ADA never gave you, which is exactly why everyone from the DOJ to the courts leans on it.
The current version is WCAG 2.2. The W3C’s current edition of it is dated December 12 2024.
The W3C states that content meeting WCAG 2.2 also meets WCAG 2.1 and WCAG 2.0. Build to the newest version and the older bars come with it.
Every requirement in WCAG sits at one of three levels, and the levels tell you how strict the bar gets.
- Level A: the floor, the bare minimum for basic access
- Level AA: the level courts and regulators reference, and it includes all of A
- Level AAA: the strictest, and not even the W3C expects entire sites to reach it
When someone says accessible website in a legal context, they almost always mean WCAG AA.
That is the phrase to use when you talk to a builder, because it names a testable bar instead of a feeling.
One more thing WCAG is not: certifiable. The W3C certifies nobody and no government agency certifies websites either.
There is no such thing as an ADA certificate, and anyone selling one is selling paper.
The lawsuits are real
Website accessibility litigation is a volume business.
UsableNet, a firm that tracks these cases, counted 4,928 web accessibility lawsuits filed against businesses in 2025.
That count covers federal courts plus the New York and California state courts the tracker follows.
None of this is a reason to panic. It is a reason to know what your site is actually built to before someone else checks for you.
The businesses that handle this calmly are the ones who asked the question before a complaint made them ask it.
Here is the honest part every vendor skips. Nothing stops a lawsuit from being filed. Anyone can sue anyone, and no build changes that.
What a real accessibility build changes is the merits.
Accessibility lawsuits cite specific barriers, like an unlabeled form or a checkout that keyboard users cannot reach.
A build that removes those barriers removes the material a complaint is made of.
That is the difference between a weak claim against you and an easy one.
See what a scan finds on your own site
Our free audit reads your live site the way customers and search engines do. Then it names the specific fixes.
Get your free auditThe widget shortcut already backfired
An accessibility overlay is a widget that promises to make a website compliant with one line of code.
The federal government has already made that promise expensive.
The FTC ordered overlay vendor accessiBe to pay $1 million over claims that its automated product could make any website WCAG compliant.
The final order landed in April 2025. The widget does not stop the lawsuits either.
In July 2026 alone UsableNet counted 401 new suits, and 113 of the businesses sued were running an accessibility widget when the complaint arrived.
The widget changes the menu on top of the page while the code underneath stays the same.
An overlay cannot write the missing labels. It cannot restructure a form or caption a video. It adds a settings panel and leaves the barriers where they were.
The screen reader user meets the same unlabeled form, now with an extra menu floating over it.
You have probably seen the pitch in your inbox.
One line of code. Instant compliance. Lawsuit protection.
Every phrase in it now reads like the order the FTC wrote.
The pitch is cheap because the work it skips is not. Real accessibility is built into the code, not laid on top of it.
What the actual work looks like
The barriers behind most complaints are concrete, and the DOJ names them itself:
- Start with color contrast: text that fails contrast loses a customer squinting at a phone in a bright driveway long before it loses an audit.
- Label every form field: a screen reader announces a labeled field by name and announces an unlabeled one as nothing at all.
- Make error messages say what went wrong and where: a form that only turns a box red is invisible to someone who cannot see the red.
- Keep the whole site usable from a keyboard: some customers never touch a mouse, and a site that traps them at the first menu has hung up on them.
- Give the page a real heading structure: a screen reader jumps between headings the way your eyes skim between them.
- Give every image that carries information a text alternative: write alt text that says what the picture is there to say, not what the file is called.
- Caption your videos: captions also serve the homeowner watching with the sound off in a waiting room.
Tab through your own homepage once and watch where the focus goes. If you cannot see where you are, neither can anyone else.
None of this work is exotic. It is the same discipline as clean wiring: invisible when done right, expensive when found wrong.
The part that surprises most people is that the work is never finished once. Conformance lives page by page. Every page you add and every edit you make can introduce a new barrier.
A site that passed in spring can fail by fall, because each new photo or form arrives with a new way to get it wrong.
That is why accessibility belongs inside ongoing site care rather than inside a one-time project.
Accessibility is included in every build
WCAG 2.2 AA practices are part of every site we build. Built into the code. No widgets. No bolt-ons.
See how we build websitesAn accessible site reaches customers you are not seeing
More than one in four US adults live with a disability, by the CDC’s estimate.
That is not an edge case. That is a customer base.
Ability also changes with age, which means this customer base includes people who could read your site fine five years ago.
Every barrier on your site is a customer who could not call you and never told you why.
The same structure does double duty.
- Screen readers: clean headings and labeled controls are what they announce
- Search engines: the same structure is exactly what they read and rank on
- AI assistants: they build answers from that structure too
Nobody can promise you a spot in an AI answer, and you should be skeptical of anyone who does.
What is knowable is the input side, and an accessible site is stronger input.
The overlap is not an accident. A screen reader and a search crawler are both software trying to understand your page without looking at it.
Build the page so software can read it and every reader you cannot see gets served by the same work.
This is why we treat accessibility as part of the build rather than a service to sell you later.
WCAG 2.2 AA practices are part of every site we build.
Built into the code. No widgets. No bolt-ons.
We check the work with accessibility linting in the code and an automated Lighthouse accessibility check on the pages we build.
Where we stand on accessibility
Our own accessibility page names the standard we build to and how we check it. Read it the way you would read any builder’s.
Read our accessibility pageWhat to do about your website now
Start by finding out where your site stands today. Ask whoever runs your website three questions.
- The standard: what accessibility standard was this site built to
- The basics: are the forms labeled and does everything work from a keyboard
- The recheck: who checks the pages when they change
If the answer to the first one is a widget name or a certificate, you have learned something important.
A widget is not a standard and a certificate is not a build. If the answers come back vague, seeing for yourself takes about a minute.