Skip to main content
SweepHound

Compliance

ADA Website Compliance Guide

ADA website compliance means making your site usable by people with disabilities as required by the Americans with Disabilities Act. For state and local government websites, that now means meeting WCAG 2.1 Level AA starting April 26, 2027 (for public entities serving populations of 50,000 or more) or April 26, 2028 (for smaller entities and special district governments). For private businesses under Title III, courts consistently reference WCAG AA as the expected standard, even though no explicit technical requirement has been codified. ADA website accessibility lawsuits remain active across consumer-facing sites.

ADA Title II: State and Local Government

In April 2024, the DOJ published a final rule under Title II requiring state and local government entities to make their websites and mobile apps conform to WCAG 2.1 Level AA. The compliance deadline depends on population size:

  • Entities with 50,000+ population: April 26, 2027.
  • Entities with fewer than 50,000 and special district governments: April 26, 2028.

This is the first time the ADA has specified an explicit technical standard for digital accessibility. It covers all web content a government entity makes available to the public, including forms, documents, and interactive tools.

ADA Title III: Private Businesses

Title III covers “places of public accommodation” — hotels, restaurants, retail stores, banks, and other businesses open to the public. The DOJ has stated that websites of covered entities are included, but no final rule specifies a technical standard yet.

In practice, federal courts have consistently held that inaccessible websites violate Title III, and settlements and consent decrees routinely reference WCAG 2.1 AA as the target. Treating WCAG AA as your benchmark is a common recommendation from accessibility consultants and counsel.

ADA Lawsuit Trends

ADA digital accessibility litigation has been rising steadily:

  • 3,948 ADA website lawsuits filed in 2025, up 23.84% from 2024 according to EcomBack.
  • E-commerce sites are the primary target, accounting for approximately 69% of all filings.
  • Plaintiff firms use automated scanning tools to identify sites with obvious violations — missing alt text, broken form labels, and insufficient color contrast — before filing.
  • Legal exposure can include defense costs, remediation work, settlement costs, and ongoing monitoring requirements.

A practical first step for reducing accessibility risk is to remediate confirmed issues that automated scanners can flag, then follow with manual keyboard, screen reader, and user-flow review.

Steps Toward ADA Compliance

1. Audit Your Site

Start with an automated scan to identify machine-detectable violations. SweepHound checks many common WCAG failure patterns in minutes and generates recommended manual follow-up for key pages and user flows. Follow up with testing using a keyboard, screen reader, and the testing checklist to catch issues automation misses.

2. Fix Priority Issues

Address critical and serious violations first: missing alt text, broken form labels, keyboard traps, and color contrast failures. These represent the highest legal risk and the biggest usability barriers.

3. Monitor Continuously

Accessibility is not a one-time fix. Content updates, new features, and third-party widgets introduce regressions. Schedule regular scans and integrate accessibility checks into your development workflow.

4. Publish an Accessibility Statement

An accessibility statement demonstrates good faith. Include the standard you target (WCAG 2.2 AA), known limitations, and a way for users to report issues. While not strictly required by the ADA, it is required by the EAA and is considered best practice.

Find out where your site stands today. Try SweepHound's free scan to run an automated WCAG scan and get actionable remediation guidance for confirmed findings.