WCAG 3.0 Is Coming: What the March 2026 Working Draft Means for WordPress Site Owners

The W3C published an updated WCAG 3.0 Working Draft on March 3, 2026 — the most significant revision yet to the document that will eventually replace the WCAG 2.x standards that govern web accessibility compliance today. If you run a WordPress site and you’re just getting up to speed on WCAG 2.2, you might wonder whether WCAG 3 should already be on your radar. The short answer: yes, but not in the way you might think.

What Is WCAG 3, and Why Does It Matter?

WCAG — the Web Content Accessibility Guidelines — has been the backbone of digital accessibility law and policy worldwide since the late 1990s. WCAG 2.0 arrived in 2008, WCAG 2.1 in 2018, and WCAG 2.2 in 2023. All of them share the same foundational architecture: success criteria, conformance levels (A, AA, AAA), and a pass/fail testing model.

WCAG 3 is a ground-up rethink. The W3C’s Accessibility Guidelines Working Group (AG WG) has been developing it for several years, and the March 2026 draft represents a meaningful step forward in its maturity. One of the first things to know: the name itself has changed. “WCAG” no longer stands for “Web Content Accessibility Guidelines” — it now stands for W3C Accessibility Guidelines. That shift in name signals a shift in scope: WCAG 3 is designed to cover more than just web content, extending to native mobile apps, emerging technologies, and beyond.

What Changed in the March 2026 Draft

The March 2026 update is substantial. Here’s what’s new or clarified:

Terminology Overhaul

The draft replaces the word “Outcomes” with “Requirements” — a change that may seem minor but matters a lot for how the document is read and applied. Guidelines are now written as outcome statements rather than rules, making the intent clearer even if the path to compliance is less prescriptive than WCAG 2.x.

New Sections on Best Practices and Conformance

The updated draft adds sections covering best practices and a conformance model that is still actively being developed. Conformance in WCAG 3 is expected to be more nuanced than the binary pass/fail structure of WCAG 2.x — likely incorporating scoring or maturity-based approaches. The details are not finalized, and the working group has indicated that a projected timeline for WCAG 3 will be published by April 2026.

174 Requirements at “Developing” Status

Deque Systems reported that the March draft contains 174 requirements that have reached “Developing” status — meaning they are substantive enough to review and provide feedback on, but not yet finalized. This is progress, but WCAG 3 remains a long way from becoming a W3C Standard.

What WCAG 3 Does NOT Change Right Now

Here is the most important thing for WordPress site owners to understand: WCAG 3 is not law yet, and it won’t be for years.

The current legal standard for web accessibility in the United States — including the ADA Title II rule that takes effect April 24, 2026 for larger government entities — requires WCAG 2.1 Level AA compliance. The European Accessibility Act, which takes effect in June 2025, references EN 301 549, which in turn references WCAG 2.1 AA. No jurisdiction has adopted WCAG 3 as a legal requirement, and none is expected to do so in the near term.

If you’re focused on legal compliance, your target remains WCAG 2.1 AA (or WCAG 2.2 AA, which is the current published version and a superset of 2.1). WCAG 3 is something to watch and learn about, not something to build compliance programs around today.

Why WordPress Site Owners Should Pay Attention Anyway

Even though WCAG 3 isn’t legally binding, there are practical reasons to follow its development:

• Future-proofing. If your site is built on strong semantic HTML, logical heading structure, and real accessibility fixes (not overlay hacks), you’ll be well-positioned for whatever WCAG 3 ultimately requires. The underlying principles — perceivable, operable, understandable, robust — aren’t going away.
• Procurement and vendor requirements. Enterprise clients, government contractors, and educational institutions are already asking vendors about WCAG 3 readiness. Knowing the roadmap helps you answer those questions.
• Conformance model changes may favor quality over checkbox-ticking. WCAG 3’s move away from binary pass/fail toward a more holistic approach could reward sites that have genuinely invested in accessibility over those that passed automated scans by accident.
• The scope expansion matters for plugin developers. If you build or rely heavily on WordPress plugins, WCAG 3’s expanded scope — covering interactive components and dynamic content more rigorously — could affect how those plugins need to be built.

What You Should Actually Do Today

Given where things stand, here is a practical framework for WordPress site owners:

1. Get to WCAG 2.2 AA now. This is the current standard, it’s what auditors check against, and it’s what the law is moving toward. Don’t wait for WCAG 3.
2. Fix real code issues — don’t mask them. Accessibility overlays won’t satisfy WCAG 2.x auditors, and they certainly won’t hold up under WCAG 3’s more holistic approach. Identify and fix actual issues in your markup.
3. Run regular automated scans. Automated tools catch a meaningful portion of WCAG failures — missing alt text, poor contrast, missing form labels, improper heading hierarchy. They’re not a substitute for manual testing, but they’re a solid first line of defense.
4. Monitor WCAG 3 development. Bookmark the W3C WCAG 3 introduction page and review the AG WG’s timeline when it’s published in April 2026. Understanding where things are headed helps you plan.
5. Document what you’re doing. Whether under WCAG 2 or 3, demonstrating a good-faith effort to identify and address accessibility issues matters — both legally and reputationally.

Take Action

WCAG 3 is coming, but WCAG 2.2 AA compliance is what you need right now. LEWCA helps WordPress site owners get there. The LEWCA scanner identifies real code-level accessibility issues — the kind that actually fail audits and invite lawsuits — rather than applying a cosmetic overlay that fools nobody. Pro users get AI-powered fix suggestions, scheduled scans, and compliance reports you can share with stakeholders. Start with the free version at lewca.com/download, or see what Pro includes at lewca.com/pricing. The April 24 deadline is less than a month away — there’s no better time to find out where your site actually stands.