ADA Website Compliance: What It Actually Means for Your Business

Search for anything about ADA compliance and your website and you will come away more confused than you started. One page says every business is legally required to meet a specific technical standard. The next says no such requirement exists. A third wants to sell you a widget that makes the whole problem disappear for fifty dollars a month.

The advice contradicts itself because the underlying legal position is genuinely unsettled, and most articles handle that by presenting whichever half supports what they are selling. This one lays out the whole picture, including the parts nobody has resolved yet, written for a business owner rather than a lawyer.

The disclaimer that matters, up front: I am not a lawyer. I can tell you what standard your site currently meets and what it would take to fix the gaps. Whether you are legally required to act, and what a specific demand letter means for you, is a question for an attorney.

The strange gap at the center of all this

The Americans with Disabilities Act was signed in 1990, before most businesses had a website. The law does not mention them. What it does is require places of public accommodation not to discriminate, and the Department of Justice has taken the position since 1996 that this reaches web content.

Here is the part almost nobody selling accessibility services will tell you. There is no federal regulation that tells a private business which technical standard its website has to meet. DOJ says so itself, in its own published guidance: the Department “does not have a regulation setting out detailed standards,” only its longstanding interpretation that the general nondiscrimination and effective communication rules apply to the web.

So you have a real legal obligation with no official yardstick attached to it. That gap is why the advice you find online is such a mess, and it is why “guaranteed ADA compliant” is a phrase I will not put in front of you. There is no federal certification to be compliant with. Anyone issuing you a compliance certificate for a private business website invented the certificate.

What fills the gap: WCAG

Courts, regulators and settlement agreements have all converged on the same reference: the Web Content Accessibility Guidelines, published by the World Wide Web Consortium. WCAG is not a law. It is the technical standard everyone points at because it is the only credible one that exists.

The current version is WCAG 2.2, published in October 2023 and updated in December 2024. It was adopted as an international standard, ISO/IEC 40500, in 2025. It comes in three conformance levels, A, AA and AAA. AA is the level that matters in practice, and it is the level nearly every settlement, procurement rule and government regulation names.

I build and remediate to WCAG 2.2 AA. It contains everything in WCAG 2.1 AA, which is what the federal rules point to, so meeting 2.2 means you clear the referenced bar with a little headroom. If you want the plain-English tour of what the standard actually asks for, I wrote one: WCAG 2.2 AA explained.

Which rules apply to you, specifically

Three different regimes get mixed together constantly, and only one of them probably applies to your business.

Title III covers private businesses open to the public. Retail, restaurants, clinics, hotels, professional services, e-commerce. This is almost certainly you. There is no technical regulation here and no compliance deadline, because DOJ never issued one. Your exposure comes from private lawsuits and demand letters, not from a filing date.

Title II covers state and local government. Cities, counties, school districts, public universities, special districts. This one does have a rule now. DOJ published it in April 2024, and it adopts WCAG 2.1 Level AA as a binding technical standard.

The compliance dates are worth getting right, because a great deal of what is written online is now out of date. DOJ pushed them back in an interim final rule in April 2026. Entities serving a population of 50,000 or more now have until April 26, 2027. Smaller entities and special district governments have until April 26, 2028. If you run or sit on the board of an Idaho city, district or public agency, those are your dates, and neither has passed yet.

Section 508 covers federal agencies and the vendors selling to them. It requires WCAG 2.0 Level AA. If you contract with the federal government, this shows up in your procurement paperwork whether or not anyone ever sues you.

The lawsuit picture, with a real number

Seyfarth Shaw, a defense-side law firm that counts federal filings by hand every year, recorded 3,117 website accessibility lawsuits filed in federal court in 2025, up about 27 percent from 2,452 the year before. I cite them because they do the actual counting, and I will note plainly that they are a law firm with a defense practice rather than a neutral statistical agency.

Two things about that number matter more than its size. The filings concentrate heavily on small and mid-size businesses, and there is no small-business exemption. Being a nine-person shop in Kuna does not put you outside the law. Demand letters, which never become filings and never show up in anyone’s count, are far more common still.

The fuller picture, including who actually files these and why the same handful of issues appear in almost every complaint, is here: how many ADA website lawsuits get filed, and who gets sued.

Why the one-line widget does not solve this

You have probably seen the pitch. Paste one line of JavaScript, get a little accessibility icon in the corner, become compliant overnight for a monthly fee. It does not work that way, and this is not my opinion against theirs.

In January 2025 the Federal Trade Commission required accessiBe, one of the largest overlay vendors, to pay $1 million to settle allegations that it misrepresented its product’s ability to make websites WCAG compliant. The FTC also alleged the company presented paid and affiliated reviews as independent opinions.

Accessibility lives in the markup, the contrast values, the focus order and the labels. A script that runs after the page loads is working on the wrong side of the problem. The longer version, including what overlays genuinely can and cannot do, is here: why overlay widgets don’t make your site compliant.

What to actually do about it

Start by finding out where you stand, which costs nothing but an hour of your afternoon. I put together a checklist you can run yourself, with no tools to buy. It will not make you conformant, but it will tell you fast whether you have a small problem or a large one.

If the answer is “a large one,” the next step is a proper audit against the standard rather than a scan. Automated tools catch somewhere around a third of real issues. The rest need a person with a keyboard and a screen reader. I wrote up exactly what happens during an accessibility audit so there are no surprises about what you are buying.

And it is worth knowing that this work pays for itself in ways that have nothing to do with the law. Accessible sites are cleaner, faster and easier for search engines to read, and they stop losing customers who could not complete a form. That case is here: accessible websites are better websites.

What I will and will not promise you

I will not promise you cannot be sued. Nobody can. Anyone who does is selling something. Good-faith conformance to WCAG 2.2 AA lowers your risk a great deal and demonstrates that you took the obligation seriously, which matters. It does not take the risk to zero, and I would rather say that here than discover it with you later.

I will not tell you this is one and done. A new image without alt text, a low-contrast promo banner, a plugin update that changes the checkout markup, any of these can reopen a gap you already paid to close. A remediation pass gets you to the standard. Staying there is a habit, which is why accessibility is built into every site I make and watched as part of the care plan.

What I will do is fix it in the code and show you the work. A real audit against WCAG 2.2 AA, the blocking issues ranked by how much they actually hurt, the fixes made at the source, and a written conformance summary at the end that says what was tested and what was found.

The full scope, the process and the pricing are on the ADA compliance page. If you have a letter in your hand right now, talk to an attorney first, then book a free 30-minute call and I will tell you honestly how big the technical job is.