WCAG 3 vs WCAG 2.2: What Businesses Should Implement Now
Understand the status of WCAG 3, why WCAG 2.2 remains the practical implementation baseline and how to prepare without delaying accessibility.
By AUZtec Innovations
WCAG 3 is the next-generation accessibility-guidance project from W3C, designed to address a broader range of technologies, disabilities and evaluation methods. It remains a draft. Businesses should continue implementing WCAG 2.2 and applicable legal requirements now, while monitoring WCAG 3 rather than claiming conformance to it.
The most valuable preparation is not a second checklist. Build accessibility into research, design systems, content, development, testing and procurement so the organisation can adapt as standards evolve.
The status in 2026
W3C’s WCAG overview identifies WCAG 2.2 as the current W3C Recommendation and notes its publication as ISO/IEC 40500:2025. W3C published further WCAG 3 draft material in 2026, but drafts can change and are not a basis for a WCAG 3 conformance claim.
Legal obligations vary by country, sector and organisation. Obtain qualified advice for formal compliance decisions. Technical guidance should support that decision, not impersonate it.
Why WCAG 3 is being developed
WCAG 2 uses testable success criteria at A, AA and AAA levels. It has created a stable shared language, but evaluating complex applications, emerging technology and the lived impact of barriers remains challenging.
WCAG 3 explores broader outcomes, methods and scoring. Its direction encourages teams to consider whether people can complete real tasks, alongside atomic technical checks.
What to implement today
Target the WCAG 2.2 level identified by your policy and legal analysis, commonly AA. Prioritise:
- semantic structure and meaningful names;
- keyboard access and visible focus;
- sufficient contrast and non-colour cues;
- text resize, reflow and zoom;
- form labels, instructions and error recovery;
- alternatives for images, audio and video;
- predictable navigation and authentication;
- target size and reduced-motion needs;
- compatibility with assistive technologies.
Our website accessibility audit checklist turns these areas into a practical review.
Test journeys, not only components
A button may pass an isolated check while the checkout remains impossible. Select priority journeys such as finding a service, submitting an enquiry, signing in, paying and obtaining support.
Combine automated scanning, code review, keyboard tests, assistive-technology testing and evaluation by disabled users where appropriate. Automated tools find only part of the problem.
Record the barrier, affected users, severity, owner and verification evidence. Retest after remediation and regression changes.
Prepare for WCAG 3 without speculative rework
Maintain an inventory of key journeys and components. Store accessibility decisions in the design system. Give content and product teams acceptance criteria, not just developers.
Track outcomes such as task completion, error recovery and support contacts. This outcome evidence is valuable now and aligns with WCAG 3’s broader direction.
Avoid creating internal “WCAG 3 scores” from an unstable draft or presenting them as official conformance.
Accessibility in an AI interface
Conversational and agentic systems introduce dynamic updates, uncertain content and complex controls. Announce state changes appropriately, preserve keyboard focus and make tool actions understandable. Provide a conventional route when an AI interaction fails.
Generated alt text or captions require quality review in consequential contexts. A fluent description may omit the information the task requires.
Procurement and governance
Ask suppliers for VPATs or equivalent evidence where relevant, but verify priority journeys. Include remediation responsibility, testing access and change notification in contracts.
Set a release rule for critical barriers and maintain a public accessibility contact route. Accessibility is an operating practice, not a one-off certificate.
AUZtec combines UI/UX design with website and application engineering so remediation improves the experience rather than adding patches. For the related browser-platform context, read Baseline 2026. To review your highest-value journeys, contact us.