Answer 01 of 50
Why Web Accessibility Has Become a Legal Requirement
Web accessibility became a legal requirement through several separate laws, and which one binds you depends on who you are. In the United States, a 2024 Justice Department rule requires state and local governments to meet WCAG 2.1 Level AA by April 2027 or April 2028, depending on size, Section 508 binds federal agencies, and the ADA’s general duty covers businesses open to the public without naming a technical standard. In the European Union, the European Accessibility Act has applied to listed consumer services since June 28, 2025, with an exemption for microenterprises.
Which rule applies to you
| Who you are | Rule | Standard it names | Key dates |
|---|---|---|---|
| US state or local government | ADA Title II web and mobile app rule (adopted April 24, 2024) | WCAG 2.1 Level AA | April 26, 2027 for entities with a population of 50,000 or more; April 26, 2028 for smaller entities and special district governments |
| US federal agency | Section 508 of the Rehabilitation Act | WCAG 2.0 Level A and AA | In force |
| US business open to the public | ADA Title III general nondiscrimination duty | None in a DOJ regulation; WCAG described as helpful guidance | In force |
| Business selling listed consumer services in the EU | European Accessibility Act, Directive (EU) 2019/882 | Accessibility requirements in the Directive's annexes, enforced through national law | Applies since June 28, 2025; microenterprises providing services are exempt |
| UK public sector body | Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 | WCAG 2.2 AA in government guidance | In force |
| Any UK service provider | Equality Act 2010, or the Disability Discrimination Act 1995 in Northern Ireland | Duty to make reasonable adjustments | In force |
The sources behind each row:
- Title II. The Justice Department’s rule summary on ADA.gov and the interim final rule published April 20, 2026. That interim rule moved the original April 24, 2026 deadline to April 26, 2027 and the April 26, 2027 deadline to April 26, 2028, and states that it “does not alter the substantive requirements adopted in the 2024 final rule.”
- Section 508. The Revised 508 Standards require public-facing electronic content to “conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0” (36 CFR Part 1194, Appendix A, E205.4); Section508.gov explains how that applies to agency websites.
- Title III. The Department’s 2022 web guidance says businesses “can currently choose how they will ensure” their online offerings are accessible, calls WCAG and the Section 508 Standards “helpful guidance”, and adds that businesses “still must ensure” accessibility.
- EU. The Directive’s scope article lists covered services, including “consumer banking services” and “e-commerce services”, provided to consumers after June 28, 2025.
- UK. The government’s guidance for public sector websites names the 2018 regulations and the WCAG 2.2 AA standard, and states that “All UK service providers have a legal obligation to make reasonable adjustments under the Equality Act 2010 or the Disability Discrimination Act 1995 (in Northern Ireland).”
Exceptions that change the answer
Two exceptions are easy to miss and matter for budgets.
EU microenterprises. Article 4(5) of the European Accessibility Act says “Microenterprises providing services shall be exempt” from its service accessibility requirements. The Directive defines a microenterprise as one that “employs fewer than 10 persons” and has annual turnover or a balance sheet total not exceeding EUR 2 million. Article 32 also allows a transitional period ending June 28, 2030 for services provided with products lawfully used before the deadline. A ten-person EU web shop and a two-person one are in different positions.
Title II content exceptions. ADA.gov lists five kinds of content that do not have to meet WCAG 2.1 AA, each with conditions:
| Exception | What has to be true for it to apply |
|---|---|
| Archived web content | Created before the compliance date, kept only for reference, research, or recordkeeping, stored in a special archive area, and unchanged since it was archived (all four) |
| Preexisting conventional electronic documents | Word processing, presentation, PDF, or spreadsheet files available before the compliance date; not documents people still use to apply for or access services |
| Content posted by a third party | Posted by someone not acting for the government; not calendars, payment tools, or other vendor content the government itself posts |
| Individualized, password-protected documents | Document files about a specific person, property, or account, behind a password or other security; not the same information shown as an HTML page |
| Preexisting social media posts | Posted before the compliance date |
ADA.gov adds that the exceptions do not remove the duty of effective communication: a government “would likely still need to provide the content to a person with a disability who needs it in a format that is accessible to them.”
What the Domino’s case decided, and what it left open
Robles v. Domino’s is easy to overstate. The Ninth Circuit’s January 15, 2019 opinion held that the ADA applied to Domino’s website and app, and called the “nexus between Domino’s website and app and physical restaurants” critical to its analysis. Footnote 6 says: “We need not decide whether the ADA covers the websites or apps of a physical place of public accommodation where their inaccessibility does not impede access to the goods and services of a physical location.” The Supreme Court then denied Domino’s petition on October 7, 2019 (docket 18-1539), which left the ruling in place without deciding the question itself.
So the case is a Ninth Circuit holding tied to a business with physical locations, not a nationwide rule for every website. A business that operates only online, or that is sued in another circuit, should not assume the same reasoning applies or does not apply; that is a question for ADA counsel before deciding whether to settle or defend.
How many lawsuits, and how they are counted
Lawsuit counts depend on who is counting and which courts they include. UsableNet’s 2023 review reported “over 4,500 federal and state-filed ADA-related digital lawsuits,” and its 2025 review says that by the end of 2025, “more than 5,000 digital accessibility lawsuits had been filed”, with nearly 2,000 in New York and California state courts combined and federal filings adding another 3,100-plus. UsableNet sells accessibility services, which is worth knowing when reading its framing; the counts themselves show that state courts are a large share of the activity.
Which WCAG version you are measured against
WCAG 2.2 is the current W3C Recommendation, and WCAG 3.0 is still a Working Draft (dated September 10, 2026 at the time of writing). The version that counts for you comes from the rule that applies: WCAG 2.1 AA for US state and local governments, WCAG 2.0 AA for federal agencies under Section 508, WCAG 2.2 AA in UK public sector guidance.
Building to WCAG 2.2 AA covers the earlier versions with one wrinkle. W3C’s summary of what’s new in WCAG 2.2 says “4.1.1 Parsing is obsolete and removed from WCAG 2.2.” If a contract or policy names WCAG 2.0 or 2.1, keep testing that criterion.
Overlays and third-party components
An accessibility overlay is a script added to a site that promises to fix problems automatically. The rules above measure the content against WCAG, not the presence of a tool, and the lawsuit data shows the gap: UsableNet reported that “Over 900 companies had already invested in widgets when they were sued” in 2023.
Third-party components are your responsibility too. Title III makes it discriminatory to deny equal participation “directly, or through contractual, licensing, or other arrangements” (42 U.S.C. 12182). A chat widget, booking tool, or video player you embed is part of the service you offer. Put accessibility requirements, including the WCAG version and a remediation timeline, into vendor contracts, and test embedded tools before launch.
How much of the testing a tool can do
Automated scanners find part of the problem, and how big a part depends on what you count. In a 2017 test by the UK Government Digital Service on a page built with deliberate failures, the best tool found 41% of the barriers when its manual inspection prompts were counted, and 37% counting only errors and warnings (GDS accessibility blog). Deque’s analysis of first-time audits, covering 13,000-plus pages and nearly 300,000 issues, found 57.38% of issues by volume through automated tests, but automated issues for only 16 of the 50 WCAG 2.1 AA success criteria. Deque sells testing tools, and either way a large share of the work is manual.
The manual work has its own guides: testing with screen readers and measuring and testing contrast ratios.
Who is affected
The World Health Organization’s disability fact sheet estimates that 1.3 billion people experience significant disability, 16% of the world’s population. Accessible markup can also give search crawlers the same clear structure, meaningful text, and logical navigation that screen readers depend on.
Find your row in the first table, note the standard and date it names, check the exceptions, and fix the core journeys first: navigation, forms, checkout or service requests, and key documents. This is general information about the laws as published, not legal advice; decisions about a demand letter, settlement, or a specific compliance deadline belong with counsel who handles accessibility law in your jurisdiction.