ADA Compliance for Websites: What Business Owners Need to Know

DEFINITION

ADA

The Americans with Disabilities Act, a federal civil rights law passed in 1990. Title III prohibits discrimination by places of public accommodation. Courts have increasingly interpreted 'places of public accommodation' to include websites, especially for businesses that also have physical locations.

DEFINITION

Title III

The section of the ADA that applies to private businesses open to the public (restaurants, hotels, retailers, service providers). Courts have applied Title III to websites of businesses that offer goods or services to the public, requiring those websites to be accessible to people with disabilities.

DEFINITION

DOJ Guidance

The Department of Justice has issued formal guidance confirming that the ADA applies to websites. In 2024, the DOJ finalized a rule requiring state and local government websites to meet WCAG 2.1 AA. While this rule directly applies to government sites, it signals the standard the DOJ considers appropriate for all websites.

DEFINITION

Structured Negotiation

A dispute resolution process where a complainant and a business negotiate accessibility improvements without filing a lawsuit. Many ADA web accessibility claims are resolved through structured negotiation rather than litigation. It typically costs less and results in an agreed-upon remediation plan.

The ADA and Websites: Where Things Stand

The ADA was written in 1990, before the commercial web existed. The law does not mention websites. But courts have spent two decades interpreting the ADA to cover digital spaces, and the DOJ has issued formal guidance confirming that web content is covered.

The practical reality for business owners: if you operate a website that offers goods or services to the public, courts and regulators expect that website to be accessible to people with disabilities. The question is not whether the ADA applies — it does — but what standard you need to meet.

What Standard Courts Expect

The ADA itself does not specify a technical standard for websites. WCAG 2.1 AA has become the de facto benchmark through DOJ consent decrees, settlement agreements, and the 2024 final rule requiring state and local government websites to meet WCAG 2.1 AA.

When courts evaluate website accessibility claims, they look at two things:

1. Is the website actually usable? Can people using screen readers, keyboard navigation, and other assistive technologies complete core tasks — making purchases, filling out forms, accessing information?

2. Did the business make reasonable efforts? Is there evidence of accessibility testing, remediation, and ongoing monitoring?

Meeting WCAG 2.1 AA and documenting your compliance efforts gives you defensible answers to both questions.

The Lawsuit Landscape

ADA web accessibility lawsuits have grown steadily. Plaintiff firms file thousands of cases annually, targeting businesses across industries. Ecommerce sites, restaurants, healthcare providers, and financial services companies are among the most frequently sued.

The typical process looks like this:

1. A plaintiff (or their attorney) identifies accessibility barriers on your website
2. You receive a demand letter claiming ADA violations
3. The letter offers to settle or threatens a lawsuit
4. If unresolved, a formal complaint is filed in federal court

Most cases settle. Settlement costs for small businesses typically range from $10,000 to $50,000, plus the cost of remediation. Fighting a case through litigation costs significantly more.

What Triggers Enforcement

The most common triggers for ADA web accessibility claims:

• Inaccessible ecommerce checkout — the plaintiff cannot complete a purchase
• Missing form labels — the plaintiff cannot fill out a contact form, application, or booking form
• Missing alt text — images convey information that the plaintiff cannot access
• Keyboard inaccessibility — the plaintiff cannot navigate the site without a mouse
• Inaccessible PDF documents — downloadable content (menus, applications, policies) that screen readers cannot read

If your site has any of these issues, you are exposed.

How to Reduce Your Risk

There is no way to guarantee you will never receive a demand letter. But you can substantially reduce your risk and build a defensible position:

Scan your site regularly. Use a tool like A11yProof to run automated scans on a schedule. Catch and fix issues before someone else finds them.

Fix issues in your source code. Overlays and widgets do not count. Courts look at whether the actual website is usable, not whether you installed a JavaScript plugin.

Document everything. Keep records of your scans, the issues you found, the fixes you applied, and the dates. This documentation demonstrates good-faith effort.

Publish an accessibility statement. Add a page to your site describing your accessibility commitment, the standard you target, and how users can contact you about barriers they encounter.

Monitor for regressions. Every code deployment, content update, and design change can introduce new accessibility issues. Scheduled scanning catches regressions before they become legal problems.

The Cost of Doing Nothing

Ignoring web accessibility creates compounding risk. Every month your site remains inaccessible, you are exposed to demand letters that cost $10,000-$50,000 to resolve. Serial plaintiff firms target the same businesses repeatedly if initial issues are not fully remediated.

The cost of proactive compliance — scanning, fixing, and monitoring — is a fraction of a single settlement. A11yProof starts at $29/month for automated scanning and remediation guidance. Even a manual audit-and-fix cycle costs less than one demand letter.

The question is not whether you can afford to make your site accessible. It is whether you can afford not to.