ADA compliance is mandatory for websites operated by public accommodations under Title III and state and local government entities under Title II. The Department of Justice has consistently held that the ADA applies to web content, and federal courts have ruled the same way in thousands of cases. There is no federal statute that exempts websites from the ADA. Businesses and public entities are expected to make their digital assets accessible to people with disabilities, and the working standard is WCAG 2.1 AA.
The question is not whether the law applies. It is how an organization meets the standard and documents its work.
| Question | Answer |
|---|---|
| Is it mandatory? | Yes, for public accommodations (Title III) and state/local government (Title II). |
| What standard applies? | WCAG 2.1 AA is the working standard. Title II entities have an explicit WCAG 2.1 AA rule. |
| Who enforces it? | The Department of Justice, plus private plaintiffs through civil lawsuits. |
| What is the risk of inaction? | Demand letters, federal lawsuits, DOJ investigations, and settlement costs. |
| How is conformance verified? | Through an accessibility audit conducted by a qualified auditor. |
What the ADA Says About Websites
The Americans with Disabilities Act was signed in 1990, before the commercial web existed. The statute itself does not mention websites. What it does is prohibit discrimination on the basis of disability in places of public accommodation (Title III) and in services offered by state and local governments (Title II).
The Department of Justice has taken the position for decades that websites fall within the scope of the ADA. Courts have largely agreed. The result is a body of case law that treats websites as covered by the same nondiscrimination requirements that apply to physical spaces.
For businesses open to the public, retailers, restaurants, hotels, healthcare providers, financial services, education, the website is treated as an extension of the business itself.
Title II and the WCAG 2.1 AA Rule
In April 2024, the DOJ published a final rule under Title II of the ADA that explicitly requires state and local government entities to meet WCAG 2.1 AA for their websites and mobile apps. The rule went into effect with compliance deadlines based on entity size. Large entities have until April 2026. Smaller entities have until April 2027.
This is the first time a specific technical standard has been written into federal regulation for digital accessibility under the ADA. It removes any ambiguity for public entities. The standard is WCAG 2.1 AA, and the deadline is fixed.
Title III does not yet have an equivalent regulation. But federal courts have routinely pointed to WCAG 2.1 AA as the working benchmark in private litigation, which means businesses are effectively held to the same standard even without a formal rule.
How Is ADA Compliance Enforced for Websites?
Enforcement comes from two directions. The DOJ can investigate and bring action against entities for ADA violations. Private plaintiffs can file civil lawsuits seeking injunctive relief and attorney fees.
Private litigation drives the vast majority of website accessibility cases. Thousands of federal lawsuits are filed each year, with New York, California, and Florida leading in volume. Most cases are settled rather than litigated through trial, and settlement costs typically include remediation work, attorney fees, and ongoing monitoring obligations.
Demand letters are the more common entry point. A law firm sends a letter alleging the website is not accessible, identifies issues, and offers to settle. Ignoring a demand letter often leads to a filed complaint within weeks.
What Does ADA Website Compliance Actually Require?
The legal requirement is nondiscrimination. The practical requirement is that the website work for people who use assistive technology, including screen readers, keyboard-only navigation, screen magnifiers, and voice control.
WCAG 2.1 AA is the standard that translates this into specific technical criteria. It covers things like text alternatives for images, keyboard operability, color contrast, form labels, and predictable navigation. Meeting WCAG 2.1 AA is how an organization demonstrates it has done the work.
Conformance is verified through an audit that includes manual evaluation. Automated scans flag roughly 25% of issues, which means a scan alone cannot determine whether a website meets the standard. A qualified auditor evaluates the site against each WCAG criterion and identifies issues that need remediation.
Who Is Covered Under Title III?
Title III covers private entities that operate places of public accommodation. The statute lists twelve categories, including restaurants, bars, and food service establishments; hotels, motels, and other places of lodging; hospitals, medical offices, and pharmacies; banks and financial service providers; schools, universities, and private education; gyms, theaters, and entertainment venues; retail stores and shopping centers; and professional service offices.
If a business falls into any of these categories and operates a website, the ADA applies. Ecommerce businesses with no physical location have also been held to Title III in many federal circuits.
Documentation and Defensibility
Meeting WCAG 2.1 AA is one part of the work. Documenting it is the other. An accessibility audit report, a remediation record, and an accessibility statement together form the documentation an organization needs to show what it has done.
When a demand letter or complaint arrives, the organization that can produce a recent audit report and a record of remediation is in a far better position than one that cannot. Documentation does not eliminate legal exposure, but it shifts the conversation from “the site is not accessible” to “here is the work we have done and continue to do.”
Accessible.org audit reports are written to give organizations exactly this kind of record.
Frequently Asked Questions
Does my small business website have to comply with the ADA?
If your business is a place of public accommodation under Title III, the ADA applies regardless of company size. There is no small business exemption for digital accessibility under the ADA. The practical risk varies by industry and traffic, but the legal obligation does not change based on revenue or employee count.
What happens if my website is not ADA compliant?
The most common consequence is a demand letter or federal lawsuit from a private plaintiff. Settlement costs typically include remediation, attorney fees on both sides, and sometimes ongoing monitoring commitments. DOJ enforcement is less common but carries higher stakes for larger entities and public bodies.
Is WCAG 2.1 AA the same as ADA compliance?
Not exactly. The ADA is a civil rights statute. WCAG 2.1 AA is a technical standard. Courts and the DOJ treat WCAG 2.1 AA conformance as the working benchmark for meeting ADA obligations on the web, and Title II entities are now explicitly required to meet it. For practical purposes, organizations target WCAG 2.1 AA to demonstrate ADA compliance.
How often should a website be audited?
An annual audit is a reasonable baseline for most organizations. Sites that release frequent updates, redesigns, or new templates benefit from more frequent evaluation. After significant changes to a site, a fresh audit confirms that new content and features meet the standard.
ADA compliance for websites is a legal requirement with a clear technical path. The organizations that treat it as ongoing work, audit, remediate, document, are the ones that hold up under scrutiny.
Contact Accessible.org to start your ADA compliance project.
