“what is WCAG 3.0 and when will it be released”
WCAG 3.0 is the next generation of the Web Content Accessibility Guidelines, currently in draft with the W3C. Unlike the pass or fail model of WCAG 2.x, it introduces a scored system with Bronze, Silver, and Gold conformance tiers. WCAG 3.0 has no confirmed release date yet, and the W3C has stated it will remain a working draft for an extended review period, so WCAG 2.2 remains the standard to build toward today.
Why WCAG 3.0 Is a Bigger Shift Than It Sounds
Every WCAG version so far, 2.0, 2.1, and 2.2, has followed the same basic structure: a list of success criteria, each one either pass or fail, rolled up into A, AA, or AAA conformance levels. WCAG 3.0 rethinks that structure from the ground up. Instead of a binary pass or fail per criterion, it introduces a points based scoring system, and instead of A, AA, AAA, it introduces Bronze, Silver, and Gold overall ratings. This isn’t a minor update. It’s a genuinely different way of measuring accessibility, which is part of why it’s taken years in draft and why the W3C has been deliberately cautious about finalizing it.
The New Bronze, Silver, Gold Model
Bronze is the proposed entry level tier, roughly comparable in spirit to today’s AA level, though the underlying scoring method is different enough that direct comparisons aren’t exact. Silver sits above Bronze, requiring a higher overall score across tested criteria along with broader coverage of different disability types. Gold is the highest proposed tier, intended for organizations treating accessibility as a core product differentiator rather than a compliance minimum. Rather than every success criterion counting equally, WCAG 3.0’s draft scoring weighs criteria based on real world impact, meaning some fixes could matter more toward your score than others. This is meant to reduce a problem in the current system, where a site can technically pass WCAG 2.2 AA while still being genuinely difficult for real users in practice.“Get ahead of the curve. See how Accessify tracks emerging WCAG 3.0 standards.”
APCA: A New Way to Measure Contrast
One of the most concrete and already discussed changes in WCAG 3.0 drafts is a move away from the current contrast ratio formula toward APCA, the Accessible Perceptual Contrast Algorithm. The current WCAG 2.x contrast formula has known blind spots, for example it can pass some color combinations that are genuinely hard to read while failing others that are perfectly readable in practice.
APCA is designed to better match how human vision actually perceives contrast, accounting for font size and weight rather than treating all text the same way.
Because APCA is already being tested and discussed widely ahead of WCAG 3.0’s finalization, it’s a reasonable area to start experimenting with now, even while WCAG 2.2’s simpler contrast ratio remains the enforceable standard. What This Means for Your Site Right Now
Nothing changes today. WCAG 3.0 is still a working draft, and the W3C has been clear that it will remain in draft status for a significant review period before any final version is published. There is no enforcement, no legal citation, and no fixed release date yet. WCAG 2.2 remains the standard to build toward for any compliance work happening now.
That said, being an early mover has real advantages. Teams that start experimenting with concepts like APCA contrast checking and a more holistic view of accessibility, beyond just pass or fail checklist items, will have an easier transition whenever WCAG 3.0 does finalize.
How to Prepare Before WCAG 3.0 Is Enforced
- Keep WCAG 2.2 as your actual compliance target. Don’t delay current work waiting for 3.0. It isn’t finalized and has no enforcement timeline yet.
- Start testing key pages with APCA alongside your current contrast checks. This gets your team comfortable with the new method without waiting for a mandate.
- Think beyond pass or fail. Start asking whether a page is genuinely usable for someone with a disability. Not just whether it technically passes a checklist item. This mindset shift maps directly onto WCAG 3.0’s scored approach.
- Follow the W3C’s public working draft updates. WCAG 3.0 is being developed in the open, so changes to the draft are visible well before finalization.
- Choose tools and partners already tracking WCAG 3.0 development. A compliance layer built only around 2.x checklist logic will need updates later. Accessify’s team actively tracks W3C draft changes, including APCA, so customers aren’t caught flat footed when the standard progresses.
“Stay compliant today and ready for tomorrow. Start your Accessify trial.”
FAQ
What is WCAG 3.0 and when will it be released?WCAG 3.0 is the next generation of web accessibility guidelines, currently a W3C working draft. It introduces Bronze, Silver, and Gold conformance tiers instead of the current A, AA, AAA system. No official release date has been confirmed, and WCAG 2.2 remains the current standard to build toward.
What is APCA and why does it matter for WCAG 3.0?
APCA, the Accessible Perceptual Contrast Algorithm, is a proposed replacement for the current WCAG contrast ratio formula. It’s designed to more accurately. Reflect how humans actually perceive contrast, accounting for factors like font size and weight that the current formula ignores.
Should I wait for WCAG 3.0 before doing accessibility work now?
No. Waiting isn’t advisable since WCAG 3.0 has no confirmed timeline. Building to WCAG 2.2 today, while keeping an eye on WCAG 3.0 developments like APCA, is the practical approach.
Do I need to comply with WCAG 3.0 today?
No. WCAG 3.0 is not finalized and is not legally enforceable anywhere yet. WCAG 2.2 AA remains the standard referenced by current laws and should remain your compliance target.
