TL;DR: In 2026, three things drive web accessibility requirements. The European Accessibility Act (EAA) has been enforceable since June 28, 2025. In the US, the ADA Title II rule for state and local governments still applies, but the compliance deadlines were extended in April 2026, to roughly April 2027 for larger entities and April 2028 for smaller ones. WCAG 2.2 is the current technical standard almost everything points to. The dates matter, but the work does not change: audit, fix, test, and maintain. Do not wait for a deadline to start.

Important: This article is for general information only. It is not legal advice, deadlines and interpretations change, and the ADA Title II dates in particular were recently revised. Confirm the current requirements that apply to you with qualified legal counsel and the official sources (ada.gov and the EU) before acting.

2026 is a pivotal year for web accessibility, but there is a lot of outdated information circulating, including about a US deadline that was recently changed. Here is the accurate picture of what applies, who it covers, and what to do about it.

The European Accessibility Act (EAA), in force now

The EAA is an EU directive that requires a wide range of products and services to be accessible. All 27 EU member states have transposed it into national law, and enforcement began on June 28, 2025. So this is not a future deadline. It is already in effect.

• Who it covers: businesses offering certain products and services in the EU, such as e-commerce, banking, transport, and e-books, including companies based outside the EU that sell into the EU market. Some small microenterprises providing services are exempt.
• The standard: conformance generally maps to WCAG through the EU standard EN 301 549. An updated version (v4.1.1), which incorporates WCAG 2.2, is expected to publish in 2026.
• The stakes: enforcement is underway, with penalties that vary by country and can reach into the tens or hundreds of thousands of euros.

If you sell into the EU, this is the requirement to check first, because it is live.

ADA Title II (US state and local government), deadlines extended

In the US, the Department of Justice finalized a rule under ADA Title II in April 2024 requiring state and local governments to make their web content and mobile apps accessible to WCAG 2.1 Level AA.

Here is the part where a lot of published guidance is now wrong. The original rule set an April 24, 2026 compliance date for larger public entities. In April 2026, the DOJ issued an interim final rule extending those deadlines. As a result:

• Larger public entities (population 50,000 or more): now approximately April 2027.
• Smaller public entities and special district governments: now approximately April 2028.
• Who it covers: state and local governments and their instrumentalities, such as public universities and school districts. Importantly, this also reaches the private vendors and contractors who build and manage those websites and apps.
• The standard: WCAG 2.1 Level AA.

Because these dates were revised so recently, confirm the exact current deadline for your entity type on ada.gov before relying on it.

What about private US businesses (ADA Title III)?

Private businesses are covered by ADA Title III, and here the situation is different: there is no specific federal regulation setting web technical standards or dates for them. That does not mean they are safe. Website accessibility lawsuits under Title III continue at a high volume every year, and courts and plaintiffs generally treat WCAG 2.1 or 2.2 Level AA as the practical benchmark.

So for a private US company, the honest guidance is: there is no single deadline, but the legal exposure is real and ongoing, and WCAG AA is the standard to aim for.

WCAG 2.2: the standard almost everything points to

Across all of the above, the common thread is WCAG, and the current version is WCAG 2.2 (published by the W3C in 2023). It builds on WCAG 2.1 by adding criteria around focus visibility, target size, dragging movements, and consistent help.

Aiming for WCAG 2.2 Level AA is a sensible target, because it satisfies the current technical bar and positions you ahead of standards that are moving toward it (such as the EU's updated EN 301 549).

The 2026 landscape at a glance

RequirementRegionStatus in 2026StandardEuropean Accessibility ActEUIn force since June 28, 2025WCAG via EN 301 549ADA Title II (large entities)US (state/local gov)Deadline extended to ~April 2027WCAG 2.1 AAADA Title II (smaller entities)US (state/local gov)Deadline extended to ~April 2028WCAG 2.1 AAADA Title IIIUS (private business)No set date, ongoing lawsuit riskWCAG 2.1 / 2.2 AA (de facto)WCAG 2.2GlobalCurrent standardn/a

What to do now, regardless of the dates

The deadlines will keep shifting, but the actual work does not. Whether your date is 2026, 2027, or "no fixed date but real risk," the path is the same:

• Audit your site against WCAG 2.2 AA, using both automated scans and manual testing.
• Fix the issues in your code, starting with the high-impact, high-frequency ones like color contrast, labels, and keyboard access.
• Test with real assistive technology (a screen reader and keyboard), and ideally with real users.
• Add a personalization layer so visitors can adjust the experience to their needs.
• Monitor over time, because accessibility drifts as you ship new content.

Waiting for a deadline is the expensive way to do this. Starting now spreads the work out and lowers your risk immediately.

Where AccessBit fits

Accessibility compliance is not a single product you install. It is remediation in your code, testing, and giving users control. AccessBit is the personalization layer in that stack: it lets visitors adjust contrast, motion, text, and reading preferences to suit them.

To be clear about what that means: a personalization layer improves the experience for many users, but it does not, on its own, make a site meet WCAG or satisfy a law. The underlying issues still have to be fixed in the site. Any tool that claims a one-click path to "full compliance" is overstating what is possible, and regulators have taken action against exactly those claims.

Frequently asked questions

1. Is the European Accessibility Act in effect?

Yes. The EAA has been enforceable since June 28, 2025, across all EU member states, and it can apply to non-EU businesses that sell products or services into the EU.

2. When is the ADA Title II web accessibility deadline?

The original deadlines were extended by the DOJ in April 2026. They are now approximately April 2027 for larger public entities (population 50,000 or more) and April 2028 for smaller ones. Confirm the exact current date for your entity on ada.gov.

3. Does the ADA require private business websites to meet a specific standard?

There is no federal regulation setting a specific technical standard or date for private businesses under ADA Title III. However, accessibility lawsuits are common, and WCAG 2.1 or 2.2 Level AA is treated as the practical benchmark.

4. Which WCAG version should I target in 2026?

WCAG 2.2 Level AA. It is the current version and aligns with where other standards, including the EU's, are heading.

5. Can an accessibility overlay make my site compliant?

No. A personalization layer or overlay can help users adjust their experience, but it does not fix underlying code issues or, by itself, make a site meet WCAG or a legal requirement. Real compliance comes from remediation, testing, and ongoing maintenance.

Want a clear picture of where your site stands?

The requirements are shifting, but the work is knowable. AccessBit is the personalization layer that sits on top of a properly remediated, tested site, so your visitors can tailor their experience while you meet the baseline in your code.