The W3C Accessibility Guidelines Working Group recently released a new WCAG 3.0 draft. This update merges WCAG 2.0 A and AA requirements into a single base conformance level, aiming to simplify compliance documentation. However, the draft also introduces supplemental requirements and assertions intended to reward organizations that exceed baseline accessibility.
This reward system is unlikely to succeed. It adds complexity without delivering measurable compliance value. Your team needs to understand why before allocating resources to track it.
Changes in the Latest Draft
WCAG 3.0 defines conformance through three components:
Core Requirements establish baseline conformance, combining WCAG 2.0 Level A and AA criteria. Meeting all core requirements means you're conformant with WCAG 3.0.
Supplemental Requirements act like WCAG 2.0 Level AAA criteria. They're additional measures that exceed baseline conformance. Organizations meeting some of these can claim Bronze, Silver, or Gold designations.
Assertions are documented commitments to specific accessibility activities, like maintaining a focus indicator style guide. They don't add testable requirements but indicate organizational maturity.
The Working Group claims this structure will "motivate organizations to go beyond minimal accessibility requirements with a conformance model that shows which organizations demonstrate a greater effort to improve accessibility."
Why This Structure Creates Risk
The optional tier system lacks enforcement. Your legal counsel won't advise exceeding baseline conformance when maintaining baseline itself is challenging. ADA Title III litigation doesn't reward Bronze or Silver conformance. The DOJ Final Rule (2024) doesn't reference tiered achievement. Section 508 procurement requires clear pass/fail conformance, not aspirational levels.
Bronze, Silver, and Gold designations offer no user-facing value. Two organizations claiming Bronze conformance might meet entirely different supplemental requirements. A user with low vision can't predict if a Bronze-conformant site meets their needs. The designation signals effort without guaranteeing outcome.
Mixing required and optional criteria complicates audits. Your conformance testing team must now differentiate between core requirements that determine legal compliance and supplemental requirements that don't. Every guideline review requires an additional decision point: Is this core or supplemental? Does our organization need to meet it? The WCAG 2 QuickRef exists to address this documentation problem, and WCAG 3.0 complicates it further.
Optional requirements serve as pressure valves for unresolved consensus. WCAG 2.2's Focus Appearance criterion landed Assistive Technology Level AAA after the Working Group couldn't agree on AA-level metrics. When optional levels exist, controversial requirements get pushed there to avoid blocking publication. Your team ends up with a baseline that excludes important accessibility measures because they were politically difficult to mandate.
Assertions conflate process maturity with technical conformance. If your focus indicator implementation meets the technical requirement, documenting a style guide doesn't enhance accessibility. It signals governance maturity, which belongs in frameworks like the Accessibility Maturity Model, not in a technical conformance standard.
Implications for Your Compliance Program
You're currently managing conformance to WCAG 2.1 or WCAG 2.2. Some jurisdictions require WCAG 2.0 Level AA through Section 508. Others reference WCAG 2.1 Level AA through EN 301 549. You've built testing protocols, vendor requirements, and Accessibility Conformance Reports around these versions.
WCAG 3.0 disrupts that continuity without adding regulatory clarity. If the core requirements roughly equal WCAG 2.0 AA with minor additions, you're retraining auditors, rewriting procurement language, and updating conformance documentation to maintain the same baseline.
Worse, you'll face a transition period where some jurisdictions adopt WCAG 3.0 and others don't. That means dual conformance claims, parallel testing protocols, and confusion about which standard governs which digital property.
The supplemental requirements don't solve this problem. They add documentation burden without reducing legal exposure.
Action Items by Priority
Monitor but don't adopt early. WCAG 3.0 is years from final publication. Don't allocate resources to Bronze/Silver/Gold conformance until you see regulatory adoption. Focus your current program on WCAG 2.1 or WCAG 2.2 Level AA conformance, which remains the enforceable standard.
Advocate for modular requirements in public comment periods. When W3C opens WCAG 3.0 for public comment, recommend that supplemental requirements be published as separate, adoptable modules rather than optional tiers. A modular approach lets policymakers specify "WCAG 3.0 + BetterCaptions" for public entities or "WCAG 3.0 + SignLanguage + EasyLang" for specific sectors. That gives you clear conformance targets instead of aspirational designations.
Separate technical conformance from governance maturity in your program. If you're tracking accessibility maturity through assertions like training documentation or style guide maintenance, use the Accessibility Maturity Model or internal governance frameworks. Don't conflate process documentation with technical conformance in your Accessibility Conformance Reports.
Plan for dual-standard conformance during transition. Budget for the scenario where your organization must claim conformance to both WCAG 2.x and WCAG 3.0 simultaneously. That means maintaining two sets of testing protocols, two conformance report templates, and two vendor requirement specifications until regulatory adoption stabilizes.
Pressure test your baseline conformance now. If your team struggles to maintain WCAG 2.1 Level AA conformance, adding optional requirements won't improve your accessibility posture. It'll create documentation theater. Fix your baseline before considering anything beyond it.
