The Americans with Disabilities Act (ADA) is a U.S. civil rights law passed in 1990 that prohibits discrimination against people with disabilities. It was written before the modern web existed, so it never mentions websites by name — but that hasn't stopped it from becoming the single biggest legal driver of web accessibility in the United States. Courts, the Department of Justice, and thousands of demand letters and lawsuits have made one thing clear: if your business serves the public, your website is expected to be usable by people with disabilities.
The core idea is simple. Title III of the ADA requires "places of public accommodation" — shops, restaurants, hotels, banks, medical offices, and most other businesses open to the public — to provide equal access to their goods and services. The Department of Justice has consistently taken the position that this obligation extends to websites and mobile apps, and most courts have agreed, especially where a site is connected to a physical business.
This guide explains who the ADA applies to, what "accessible" actually means in practice, what enforcement looks like, and the concrete steps you can take to reduce your risk while genuinely improving the experience for disabled users.
Applies to most businesses
Title III covers businesses open to the public regardless of size, and Title II covers state and local governments. There is no small-business exemption from Title III's accessibility obligations.
WCAG is the de facto standard
The ADA itself sets no technical standard for websites, but courts, the DOJ, and settlement agreements consistently point to the Web Content Accessibility Guidelines (WCAG) as the benchmark.
Enforcement is lawsuit-driven
Most ADA web accessibility actions arrive as private lawsuits or demand letters rather than government fines, which means any public-facing site can be a target at any time.
Accessibility is ongoing
Compliance isn't a one-time certification. Every redesign, new feature, or content update can introduce new barriers, so accessibility needs to be part of your regular workflow.
What the ADA is and why it matters online
The ADA is organized into titles. Title I covers employment, Title II covers state and local government services, and Title III covers private businesses that serve the public. For website owners, Titles II and III are the ones that matter: Title II if you're a government entity, Title III if you're a business.
Because the law predates the web, its application to digital properties has been shaped by regulation, court decisions, and Department of Justice guidance rather than by explicit statutory text. In 2024, the DOJ finalized a rule under Title II requiring state and local government websites and mobile apps to conform to WCAG 2.1 Level AA, with compliance deadlines phased in by entity size (April 2026 for larger entities, April 2027 for smaller ones). For private businesses under Title III there is still no formal technical regulation — but the DOJ has repeatedly stated that the ADA applies to websites, and its settlements have long referenced WCAG.
Who must comply
If your organization fits any of the following, you should treat web accessibility as a legal obligation, not a nice-to-have:
- Private businesses open to the public — retail, restaurants, hospitality, healthcare, finance, entertainment, professional services, and e-commerce (Title III).
- State and local government entities, including public schools, libraries, courts, and transit agencies (Title II, now with an explicit WCAG 2.1 AA rule).
- Businesses with a physical location and a website — courts have been most consistent in applying the ADA where the site connects to a brick-and-mortar "place of public accommodation".
- Online-only businesses — court outcomes vary by circuit, but many online-only companies have faced (and settled) ADA lawsuits, so operating without a storefront is not reliable protection.
What an accessible website looks like
The ADA doesn't include a technical checklist, so in practice "ADA compliant" means conforming to WCAG — usually version 2.1 at Level AA, the target named in the DOJ's Title II rule and in most settlements. WCAG organizes accessibility around four principles: content must be perceivable, operable, understandable, and robust.
For a typical business website, the most common barriers — and the ones that show up again and again in lawsuits — include:
- Images without text alternatives, so screen reader users can't tell what they show.
- Poor color contrast that makes text hard to read for people with low vision.
- Forms and buttons that aren't labeled properly for assistive technology.
- Menus, modals, and checkout flows that can't be operated with a keyboard alone.
- Videos without captions and audio content without transcripts.
- Missing document structure — headings, landmarks, and page titles that let users navigate efficiently.
Enforcement and what non-compliance can cost
ADA web accessibility enforcement comes from two directions. The Department of Justice can investigate and bring enforcement actions, and civil penalties for ADA violations can reach into the tens of thousands of dollars for a first violation and higher for subsequent ones. In practice, though, most businesses first hear about the issue through a private lawsuit or a demand letter from a plaintiff's firm.
Title III doesn't allow private plaintiffs to collect damages in federal court — they can seek injunctive relief (an order to fix the site) plus attorney's fees. But many suits are filed under state laws like California's Unruh Act, which do allow monetary damages, and defense costs alone typically run well into five figures even when a case settles quickly. Thousands of web accessibility lawsuits are filed in U.S. federal and state courts every year, and e-commerce sites are the most frequent targets. The cheapest time to deal with accessibility is before the demand letter arrives.
Practical steps toward ADA compliance
You don't need to fix everything overnight. Regulators and courts look far more favorably on organizations that can show a genuine, documented effort. A sensible roadmap looks like this:
- Audit your site against WCAG 2.1 AA using a combination of automated scanning and manual testing with a keyboard and a screen reader.
- Prioritize fixes on high-traffic, high-stakes pages first: homepage, navigation, search, product pages, forms, and checkout.
- Fix content-level issues (alt text, headings, link text, captions) alongside code-level issues (focus management, ARIA labels, contrast).
- Publish an accessibility statement with a working contact channel, and respond quickly when users report barriers.
- Build accessibility into your workflow — design reviews, developer checklists, and regression testing — so new releases don't reintroduce old problems.
- Use supporting tools thoughtfully. An AI-powered solution like AccessWiser can help identify and remediate common barriers and improve the day-to-day experience for assistive technology users, but no tool by itself guarantees legal compliance — pair tooling with audits and human review.
How the ADA relates to WCAG and other laws
Think of the ADA as the legal obligation and WCAG as the technical yardstick used to measure whether you've met it. WCAG is published by the W3C and isn't a law anywhere on its own, but it is referenced by accessibility legislation worldwide — including the ADA Title II rule, Section 508 for U.S. federal agencies, Canada's AODA, and the European Accessibility Act, whose obligations have applied since June 28, 2025.
If you conform to WCAG 2.1 Level AA (or the newer 2.2), you'll be in a strong position under the ADA and simultaneously cover most of what other jurisdictions require. That's why accessibility work is rarely wasted effort: one well-executed program addresses multiple legal regimes at once.
Frequently asked questions
Is my website legally required to be ADA compliant?
If you're a state or local government entity, yes — an explicit DOJ rule requires WCAG 2.1 AA conformance. If you're a private business open to the public, the DOJ and most courts treat the ADA as applying to your website, so as a practical matter you should assume the obligation applies, even though no formal technical regulation exists yet for the private sector.
What standard should I aim for?
WCAG 2.1 Level AA is the benchmark used in the DOJ's Title II rule, in settlements, and in most legal complaints. Targeting WCAG 2.2 AA, the current version of the guidelines, gives you a little extra headroom and covers everything in 2.1.
Does an accessibility widget or overlay make my site ADA compliant?
No single tool can guarantee legal compliance. Widgets and AI-powered remediation can meaningfully reduce barriers and improve usability, and they're a reasonable part of an accessibility program — but they should complement, not replace, fixing underlying issues in your code and content and testing with real assistive technology.
I run a small business — am I exempt?
Title III has no small-business exemption based on size or revenue (the ADA's small-employer threshold applies to Title I employment rules, not to serving the public). Small businesses are sued over website accessibility regularly, so size alone won't protect you.
What should I do if I receive an ADA demand letter?
Don't ignore it, and talk to a lawyer experienced in ADA defense before responding. In parallel, start documenting your accessibility efforts and begin remediation — demonstrable progress toward WCAG conformance is usually central to resolving these claims.
This article is provided for general information about accessibility regulations and standards. It is not legal advice — consult a qualified professional about your specific compliance obligations.