What is the latest version of WCAG?

The latest version of WCAG is 2.2, released in October 2023. It builds on previous versions and adds nine new accessibility requirements, most of which aim to make life easier for people with cognitive or physical impairments. In short, it’s not a massive shift, but it’s definitely one worth knowing about.

If your site already complies with WCAG 2.1 (which it should, especially if you’re in the public sector), then you’re already most of the way there. But 2.2 tightens things up. It focuses on the real-world challenges people face when using websites, fiddly buttons, disappearing form help, inconsistent navigation, things that might seem small, but aren’t when you’re the person being affected by them.

What exactly is WCAG?

Let’s rewind briefly. WCAG stands for Web Content Accessibility Guidelines. It’s not the most glamorous acronym in the world, but it does a lot of heavy lifting when it comes to inclusion.

Put simply, WCAG tells you how to make your website usable for as many people as possible. It’s published by the World Wide Web Consortium (W3C), the people responsible for setting the standards that keep the web working as it should.

The guidelines are based on four principles: your content should be perceivable, operable, understandable and robust. If that sounds a bit like something off a government whiteboard, that’s because it sort of is. But in practice, these principles mean things like:

• Can someone navigate your site using just a keyboard?
• Does your colour contrast work for people with low vision?
• Is your content structured properly so screen readers can interpret it?
• Are your buttons big enough to tap without needing surgeon-level precision?

WCAG covers all this and more.

A quick look back

The original WCAG 2.0 came out in 2008. It was solid, but the internet looked very different then. Phones weren’t yet the default browsing device. Tablets were still novel. Accessibility was something you often saw bolted on as an afterthought.

In 2018, WCAG 2.1 arrived. It added 17 new success criteria to deal with mobile browsing, visual impairments and cognitive challenges. Things like orientation lock, improved input methods and better contrast all became clearer and more enforceable.

And now we have 2.2, which extends things again. This time, it’s a more focused update. Less about broad trends, more about smoothing out everyday frustrations.

So what’s new in 2.2?

WCAG 2.2 adds nine new success criteria. These aren’t sweeping changes, but they tackle some long-standing usability issues. Think of them as quality-of-life improvements.

Here are a few examples:

• Interactive elements (like buttons and links) now need to meet a minimum size. If you’ve ever tried to tap a tiny link on your phone with cold fingers, you’ll know why this matters.
• Drag-and-drop interactions must have alternatives. Not everyone can hold and drag a mouse or finger steadily across a screen.
• Help content, like contact info or live chat, should appear in the same place on every page. That way, users aren’t stuck hunting around when they need it most.
• Focus indicators, the outlines that show where you are on a page when using a keyboard, must always be visible. Hidden focus means lost users.

There’s also been a clean-up. One outdated criterion has been removed entirely. It related to how code was parsed for assistive tech, but modern browsers have made that concern more or less irrelevant.

Who needs to care?

If you’re working in the public sector, you probably already know the answer. In the UK, government websites and digital services are required to meet WCAG 2.1 AA as part of the Public Sector Bodies Accessibility Regulations. WCAG 2.2 isn’t law yet, but it’s expected to become the new standard in time. And even if the legal requirement hasn’t caught up, the moral and practical argument is already there.

For everyone else, private companies, charities, agencies, you’re not off the hook. The Equality Act 2010 still applies. If your website isn’t accessible, you could be seen as failing to make reasonable adjustments. More importantly, you’re making it harder for customers to do business with you.

And honestly, accessibility is just good design. Cleaner layouts, clearer content, more consistent navigation, these things help everyone, not just users with disabilities.

Is upgrading to 2.2 difficult?

That depends on where you’re starting from.

If your site already meets WCAG 2.1 AA, then you’ve done most of the hard work. The changes in 2.2 are more about refinement than reinvention. You might need to adjust button sizes, review how help content is displayed, or tweak your form behaviour, but it’s all manageable.

If, on the other hand, accessibility has never been a priority, then you could be looking at something more substantial. It’s a bit like home renovations. If the structure is sound, a fresh coat of paint will do. If the foundations are cracked, you’ve got some rebuilding to do.

Either way, the best place to start is with an accessibility audit. It’s not just about ticking boxes. It helps you understand how your site performs in the real world, and where the biggest usability barriers are hiding.

What about WCAG 3.0?

WCAG 3.0 is in development, but don’t panic. It’s still a long way off and it won’t replace WCAG 2.2 overnight. The goal is to eventually move from a strict pass/fail system to a more nuanced scoring model. It’ll offer flexibility and reflect real user experience more accurately, but right now, it’s still a work in progress.

Until then, WCAG 2.2 is where your focus should be. It’s stable, well-supported and represents the current best practice for digital accessibility.

Wrapping Up

Accessibility isn’t a box to tick at the end of a project. It’s something that should be baked into how you plan, build and maintain your website. WCAG 2.2 is the latest step in making that easier to do, not just for developers, but for users who need the web to work for them, not around them.

Whether you’re working in government, healthcare, education or the private sector, getting your site in line with the latest guidelines isn’t just about avoiding complaints. It’s about building something better.

If you’re not sure where to start, an audit is a smart first move. If you’ve already done the groundwork, now’s a good time to check whether your site’s ready for the next stage.

And if you’re still stuck with a site from 2014 that breaks every accessibility rule in the book? Well, now’s the perfect excuse to sort it properly.