ADA Title III vs Title II for Websites
ADA Title III applies to private businesses (places of public accommodation), and ADA Title II applies to state and local government entities. Both carry obligations related to web accessibility, but the specifics of those obligations differ in scope, enforcement, and technical standards.
| Key Point | What It Means |
|---|---|
| Title II Applies To | State and local government websites, including public universities, courts, transit agencies, and municipal services |
| Title III Applies To | Private businesses that qualify as places of public accommodation, such as retail, hospitality, banking, and healthcare |
| Technical Standard | Title II references Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Title III does not specify a technical standard. |
| Enforcement | Title II includes a formal rulemaking with defined conformance dates. Title III relies on litigation and Department of Justice (DOJ) guidance. |
Who Does Each Title Cover?
Title II covers any program, service, or activity of a state or local government. If a city publishes a website for paying water bills, that website falls under Title II. Public school districts, county health departments, and state DMV portals all carry Title II obligations.
Title III covers private entities that operate places of public accommodation. This includes restaurants, hotels, retail stores, banks, hospitals, and many online businesses. The ADA lists 12 categories of places of public accommodation, and courts have increasingly interpreted websites as extensions of those physical locations or as places of public accommodation themselves.
How Do the Technical Requirements Differ?
Title II now has a formal rule. The DOJ published a final rule in 2024 that specifically references WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile applications. This rule went into effect with conformance dates based on entity size.
Title III has no equivalent rule for websites. There is no DOJ regulation that specifies a technical standard for private business websites under Title III. Instead, the obligation comes from the general nondiscrimination requirement: goods and services must be accessible to people with disabilities. Courts and settlement agreements have frequently pointed to WCAG 2.1 AA as the benchmark, but it is not codified in a Title III regulation.
How Is Each Title Enforced?
Title II enforcement follows a regulatory framework. The 2024 rule establishes specific conformance dates, and government entities that do not meet WCAG 2.1 AA by those dates are in violation. The DOJ can investigate complaints and take enforcement action. Private individuals can also file lawsuits.
Title III enforcement is driven primarily by private litigation. Individuals file lawsuits alleging that a website is inaccessible and therefore violates the ADA. There is no regulatory checklist to follow. Organizations reduce risk by conforming to WCAG 2.1 AA or WCAG 2.2 AA, conducting accessibility audits, and remediating identified issues.
What This Means for Website Accessibility Programs
Government entities have a defined technical standard and a deadline. The path is clear: conform to WCAG 2.1 AA by the applicable date.
Private businesses operate with more ambiguity. The absence of a specific Title III web rule does not eliminate risk. It means the standard is established through litigation rather than regulation. Organizations that proactively adopt WCAG 2.1 AA or 2.2 AA as their conformance target, conduct regular audits, and maintain ongoing monitoring are in a stronger position to demonstrate good faith and reduce exposure.
Regardless of which title applies, the practical work is the same: evaluate web content against WCAG, identify and remediate issues, and maintain conformance over time.