What ADA Web Accessibility Actually Requires

What federal law actually requires

The Americans with Disabilities Act requires that people with disabilities have equal access to goods and services. Applying that to websites is where the picture divides, and the distinction matters more than most summaries admit.

Title II covers state and local governments. Here there is an actual regulation. In April 2024 the Department of Justice published a final rule adopting WCAG 2.1 Level AA as the technical standard for web content and mobile apps provided by public entities. This is binding, with dates attached.

Title III covers private businesses. Here there is no web accessibility regulation at all. The DOJ has issued guidance stating that the ADA applies to the websites of public accommodations, and it has brought enforcement actions, but guidance is not a rule, and no regulation specifies a technical standard for private-sector sites.

That gap is filled by litigation, and the federal appeals courts have not agreed. Several circuits require a "nexus" between a website and a physical location before Title III applies. Others hold that a website can be a place of public accommodation on its own, with no physical premises involved. The Eleventh Circuit's opinion in Gil v. Winn-Dixie, later vacated as moot, reflected the narrower reading; the Ninth Circuit's decision in Robles v. Domino's Pizza reflects the broader one.

The practical effect of the split is smaller than it sounds. Plaintiffs file where the law favors them, and a business selling nationally can generally be reached in a favorable forum. A narrow rule in your own circuit is not protection.

This is general background, not legal advice about any particular business. Anyone weighing actual exposure should talk to counsel who handles ADA Title III matters in the relevant circuit.

WCAG is the standard courts use

The Web Content Accessibility Guidelines, published by the World Wide Web Consortium, are the reference point in practice. WCAG 2.1 Level AA is what the DOJ adopted by regulation and what courts and settlement agreements overwhelmingly cite. WCAG 2.2, finalized in 2023, adds success criteria covering mobile interaction and cognitive accessibility.

Section 508 of the Rehabilitation Act applies to federal agencies and to organizations supplying them, and incorporates WCAG by reference through the U.S. Access Board's standards.

The deadlines that are actually in regulation

The Title II rule set compliance dates that have since moved. On April 20, 2026 the DOJ published an interim final rule extending them by one year. The technical standard did not change.

• Public entities with a population of 50,000 or more: April 26, 2027
• Smaller public entities and special district governments: April 26, 2028

A parallel rule from the Department of Health and Human Services, covering recipients of HHS funding with 15 or more employees, moved from May 11, 2026 to May 11, 2027.

These extensions are being challenged. The National Federation of the Blind filed suit in May 2026 contesting the DOJ and HHS delays. Organizations planning against the later dates should watch that case rather than treat 2027 and 2028 as settled.

There is no ADA certificate

No government agency certifies websites as accessible. There is no seal, no registry, and no test that confers immunity from a claim. Vendors selling "certification" are selling their own opinion.

Accessibility is also not binary. A site conforming to WCAG on Monday can fail on Tuesday after a content update. What holds up under scrutiny is a documented, ongoing process: audits performed on a schedule, findings prioritized, fixes shipped, and dates recorded.

Automated overlay widgets deserve specific mention. The DOJ's 2022 guidance addressed them directly, and sites using overlays have continued to be sued successfully. They are not a remedy.

What actually fails on real websites

WebAIM, part of Utah State University's Institute for Disability Research, scans the home pages of the top one million websites every year. The February 2026 scan detected 56,114,377 distinct errors, an average of 56.1 per page.

The concentration is the useful part. Six failure types account for 96% of everything detected, and they have topped the list for seven consecutive years:

• Low contrast text, found on 83.9% of home pages and rising
• Missing alternative text on images
• Missing form input labels
• Empty links
• Empty buttons
• Missing document language

None of these require specialist knowledge to find or fix. Contrast can be checked in any design tool. A form label is one attribute. That the same six have dominated for seven years suggests the barrier is process, not difficulty.

Two things the scan does not capture: it tests home pages rather than complete user journeys, and automated tools detect only a subset of WCAG requirements. Keyboard traps, focus order, and whether a screen reader can actually complete a checkout are found by people, not scanners.

Who is affected, and how

More than one in four U.S. adults, 28.7%, report some type of disability, according to CDC data drawn from the 2022 Behavioral Risk Factor Surveillance System.

The breakdown is worth knowing because it cuts against a common assumption. Cognitive disability is the most prevalent at 13.9% of adults, followed by mobility at 12.2% and independent living at 7.7%. Vision disability, which most accessibility discussion centers on, affects 5.5%. This is part of why WCAG 2.2 expanded its cognitive accessibility criteria.

On litigation volume and who gets targeted, the available figures come largely from accessibility vendors and defense law firms, both of which have an interest in the numbers. We cover what the filing data does and does not show in a separate post on who is actually being sued.

Requirements outside the United States

The European Accessibility Act took effect on June 28, 2025. It reaches many private businesses selling into the EU and relies on the EN 301 549 standard, which is closely aligned with WCAG. An organization conforming to WCAG 2.1 or 2.2 Level AA is generally positioned for it.

How we handle accessibility

We audit client sites against WCAG on a schedule and validate content updates before they go live, using WAVE and comparable tools. Our team has formal training in accessibility standards through Utah State and continuing education. Automated testing is the floor, not the ceiling, so higher-stakes sites also warrant human testing by people who use assistive technology daily.

Risingline manages content changes rather than handing clients a login. That is a deliberate choice about where accessibility, SEO, and performance decisions get made, and it means a trained person touches every update. It is a service model, not a legal requirement; plenty of organizations maintain accessible sites with in-house editors who have been trained properly.

If you want a starting point that does not involve us, run your own home page through WAVE and look at what comes back. It is free, and it will find several of the six failures above in about a minute.

We perform periodic audits for all managed clients, and offer standalone audits to any organization, including those who work with another developer and intend to keep doing so. Get in touch if you'd like one.

Sources

• WebAIM, The WebAIM Million: 2026 report on the accessibility of the top 1,000,000 home pages (March 2026)
• U.S. Department of Justice, Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments, ADA.gov
• U.S. Department of Justice, Interim Final Rule extending Title II compliance dates (91 Fed. Reg. 20902, April 20, 2026)
• W3C, Web Content Accessibility Guidelines (WCAG) 2.2
• U.S. Access Board, Section 508 Standards
• Centers for Disease Control and Prevention, Disability Impacts All of Us (updated July 2024, 2022 BRFSS data)
• European Commission, European Accessibility Act
• Risingline, ADA Website Lawsuits: Who Is Actually Being Sued