The Accessibility Guidelines Working Group has released the first public draft of WCAG 3.0, prompting compliance teams to ask: should we start planning now, or wait until it's finalized?
This question isn't trivial. Your team already manages WCAG 2.1 conformance, Section 508 of the Rehabilitation Act requirements, and the DOJ Final Rule (2024). Adding another standard could complicate things prematurely. However, ignoring WCAG 3.0 might leave you unprepared when it's adopted.
Here's the debate dividing compliance leaders.
The Case for Waiting
Many compliance officers prefer a wait-and-see approach, and they have valid reasons.
First, WCAG 3.0 is still a draft. The W3C's development process can take years. WCAG 2.1 took four years from draft to publication. Investing resources in a potentially changing standard could waste budget and create technical debt.
Second, regulatory adoption lags. The DOJ Final Rule (2024) references WCAG 2.1 for state and local government websites. Section 508 currently points to WCAG 2.0 Level AA, with some agencies adopting WCAG 2.1 voluntarily. No regulation requires WCAG 2.2, let alone 3.0.
Your legal risk today comes from not meeting WCAG 2.1 Level AA. Courts cite WCAG 2.0 and 2.1 in ADA Title III cases. No attorney will argue you violated a non-existent standard.
Third, WCAG 3.0's structural changes could make early adoption risky. If the final version alters its scoring model or reorganizes outcomes, you'll need to redo the work. It's better to wait for the standard to stabilize before committing resources.
Lastly, your current WCAG 2.x efforts aren't wasted. The core principles of accessibility remain. Fixing contrast issues, keyboard navigation, and screen reader compatibility now will still be relevant as WCAG 3.0 evolves.
The Case for Planning Now
Some compliance leaders take the opposite view, and they have their reasons too.
WCAG 3.0 offers a new way to measure accessibility. Waiting until it's final means missing the chance to align your program with its structure from the start. If WCAG 3.0 introduces new scoring mechanisms, your current testing workflows might not fit.
More importantly, the draft phase is when your feedback matters. The Accessibility Guidelines Working Group seeks input from practitioners during this period. Waiting until WCAG 3.0 is final means losing the chance to flag issues or suggest alternatives.
Consider procurement cycles. If you're developing a new system with a two-year timeline, you're making decisions now that will affect your accessibility in 2027. By then, WCAG 3.0 might be required, especially for federal contracts or under the European Accessibility Act.
Early planning also aids vendor management. Your SaaS providers aren't thinking about WCAG 3.0 yet. By asking about their roadmap now, you push them to prepare. Waiting means dealing with vendors who rush to comply later.
Finally, there's a risk management angle. Accessibility lawsuits increasingly cite "industry standards" as evidence of reasonable accommodation. If WCAG 3.0 gains traction while you're focused on WCAG 2.0, you risk falling behind professional consensus.
Where Practitioners Actually Land
In practice, most teams find a middle ground.
They're not overhauling their entire program for WCAG 3.0. Instead, they're tracking the draft, assigning someone to review updates, and watching for changes that might affect their tech stack.
Teams comfortable with this ambiguity focus on principles rather than specific criteria. They prioritize screen reader compatibility, keyboard operability, and clear content structure over checking WCAG 2.1 boxes. When WCAG 3.0 arrives, they'll validate conformance without needing to rebuild their approach.
Teams struggling most rely heavily on automated WCAG 2.x testing. If WCAG 3.0 changes conformance measurement, their tools and workflows could break.
Our Take
Start monitoring WCAG 3.0 now, but don't change your compliance strategy yet.
Assign a senior accessibility specialist to review each draft update. Participate in W3C feedback periods if you have concerns. Track how the scoring model evolves and whether it conflicts with your current testing approach.
Keep your conformance testing, Accessibility Conformance Report generation, and Section 508 documentation focused on WCAG 2.1 Level AA. That's what regulators require, what courts recognize, and what auditors check.
The exception: if you're starting a multi-year project or procurement process, include WCAG 3.0 readiness in your vendor criteria. You don't need conformance yet, but you need vendors who are preparing.
The bigger risk isn't choosing the wrong side of this debate. It's treating accessibility as a compliance checkbox instead of a design principle. If your team only thinks about accessibility when a new standard drops, you're already behind.
