WCAG 3.0 Guidelines: What?s New and What to Expect

The WCAG 3.0 Guidelines are the next-generation accessibility guidance being developed by the W3C Web Accessibility Initiative (WAI). This article explains what WCAG 3.0 aims to change, how it differs from WCAG 2.x, what organisations should do now, and where to check the current status. Read the sections below for concrete steps you can take today.

What are the WCAG 3.0 Guidelines?

WCAG 3.0 is a working effort to create more modern, measurable, and broader web accessibility guidance. It moves away from the strict success criteria model used in WCAG 2.x. The intent is to cover more technology types and user needs, and to allow more flexible conformance claims.

Key changes in WCAG 3.0 Guidelines

Outcomes and tests replace success criteria

WCAG 2.x uses success criteria that websites either meet or fail. WCAG 3.0 proposes outcomes that are linked to specific tests and methods. Each outcome is designed to be measurable by automated checks, manual inspection or user testing. That makes conformance easier to verify and to track over time.

A testing layer with methods and metrics

The new model separates the requirement from the way it is tested. For many outcomes, there will be multiple test methods. Tests can be automated checks, manual steps for a reviewer, or defined user tasks for real people with disabilities. The emphasis is on repeatable, documented tests so results are reproducible.

A scored conformance model rather than pass/fail

Rather than the A, AA, AAA levels from WCAG 2.x, WCAG 3.0 introduces a rubric approach. Each outcome carries weight. You gain points by meeting outcomes with accepted tests. The total builds a score you can use in a conformance claim. This supports more granular improvement tracking and lets organisations show progress even when not all outcomes are met.

Wider scope and modular design

WCAG 3.0 is intended to be more modular and to cover contexts that are not well addressed by WCAG 2.x. That includes mobile apps, web components, PDFs and emerging interaction patterns. The modular approach aims to let guidance evolve without rewriting the whole standard.

What stays the same

• Accessibility remains focused on people with a range of disabilities.
• WCAG 2.x material is still widely used and referenced. Existing legal requirements often cite WCAG 2.1 or 2.2.
• Principles such as perceivable, operable, and understandable remain central to thinking about accessibility.

How WCAG 3.0 might affect legal and procurement work

Many laws and public procurement rules currently reference WCAG 2.x. A new standard does not change those rules until governments update them. Expect a period where both sets of guidance are referenced. Organisations should plan to meet current legal requirements and to be ready to adopt newer outcomes where it improves accessibility.

Practical steps to prepare now

Use these steps to reduce risk and be ready for WCAG 3.0 changes.

1. Run a current accessibility audit against WCAG 2.1 or 2.2. Document gaps and remediation status.
2. Adopt a testing mix: automated tooling, manual expert review, and real-user testing. Keep test records and evidence for each issue.
3. Update procurement and acceptance criteria so accessibility metrics and test evidence are required from vendors.
4. Train product teams on accessible design patterns and WCAG 2.x requirements. Make accessibility part of the definition of done.
5. Start measuring accessibility with a repeatable scorecard. Track trends for key user journeys rather than isolated pages.
6. Include people with disabilities in usability testing. Their feedback often reveals gaps that tests miss.

Common mistakes teams make

• Relying only on automated checks. Automated tools find many issues but miss keyboard, cognitive and content problems.
• Treating WCAG as a one-off project. Accessibility works best when it is embedded in design and release cycles.
• Not keeping evidence. For audits and procurement you need documented tests, screenshots and test steps.
• Assuming new guidance cancels the old. Legal obligations tied to WCAG 2.x remain until changed by law.

Two practical examples (how outcomes and tests work)

Example 1: A colour contrast outcome might be met by an automated contrast test for normal text, plus a manual check for images that contain text. Both tests are documented and accepted methods for that outcome.

Example 2: A component outcome for a custom dropdown could require a keyboard interaction test, a screen reader test, and a user task where someone with a mobility or vision impairment completes the action. Evidence is logged for each test.

How to write a WCAG 3.0 friendly conformance claim

A clear claim should say which outcomes were assessed, which test methods were used, the date of testing, and who did the tests. Include the score or rubric result and links to evidence. Avoid vague statements like accessible without noting scope and method.

Status and where to check for updates

WCAG 3.0 is a W3C working effort. The safest way to track changes is to check the W3C WAI web site and the public working group publications. Do not assume drafts are final. Look for published test methods and the official conformance rubric before making sweeping policy changes.

Quick FAQ

Will WCAG 3.0 replace WCAG 2.1 or 2.2?

Not immediately. WCAG 2.x versions will remain relevant. Organisations and regulators will move at different speeds. Plan for a transition period where both are used.

Should I stop fixing WCAG 2.x issues?

No. Continue to fix current issues. That work reduces risk now and makes adopting new outcomes easier later.

How should product teams change testing?

Add documented manual tests and regular real-user testing. Keep automated scans but use them as one input. Aim for reproducible test procedures for key journeys.

Resources and next steps

• Keep following W3C WAI publications for official drafts and test method guidance.
• Update procurement templates to require test evidence for accessibility.
• Build or update an accessibility scorecard for primary user journeys and run it monthly.

WCAG 3.0 Guidelines aim to make accessibility more measurable and relevant to modern interfaces. Use the time before any final standard to build stronger testing practices, collect evidence, and include people with disabilities in product work. That will reduce risk and make any future transition smoother.