Ontario businesses & non-profits: the AODA reporting deadline is December 31, 2026. Check what applies to you

Legal Compliance

ADA Website Compliance Guide

The Americans with Disabilities Act applies to websites. Learn what the ADA requires, who must comply, and the practical steps to make your website legally defensible.

What is the ADA?

The Americans with Disabilities Act (ADA) is a landmark civil rights law enacted in 1990 that prohibits discrimination against people with disabilities in all areas of public life. It covers employment, transportation, public accommodations, and more.

Although the ADA predates the modern internet, courts have consistently ruled that Title III of the ADA, which governs "places of public accommodation", applies to websites and digital services. The Department of Justice (DOJ) has repeatedly affirmed this position, and ADA website litigation has surged in recent years, with thousands of lawsuits filed annually.

Key Point: The DOJ issued a final rule in 2024 under Title II explicitly requiring state and local government websites to conform to WCAG 2.1 Level AA. For private businesses under Title III, while no equivalent rule has been finalized, courts widely apply the WCAG 2.2 standard as the benchmark for compliance.

Who Must Comply?

ADA compliance obligations differ based on the type of organization and its size. Here is a practical breakdown:

Private Businesses (Title III)

Any business that serves the public and has 15 or more employees, or that qualifies as a "place of public accommodation" (restaurants, hotels, retail stores, banks, etc.) must make their websites accessible. Courts have ruled that even online-only businesses fall under Title III.

State & Local Governments (Title II)

All state and local government entities, regardless of size, must ensure their websites and digital services are accessible. The DOJ's 2024 final rule sets WCAG 2.1 Level AA as the explicit standard for these entities.

Federal Agencies (Section 508)

Federal agencies are separately governed by Section 508 of the Rehabilitation Act. The 2017 Section 508 Refresh incorporates WCAG 2.0 Level AA as the technical standard for electronic and information technology, a lower codified bar than the Title II rule, though federal procurement often asks for more.

ADA Requirements for Websites

The ADA itself does not name a technical standard for websites. Where regulators have been explicit, they have named a specific version: the DOJ's 2024 Title II rule requires WCAG 2.1 Level AA, and Section 508 codifies WCAG 2.0 Level AA. Title III litigation and settlements have generally referenced WCAG 2.0 or 2.1 Level AA rather than a single agreed standard. Because WCAG 2.2 adds criteria without removing the earlier ones, testing against WCAG 2.2 Level AA covers those bars as well, which is why most teams choose it. Conformance at Level AA requires addressing these core areas:

Images & Alt Text

All meaningful images must have descriptive alternative text. Decorative images should have empty alt attributes.

Keyboard Navigation

All functionality must be accessible via keyboard alone. No keyboard traps. Logical focus order throughout.

Color Contrast

Text must have at least 4.5:1 contrast ratio against its background. Large text requires 3:1 minimum.

Video & Audio

Videos require captions. Audio content needs transcripts. Controls for pausing, stopping, and adjusting volume.

Text Resizing

Text must be resizable up to 200% without loss of content or functionality. Avoid using fixed font sizes in pixels.

Forms & Labels

All form fields must have associated labels. Errors must be identified clearly with suggestions for correction.

E-Commerce & Online Stores

E-commerce websites are among the most frequently targeted in ADA litigation. An inaccessible checkout process, product images without alt text, or form fields without labels can result in a lawsuit. Key considerations for online stores include:

  • Product images must have descriptive alt text (include product name, color, key features)
  • The entire checkout flow must be keyboard accessible
  • CAPTCHA, if used, must have an accessible alternative (audio CAPTCHA or alternative verification)
  • Payment forms must be properly labeled and support autofill
  • Error messages during checkout must be specific and actionable
  • Promotional pop-ups and overlays must be closeable via keyboard and not trap focus
  • PDF receipts and invoices should be accessible or accompanied by an HTML alternative

Common ADA Violations

Based on our audit experience and ADA litigation data, these are the most frequently cited accessibility failures:

Missing alt text : Images without descriptive alternative text, the most cited violation in ADA lawsuits.
Inaccessible menus & dropdowns : Navigation menus that cannot be opened or navigated using only a keyboard.
Insufficient color contrast : Light gray text on white backgrounds, or low-contrast button text.
Unlabeled form fields : Input fields that use placeholder text instead of a visible, associated label element.
Videos without captions : Auto-generated captions do not meet the standard. Captions must be accurate.
Inaccessible pop-ups and modals : Modal dialogs that cannot be dismissed with the keyboard or that do not manage focus.
Inaccessible PDFs : Scanned PDFs without text layers, or PDFs missing reading order and tags.
Auto-playing media : Videos or audio that start automatically without providing pause/stop controls.

How to Achieve Compliance

1

Conduct a Thorough Audit

Combine automated tools (axe, WAVE) with expert manual testing and screen reader testing. Automated tools catch only 25–35% of issues.

2

Prioritize Critical Paths

Fix your highest-traffic pages and most critical user flows first (checkout, contact, sign-up). Address show-stopping barriers before cosmetic issues.

3

Remediate & Test

Fix identified issues and verify each fix with assistive technology. Regression test after every major update or deployment.

4

Publish an Accessibility Statement

Document your conformance level, known limitations, and contact information for users who need assistance. This demonstrates good faith.

5

Train Your Team

Developers, designers, and content editors all contribute to accessibility. Build accessibility into your design and development process rather than auditing at the end.

6

Monitor Continuously

Accessibility is not a one-time project. Schedule regular audits, monitor for regressions, and re-test when major features are added.

Frequently Asked Questions

What standard does the ADA require for websites?

The ADA itself does not name a specific technical standard. The versions regulators have named are WCAG 2.1 Level AA (the DOJ's 2024 Title II rule) and WCAG 2.0 Level AA (Section 508); Title III litigation has generally referenced WCAG 2.0 or 2.1 Level AA. Most teams test against WCAG 2.2 Level AA because it covers the earlier versions. What conformance testing gives you is documented evidence of what was tested and what was fixed. How that evidence bears on any particular legal exposure is a question for your counsel.

Can I be sued even if my website is partially accessible?

Partial accessibility has generally not prevented claims from being brought. Demand letters and complaints are routinely filed against sites that are usable in some journeys but not others. Whether a specific barrier creates liability in your situation depends on facts and jurisdiction, and is a question for your counsel rather than for an accessibility consultant. What testing can tell you is which journeys a person using assistive technology can and cannot complete today.

Does an accessibility overlay make my site compliant?

No. Accessibility overlays, third-party JavaScript widgets that claim to auto-fix accessibility, do not achieve compliance and have been the subject of their own lawsuits. Real compliance requires fixing underlying code.

How much notice do I get before an ADA lawsuit?

Unlike some state laws (like California's Unruh Act), federal ADA website lawsuits do not require pre-suit notice. A plaintiff can file immediately. This is why proactive compliance beats reactive remediation.

This guide is technical information, not legal advice. It describes accessibility standards and how to test against them. Whether a specific obligation applies to your organization, and how to answer any regulatory filing, is a question for your counsel. No consultant can certify legal compliance or guarantee that an organization will avoid a complaint, claim, or enforcement action.
Last reviewed August 31, 2026.

Want to know where you actually stand?

Send one public URL for three manually verified findings, free, or scope a full conformance audit that documents what was tested, what failed, and what changed after remediation.

Get 3 findings on your site