The ADA and the European Accessibility Act (EAA) are laws; WCAG is a technical standard. They are related, but “WCAG compliant” is not a universal legal finding: the applicable requirements depend on the jurisdiction, organization, product or service, exceptions, and the standards incorporated by the relevant rule.
For U.S. state and local governments covered by the Department of Justice’s Title II web rule, the specified standard is WCAG 2.1 Level AA. The EAA covers specified products and consumer services in the EU, with application beginning June 28, 2025, subject to its scope and transitional provisions. Private U.S. businesses have ADA obligations, but DOJ’s general web guidance does not set a detailed technical standard for their websites.
As an Amazon Associate I earn from qualifying purchases.
What is the difference between ADA, EAA, and WCAG?
The ADA (Americans with Disabilities Act) is a U.S. federal civil-rights statute. The EAA is an EU directive implemented through Member State law. WCAG (Web Content Accessibility Guidelines) is a set of technical guidelines published by the World Wide Web Consortium (W3C), not a law. Laws and standards can work together: a law establishes obligations, while a technical standard can specify ways to assess or meet accessibility requirements.
| Question | ADA | European Accessibility Act | WCAG |
|---|---|---|---|
| What is it? | U.S. civil-rights law. DOJ has a specific web and mobile-app rule for state and local government entities under Title II. | Directive (EU) 2019/882, implemented in national law, covering listed products and services. | W3C technical guidelines with testable success criteria and conformance levels. |
| What is in focus? | Title II’s web rule covers web content and mobile apps provided or made available by state and local government entities. ADA obligations also apply more broadly, including to businesses open to the public. | Specified consumer products and services, including e-commerce, consumer banking, e-books, and certain transport and electronic communications services. | Digital content and experiences assessed against its criteria. It is used in legal and procurement contexts, but is not itself a statute. |
| Technical reference | WCAG 2.1 Level AA under the DOJ Title II web rule. | The directive sets accessibility requirements. Organizations commonly use WCAG and EN 301 549; the applicable harmonized standard and national rules must be checked for the specific case. | WCAG 2.1 and later versions are maintained by W3C. Which version applies depends on the law or procurement requirement. |
| Key timing | The DOJ factsheet retrieved October 3, 2026 lists April 26, 2027 or April 26, 2028 for Title II compliance, depending on entity category and population. | Applies from June 28, 2025 to covered products placed on the market and consumer services provided after that date, subject to scope and transitional provisions. | A WCAG publication date is not, by itself, a legal compliance deadline. |
The U.S. dates above come from the DOJ’s current Title II factsheet as of October 3, 2026. They may change; verify the latest DOJ information and applicable regulation before relying on them.
#1 Best Overall
Does WCAG compliance mean a website is ADA compliant?
No. WCAG conformance may be relevant evidence of accessibility, and a law or contract may require a particular WCAG version and level. But WCAG conformance alone does not establish that an organization has met every applicable legal obligation. The law, entity type, digital content, effective date, exceptions, and any other duties still matter.
State and local government websites and apps
The DOJ’s 2024 Title II final rule specifies WCAG 2.1 Level AA for web content and mobile apps provided or made available by state and local government entities. The rule can also reach content provided through third parties under arrangements with a public entity. Under the DOJ factsheet retrieved October 3, 2026, covered entities serving 50,000 or more people have until April 26, 2027; entities serving fewer than 50,000 and special district governments have until April 26, 2028. Check the factsheet again before acting because the dates are subject to change.
Private businesses in the United States
DOJ’s general ADA web guidance says that nondiscrimination and effective-communication provisions apply to businesses open to the public. It does not prescribe a detailed technical standard for their websites, and the guidance warns that it predates the 2024 Title II rule. Do not treat Title II’s express WCAG 2.1 Level AA requirement as a universal rule for every private website. The obligations for a particular business depend on its circumstances and applicable law; a specific legal conclusion requires case-specific analysis.
Recommended Free Tools
Does the European Accessibility Act apply to an online store?
It can: e-commerce is among the services covered by the EAA. But the directive is not a rule for every website or every digital product. Assess whether the service, consumer audience, provider, and relevant content fall within the directive and the national law implementing it.
Products covered by the directive
- General-purpose consumer computer hardware and operating systems.
- Payment terminals and certain ATMs, ticketing machines, check-in machines, and interactive information terminals.
- Consumer terminal equipment used for electronic communications or access to audiovisual media services.
- E-readers.
Services covered by the directive
- Electronic communications and access to audiovisual media services.
- Specified elements of passenger transport services.
- Consumer banking, e-books and dedicated software, and e-commerce.
- Answering emergency communications to 112.
The directive applies from June 28, 2025 to covered products placed on the market and services provided to consumers after that date, subject to transitional provisions. Its scope and exclusions should be assessed under Directive (EU) 2019/882 and the relevant Member State’s implementing law.
Important EAA exclusions and exemption
- Certain prerecorded time-based media and office file formats published before June 28, 2025 are excluded.
- Online maps are excluded when essential information is made accessible digitally.
- Content that the economic operator neither funds, develops, nor controls is excluded.
- Qualifying archived content that has not been updated or edited after June 28, 2025 is excluded.
- Microenterprises providing services are exempt from the directive’s accessibility requirements and related obligations. This service-provider exemption should not be generalized to all small companies or to microenterprises dealing in products.
What WCAG level does the ADA require?
For web content and mobile apps covered by the DOJ Title II rule, the specified technical standard is WCAG 2.1 Level AA. That statement is limited to the entities and content within that rule; it is not a blanket statement about every website covered by the ADA. The DOJ’s separate general guidance for businesses open to the public does not establish a detailed technical standard for private-business websites.
Rank #4
There is no single WCAG level that can be declared universally controlling for both the ADA and the EAA. Identify the governing law or procurement requirement first, then confirm which standard version and conformance level it specifies.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to work out which requirements apply
- Identify where you operate and offer the product or service. Consider U.S. federal requirements and, for EU-facing activity, relevant EU and Member State law.
- Classify the organization. Determine whether you are a U.S. state or local government entity, a private business, an EAA service provider, or a manufacturer or seller of a covered product.
- Name the specific digital subject. Identify the website, app, product, service, and content at issue; do not assume that all online content falls into the same legal category.
- Find the rule and technical reference. Check the applicable law, national implementation, procurement contract, or other binding requirement for the standard version and level it calls for.
- Check dates and exceptions. Account for the relevant deadline, EAA transition provision, content exclusion, or qualifying exemption. Do not assume that an exemption for one category applies to another.
- Document the assessment and actions. Keep a record of the scope you assessed, applicable requirements, issues found, remediation, and any relevant exception or burden analysis. A technical test result does not itself settle legal compliance.
How to use WCAG in an accessibility program
Use WCAG as a technical assessment framework when it is relevant to the applicable law, contract, or accessibility program. W3C explains that organizations addressing the EAA commonly use WCAG and European Standard EN 301 549. That practical relationship does not make WCAG the EAA statute or prove that conformance alone resolves every obligation, product requirement, documentation duty, exception, or national enforcement question.
Best Value
Accessibility audits and testing can help teams identify issues; training can help staff prevent recurring barriers. Neither a tool, a course, nor a single test result establishes legal compliance. Match the assessment to the applicable requirements and seek qualified legal advice when the scope or obligations are uncertain.
Capture visual evidence without treating it as an accessibility test
A screenshot can record what a page looked like at a particular capture, which may help a team keep visual evidence alongside its accessibility review. It cannot establish keyboard access, screen-reader behavior, or legal compliance. ScreenshotNeo is a website screenshot API and MCP server; it is an optional way to capture a page, not an accessibility auditor.
Or skip the browser setup
Make one GET request using your ScreenshotNeo API key; see the ScreenshotNeo API documentation for request details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://screenshotneo.com -o shot.webpScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. Its MCP server offers the tools take_screenshot, get_page_info, and capture_pdf for AI agents using Claude, Cursor, or another MCP client. The free plan includes 1,000 screenshots per month with no card required; paid plans start at $5 for 3,000 screenshots.
Sign up for 1,000 free screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
