Nobody has complained and no letter has arrived. But a new marketing manager asked in a meeting whether the website “meets the ADA,” and nobody at the table knew. Or you are about to rebuild the booking page and would rather do it right the first time. Either way, you want a plain account of what ADA compliance for websites involves before anyone tries to sell you something.
This guide is that account. It covers what the law says and leaves unsaid, which rules reach which kind of organization, why one technical standard shows up in every conversation, and a sensible order of work. It is general information, not legal advice. If a demand letter or lawsuit is already involved, a lawyer should lead; this guide stays on the technical side.
ADA requirements for websites: what the law actually says
At heart the ADA is a civil rights statute. The part that matters to most businesses is Title III, which says a business serving the public (the statute’s phrase is “place of public accommodation”) may not shut people with disabilities out of its goods and services. Dental offices, hardware stores, hotels, accountants, yoga studios and car dealers all fit.
The ADA was written before businesses had websites, so the statute is silent on them. Everything since has been interpretation. The Department of Justice, which enforces the law, has said for years that Title III reaches the web content of public accommodations, and it repeated that view in web accessibility guidance published in March 2022. Courts, meanwhile, have not all read the law the same way where websites are concerned.
The piece that surprises people: the DOJ has never written a Title III regulation with a technical web standard. No federal rule lists the exact tests a business site must pass. So the ADA requirements for websites of private businesses amount to a duty (people with disabilities must be able to use what you offer online) rather than a checklist written into law.
The government’s own materials are on ADA.gov, which is also where any change will show up first.
Three sets of rules, three different audiences
“ADA website rules” is often used loosely to cover three separate frameworks. Each reaches a different kind of organization, and only one currently names a web standard in a regulation.
| Framework | Who it reaches | Website standard |
|---|---|---|
| ADA Title III | Private businesses open to the public | No DOJ technical regulation; audits and letters measure against WCAG AA (2.1 or 2.2) |
| ADA Title II | State and local governments: cities, counties, school districts, public libraries, transit agencies | DOJ final rule (April 2024) adopts WCAG 2.1 Level AA for web content and mobile apps |
| Section 508 | Federal agencies, and often their contractors and grantees through contract terms | The 2017 refresh incorporates WCAG 2.0 AA |
If you run a private business, the first row is yours. The open questions there (which businesses count, and what happens with companies that have no physical location) are covered in our post on who Title III reaches and how courts split on online-only businesses.
Public bodies are in a different position since the 2024 rule. Its compliance dates depend on population size and could be revised, so check ADA.gov for the current ones, and see our page on the Title II web accessibility rule for public bodies.
Section 508 is mainly a federal agency matter. A business that sells to federal agencies or receives federal grants may meet it through contract terms, and a buyer may ask for an Accessibility Conformance Report written on the VPAT template.
Where WCAG fits in
Because Title III names no web standard, lawyers, auditors and courts all use the one the web industry already had: the Web Content Accessibility Guidelines (WCAG), published by the W3C’s Web Accessibility Initiative. Demand letters cite its success criteria by number, settlements name a version, and audit reports are organized around it. In practice the target is Level AA of version 2.1 or 2.2.
WCAG 2.2 became a W3C Recommendation in October 2023. It adds nine success criteria to 2.1 and retires one (4.1.1 Parsing), so a site built to 2.2 AA covers everything 2.1 AA asks apart from that retired item. For new work, 2.2 AA is the sensible target. The relationship between the law and the standard, and why they are so often confused, is the subject of our ADA vs WCAG explainer. If WCAG is new to you altogether, start with what WCAG is and how its levels work.
What the standard means for a visitor
Success criteria read like engineering, but each one protects a person trying to do something ordinary on your site:
- A blind visitor using a screen reader hears what your product photo shows, and hears “Email address, required” instead of “edit text” when she reaches the form.
- A visitor who cannot use a mouse reaches every menu item, button and field with the Tab key, can always see which one is active, and never gets stuck inside a pop-up.
- A visitor with low vision zooms the page to twice its size and still reads each line without scrolling sideways, because the text has enough contrast and the layout reflows.
- A deaf visitor follows your explainer video through accurate captions.
- A visitor who makes a mistake on your booking form gets a written explanation next to the field, not just a red border.
Most of that comes down to building carefully and writing content with some attention. Little of it requires special technology.
What ADA compliance for websites can honestly mean
No one can issue you a certificate saying your site is ADA compliant. There is no official certifying body for Title III websites, and no plugin, scan or badge decides the question. Whether a business met its legal duties is decided by a court, in a specific case, on specific facts.
What you can have is more modest and more useful: a site tested against WCAG 2.2 AA by people who know how to test, barriers found and fixed, a dated record of that work, and a habit that stops new problems from piling up. That helps the customers who were getting stuck, and it is the material your lawyer would ask for if the question ever came up.
The quick-fix pitch deserves particular suspicion. Overlay toolbars and scripts that promise compliance from one line of code draw objections from disability advocates and many practitioners, owners who installed them have still faced lawsuits, and the FTC acted against one overlay vendor, accessiBe, in 2025 over misleading claims. Our post on what overlay widgets can and cannot do goes through the technical reasons.
A sensible order of work
Working toward ADA compliance for websites does not require learning every success criterion. It requires doing things in the right sequence.
- Look before you spend. Try your own key pages with a keyboard, a zoomed browser and a free scanner. Our half-hour owner self check walks through it. It will not find everything, but it tells you whether the problem is small or large.
- Get the key journeys audited. Scanners find only part of the problems. A useful audit adds keyboard testing and a screen reader pass (NVDA on Windows, VoiceOver on Mac and iPhone) on the pages people use to contact you, book, buy or find essential information.
- Fix what blocks a task first. A form that cannot be submitted, a menu the keyboard cannot open or a checkout button that cannot be reached outranks a slightly faint footer.
- Fix shared code before individual pages. On WordPress, many barriers live in the theme and a few plugins, so one repair there clears the same fault on every page. Content (images, headings, link wording, PDFs, video) comes next.
- Retest and keep a record. Log what was found, what changed, when, and what is still open. Publish an honest accessibility statement with a way for people to report problems.
- Check again as the site changes. Plugin updates, new pages and new pop-ups bring barriers back. A short monthly check catches them early.
For a printable list of everyday items, see our accessibility checklist for small business sites.
If a letter has already arrived
Do not ignore it, and do not reply to it yourself. Take it to a lawyer, keep a full copy of the site as it stands, and let the technical work follow your lawyer’s direction. The order of steps and the classic mistakes are set out in our step-by-step response to a demand letter.
More in this ADA and website risk series
Each of these posts takes one question further:
- How website accessibility lawsuits arise: where claims come from and what they usually point to, without scare numbers.
- The DOJ’s web accessibility guidance in plain words: the barriers it names, the room it leaves businesses, and its limits.
- ADA expectations for small business websites: what size does and does not change, and a plan for a few hours a month.
For how audit, remediation and monitoring fit together as services, see our main page on website accessibility services.
Frequently asked questions
Who enforces the ADA when it comes to websites?
The Department of Justice enforces the ADA and can investigate or bring cases. Title III also lets private individuals bring claims, and that is how most business owners first meet the issue, through a demand letter or a lawsuit. Either way, the legal questions belong with a lawyer.
Does publishing an accessibility statement count as ADA compliance?
No. A statement describes the standard you work toward, what you have tested, known gaps and how people can report problems. It is useful and shows good faith, but it removes no barriers by itself. Write it after real testing, and never claim the site is fully accessible.
Do the same expectations apply to our mobile app?
For state and local governments, the 2024 Title II rule covers mobile apps as well as web content. For private businesses there is no technical regulation for either, and how the law applies to an app is a question for your lawyer. On the technical side, WCAG principles apply to apps too.
How long does it take to make a website accessible?
It depends on how many page templates you have, the state of the theme and plugins, the number of forms, documents and videos, and how much content needs editing. An audit is what tells you the scope. The work also never fully ends, because updates and new pages can introduce new barriers.
If you would like help with the technical side, our page on ADA website compliance work for business sites describes our WCAG 2.2 AA testing, the repairs that follow, and the written record you and your lawyer can use.
All guides in this section
- Is My Website ADA Compliant? A 30-Minute Self Check
- ADA Website Lawsuits Explained for Business Owners
- What to Do After an ADA Demand Letter About Your Site
- ADA Title III Website Accessibility: Who It Covers
- DOJ Website Accessibility Guidance in Plain Words
- Does a Small Business Website Need to Be ADA Compliant?
- Accessibility Overlays: What They Do and Cannot Fix
- ADA vs WCAG: How the Law and the Standard Connect
- Does Accessibility Help SEO? The Honest Overlap
- Website Accessibility Cost: What Drives the Effort
- Website Accessibility Myths Owners Still Believe
Next in this series: Is My Website ADA Compliant? A 30-Minute Self Check
