ADA Website Compliance for Small Businesses: What the Law Actually Requires

If you run a business in the US and have a website, the question is not whether the ADA applies to it. The Department of Justice has said for years that it does. The real questions are what "compliant" means when there is no official rule for private businesses, how likely you are to be sued, and what it actually takes to fix a site.

This guide answers those three, with the sources linked so you can check every claim. It is written for owners and founders, not lawyers. It is general information, not legal advice; if you have received a demand letter or a complaint, talk to an attorney first.

What the ADA says about websites (and what it doesn't)

The Americans with Disabilities Act was signed in 1990, before most businesses had a website. Two parts matter here:

• Title II covers state and local governments: cities, counties, public schools, public universities, transit agencies.
• Title III covers "public accommodations": businesses open to the public, such as shops, restaurants, clinics, hotels, gyms, law firms and, depending on the court, online-only businesses.

For Title II there is now a precise rule. In April 2024 the DOJ published a final rule adopting WCAG 2.1 Level AA as the technical standard for state and local government websites and apps. The deadlines have since moved: an interim final rule published on April 20, 2026 pushed them back one year, to April 26, 2027 for entities serving 50,000 people or more and April 26, 2028 for smaller ones and special districts. The DOJ also said it may propose changes to the rule's substance. As of October 2026 no such proposal has been published, so the 2024 standard stands.

For Title III, the one that covers your business, there is no equivalent rule. The DOJ withdrew its pending Title III web rulemaking in December 2017 and has not proposed a new one since. What it has published is guidance from March 2022 saying, in plain terms, that businesses open to the public must make their websites accessible:

The guidance lists WCAG and the federal Section 508 standards as helpful references, without making either mandatory. That word "flexibility" is why people say "there's no legal standard". It's true on paper. In practice, flexibility means a judge decides whether your site was accessible enough, and the yardstick every expert witness, settlement and DOJ agreement reaches for is WCAG 2.1 AA.

Online-only businesses. Federal courts disagree on whether a business with no physical location is a "place of public accommodation". The Ninth Circuit held in Robles v. Domino's Pizza (2019) that the ADA applied to Domino's website and app because they connect customers to its restaurants, and the Supreme Court declined to review it. Other circuits read the law more narrowly. That uncertainty is not a shield: state laws fill the gap. California's Unruh Civil Rights Act allows a minimum of $4,000 in damages per violation, and New York state courts see a large share of website suits.

Selling into Europe too? The European Accessibility Act has applied since June 28, 2025 to many e-commerce sites selling to EU consumers. Its technical baseline is close to WCAG 2.1 AA, so one fix covers both.

How real is the lawsuit risk?

Real, and rising again after two quieter years. Seyfarth Shaw, a law firm that tracks ADA filings, counted 3,117 website accessibility lawsuits in federal court in 2025, up 27% from 2,452 in 2024 and the highest total since 2022. Websites made up 36% of all ADA Title III suits in federal court.

Federal court is only part of the picture. UsableNet, which also counts state filings, tallied 5,114 digital accessibility suits in 2025, with 1,919 of them in New York and California state courts. Its breakdown is the useful part for a small business:

• About 70% targeted e-commerce. Food service was next, at about 21%.
• 45% of federal filings hit companies that had been sued before. Settling without fixing the site does not end it.
• Most defendants are not household names. Plaintiffs' firms use automated scanners to find sites with obvious errors, then file many near-identical complaints.

Behind the suits sit demand letters: a letter from a law firm listing barriers on your site and proposing a settlement before anything is filed. Nobody publishes reliable counts of these, because most are settled privately. They follow the same pattern as the suits: a scan, a list of WCAG failures, a deadline.

None of this means every small site will be sued. It means the odds go up sharply if you sell online, have customers in New York or California, and have obvious, scannable errors. The last one is the only factor you control.

WCAG 2.1 AA: the practical standard

WCAG (Web Content Accessibility Guidelines) is published by the W3C. WCAG 2.1 became a W3C Recommendation in June 2018; WCAG 2.2 followed in October 2023 and adds nine criteria on top. Each version has three levels: A (the minimum), AA (the one everyone means), AAA (aspirational, rarely required).

WCAG 2.1 level AA compliance means meeting all 50 Level A and AA success criteria. They are grouped under four principles, which are easier to remember than the numbers:

If you are building or rebuilding now, target WCAG 2.2 AA: it covers everything in 2.1 AA (minus one obsolete parsing criterion), and the extra criteria (target sizes, focus not hidden behind sticky headers, no puzzle-only logins) are cheap to get right from the start and annoying to retrofit.

What fails in practice

Audits of small-business sites find the same handful of problems again and again. WebAIM scans the top million home pages every year; in its 2026 report, 95.9% had detectable failures, averaging 56 errors per page, and six error types made up almost all of them. Here are the ones that matter most, on a typical home page:

1. Low-contrast text. Light grey on white looks elegant and fails WCAG 1.4.3, which asks for a contrast ratio of 4.5:1 for normal text. It is the most common failure on the web. The fix is usually a darker shade of the same color, which keeps the design intact.
2. Images without alt text. A screen reader announces "image" or reads the file name. Meaningful images need a short description; decorative ones need an empty alt so they are skipped.
3. Form fields without labels. A placeholder that disappears when you type is not a label. Contact, booking and checkout forms are where this hurts most, because they are where customers convert, and where plaintiffs test.
4. No visible keyboard focus. Many themes remove the focus outline because it looks untidy. Without it, someone using Tab has no idea where they are. Add a designed focus style instead of removing it.
5. Video without captions. Promo videos, recipe reels, product demos. Auto-generated captions are a start, but they need a human pass.

Two more that scanners miss and audits catch: PDFs (menus, price lists, intake forms) that are just scanned images, and custom widgets like date pickers, carousels and cookie banners that can't be operated by keyboard. If your checkout or booking flow uses a third-party widget, test it: you are responsible for what your customers have to use.

Why overlays don't make a site compliant

An overlay is a script you paste into your site that adds an accessibility toolbar and tries to repair the page automatically. They are cheap and promise compliance in minutes, which is why "ada compliance accessibe" is a common search. The problem is that they change what's displayed, not the underlying code that screen readers and keyboards rely on, and many fixes need human judgment (what should this image's alt text say?).

The regulator has weighed in. In January 2025 the FTC announced a complaint against accessiBe, and in April 2025 it finalized the order: accessiBe pays $1 million and may not claim that its automated products can make any website WCAG-compliant, or keep it compliant over time, unless it has evidence to support it. The FTC also alleged that accessiBe presented paid reviews as independent. The FTC's own business blog post on the case is worth five minutes.

To be fair to the tools: some widget features (a contrast toggle, a reading guide) help some users, and a few vendors pair their script with real manual audits. Treat a widget as an extra at best, never as the fix.

How to get compliant, step by step

The work is less dramatic than the lawsuits suggest. For most small sites, it is a defined project followed by a habit.

1. Run the free checks yourself (an hour). Unplug your mouse and try to use the site with Tab, Shift+Tab and Enter: can you reach every link, see where you are, open the menu, send the form? Then run a free checker such as WAVE or the Lighthouse accessibility audit built into Chrome on your home page, contact page and checkout. Zoom to 200%. You will learn more in an hour than from any sales call.

2. Get a manual audit against WCAG 2.1 AA (or 2.2 AA). A good audit covers your key templates and journeys (home, a service or product page, contact, booking or checkout), tested with a keyboard and at least one screen reader, and gives you a prioritized list: what fails, which criterion, where, and how to fix it. Avoid audits that are just a scanner export with a logo.

3. Fix in the code, in order of impact. Checkout, booking and contact forms first, then navigation, then content. Most fixes are small: colors, labels, alt text, focus styles, heading order, button names. If your site runs on a theme you can't change much, this is where the platform matters. We compared the trade-offs in Webflow vs custom code.

4. Publish an accessibility statement. A short page saying which standard you aim for, what you know still needs work, and how to reach you if something doesn't work. It doesn't make you compliant, but it shows good faith and gives customers a route other than a lawyer.

5. Keep it compliant. Accessibility breaks quietly: a new landing page with grey text, a plugin update, a video without captions. Build checks into your publishing routine, and re-audit once a year or after any redesign. This fits naturally into a maintenance plan.

What it costs

For a typical small marketing site or shop, a manual audit plus fixing what it finds lands in the low thousands, not tens of thousands. In our cost estimator, accessibility audit and remediation adds €1,000–3,000 to a project (October 2026). What pushes it up:

• Platform limits. Locked themes and page builders sometimes need workarounds, or a rebuild of key templates.
• Custom checkout or booking flows, which need careful testing with assistive technology.
• Content volume: hundreds of product images needing alt text, a video library needing captions, a folder of PDFs.

What brings it down: building it in from the start. On a new site, accessibility is mostly a matter of good design decisions and clean code, and costs a fraction of a retrofit. If you're planning a rebuild anyway, read what a website redesign really costs and make WCAG 2.2 AA part of the brief. Accessible sites also tend to be faster and better structured, which helps with Core Web Vitals and search.

Where does your site stand?

Our take

ADA compliance for a small business website is not a legal mystery and not a product you install. It is a known standard, WCAG 2.1 AA, applied to your site by people who test it the way your customers use it. The lawsuit numbers are real, but they mostly land on sites with obvious, scannable errors, and those are the cheapest to fix.

We audit sites against WCAG 2.1 and 2.2 AA by hand (keyboard and screen reader, not just a scanner), fix them in the code, and build new sites accessible from the first line. You get a written report you can keep, whether we do the fixes or your own team does. If you're comparing options, our guide to what a website costs shows where accessibility fits in a budget.

This article is general information about US law as of October 2026, not legal advice. Laws, rules and court decisions change; check the linked sources and consult an attorney about your situation.