WCAG 3.0 is Coming: Here’s What WordPress Agencies Need to Know
We’ve watched accessibility standards continually evolve from basic guidelines to comprehensive technical requirements. But WCAG 3.0 represents the biggest shift we’ve seen yet—and it’s going to change how we think about compliance.
The Big Picture Change
WCAG 2.2 gave us 86 success criteria organized into three conformance levels (A, AA, AAA). WCAG 3.0 is fundamentally different. Instead of pass/fail checkboxes, it introduces outcome-based guidelines built around actual user needs.
Think of it this way: WCAG 2.2 asks “Did you meet criterion 1.4.3?” WCAG 3.0 asks “Can users with low vision actually read your content?”
Key Differences That Matter
1. From Success Criteria to Requirements WCAG 3.0 uses “requirements” instead of success criteria. The current draft includes more specific tests than WCAG 2.2’s 86 criteria, but they’re organized around functional user needs rather than technical benchmarks.
2. Broader Scope WCAG 2.2 primarily addressed web content. WCAG 3.0 explicitly covers mobile apps, IoT devices, virtual reality, authoring tools, and even user agents (browsers and assistive tech). If you’re building WordPress experiences for wearables or voice interfaces, this matters.
3. New Conformance Model The pass/fail model is evolving toward “Foundational Requirements” (comparable to current AA) plus “Supplemental Requirements” for higher conformance levels. The working group is exploring points-based or percentage-based scoring rather than simple levels.
4. Focus on Actual Testing WCAG 3.0 emphasizes that automated tools can’t catch everything. The guidelines explicitly recognize that both advanced automated testing and manual testing are necessary .
What This Means for Your Agency
The good news: Content that meets WCAG 2.2 Level AA will satisfy most WCAG 3.0 foundational requirements. But “most” isn’t “all.”
The challenge: WCAG 3.0 includes additional tests and different scoring. You’ll need tools that can handle outcome-based testing, not just code-level checks.
The timeline: WCAG 3.0 is still in Working Draft status. The W3C expects organizations may continue using WCAG 2.2 while others migrate to the new standard, with transition support materials coming.
The Bottom Line
Don’t panic, but don’t wait. Start thinking about accessibility as user outcomes, not compliance checkboxes. Build testing processes that include actual browser rendering, not just code analysis.
Because when WCAG 3.0 arrives, the agencies that understand the “why” behind accessibility—not just the “what”—will be the ones helping clients navigate the transition successfully.
