You just finished retrofitting your site for WCAG 2.2. Your focus indicators are visible, your target sizes are fixed, and your audit report is finally clean.
Then someone on your team drops a link in Slack: "Wait, isn't WCAG 3.0 already changing everything? Something about a new contrast formula called APCA?"
Take a breath. Nothing you just finished is obsolete. Let's separate what's real from what's still years away.
Picture This Scenario
A product manager at a mid-size SaaS company spends a quarter getting her app to WCAG 2.2 AA. She's proud of the work — real keyboard testing, real screen reader passes, real color contrast fixes using the standard 4.5:1 ratio math.
Then a designer joins the team, fresh from a conference talk on WCAG 3.0, and starts pushing for APCA-based contrast values instead — insisting the old contrast ratio formula is "already outdated." The PM panics. Did she just spend a quarter building to a standard that's about to be replaced?
She hadn't. And if you're in a similar spot, you haven't either. Here's why.
What WCAG 3.0 Actually Is (And Isn't Yet)
WCAG 3.0 — developed publicly under the working-group nickname "Silver" — is not simply the next number after 2.2, the way 2.1 followed 2.0. It's a substantially different effort: a rework of how web accessibility conformance itself is structured and scored, not just a list of new success criteria bolted onto the old framework.
It's been in active, public working-draft development for an extended period. Draft documents are public. Working groups are iterating. But as of now, WCAG 3.0 has not reached official W3C Recommendation status. That distinction matters more than almost anything else in this article.
A W3C "Recommendation" is the finalized, stable version of a standard — the version that regulators, courts, and procurement teams can actually point to. A working draft, no matter how mature or how many conference talks reference it, is not that. It can still change. Sections can be rewritten. Scoring models can be scrapped and rebuilt.
So What Legal Standard Actually Applies Right Now?
This is the part worth bolding and reading twice: no current legal or regulatory framework references WCAG 3.0 as the operative technical standard. Not ADA-related guidance. Not Section 508. Not the European Accessibility Act's EN 301 549.
Every one of those frameworks currently names WCAG 2.0, 2.1, or 2.2 — specifically because those are finalized, stable Recommendations that regulators can safely cite without the ground shifting under them. Regulatory language doesn't get built on drafts. It gets built on things that are done.
That means the only technical target you are currently, actually, legally on the hook for is WCAG 2.1 or 2.2 Level AA — the exact standard covered throughout the rest of this blog. If your team has been building toward that, you have not wasted your time, and you're not suddenly behind.
What Is APCA, Really?
APCA — the Accessible Perceptual Contrast Algorithm — is one of the most talked-about ideas bundled into the WCAG 3.0 conversation. It's a proposed alternative to the current WCAG 2.x contrast ratio formula, the one behind familiar success criteria like 1.4.3 Contrast (Minimum), Level AA and 1.4.6 Contrast (Enhanced), Level AAA.
The pitch behind APCA is genuinely interesting: it's designed to more accurately model how humans actually perceive contrast, factoring in things like font weight and text size — variables the current 2.x contrast math doesn't directly account for. Two color pairs with an "identical" contrast ratio under today's formula can look very different in real-world legibility depending on whether the text is bold and large or thin and small. APCA tries to close that gap.
But here's the key fact to hold onto: APCA is not yet the adopted, official contrast method in any finalized WCAG version. It's a proposal under active discussion, not a requirement you're out of compliance with.
The Stat: WebAIM's annual "WebAIM Million" evaluation of the top 1,000,000 home pages has repeatedly found the vast majority — in recent years around 95-96% — have detectable WCAG 2 failures, with low-contrast text among the most common. Getting current contrast requirements right is still where almost every site is falling short — long before anyone needs to worry about a future formula. (WebAIM: The WebAIM Million)
The Relationship Between "Draft" and "Required"
It's worth being blunt about the practical relationship here, because a lot of the anxiety around WCAG 3.0 comes from blurring these two categories together:
Organizations should not treat draft WCAG 3.0 concepts — including APCA — as something they're currently out of compliance with. Neither is a finalized requirement anywhere. There is no auditor, regulator, or court that can cite you for failing a standard that hasn't been ratified.
That said, "no current legal requirement" is not the same thing as "safe to ignore entirely." Forward-looking teams can absolutely track WCAG 3.0's development and experiment with APCA-informed contrast choices in new design work, without disrupting current compliance efforts. In most practical cases, APCA-friendly contrast choices tend to be a superset of, not a conflict with, current 2.x contrast requirements — meaning designing with APCA in mind now is unlikely to create rework later.
Where This Leaves Your Roadmap
Draft vs. finalized — where the two standards stand right now
| Question | WCAG 2.1 / 2.2 AA | WCAG 3.0 (incl. APCA) |
|---|---|---|
| W3C status | Finalized Recommendation | Public working draft, not yet Recommendation |
| Referenced by ADA-related guidance, Section 508, EAA/EN 301 549 | Yes, directly | Not currently |
| Legally enforceable today | Yes | No |
| Safe to build a compliance program around today | Yes | Not yet — still subject to change |
| Worth monitoring / experimenting with | N/A (this is the baseline) | Yes, for future-proofing new design work |
Practical Guidance: Don't Let the Future Stall the Present
Here's the mistake we see teams make: they hear "WCAG 3.0 is coming" and either freeze up, waiting to see what happens before finishing their current work, or they overcorrect, chasing an unfinished draft standard instead of the one that's actually enforceable.
Both are wrong moves. Don't let uncertainty about a future standard slow down or distract from real, current WCAG 2.1/2.2 AA work. Get the finalized, legally-referenced standard solid first. Treat WCAG 3.0 and APCA as something to monitor and revisit specifically once — and if — WCAG 3.0 reaches official Recommendation status and starts actually appearing in legal or procurement language.
That's not a dismissive stance. It's the same discipline that keeps accessibility programs sustainable instead of reactive. Remember: a large share of the demand letters and lawsuits documented every year by trackers like UsableNet's ADA Digital Accessibility Lawsuit Report cite failures against the current standard — things like missing alt text and insufficient contrast under today's formula, not hypothetical future ones. Retail and ecommerce sites are consistently among the most-targeted industries in those reports. That's where the real, present-day risk sits.
Get the Baseline Right, Then Watch the Horizon
WCAG 3.0 and APCA are worth keeping an eye on. They may genuinely reshape how contrast and conformance get measured down the road, and teams that experiment thoughtfully now will have a head start when that day comes.
But your legal and reputational exposure today is tied to WCAG 2.1 and 2.2 Level AA — full stop. If your baseline isn't locked in yet, that's the fire to put out before you spend another minute on a standard that hasn't been finalized.
Stay ahead of the standard — get your current WCAG 2.2 AA baseline locked in first, so you're building on solid ground before any future standard ever becomes enforceable. Get your baseline assessment →