← Blog
ADA ComplianceMarch 27, 2026 · 13 min read

ADA Title II vs Title III: Key Differences for Website Owners (2026)

ADA Title II just got a hard deadline: government websites must meet WCAG 2.1 AA by April 2026. Title III has no equivalent rule yet — but it drives thousands of private website lawsuits every year. Here is what each title requires, how courts interpret them, and what website owners need to do.

ADA Title II vs Title III — two-panel graphic comparing government entities (public sector, DOJ rule, mandatory compliance) and private businesses (commercial sites, litigation risk, court-accepted WCAG 2.1 AA standard)

Most coverage of ADA Titles II and III focuses on ramps, restrooms, and physical barriers. That matters — but if you manage a website, the more urgent question is digital: which title applies to your site, what does it require, and what happens if you do not comply?

The answer depends on who you are. State and local government entities fall under Title II, which now has a federally mandated WCAG 2.1 AA deadline. Private businesses fall under Title III, which has no federal web rule yet — but courts have consistently ruled that inaccessible websites violate Title III, and over 5,000 website accessibility lawsuits were filed in 2025 alone.

This guide explains both titles — their requirements, enforcement mechanisms, landmark cases, and practical compliance steps for websites.

The ADA at a Glance

The Americans with Disabilities Act (1990) is divided into five titles. Two are directly relevant to website owners:

Title IEmployment — prohibits discrimination in hiring and workplace accommodations.
Title IIPublic Services — state and local governments must make programs and services accessible, including websites.
Title IIIPublic Accommodations — private businesses open to the public must remove barriers, including on their websites.
Title IVTelecommunications — accessible phone and internet relay services.
Title VMiscellaneous — anti-retaliation, attorney fees, and ADA scope clarifications.

Section 508 is a separate law — not part of the ADA — that applies specifically to federal agencies and their contractors. If you sell software or services to the federal government, Section 508 may also apply to you. See our Section 508 compliance guide for a full breakdown.

Title II vs Title III: Side-by-Side Comparison

FeatureTitle II — Public EntitiesTitle III — Private Businesses
Applies toState and local government entitiesPrivate businesses open to the public
ExamplesCity websites, public schools, courts, transit agenciesE-commerce, restaurants, hotels, SaaS, healthcare portals
Website ruleDOJ Final Rule: WCAG 2.1 AA by April 2026No federal rule yet — courts use WCAG 2.1 AA as benchmark
Barrier removal standardFull accessibility required — no cost defense"Readily achievable" — scaled to financial feasibility
New construction/renovationMust meet ADA Standards for Accessible DesignMust meet ADA Standards for Accessible Design
EnforcementDOJ investigates complaints; private lawsuits permittedPrivate lawsuits; DOJ may also enforce
DamagesInjunctive relief + attorney fees (no monetary damages)Injunctive relief + attorney fees + potential compensatory damages in some states
Reasonable modificationsRequired — unless it fundamentally alters the programRequired for policies — e.g., allowing service animals

ADA Title II: Public Entities

Title II prohibits discrimination by state and local governments. It covers every government entity — schools, courts, transit agencies, parks, libraries — regardless of size or federal funding status.

The April 2026 Website Deadline

In April 2024, the DOJ published a Final Rule under Title II specifying that government websites and mobile apps must conform to WCAG 2.1 Level AA. Compliance deadlines depend on population size:

Entity sizePopulation servedCompliance deadline
Large50,000+April 24, 2026
SmallUnder 50,000April 26, 2027

This is the first time the DOJ has issued a specific technical standard for government web accessibility. Before this rule, government entities were required to make websites accessible under Title II but had no defined measure. For a complete breakdown of the rule and what it covers, see our guide to the ADA Title II April 2026 deadline.

Core Title II Requirements

Program accessibility: Programs and services must be usable by people with disabilities — this includes digital services, not just physical buildings.
Physical accessibility: Government buildings must have ramps, accessible restrooms, elevators, and signage meeting ADA Standards for Accessible Design.
Effective communication: Government entities must provide sign language interpreters, captioning, braille, or accessible digital formats — whichever is needed.
Reasonable modifications: Policies must be adjusted to accommodate disabilities unless doing so fundamentally alters the nature of the program.
No cost defense: Unlike Title III, Title II does not allow a "too expensive" defense. Full accessibility is required.

ADA Title III: Private Businesses

Title III requires private businesses that are "places of public accommodation" to be accessible. The ADA lists 12 categories of covered entities: restaurants, hotels, retail stores, theaters, healthcare providers, gyms, private schools, and more. If your business serves the public, Title III almost certainly applies to you.

Title III and Website Accessibility

The ADA was written in 1990 — before the web existed. The statute does not mention websites. But federal courts across multiple circuits have ruled that websites operated by places of public accommodation are covered by Title III. The logic: if a blind customer cannot use your website, they are denied equal access to your goods and services.

No federal web rule — but courts fill the gap

There is currently no DOJ final rule specifying a WCAG version for private businesses under Title III. The DOJ issued an Advance Notice of Proposed Rulemaking in 2010 but never finalized it. In the absence of a rule, plaintiffs point to WCAG 2.1 AA as the standard — and courts have accepted it. Making your site WCAG 2.1 AA compliant is the most defensible position available.

Core Title III Requirements

Barrier removal (existing structures): Remove architectural barriers if "readily achievable" — meaning easily accomplishable without significant difficulty or expense. Ramps, accessible signage, and door widening are common examples.
New construction and alterations: Any new building or significant renovation must comply fully with ADA Standards for Accessible Design — no readily achievable exception applies here.
Auxiliary aids and services: Businesses must provide aids for effective communication: large-print menus, sign language interpreters, captioned videos, screen-reader-compatible websites.
Reasonable modifications to policies: Adjust rules to accommodate disabilities — for example, allowing service animals despite a "no pets" policy, or allowing extra time for customers with cognitive disabilities.

For a checklist of what Title III compliance looks like for a small business website, see our ADA compliance checklist for small businesses.

Landmark Cases

Court decisions have shaped how both titles apply in practice — especially for websites.

Robles v. Domino's Pizza (9th Cir. 2019)

Title III

Plaintiff Guillermo Robles, who is blind, sued Domino's after its website and app were incompatible with his screen reader. The Ninth Circuit reversed a lower court dismissal and held that Title III applies to websites and apps that connect to physical places of public accommodation.

Impact

Established that websites serving customers of a physical business fall under Title III. Domino's ultimately settled. This case is widely cited in ADA website litigation.

Gil v. Winn-Dixie (11th Cir. 2021)

Title III

A visually impaired plaintiff sued Winn-Dixie after its website — used for coupons, pharmacy refills, and store locator — was not screen-reader accessible. The Eleventh Circuit ruled Title III applies to websites with a sufficient nexus to a physical place of public accommodation.

Impact

Reinforced the nexus test for applying Title III to websites. Also highlighted that a website does not need to sell products directly — service features like pharmacy refills count.

National Federation of the Blind v. Target (N.D. Cal. 2006)

Title III

One of the earliest website accessibility cases. Target's website was inaccessible to blind customers. The court held that Target's website, as an integral extension of its physical stores, was covered by Title III.

Impact

Set the template for the "nexus to physical location" argument used in thousands of subsequent cases. Target paid $6 million to settle.

Tennessee v. Lane (U.S. Supreme Court 2004)

Title II

Two individuals with mobility impairments could not access upper floors of a Tennessee courthouse. One had to crawl up the stairs to attend his own hearing. The Supreme Court held Title II allows lawsuits to enforce access to fundamental public services.

Impact

Affirmed that Title II requires government entities to provide physical access to essential services — courts, hearings, and public proceedings. Strengthened ADA enforcement against government barriers.

When Both Titles Apply

Some organizations operate under both Title II and Title III simultaneously — particularly when a public institution also offers private services.

Public universities

Title IIAcademic programs, student services, and the main institutional website fall under Title II.
Title IIIPrivately operated services on campus — bookstores, cafeterias, sports events open to the public — fall under Title III.

Airport terminals

Title IIGovernment-operated services and the public terminal areas are Title II.
Title IIIPrivately leased restaurants, retail shops, and airline lounges inside the terminal are Title III.

Public hospital systems

Title IIGovernment-run hospitals and health departments fall under Title II.
Title IIIPrivate medical practices leasing space within the building, or contracted telehealth vendors, are Title III.

Practical Compliance: What to Do

For government entities (Title II)

Audit your website and mobile app against WCAG 2.1 AA criteria — the April 2026 deadline is binding.
Develop a transition plan with documented timelines for fixing identified violations.
Ensure all public-facing PDFs, videos, and documents meet accessibility standards.
Train staff on ADA obligations, including how to handle accommodation requests.
Post an accessibility statement on your website and provide a clear contact method for accommodation requests.

For private businesses (Title III)

Run an accessibility scan of your website — WCAG 2.1 AA is the court-accepted benchmark and the most defensible standard.
Fix high-impact violations first: missing alt text, keyboard navigation failures, poor color contrast, and unlabeled form fields.
Avoid accessibility overlay widgets — courts have not accepted them as a substitute for genuine WCAG compliance.
Add an accessibility statement and a contact method so users can report issues without filing a complaint.
If you receive a demand letter, review our guide on responding to an ADA demand letter before settling.

For step-by-step guidance on correcting specific violations found in a scan, see our complete guide to fixing WCAG violations. If you have already received a demand letter, our ADA demand letter guide explains what it means and how to respond.

Check your site against WCAG 2.1 AA now

WCAGsafe scans your pages against WCAG 2.1 AA and returns a full violation list with plain-English explanations and fix instructions — free, no account required.

Run a free scan

Frequently Asked Questions

Does ADA Title III apply to websites?

Yes. Federal courts across multiple circuits have ruled that private business websites are places of public accommodation under Title III. The Ninth Circuit (Robles v. Domino's, 2019) and multiple others have held websites must be accessible. Courts use WCAG 2.1 Level AA as the benchmark. There is no federal rule specifying a WCAG version for private businesses, but the case law is clear: inaccessible websites can violate Title III.

What is the difference between ADA Title II and Title III?

Title II applies to state and local government entities — including government websites. The DOJ issued a final rule requiring WCAG 2.1 AA compliance by April 2026 for large government entities. Title III applies to private businesses open to the public. There is no equivalent federal rule for private websites yet, but courts consistently rule that inaccessible business websites violate Title III.

What WCAG standard does ADA require?

The DOJ Title II Final Rule (effective April 2026 for large government entities) requires WCAG 2.1 Level AA. For private businesses under Title III, courts use WCAG 2.1 AA as the benchmark — it is the most defensible standard to target.

Can a private business be sued under ADA Title III for an inaccessible website?

Yes. Title III allows private lawsuits, and website accessibility claims have resulted in settlements averaging $25,000–$50,000 plus attorney fees. Over 5,000 website accessibility lawsuits were filed in 2025. Many cases settle quickly to avoid litigation costs, making proactive remediation significantly cheaper than waiting.

Does a small business need to comply with ADA Title III?

Yes, with a qualification. Title III applies to all private businesses open to the public regardless of size — there is no small business exemption. The "readily achievable" standard scales barrier removal requirements to financial feasibility. However, website accessibility fixes are generally considered low-cost and therefore readily achievable for most businesses.

Related Guides