Contact Us
Contact Us
UX & Product Design

Accessibility Is a Growth Lever: WCAG 2.2 Basics for Australian Product Teams

Accessibility widens your market and removes friction for everyone. What WCAG 2.2 adds, what Australian law expects, and a starter checklist.

JRC Software Team
6 min read
Accessibility Is a Growth Lever: WCAG 2.2 Basics for Australian Product Teams

A keyboard user tabs into your checkout form. Focus lands on the "Pay now" button, but a sticky chat widget sits right on top of it, so they can't see where they are. A screen reader user on the same page hears "button, button, button" because the icon buttons have no labels. Neither of them complains. They just buy somewhere else.

Most teams leave accessibility until the end of a project: run a WCAG 2.2 scanner, fix the red items, ship. The product passes some automated checks and still shuts out people who use screen readers, keyboards, magnification or voice control, and annoys plenty more who are older, tired or squinting at a phone in the sun.

It's the current version of the international web accessibility standard and a sensible baseline for any Australian product team. The better reason to adopt it is commercial, though. An accessible product reaches more customers and is cheaper to maintain than one retrofitted after a complaint.

Note: This article is general information, not legal advice. Check the official guidance and get advice for your situation.

One in five Australians, and most of the web still fails

The market is bigger than many teams assume. The Australian Bureau of Statistics Survey of Disability, Ageing and Carers found 5.5 million Australians (21.4%) had disability in 2022, up from 17.7% in 2018. That included 2.3 million people aged 65 and over, or 52.3% of that age group.

The W3C's business case for digital accessibility describes people with disabilities as a global market of over 1 billion people. It also notes that accessible design improves the experience for everyone, including people on small screens, older people and anyone on a slow connection.

Meanwhile, most of the web still fails basic checks. The WebAIM Million 2026 analysis, run in February 2026, detected WCAG 2 failures on 95.9% of the top one million home pages, averaging 56.1 errors per page. If your competitors sit in that 95.9%, getting the basics right is a real point of difference.

What Australian law expects

The Disability Discrimination Act 1992 makes disability discrimination unlawful in a range of areas, including the provision of goods, services and facilities (section 24). Many organisations now deliver their services through websites and apps, so it's prudent to treat those as in scope.

The DDA doesn't name a WCAG version or any technical standard. In practice, WCAG conformance is the benchmark most organisations use to show they've taken reasonable steps. Government agencies and their suppliers often face more specific requirements through contracts and procurement. Check current guidance from the Australian Human Rights Commission and get advice for your situation.

Nine new success criteria, six you'll target

The W3C published WCAG 2.2 on 5 October 2023. Content that conforms to 2.2 also conforms to 2.1 and 2.0, and the W3C encourages organisations to use the latest version. WCAG 2.2 is also approved as ISO/IEC 40500:2025.

The W3C's What's new in WCAG 2.2 lists nine new success criteria and the removal of 4.1.1 Parsing as obsolete. Six are at levels A and AA, which is what most organisations target:

Success criterionLevelWhat it means for your product
2.4.11 Focus Not Obscured (Minimum)AASticky headers, cookie banners and chat widgets mustn't completely hide the element with keyboard focus.
2.5.7 Dragging MovementsAAAnything done by dragging, such as reordering or sliders, also needs a single-pointer alternative like buttons.
2.5.8 Target Size (Minimum)AAPointer targets should be at least 24 by 24 CSS pixels, with exceptions such as enough spacing or inline links.
3.2.6 Consistent HelpAHelp options repeated across pages, such as contact details or chat, appear in the same relative order.
3.3.7 Redundant EntryADon't make users re-enter information they already gave in the same process; auto-fill it or let them select it.
3.3.8 Accessible Authentication (Minimum)AADon't require a cognitive test, such as remembering a password or solving a puzzle, without an alternative or help. Supporting password managers and paste counts.

Several of these help every user, not just people with disability. Redundant Entry shortens checkout. Accessible Authentication means not blocking password managers, which cuts failed logins. Bigger targets mean fewer mis-taps on mobile.

Two developer gotchas come up again and again. Blocking paste on password fields (an onpaste handler that returns false) or fighting autofill with autocomplete="off" gets in the way of password managers and works against 3.3.8. And for 2.4.11, CSS scroll-padding-top set to your sticky header height stops focused elements from scrolling under it.

A WCAG 2.2 accessibility testing checklist for your next sprint

Scanners only catch part of the picture, so pair them with short manual checks. Run this on your five most important journeys, such as sign-up, sign-in, search, checkout and contact.

  1. Run an automated scanner on each page and fix contrast, missing alt text, missing form labels, and empty links or buttons. Those were among the most common failures in the WebAIM Million, with low contrast text on 83.9% of home pages.
  2. Put the mouse away and complete each journey with the keyboard only. Focus should always be visible and never hidden behind sticky elements.
  3. Turn on a screen reader (VoiceOver on Apple devices, TalkBack on Android, NVDA on Windows) and check headings, buttons and form errors are announced sensibly.
  4. Zoom the browser to 200% and check nothing is cut off or overlapping.
  5. Check every icon button and small link meets the 24 by 24 CSS pixel target size, or has enough spacing around it.
  6. Confirm sign-in allows paste and password managers, and offers an alternative to any puzzle CAPTCHA.
  7. Check multi-step forms don't ask for the same information twice.
  8. Make sure anything done by dragging also works with simple taps or clicks.
  9. Check help or contact options sit in the same place on every page.
  10. Test with a few real users with disability before a major release.

Put the automated checks in your CI pipeline so regressions get caught before release, and keep the manual checks in your definition of done for new features.

How JRC Software runs an accessibility audit

Week one is evidence. Our UX and product design team takes your top journeys and tests them against WCAG 2.2 level AA with automated scans, keyboard-only runs, and screen reader passes on at least one desktop and one mobile reader. We also review your shared components, because that's usually where the problems start.

You get a prioritised list: each issue with the user impact, the success criterion it fails, the component it lives in, and a recommended fix. Most of the time the fix list is shorter than the issue list, because a handful of shared components, tokens and patterns cause most of the failures. That's why we recommend building accessibility into a small design system. We apply the same standard to onboarding flows and AI features, where gaps tend to hide.

If someone suggests an accessibility overlay widget as the fix, push back. It doesn't fix the underlying markup.

If you want to reach more Australian customers and cut your risk at the same time, book an accessibility audit and we'll show you where to start.

Frequently asked questions

What is WCAG 2.2?

WCAG 2.2 is version 2.2 of the Web Content Accessibility Guidelines, published by the W3C on 5 October 2023. It adds nine success criteria to WCAG 2.1, covering areas such as focus visibility, target size, dragging alternatives and accessible sign-in. Content that conforms to WCAG 2.2 also conforms to the earlier 2.1 and 2.0 versions.

Is WCAG 2.2 a legal requirement in Australia?

Not by name. The Disability Discrimination Act 1992 doesn't mention WCAG, but it makes disability discrimination unlawful in providing goods, services and facilities, which can include websites and apps. WCAG conformance is the common benchmark organisations use to show they've taken reasonable steps. This is general information, not legal advice, so check official guidance for your situation.

How do I start accessibility testing?

Start with your most important user journeys. Run an automated scanner, then complete each journey using only a keyboard and again with a screen reader. Check colour contrast, form labels, focus visibility and target sizes. Automated tools miss many issues, so manual testing and feedback from users with disability belong in any accessibility testing plan.

Does accessibility improve conversion?

It removes barriers that slow everyone down, which helps conversion. Forms without repeated entry, larger tap targets, clear focus states and sign-in that works with password managers all cut friction in key journeys. It also opens your product to the 5.5 million Australians with disability counted by the ABS in 2022, a market inaccessible competitors miss.

UX & Product Design

Book an accessibility audit

Tell us where you're stuck and we'll come back with practical next steps.

Get in touch

Sources