Summary
WCAG 2.2 compliance defines how Australian websites must design and test digital services so people with disabilities can access them. The update expands accessibility guidance around focus visibility, authentication, and mobile interaction. For organisations operating government, financial, and service platforms, WCAG 2.2 introduces practical design, research, and testing obligations that reduce legal risk and improve customer experience quality.
What Is WCAG 2.2 Compliance?
The Web Content Accessibility Guidelines, usually shortened to WCAG, are the international standard for accessible digital services published by the World Wide Web Consortium. WCAG 2.2 expands earlier versions of the framework by adding new success criteria designed to address modern interaction patterns, particularly mobile usage and cognitive accessibility.
Australia follows WCAG through government policy frameworks such as the Digital Service Standard and the Australian Government Accessibility requirements. Public sector organisations generally require WCAG 2.1 Level AA compliance, and many agencies are now moving toward WCAG 2.2 as the new benchmark¹.
WCAG defines accessibility across four principles:
- Perceivable
- Operable
- Understandable
- Robust
Each principle contains testable success criteria. These criteria describe how websites must present content, support keyboard navigation, provide alternatives for visual or auditory media, and maintain predictable interactions for users with assistive technologies.
For organisations delivering customer portals, digital service channels, or enterprise platforms, WCAG compliance is now tightly connected to customer experience design and digital risk management.
Why Are Australian Organisations Moving Toward WCAG 2.2?
Digital service delivery has shifted heavily toward mobile devices and multi-factor authentication. Older accessibility rules did not always account for these patterns.
WCAG 2.2 closes several practical gaps.
It adds new requirements for focus indicators, target sizes, authentication flows, and consistent help mechanisms. These updates reduce friction for users who rely on keyboard navigation, screen readers, or cognitive support tools.
Accessibility affects a large share of the Australian population. Around 21 percent of Australians live with disability according to the Australian Bureau of Statistics². When websites fail accessibility tests, those users experience barriers to completing tasks such as applying for services, managing accounts, or submitting forms.
Regulators also expect accessible design. The Disability Discrimination Act allows legal action when digital services prevent equitable access³. Organisations that treat accessibility as part of CX governance reduce both compliance exposure and service failure.
How WCAG 2.2 Works in Practice
WCAG 2.2 introduces nine new success criteria and modifies several earlier ones. Each criterion is testable through structured accessibility audits.
New Focus Appearance Requirements
Keyboard users rely on visible focus indicators to understand which element is active on the page. WCAG 2.2 requires stronger visual contrast and larger focus indicators so users can track navigation without a mouse.
Many existing websites fail this requirement. Design systems frequently hide focus styles during aesthetic redesigns.
Accessible Authentication
Authentication processes often require cognitive tasks such as memorising passwords or solving puzzles. WCAG 2.2 requires that authentication not rely solely on memory tests unless alternatives are provided.
Examples include:
- Password managers
- Copy-paste functionality
- Biometric login
- Magic links or secure tokens
Target Size for Interactive Elements
Mobile interaction presents a common barrier. Small buttons create problems for users with limited dexterity.
WCAG 2.2 introduces minimum target sizes for interactive elements so touch navigation remains usable.
These adjustments appear small. But they have measurable effects on usability and task completion.
WCAG 2.2 vs WCAG 2.1: What Changed?
WCAG 2.2 builds on WCAG 2.1 rather than replacing it. Organisations already compliant with 2.1 Level AA will recognise most requirements.
But several new areas require attention.
Key additions include:
- Focus Appearance (Minimum)
- Focus Not Obscured
- Accessible Authentication
- Consistent Help
- Dragging Movements
- Target Size (Minimum)
These additions reflect research on common barriers faced by users with motor, cognitive, and visual impairments⁴.
For Australian organisations managing complex digital services, the biggest operational change is not design rules. It is testing scope. Accessibility validation must now include more interaction scenarios, including mobile behaviour and authentication flows.
How Do CX Research and Design Teams Achieve WCAG 2.2 Compliance?
Accessibility rarely succeeds when treated as a late-stage technical check. It works best when embedded inside customer research and design practice.
Structured accessibility research often includes:
- Screen reader testing with NVDA, VoiceOver, or JAWS
- Keyboard-only navigation testing
- Cognitive load testing for complex forms
- Mobile usability testing with accessibility settings enabled
- Automated accessibility scanning tools
Organisations commonly integrate these tests within CX research and design programs. The approach connects accessibility requirements with real customer behaviour, rather than treating compliance as a checklist exercise.
For teams building accessible digital services, the first step usually involves a structured accessibility review supported by specialist research and design expertise.
See the CX Research and Design framework:
https://customerscience.com.au/solution/cx-research-design/
This approach combines accessibility audits with usability testing, helping organisations identify barriers early in the design lifecycle.
Where WCAG 2.2 Applies Across Digital Services
WCAG compliance applies broadly across digital channels used by customers or employees.
Common examples include:
- Government service portals
- Online banking platforms
- Insurance and health portals
- Utility provider customer dashboards
- Public information websites
- E-commerce platforms
But accessibility is not limited to websites.
Digital forms, documents, dashboards, and automated service systems must also meet accessibility expectations when used in regulated environments.
Large enterprises often include WCAG checks inside digital service governance frameworks so new products meet accessibility standards before launch.
What Risks Occur When Websites Ignore Accessibility?
Accessibility failures create operational, legal, and reputational risks.
Service failures are the most immediate impact. Users who cannot complete tasks often move to call centres or in-person support channels. That increases operational costs.
Legal exposure also exists. Complaints under the Disability Discrimination Act have already involved inaccessible websites and online forms³.
But another issue sits underneath. Poor accessibility often signals broader design problems. Low contrast text, inconsistent navigation, or confusing authentication flows affect many users, not only those with disabilities.
When organisations improve accessibility, usability metrics often improve at the same time.
How Do Organisations Measure WCAG Compliance?
Accessibility performance can be measured through a combination of automated tools and manual testing.
Typical metrics include:
- Percentage of pages passing WCAG automated checks
- Keyboard navigation success rate
- Screen reader task completion rates
- Accessibility issue severity scores
- Compliance against Level A and Level AA success criteria
Enterprise organisations often combine these metrics with customer insight platforms that track usability issues across digital services.
For example, the Customer Science Insights platform helps teams capture and analyse customer feedback linked to digital experiences and accessibility performance.
Learn more about the platform:
https://customerscience.com.au/csg-product/customer-science-insights/
This type of measurement creates a continuous accessibility improvement cycle rather than a one-off compliance project.
What Should Organisations Do Next?
WCAG 2.2 introduces incremental changes, not a full redesign requirement.
Most organisations follow a structured pathway:
- Conduct a WCAG accessibility audit
- Identify gaps against WCAG 2.2 Level AA criteria
- Prioritise high-impact usability barriers
- Update design systems and component libraries
- Validate accessibility through user testing
Accessibility maturity grows over time. Organisations that embed accessibility into CX governance often see fewer redesign costs and stronger digital adoption.
And that shift matters. Digital services now sit at the centre of customer interaction across government, banking, insurance, and utilities.
Accessibility is simply part of delivering reliable digital service.
Evidentiary Layer
Research consistently shows that accessible design improves service outcomes across broad populations.
Studies of government digital services show accessibility improvements increase task completion and reduce support requests⁵. Screen reader usability research also shows that inconsistent navigation and weak focus indicators remain among the most common failure points on public websites⁶.
Mobile accessibility testing further highlights the impact of small interactive targets and complex authentication flows on user success⁷.
The WCAG 2.2 update addresses these patterns directly. It reflects real interaction failures observed across large-scale digital systems.
For organisations delivering public-facing digital services in Australia, compliance is increasingly linked to service quality, regulatory expectation, and customer trust.
FAQ
What is WCAG 2.2 compliance in Australia?
WCAG 2.2 compliance means designing digital services so people with disabilities can access content, navigation, and interaction features. Australian government policy aligns with WCAG Level AA standards for public services.
Is WCAG 2.2 legally required in Australia?
The guidelines themselves are not legislation. But inaccessible websites may breach the Disability Discrimination Act if users cannot access essential services³.
What changed in WCAG 2.2 compared with WCAG 2.1?
WCAG 2.2 adds new requirements around focus visibility, authentication accessibility, target sizes, and consistent help systems. These updates address mobile and cognitive accessibility issues.
How do organisations test accessibility?
Testing combines automated scanning tools with manual usability testing using assistive technologies such as screen readers and keyboard-only navigation.
How can Customer Science help with WCAG accessibility?
Customer Science provides structured accessibility research, digital experience evaluation, and CX consulting to identify barriers and improve inclusive service design.
Explore the Knowledge Quest platform:
https://customerscience.com.au/csg-product/knowledge-quest/
Does accessibility improve customer experience?
Yes. Accessibility improvements often reduce usability barriers across the entire customer base. Clear navigation, readable text, and consistent interactions improve completion rates for all users.
Sources
- World Wide Web Consortium. Web Content Accessibility Guidelines (WCAG) 2.2. https://www.w3.org/TR/WCAG22/
- Australian Bureau of Statistics. Disability, Ageing and Carers, Australia 2022. https://www.abs.gov.au/statistics/health/disability
- Australian Human Rights Commission. Disability Discrimination Act guidance. https://humanrights.gov.au
- W3C Accessibility Guidelines Working Group. WCAG 2.2 Candidate Recommendation research notes. https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/
- UK Government Digital Service. Accessibility monitoring of public sector websites. https://www.gov.uk
- Lazar J, Goldstein D, Taylor A. Ensuring Digital Accessibility Through Process and Policy. Morgan Kaufmann, 2019.
- Bigham J et al. Accessibility in Mobile Interaction Design. ACM Transactions on Accessible Computing. https://doi.org/10.1145/3290605
- ISO 30071-1:2019. Accessibility of ICT products and services. International Organization for Standardization.
- Australian Government Digital Transformation Agency. Digital Service Standard. https://www.dta.gov.au
- WAI-ARIA Authoring Practices 1.2. W3C. https://www.w3.org/TR/wai-aria-practices/