If you run a website or digital service, you've probably heard the words "accessibility" and "WCAG" in the same sentence. That goes for government departments, NFPs, schools and businesses alike. You may have nodded and moved on. This article is for the moment you decide to stop nodding.
WCAG 2.2 is a standard for web accessibility that's used around the world. It isn't legislation (in Australia, that's the Disability Discrimination Act and the Web Accessibility National Transition Strategy), but it is a practical benchmark for what an accessible website actually looks like.
What is WCAG, and why should a non-technical person care?
WCAG stands for Web Content Accessibility Guidelines. It's published by the World Wide Web Consortium (W3C), the international body that sets web standards. It exists because, for a lot of people, the web is really hard to use.
Around 1 in 6 Australians live with some form of disability. Many more have temporary or situational impairments, like a broken arm, bright sunlight, a noisy room or a slow connection. Building for accessibility helps all of them. It also helps people whose first language isn't English, busy people skimming on their phones, and anyone under stress who needs information quickly.
What changed in version 2.2.
WCAG 2.2 was published in October 2023. The changes are fairly modest (nine new success criteria and one removed), but they cover things that matter. These are the ones we'd want any team to know about:
- Focus appearance (2.4.11): Focus indicators must have a minimum size and contrast, so a barely visible dotted outline won't cut it at AA any more.
- Target size minimum (2.5.8): Anything people tap or click must be at least 24×24 CSS pixels. Small tap targets, especially on mobile, are a real barrier for people with motor difficulties.
- Redundant entry (3.3.7): If you've already asked for something, don't make people type it in again in the same session.
- Accessible authentication (3.3.8): Don't make people solve puzzles or copy out characters to log in, unless you offer another supported way in.
What happened to 2.1?
WCAG 2.1 is still valid. WCAG 2.2 is backward compatible, so if you meet 2.2, you meet 2.1. If you're already aiming for 2.1 AA, the gap to 2.2 AA is manageable and shouldn't mean a full rebuild. If you're starting fresh, 2.2 AA is the better target.
What this means for Australian organisations.
For government agencies, WCAG 2.0 Level AA is the mandatory standard under the Web Accessibility National Transition Strategy. That standard lags behind WCAG 2.2 guidance. Agencies should be targeting 2.2 AA, not because every clause is legally mandated, but because it better reflects how people use digital services.
For private and non-government organisations, the Disability Discrimination Act 1992 means you have to take reasonable steps toward accessibility. Saying "we didn't know WCAG 2.2 was the standard" won't hold up as a defence. The Australian Human Rights Commission has said outright that inaccessible websites can be unlawful discrimination.
Where to start.
Start with an automated scan. Tools like axe or Lighthouse catch about 30-40% of issues on their own. Next, do a keyboard pass: tab through every page without touching the mouse. Then, if you can, test with a screen reader.
If that sounds like a lot, it's what we're here for. We help organisations work out where they stand against WCAG 2.2 AA. Then we help them get there in practical steps, at a pace that suits them, and we keep it all in plain English.