WCAG 3.0: What Businesses Should Prepare For Now

For businesses, that means one thing above all: WCAG 2.2 remains the benchmark that digital accessibility is measured against today, legally and technically. If you still want to know what WCAG 3.0 will change and how to prepare sensibly, here is the current state of play, without speculation and without alarmism.

This is not just a legal formality. Accessibility increasingly determines how many people can actually use a digital offering at all, and WCAG 3.0 already points to where these requirements are heading: away from the isolated single page and toward the complete user experience across websites, apps and documents.

What is WCAG 3.0, and why a new standard at all?

The Web Content Accessibility Guidelines (WCAG) have been the core technical standard for digital accessibility for years and currently stand at version 2.2. Since 2016, the World Wide Web Consortium (W3C) has been working in parallel on a fundamentally revised successor, because accessibility no longer happens only on classic websites, but in apps, PDF documents, content management systems and emerging technologies such as VR and AR applications. Earlier WCAG versions were originally designed for websites and later extended to other formats through supplementary documents, a workaround WCAG 3.0 is meant to avoid from the outset. The new standard is meant to cover this broader scope directly while also being easier to understand and addressing more needs, in particular those of people with cognitive disabilities, an area many practitioners feel today's model still defines too loosely.

The new conformance model: guidelines instead of success criteria

Today's model of success criteria, each simply passed or failed, gives way in WCAG 3.0 to a graded system. Instead of the conformance levels A, AA and AAA, the draft works with guidelines structured into foundational requirements, supplemental requirements and so-called assertions. This makes it possible to reflect that some requirements are non-negotiable while others further improve accessibility without making an entire website non-conformant. For testing processes, that means more nuance, but also more effort in assessment, which is why the W3C says the exact conformance model is still under discussion.

• ✓ Graded conformance, replacing a simple binary pass or fail with a more differentiated assessment
• ✓ Views and processes, evaluating the entire user journey rather than a single page
• ✓ Broader scope, explicitly covering apps, PDF documents and emerging technologies
• ✓ More cognitive accessibility, including requirements for clear, non-literal language

How far along is the draft, really?

The current working draft is dated March 3, 2026 and carries the maturity status "Developing"; individual guidelines, requirements and assertions have reached that status, but according to the W3C, many questions about the final conformance model remain open. The consortium itself states that several more years of work lie ahead. For comparison: fifteen years passed between WCAG 2.0 in 2008 and WCAG 2.2 in 2023, a reminder of how slowly international standards in this field usually move. Industry observers such as AbilityNet estimate that candidate status is unlikely before late 2027, with a final recommendation at the earliest in 2028. What matters in practice: according to the W3C, WCAG 3.0 will not deprecate WCAG 2, which will remain valid alongside it for at least several years after WCAG 3.0 is finalized.

What legally counts for businesses today

The draft changes nothing about the current legal situation. The European Accessibility Act, Germany's Accessibility Strengthening Act and the technical implementation standard EN 301 549 all reference WCAG 2.2 at conformance level AA, not WCAG 3.0. The W3C draft itself explicitly states that it is a working document that may still be changed or replaced, so it is deliberately not yet a basis for regulation. How seriously the current requirements are already being enforced is shown by our article on the start of market surveillance for accessibility: businesses that fail to meet today's criteria risk fines and warning letters now, regardless of when WCAG 3.0 is finished.

Checklist: what to prepare for already now

• ✓ Implement WCAG 2.2 AA fully and verifiably, it remains the binding baseline for the EAA, national laws such as the BFSG, and EN 301 549, unaffected for now by WCAG 3.0
• ✓ Monitor continuously, not just once, since WCAG 3.0 will assess entire user processes over time rather than single pages on a fixed date
• ✓ Factor in cognitive accessibility, for example through clear, plain language in key processes such as checkout, forms or booking flows
• ✓ Gather user feedback, from people with different abilities, not only from automated testing
• ✓ Keep documentation current, so evidence is always ready for regulators, auditors and customers alike