ADA Compliance Checker

The Americans with Disabilities Act (ADA) is a US federal civil rights law passed in 1990 that prohibits discrimination against people with disabilities. Although the law predates the modern web, courts have consistently ruled that Title III — which covers “places of public accommodation” — applies to business websites and mobile apps. The Department of Justice has repeatedly stated that WCAG 2.1 Level AA is the technical standard courts should use to evaluate whether a website is ADA compliant. Over 4,000 ADA web accessibility lawsuits were filed in 2023 alone, and the number continues to climb each year.

Any business operating in the United States with a public-facing website
E-commerce stores, SaaS platforms, online services, and marketplaces
Restaurants, hotels, retail stores, and service providers with online presences
Educational institutions, healthcare providers, and financial services
Mobile applications connected to business operations

$75,000

Maximum civil penalty for a first ADA violation by the DOJ.

$150,000

Maximum civil penalty for subsequent ADA violations.

$25K–$75K

Average private lawsuit settlement range for ADA web accessibility claims.

4,000+

ADA web accessibility lawsuits filed in 2023 — a record and still climbing.

The Americans with Disabilities Act and Website Accessibility: A Complete Guide

The Americans with Disabilities Act (ADA), signed into law by President George H.W. Bush in 1990, was originally conceived to eliminate barriers in physical spaces — ramps for wheelchairs, Braille signage, accessible restrooms. The internet as we know it barely existed. But the law's broad mandate in Title III, requiring “places of public accommodation” to be accessible to people with disabilities, has proven remarkably durable. Over three decades of regulatory guidance, litigation, and rulemaking have extended that mandate squarely into the digital world.

A Brief History of ADA Web Accessibility

For years after the ADA's passage, the Department of Justice (DOJ) signaled that websites operated by businesses open to the public fell under Title III, but never issued a formal rule. In 2010, the DOJ published an Advance Notice of Proposed Rulemaking (ANPRM) explicitly proposing web accessibility standards for public accommodations. That rulemaking stalled for years, but the legal landscape didn't wait for regulators.

In 2017, Gil v. Winn-Dixie Stores became one of the first federal trials to find that a grocery chain's inaccessible website violated the ADA. The court ordered Winn-Dixie to conform its site to WCAG 2.0 Level AA.

The real landmark came in 2019 with Robles v. Domino's Pizza. Guillermo Robles, who is blind, sued Domino's because he could not order food through their website or mobile app using a screen reader. Domino's argued that the DOJ had never issued specific web accessibility regulations, so no obligation existed. The Ninth Circuit disagreed, and the Supreme Court declined to hear Domino's appeal.

The DOJ finally acted decisively in April 2024, publishing a final rule under Title II requiring state and local government websites to meet WCAG 2.1 Level AA. For practical purposes, WCAG 2.1 AA is the standard that courts, regulators, and plaintiff attorneys now treat as the measuring stick for ADA web compliance.

What WCAG 2.1 AA Actually Requires

The Web Content Accessibility Guidelines are organized around four foundational principles, collectively known by the acronym POUR:

Perceivable — Information must be presentable to users in ways they can perceive. Text alternatives for images, captions for video, sufficient color contrast (at least 4.5:1 for normal text).
Operable — Every function available by mouse must also work by keyboard. Users must have enough time to interact with content. No flashing that causes seizures.
Understandable — Page language must be declared. Form inputs need labels and clear error messages. Navigation must be consistent across pages.
Robust — Content must work with assistive technologies. Semantic HTML, proper ARIA roles, and programmatically associated form labels.

Common Violations That Trigger Lawsuits

ADA web accessibility lawsuits target specific, well-documented failures:

Missing or empty alt text on images. The single most common WCAG failure. Every meaningful image needs a concise, descriptive text alternative.
No keyboard navigation. Dropdown menus, modals, and custom widgets built with mouse-only handlers are invisible to keyboard users.
Inaccessible forms. Fields without labels, error messages communicated only through color, CAPTCHAs with no accessible alternative.
Insufficient color contrast. Light gray on white, colored links indistinguishable from body text. WCAG requires 4.5:1 for normal text, 3:1 for large text.
Missing captions on video. Excludes deaf and hard-of-hearing users.
Missing page language declaration. Without a lang attribute on the <html> element, screen readers can't determine pronunciation.

How Plaintiff Firms Find Targets

ADA web accessibility litigation is a volume business. A small number of plaintiff firms account for the majority of demand letters:

Automated scanning at scale. Firms use tools to crawl thousands of websites and flag violations. A site with 50+ automated failures is a soft target.
Industry targeting. E-commerce, hospitality, healthcare, and financial services are disproportionately targeted because their sites are transactional.
Serial filers. Some plaintiffs file hundreds of lawsuits per year. A single firm might generate 500+ demand letters in a quarter.

If your site has basic accessibility failures that an automated scanner can detect in seconds, you are visible to these firms. Fixing the detectable issues removes you from their target list.

Steps to Achieve ADA Compliance

1. Audit your current state. Run an automated scan to catch machine-detectable violations. Follow up with manual testing: navigate by keyboard, test with a screen reader.
2. Remediate by priority. Fix critical barriers first (keyboard traps, missing form labels), then moderate issues (contrast, headings), then lower-severity items.
3. Monitor continuously. Every new page or design update can introduce violations. Run periodic scans monthly at minimum.
4. Document your efforts. Publish an accessibility statement describing your commitment, the standard you target (WCAG 2.1 AA), and a way for users to report barriers. In litigation, documented good-faith effort is a meaningful defense.

Automated Testing vs. Manual Testing

Automated tools reliably catch images without alt attributes, form inputs without labels, color contrast failures, missing document language, and basic ARIA misuse — roughly 30-40% of WCAG criteria. The remaining 60-70% require human judgment: Is this link text meaningful? Does this custom widget communicate its state to assistive technology? The most effective approach combines both.

What a Remediation Guide Includes

A wcagrepair remediation guide is a prioritized, page-by-page breakdown of every accessibility issue. For each violation: the WCAG criterion, the failing element, the impact on users, and a concrete fix — often including the exact HTML or CSS change needed. Issues are ranked by severity so you know what to fix first.

At $8.99, a remediation guide costs less than a single hour of a developer's time and a tiny fraction of the $5,000–$150,000+ that ADA demand letters typically seek.

Is my website required to be ADA compliant?

If your business is open to the public — a store, restaurant, hotel, medical practice, bank, or any other “place of public accommodation” under ADA Title III — courts have consistently held that your website must be accessible. The Ninth Circuit's 2019 ruling in Robles v. Domino's Pizza established that websites and mobile apps connected to a physical business are covered. Even purely online businesses have been sued successfully in several circuits. The practical answer: if customers interact with your business through your website, you should treat ADA web accessibility as a legal requirement.

What happens if I get an ADA demand letter?

An ADA demand letter typically comes from a plaintiff's attorney alleging that your website has specific accessibility barriers that violate Title III. The letter usually demands a monetary settlement (commonly $5,000–$25,000 for a first offense) and a commitment to remediate your site to WCAG 2.1 AA within a set timeframe. If you ignore it, the next step is a federal lawsuit. The best response is to consult an attorney experienced in ADA defense, begin remediating the cited issues immediately, and document your efforts. Having a remediation guide and an accessibility statement already in place significantly strengthens your negotiating position.

Does ADA require WCAG 2.1 or 2.0?

The ADA itself does not name a specific WCAG version — it prohibits discrimination on the basis of disability without prescribing a technical standard. However, the DOJ's 2024 final rule under Title II explicitly adopted WCAG 2.1 Level AA as the required standard for state and local government websites. Courts in Title III cases have overwhelmingly pointed to WCAG 2.0 AA or WCAG 2.1 AA as the benchmark. Since WCAG 2.1 is a superset of 2.0, targeting WCAG 2.1 AA covers both and aligns with the direction regulators are moving.

Can I use an overlay widget for ADA compliance?

Accessibility overlay widgets — JavaScript tools that claim to make your site compliant by injecting modifications on the client side — are not a reliable path to ADA compliance. Over 800 accessibility advocates have signed a public statement opposing overlays. The National Federation of the Blind has actively opposed them. Multiple lawsuits have been filed against sites using overlays, and courts have not accepted an overlay as a defense. The only reliable approach is fixing the underlying HTML, CSS, and JavaScript of your site.

How often should I test for ADA compliance?

At minimum, run an automated accessibility scan monthly and conduct a thorough manual audit at least once a year. Beyond that, test whenever you make significant changes: a redesign, a new checkout flow, a CMS migration, a new plugin, or a major content update. Accessibility regressions are common and continuous monitoring catches them before they become lawsuit material.

What's the difference between ADA and Section 508?

The ADA (Title III) applies to private businesses that are “places of public accommodation.” Section 508 applies to federal agencies and organizations receiving federal funding. If you are a private business, the ADA is your primary concern. If you are a federal contractor or government agency, Section 508 applies directly and WCAG 2.0 AA conformance is a hard contractual requirement.

Automated ADA audit mapped to WCAG 2.1 success criteria your regulation requires
Severity breakdown by critical, major, and minor issues to prioritize remediation
AI-generated remediation guide with copy-paste code fixes for every issue
Ongoing monitoring to stay compliant as your site changes
Downloadable compliance certificate showing your site's current audit status

ADA Compliance Checker

What is ADA?

Who Needs to Comply?

Penalties for Non-Compliance

ADA Compliance: The Complete Guide