ADA Title III and Business Websites
ADA Title III requires businesses that qualify as places of public accommodation to provide equal access to their goods and services. Courts and the Department of Justice have increasingly applied this requirement to websites, meaning most business websites fall under Title III’s scope even though the law does not specify a technical standard for the web.
| Key Point | What It Means |
|---|---|
| Who It Covers | Private businesses open to the public, including retail, hospitality, healthcare, banking, and e-commerce |
| Technical Standard | Title III does not reference a specific technical standard, but WCAG 2.1 AA is the widely accepted benchmark |
| Legal Risk | Demand letters and lawsuits cite inaccessible websites as violations of Title III’s equal access obligation |
| Contrast with Title II | Title II covers state and local governments and explicitly references WCAG 2.1 AA. Title III has no equivalent mandate. |
How ADA Title III Applies to Websites
Title III of the Americans with Disabilities Act covers private entities that operate places of public accommodation. The statute lists 12 categories, including hotels, restaurants, retail stores, banks, hospitals, and places of education.
The law was written in 1990, before commercial websites existed. It does not mention websites, apps, or any digital property. However, DOJ guidance and federal court rulings have treated websites operated by places of public accommodation as extensions of those businesses. If a restaurant, retailer, or bank must be accessible in person, the logic extends to its online presence.
Why There Is No Technical Standard Under Title III
Unlike Title II, which the DOJ updated in 2024 to reference WCAG 2.1 Level AA as the conformance standard for state and local government websites, Title III has no parallel rulemaking. The DOJ withdrew its Title III web accessibility rulemaking in 2017 and has not restarted it.
This creates ambiguity. Businesses know they have a general obligation to provide accessible websites, but no federal regulation tells them exactly what that means in technical terms. In practice, WCAG 2.1 AA has become the standard that courts, plaintiff attorneys, and accessibility professionals reference. Organizations that conform to WCAG 2.1 AA are in the strongest position to demonstrate good faith.
What This Means for an ADA Title III Business Website
The absence of a defined standard does not reduce risk. It increases it. Without a clear regulatory threshold, any accessibility issue on a business website could become the basis for a demand letter or legal action.
Organizations reduce their exposure by treating WCAG 2.1 AA conformance as the target. This typically involves conducting an accessibility evaluation to identify issues, prioritizing remediation based on user impact and legal risk, and conducting regular scans to monitor for new issues over time. Scans flag approximately 25% of accessibility issues, so periodic evaluations by qualified professionals remain necessary.
Title III vs. Title II: A Practical Distinction
Title II went into effect with explicit WCAG 2.1 AA requirements and conformance deadlines for government entities. Title III carries no such specificity. For businesses, this means there is no safe harbor, no deadline to meet, and no government checklist to follow.
The practical takeaway is that Title III businesses operate under a general obligation interpreted through case law and DOJ statements. Proactive conformance with WCAG 2.1 AA is the most widely recognized way to meet that obligation.
How Organizations Respond
Businesses that take accessibility seriously typically build a repeatable program: an initial evaluation, a remediation plan, ongoing monitoring through scheduled scans, and periodic re-evaluation. An accessibility policy or statement published on the website also signals commitment and provides a feedback mechanism for users with disabilities.
The cost of an accessibility evaluation typically starts at 1,000 dollars and ranges to 3,000 dollars depending on the size and complexity of the site. This is a fraction of the cost associated with legal action.
Title III’s lack of a codified web standard does not make accessibility optional. It makes a documented, proactive approach the clearest path to reducing risk.