ADA Title II vs Title III 2026 | Which Web Rules Apply to You?

Last updated: 2026-07-06

The Americans with Disabilities Act is often discussed as a single web accessibility requirement, but it actually splits into different titles that cover different kinds of organizations — and in 2026 the distinction matters more than ever. Title II covers state and local governments and the entities that act on their behalf: city websites, public universities, courts, public transit agencies, libraries, and public school districts. Title III covers 'public accommodations' — private businesses open to the public, such as shops, restaurants, hotels, banks, clinics, and the online stores and booking sites that go with them. The practical difference in 2026 is that Title II now has an explicit technical standard: the Department of Justice finalized a rule requiring state and local government web content and mobile apps to meet WCAG 2.1 Level AA, with compliance deadlines that have begun to arrive (larger public entities first, smaller ones following). Title III, by contrast, still has no single regulation naming a specific version of WCAG, yet businesses are sued constantly under it, with courts and the DOJ repeatedly pointing to WCAG 2.1 AA as the practical benchmark. This comparison explains who falls under each title, what each one actually requires, and why WCAG 2.1 AA has effectively become the shared target either way. This is general information, not legal advice.

At a Glance

Feature ADA Title II ADA Title III
Who it covers State and local governments and their agents Private businesses open to the public
Explicit technical standard Yes — WCAG 2.1 AA (DOJ rule) No named standard in regulation
Fixed compliance deadlines Yes — phased by entity size No — driven by litigation
Practical target to aim for WCAG 2.1 AA WCAG 2.1 AA (per case law)
Main enforcement mechanism Federal oversight and funding conditions Private lawsuits and demand letters
Covers mobile apps Yes — explicitly Yes — in practice via case law
Who is most at risk Public entities past their deadline Small businesses targeted by serial filers

ADA Title II

Type: Covers state and local governments and their contractors Pricing: Compliance cost varies; non-compliance risks federal enforcement and loss of funding Best for: City and county sites, public universities and schools, courts, transit, and libraries — anyone acting as or for a government body.

Pros

  • Has a clear, explicit technical standard — WCAG 2.1 Level AA — thanks to the DOJ's finalized rule
  • Defined compliance deadlines give public entities a concrete timeline to plan and budget around
  • Applies to web content and mobile apps, closing ambiguity about what 'accessible' means for governments
  • Removes the guesswork that private businesses still face about which standard to follow

Cons

  • Broad scope covers vast amounts of legacy content, documents, and third-party integrations
  • Public entities often have limited budgets and large archives, making remediation genuinely hard
  • Third-party tools and vendor content still have to be brought into conformance
  • Deadlines differ by population size, so smaller entities must track which date applies to them

ADA Title III

Type: Covers private businesses that are 'public accommodations' Pricing: No fixed standard; litigation and settlement costs are the main financial exposure Best for: Retailers, restaurants, hotels, clinics, professional services, and any private business with a website, online store, or booking system.

Pros

  • Flexible in principle — no single mandated code version means multiple paths to defensible conformance
  • Courts and the DOJ consistently treat WCAG 2.1 AA as the practical benchmark, giving a clear target to aim at
  • Meeting WCAG 2.1 AA generally satisfies both the spirit of Title III and most demand letters
  • Improvements also help SEO, mobile usability, and conversion, so the work pays back beyond compliance

Cons

  • No regulation names a specific WCAG version, leaving businesses to infer the requirement from case law
  • One of the most litigated areas of the ADA, with thousands of website lawsuits and demand letters each year
  • Small businesses are frequent targets, often over the same common failures (missing labels, contrast, keyboard traps)
  • Uncertainty makes it hard to know when you have done 'enough' without a formal audit

Our Verdict

The most useful takeaway is that Title II and Title III now point at the same finish line even though they get there differently. If you are a state or local government or work on their behalf, Title II removes the ambiguity: the DOJ rule names WCAG 2.1 Level AA and sets deadlines, so your job is to inventory your web content and apps, prioritize the pages people actually use, and work systematically toward AA before your entity's date. If you are a private business under Title III, you have no regulation naming a version — but do not mistake that silence for freedom, because courts and demand letters overwhelmingly measure you against WCAG 2.1 AA anyway, and Title III is one of the most litigated corners of the entire ADA. In both cases the practical instruction is identical: treat WCAG 2.1 Level AA as your standard, fix the high-frequency failures first (missing form labels, low contrast, keyboard traps, unlabeled images and buttons), keep evidence of your remediation, and publish an accessibility statement. Governments get a deadline; businesses get a lawsuit risk that never really goes away. The winning move for either is the same — reach WCAG 2.1 AA and keep it there. This is general information, not legal advice; consult a qualified attorney about your specific situation.

Further Reading

Other Comparisons