A letter arrives. It says a blind user could not complete a purchase on your site using a screen reader, cites the Americans with Disabilities Act, lists a dozen technical failures, and proposes a settlement. Nothing in the letter cites a federal regulation that tells private businesses what an accessible website must look like — because no such regulation exists. That gap is the central fact of this area of law.
What does exist is a broadly worded statute, decades of case law about physical places, a genuine disagreement among the federal courts of appeals, a technical standard written by a private standards body, and a very active plaintiffs' bar. Businesses respond to all five at once.
What the statute actually says
Title III of the ADA prohibits discrimination "on the basis of disability in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation." The operative text sits at 42 U.S.C. § 12182, and the statutory list of public accommodations that follows it — hotels, restaurants, theaters, stores, offices, schools — is a list of physical places. The statute was enacted in 1990.
Two consequences follow. First, plaintiffs must connect a website to that list, either by arguing the site is itself a place of public accommodation or by arguing it is a service of one. Second, because Congress never wrote web-specific requirements and the Justice Department has not issued Title III web regulations, courts assess accessibility case by case against the general non-discrimination duty. Remedies under Title III are injunctive relief and attorney's fees, not damages — which is why demand letters focus on settlement of fees and a remediation commitment.
The split, described honestly
There is no national answer to whether a website standing alone is covered. Two lines of authority have developed, and both are still live.
| Approach | Reasoning | Practical effect |
|---|---|---|
| Broad reading | "Place of public accommodation" describes categories of businesses, not only physical structures, so a web-only business can be covered | Online-only retailers and services face direct exposure |
| Nexus requirement | Coverage attaches to physical places; a website is reached when it is a service of, or gateway to, a physical location | Web-only businesses may fall outside; businesses with stores remain exposed |
Neither camp is a fringe position, the Supreme Court has not resolved the question, and appellate decisions in this area have sometimes been vacated or narrowed on procedural grounds rather than settled on the merits. Anyone telling you the question is closed — in either direction — is describing a preference, not the law. For a business operating nationally, the practical takeaway is that at least some courts hearing a claim against you will apply the broader reading.
Watch out: Vendors sometimes market overlay widgets as producing "ADA compliance." Accessibility advocates and testers have criticized these tools, and their presence has not prevented claims. Treat an overlay as, at most, a supplement to real remediation of the underlying code.
What DOJ's 2024 rule does — and who it covers
In 2024 the Justice Department issued a final rule under Title II of the ADA adopting a specific technical standard for the web content and mobile applications of state and local government entities. It is important to read that sentence precisely: Title II covers public entities — city governments, public universities, transit agencies, public school districts. It does not cover private businesses, which are governed by Title III and remain without an analogous federal technical rule.
The rule set staggered compliance dates keyed to population size, with the deadline for larger public entities falling in spring 2026 and a later date for smaller ones; as of mid-2026 the first of those deadlines has passed. The Department's own explanatory materials on web accessibility and the ADA and the wider resources at ADA.gov are the authoritative place to confirm current dates and scope before relying on any secondhand summary.
The rule still matters to private companies for two indirect reasons. It signals what the enforcing agency considers achievable, and it reaches private vendors through procurement: a company selling software to a covered public entity will be asked to meet the standard by contract even though the statute does not reach it directly. That is a negotiation to handle in software and SaaS agreements rather than after a public-sector customer fails an audit.
WCAG 2.1 Level AA as the working benchmark
Absent a Title III regulation, the reference point in litigation, consent decrees, and settlement agreements is the Web Content Accessibility Guidelines published by the World Wide Web Consortium. Level AA of WCAG 2.1 is the version most frequently named. Later versions exist — the guidelines are periodically updated, and the current family is documented at the W3C Web Accessibility Initiative — but 2.1 AA remains the de facto benchmark that courts and settlements reference.
WCAG is organized around four principles: content should be perceivable, operable, understandable, and robust. In practice, a small number of failures generate most complaints.
- Images, icons, and charts without meaningful alternative text.
- Form fields with no programmatic labels, so a screen reader announces "edit text" with no context.
- Functions reachable only by mouse — menus, carousels, modal dialogs that trap keyboard focus.
- Insufficient color contrast, and information conveyed by color alone.
- Video without captions and audio without transcripts.
- Dynamic content updates that are never announced to assistive technology.
- PDFs and downloadable documents that are untagged scans.
- Checkout, scheduling, and account-recovery flows that break at one step — usually the most consequential failure of all.
A workable response sequence
- Preserve and assess. Hold relevant records, and capture the current state of the pages identified. Do not quietly change the site before documenting what it looked like.
- Verify the allegations. Automated scanners catch perhaps a third of real issues. Pair a scan with manual testing using a screen reader and keyboard-only navigation on the specific flows named.
- Scope the fix. Separate quick wins (alt text, labels, contrast) from structural work (a component library rebuild, a third-party booking widget you do not control).
- Build a dated remediation plan. A written plan with owners and milestones is the single most useful document in settlement discussions.
- Deal with third-party components. Payment widgets, chat tools, and embedded video players are common failure points. Push obligations back to the vendor in writing.
- Publish and maintain. Post an accessibility statement with a real contact channel, then re-test on a schedule. Sites regress with every release that ships without an accessibility check.
Practical step: Add accessibility acceptance criteria to your definition of "done" for front-end work and require a keyboard-only pass before release. Prevention costs a fraction of remediation, and it is what stops the same page from generating a second letter two years later.
Quick answers
We are online only, with no stores. Are we safe?
No. In circuits requiring a physical nexus you have a real argument, but in circuits reading the statute broadly you do not, and plaintiffs choose where to file. Many web-only businesses also face state accessibility statutes that are worded differently from the ADA. The absence of physical locations is a defense worth raising, not a reason to skip remediation.
Does meeting WCAG 2.1 AA guarantee we cannot be sued?
It does not. WCAG is a private technical standard, not a federal safe harbor for private businesses, and anyone can file a complaint. What conformance does is give you a documented, testable answer to the allegations and a strong position in early settlement discussions — which in practice resolves most of these matters.
Is this the same law that governs accommodations for our employees?
Same statute, different title. Employment accommodations arise under Title I and turn on an individualized interactive process with a specific employee, described in the guide to the workplace accommodation process. Public-facing website claims arise under Title III and turn on access to goods and services by the public generally. Internal HR systems can implicate both.
Our site runs on a third-party platform we cannot modify. Now what?
You remain the party the public deals with, so responsibility does not simply transfer. Document the limitation, escalate formally with the platform, and check your contract for accessibility warranties or support commitments. When renewing, make conformance an express vendor obligation with remediation timelines — the same discipline applied to security and privacy terms.
Should we publish an accessibility statement?
Yes, if it is accurate. Describe the standard you are working toward, the known gaps, and how to reach a human who can provide an alternative way to complete a transaction. Avoid absolute claims of full compliance; an overstated statement can become the evidence used against you. Keep it dated and revise it as work progresses.
Where this leaves you
Treat WCAG 2.1 AA as the target, test the transactional paths first, and keep a written remediation plan with dates. Confirm current federal requirements at ADA.gov rather than from vendor marketing, and remember the 2024 rule speaks to public entities under Title II. Push accessibility duties into vendor contracts, and build testing into release process so gains hold. Related interface obligations — from how your terms of service secure assent to privacy disclosures — are collected in the technology, privacy, and IP pathway, and they tend to be solved by the same front-end team in the same sprint.