What WCAG 2.2 means for Australian businesses – and why most are still unprepared
WCAG 2.2 has been live since October 2023. Most Australian businesses are still running on 2.1 - or less. Here's what changed, what the risk looks like, and what to
The most common thing we hear when we start talking to businesses about web accessibility is some version of: “we already did that.”
Sometimes it means they had an audit done a few years ago. Sometimes it means they fixed a handful of issues that came up in a complaint. Sometimes it just means they’re aware it’s a thing and assume someone on their team has it handled. What it almost never means is that their site is genuinely, sustainably accessible to the people who need it to be.
WCAG 2.2 was published in October 2023. At this point, well over a year has passed, and the majority of Australian businesses haven’t meaningfully reviewed their position against it. Some are still working to WCAG 2.1. A good number are working to something older than that, or to nothing formally defined at all. The gap between where most organisations think they are and where they actually sit is, in our experience, usually wider than they expect.
Accessibility work tends to be reactive, and without a clear regulatory deadline driving urgency, WCAG 2.2 simply hasn’t made it onto the backlog for most teams. But the standard doesn’t wait, and neither do the users who depend on it.
96.3% of the top one million websites have detectable WCAG failures.
What actually changed in WCAG 2.2
Think of the move from 2.1 to 2.2 as a refinement rather than a ground-up rethink – a set of new success criteria and one removal that reflect how people actually use the web now, including the reality that a large proportion of users are on mobile, and that assistive technology use has grown significantly since 2.1 was published in 2018.
One criterion was removed: 4.1.1 (Parsing), which had become largely redundant given how modern browsers handle HTML errors. Its removal doesn’t change much in practice, but it’s worth knowing if you’re working from a 2.1 compliance checklist.
The additions are where WCAG 2.2 gets interesting. There are nine new success criteria across levels A, AA, and AAA. At AA – which is the level most Australian organisations target – the ones worth understanding are:
Target size (minimum)
Requires that interactive elements like buttons, links, and form controls meet a minimum size of 24×24 pixels. If your interface was designed for desktop and adapted for mobile rather than built mobile-first – and a lot of enterprise systems were – this is probably where gaps will show up.
Dragging movements
Requires that any functionality relying on a drag interaction can also be achieved through a single pointer action – a click, tap, or similar. This matters for users with motor disabilities for whom sustained dragging is difficult or impossible. Sliders, map interactions, and drag-to-reorder functionality are common areas to check.
Accessible authentication (minimum)
The one that tends to surprise teams most. WCAG 2.2 now specifically requires that authentication processes don’t rely on cognitive function tests – which includes the object-identification and text-transcription CAPTCHAs that are still very common in login and form flows. These create real barriers for users with certain cognitive or visual disabilities. If your site has a login, a checkout, or a contact form with a CAPTCHA, this needs to be on your radar.
Redundant entry
If a user has provided information earlier in a process, they shouldn’t have to enter it again at a later step. The classic example is a checkout flow that asks for billing and shipping addresses separately even when they’re the same, but the principle applies across multi-step forms, booking flows, and any process that spans more than one screen. It’s an accessibility improvement that also happens to reduce friction for everyone.
Focus appearance
Sets minimum size and contrast requirements for the visible focus indicator – the outline or highlight that shows keyboard users where they currently are on a page. It’s one of those things that gets accidentally broken in CSS resets, design refreshes, and component library updates, and is surprisingly common to find missing on sites that otherwise score reasonably well on automated accessibility checks.
None of these are obscure edge cases. They’re practical improvements that address real friction points for real users, and most of them have benefits that extend well beyond accessibility.
Why most Australian businesses haven’t caught up
There’s no mandatory deadline for WCAG 2.2 adoption in Australia. The Disability Discrimination Act 1992 creates a legal obligation not to discriminate – and courts and the Australian Human Rights Commission have increasingly looked to WCAG as the de facto standard for determining whether a website meets that obligation – but the DDA doesn’t specify a version, and there was no moment at which businesses were legally required to upgrade from 2.1 to 2.2.
That’s a significant part of why most haven’t. When the update trigger is voluntary rather than regulatory, it has to compete with everything else on the product roadmap. It usually loses. Teams care about accessibility – but without a hard deadline, it gets outcompeted by release work, feature sprints, and everything else with a date attached.
There’s also a confidence problem worth naming. Businesses that commissioned a WCAG audit a few years ago, worked through the findings, and signed off on a remediation plan often feel like they’ve handled accessibility. What they’ve actually done is handle a point-in-time snapshot of their site against a previous version of the standard. The site has likely changed since then. The standard has definitely changed. And the gap between “we passed an audit in 2021” and “we’re genuinely accessible in 2025” is often significant in ways that aren’t obvious without looking.
The global disability market represents $13 trillion in spending power. 69% of those users click away from inaccessible websites without saying a word.
What the risk actually looks like
The legal exposure under the DDA is real, even without a structured enforcement mechanism like the European Accessibility Act or the ADA in the US. Accessibility complaints against Australian organisations have been upheld – the HREOC case involving the Sydney 2000 Olympics website is the landmark example, but the pattern has continued. As awareness of digital rights grows and as accessibility audit tooling becomes more widely available, the likelihood of complaints being made – and taken seriously – is increasing.
But legal risk is probably not the most immediate reason to care. The more direct impact is commercial. The Australian Network on Disability estimates that around one in five Australians has some form of disability. Not all of those involve web accessibility barriers, but a meaningful proportion do – and the users who encounter those barriers mostly don’t complain. They leave. They find an alternative. They don’t come back.
The other thing that often gets missed in this conversation is that accessibility improvements tend to benefit everyone, not just users with disabilities. Better focus indicators help keyboard-only users, a category that includes plenty of people who simply prefer not to use a mouse. Minimum target sizes improve the experience on mobile for everyone. Removing CAPTCHAs reduces friction in login and checkout flows across your entire user base. The overlap between accessibility and good UX is much larger than most teams realise until they start doing the work.
What to do about it
If you’ve had a WCAG 2.1 audit done relatively recently, the practical starting point is a gap analysis against 2.2 rather than a full audit from scratch. The new criteria have a finite surface area – authentication flows, interactive component sizing, focus visibility, drag interactions, multi-step form behaviour. A targeted review of those areas will tell you quickly where you sit.
If you haven’t had any structured accessibility work done in the last couple of years – or if your site has gone through significant changes since the last audit – a proper baseline audit is the right starting point. The goal is an honest picture of where you actually are. You can’t prioritise what you haven’t measured.
The pattern we’d encourage moving away from is the one-off audit and fix sprint cycle. Audit, remediate, done. It feels efficient, but it means accessibility is always playing catch-up with your product. Features get built, design gets updated, third-party components get swapped in – and the compliance picture quietly degrades between audits. Building accessibility into your design and development process from the start, rather than auditing it out after the fact, is a materially different way to work, and it’s how the teams that consistently do it well approach it.
WCAG 2.2 won’t upend everything you’ve already done. But the standard keeps moving, and “we handled this a few years ago” tends to mean less the longer ago that was. If you’re not sure where your site currently sits against it, that’s the right place to start.
Ready to find out where you sit against WCAG 2.2? Talk to our team.
Related articles
Real outcomes, for real Australian organisations.
How accessible design nearly doubled loyalty membership for a leading Australian retailer.