WCAG 2.2: Don’t Wait for WCAG 3 to Get Accessibility Right

  • 4 minute read
Back to search

It’s tempting to look ahead. The next version of the Web Content Accessibility Guidelines, WCAG 3.0, has been in the works for years, promising clearer outcomes, fairer scoring models, and a wider lens on user needs.

The reality is different. WCAG 2.2 is the accessibility standard that matters right now. Regulators, auditors, and organisations are already referencing it, and it’s shaping compliance expectations today.

Continue reading to learn why WCAG 2.2 should be your focus to stay compliant, what it changes, and how to prepare without getting sidetracked by WCAG 3.

Is WCAG 3 out yet?

No, WCAG 3 has not been officially released. The latest working draft, published in September 2025, shows ambition but not stability. The conformance model is still unsettled. Key sections, including those on cognitive accessibility, neurodivergence, AI bias, and dark patterns, remain exploratory. Testing methods have not been agreed upon. There is no defined migration path from WCAG 2.2, and no regulator or legal body has formally adopted it.

In other words, WCAG 3 is a fascinating conversation, not a compliance framework.

What version of WCAG are we on?

The latest WCAG version is 2.2, released by the W3C in October 2023. It extends earlier versions in the WCAG 2 family by adding success criteria that improve accessibility for people with low vision, motor limitations, and cognitive differences.

Although many laws and procurement rules still reference WCAG 2.1 AA, WCAG 2.2 is already being cited in audits, lawsuits, and policy updates. For organisations working on web content accessibility today, it is the version that matters.

WCAG 2.2: The Standard You Should Care About

While WCAG 3 continues to evolve, WCAG 2.2 is already here and increasingly recognised as the global benchmark.

  • In Europe, EN 301 549 currently maps to WCAG 2.1 AA, with updates expected to reference 2.2.

  • In the UK, procurement and public sector rules still set WCAG 2.1 AA as the minimum, yet many organisations are moving toward 2.2 to future-proof their compliance.

  • Legal cases, accessibility audits, and public complaints are already citing WCAG 2.2 success criteria.

The new requirements address real-world usability issues, including:

  • Clearer focus indicators that help keyboard users see where they are on a page.

  • Minimum target sizes that make buttons and links easier to activate.

  • Better support for people with low vision, motor limitations, and cognitive differences.

Taken together, WCAG 2.2 strengthens the basics of navigation, form completion, and interaction, helping people use digital services with greater confidence.

Is WCAG 2.2 a Legal Requirement in the UK?

UK law currently requires public sector websites and mobile apps to meet WCAG 2.1 AA. This is set out in the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. For private organisations, there is no single accessibility law that names WCAG, but the Equality Act 2010 can be applied when digital services exclude disabled users.

Although WCAG 2.2 has not yet been written into UK regulations, it is already shaping practice. Accessibility audits, legal challenges, and procurement contracts are beginning to reference the new criteria, especially around focus indicators and minimum target sizes. Many organisations are moving to WCAG 2.2 AA now to stay ahead of compliance expectations and reduce risk.

In short, WCAG 2.2 is not yet a legal requirement in the UK, but aligning with it is the safest approach for both compliance and usability. Organisations looking to stay ahead of regulatory risk can explore our procurement and compliance support.

What Should You Be Doing Right Now for WCAG 2.2 Compliance?

WCAG 2.2 sets the benchmark for accessibility today, and meeting it requires more than awareness. Organisations need clear standards, effective testing, and processes that hold both teams and suppliers accountable.

If you are leading accessibility, your energy is best spent on the following priorities:

Anchor your standards

Update internal policies and supplier requirements to WCAG 2.2 AA. If you’re still citing 2.0 or 2.1, it’s time to refresh.

Test smarter

Moving from theory to practice is where accessibility progress is made. If you are responsible for web content accessibility, your priority should be to align with WCAG 2.2 AA and embed it across policies, processes, and procurement. The following actions will help you focus your energy where it counts.

Validate the user experience

Don’t just chase conformance; test with real disabled users. They’ll tell you what works and what doesn’t, and that insight is invaluable.

Fix your procurement

Ask vendors for up-to-date VPATs (aligned to WCAG 2.2), and include enforceable accessibility clauses in contracts. Make accessibility a shared responsibility, not just your internal problem.

Track and prioritise access risks

Log accessibility issues like you would any critical defect, assign impact, track progress, and report it. Accessibility is a business risk, not a nice-to-have.

Keep One Eye on WCAG 3, But Stay Grounded

It is sensible to stay informed about the direction of WCAG 3. Ideas such as ethical design, AI transparency, and cognitive accessibility are worth exploring, especially if you have the capacity to run pilots or innovation projects. They point to where accessibility standards may eventually move.

Compliance, however, cannot wait for the future. WCAG 2.2 is the accessibility benchmark today. It is the version that regulators and auditors are beginning to apply, the version that procurement teams are starting to request, and the version that reflects real-world usability needs.

The priority is clear: embed WCAG 2.2 in your policies, testing, and procurement now. Use WCAG 3 themes as inspiration, not as an excuse to delay.

The people who depend on accessible digital products cannot wait for a draft to mature. They need you to deliver services that meet current web content accessibility standards today.

If your organisation needs support, our digital accessibility agency can help. Get in touch to embed WCAG 2.2 into your policies, testing, and procurement, and ensure your digital services stay accessible.

Similar posts

Discover how we’ve helped organisations overcome accessibility challenges and achieve success.

FAQs

WCAG 2.2 builds on earlier versions of the Web Content Accessibility Guidelines by extending requirements that support people who experience barriers online. The update introduces additional success criteria designed to strengthen navigation, improve visibility of interactive elements, and reduce obstacles in completing tasks such as filling out forms or using controls.

Rather than replacing WCAG 2.1, it expands the framework so organisations have clearer, more practical checkpoints to measure accessibility against. Meeting WCAG 2.2 AA means aligning with the most up to date global benchmark for digital accessibility.

Yes. While the exact legal requirement depends on your country, most organisations are expected to meet at least WCAG 2.1 AA today, with many already moving to WCAG 2.2 AA. Even where the law does not explicitly mandate WCAG, accessibility obligations often fall under broader equality or anti-discrimination laws. Our governance management support helps organisations put the right policies in place.

Yes, WCAG 2 was created for websites, but the principles extend to many types of digital products and software interfaces. Mobile applications, SaaS platforms, and interactive tools that behave like websites are all expected to meet the same accessibility standards. Organisations often apply WCAG as a universal benchmark for digital accessibility, not only for web pages.

See more FAQs

Website accessibility monitoring is the fundamental process of scanning your website to detect any issues that could prevent users with disabilities from using it. Automated web accessibility monitoring tools continuously check for accessibility issues across your site, providing instant alerts for new and updated content, as well as your overall site health.

 

They track compliance with standards like the Web Content Accessibility Guidelines (WCAG) and show you how accessible your site is, where it should be, and what improvements should be made to deliver a better experience for all users.

 

In addition to measuring your compliance, they also provide a clear picture of your progress over time, so you can track the impact of your improvements and maintain ongoing accessibility.

The two main types are automated and manual monitoring. Together, they provide you with a comprehensive view of how accessible your site is and where improvements are needed.

 

  • Automated monitoring uses specialised web accessibility monitoring tools to scan your website for non-compliant features and common issues, such as missing alt text, poor colour contrast, or keyword navigability issues. These tools can also provide instant alerts for when site elements present accessibility risks and site health reports so you can prioritise any issues.

  • Manual monitoring is where accessibility experts and testers come in to review your site as a real user would, often using assistive technologies like screen readers. They will usually check how easy it is to navigate through pages, interact with content, and understand messages or instructions. The aim is to identify any areas which may present barriers for individuals with disabilities.

Accessibility monitoring is crucial for ensuring that everyone can use and experience your site in the same way, regardless of ability. It is also essential for staying compliant with standards like WCAG and with laws like The European Accessibility Act 2025.

 

Without regular monitoring, accessibility issues can easily appear when new pages are added, content is updated, or designs are changed.

 

Continuous website accessibility monitoring gives you a framework to:

  • Stay compliant

  • Improve user experience

  • Respond to issues quickly

  • Track progress over time

Accessibility monitoring should be integrated into your process rather than a one-time check. Websites can change frequently, with new pages, designs, and content changes, but each update can introduce accessibility issues.

 

Continuous monitoring, both manual and through an automated website monitor, is recommended to catch any issues as soon as they appear, particularly after any big changes, such as adding interactive elements, redesigns, and when legal or accessibility guidelines are updated.

 

Even without significant changes, monitoring should be a consistent part of your organisations website maintenance.

 

The more you test the better, but for those looking for an exact amount, ideally once a month is a good starting point to catch any emerging issues.

Book a meeting

This field is for validation purposes and should be left unchanged.

Signup

This field is for validation purposes and should be left unchanged.