Website accessibility is not something you can ignore in Australia if your organisation has a website, app or digital service.
The Australian Human Rights Commission has made its position clear and your legal exposure is real.
This guide breaks down exactly what WCAG compliance means, who it applies to and what you need to do about it.
What Is WCAG & Why Does It Matter?
The Web Content Accessibility Guidelines (known as WCAG) are an internationally recognised standard created by the World Wide Web Consortium (W3C).
They define how to make digital content accessible to people with visual, hearing, mobility, cognitive and learning disabilities, and neurological disabilities.
WCAG applies not just to websites but to web applications, mobile apps, documents, media and other digital content.
Three versions are relevant in Australia:
- WCAG 2.0 (2008): The foundational version for web accessibility
- WCAG 2.1 (2018): Added criteria for mobile devices, low vision and cognitive disabilities
- WCAG 2.2 (2023): The current version referenced by the Australian Government and AHRC guidance.
WCAG 2.2 is backwards compatible with WCAG 2.1, meaning the upgrade is evolutionary rather than a complete rebuild.
All versions share the same structure: four core principles (Perceivable, Operable, Understandable, Robust), testable statements called success criteria, and three conformance levels.
Across all versions, WCAG has a total of 86 success criteria.
Crucially, accessible web content benefits all users, not just those with disabilities.
Over 16% of the global population has accessibility needs, and accessible design also improves usability for older Australians, people on mobile devices and those on slow internet connections.
Throughout this article, the focus will be on WCAG 2.2 Level AA as the recommended standard for mainstream Australian organisations.
AHRC’s official guidance: “Organisations should conform with WCAG 2.2 at a minimum Level AA and consider appropriate Level AAA success criteria such as video transcripts, audio contrast, clear links and section headings.”
Why Website Accessibility is a Legal Requirement in Australia
Let’s connect the technical WCAG guidelines directly to Australian law to outline the real risks and exposure an online business faces today.
The Disability Discrimination Act 1992
The Disability Discrimination Act 1992 makes discrimination against people with disabilities unlawful in Australia.
Under Section 24, it is illegal to discriminate on the basis of disability in the provision of goods, services and facilities.
Since the early 2000s, courts and the AHRC have interpreted this to include websites, apps and other digital services.
Failing to provide accessible web content can lead to formal complaints and litigation.
The Precedent: Maguire v SOCOG
The landmark case Maguire v Sydney Organising Committee for the Olympic Games (2000) confirmed WCAG applicability under the Act.
A blind user successfully challenged the Sydney Olympics website for lacking alt text and keyboard navigation, establishing that an inaccessible website constitutes unlawful discrimination.
This case remains the pivotal precedent in Australian digital accessibility law.
The AHRC Position
The Australian Human Rights Commission recognises WCAG as a benchmark for digital accessibility.
Its 2025 guidelines state that following the accessibility guidelines (specifically WCAG) is the best way to demonstrate that a digital service is accessible “as far as reasonably possible”.
WCAG compliance is a legal requirement in many jurisdictions worldwide, and while WCAG itself is not a law in Australia, it has become the de facto technical standard used by the AHRC, regulators and courts when assessing whether an organisation has met its obligations under the DDA.
WCAG compliance helps meet obligations under the Disability Discrimination Act directly.
The Three Levels of WCAG Compliance
WCAG success criteria are grouped into three WCAG levels (A, AA and AAA) which are cumulative.
To achieve Level AA, a site must already meet all Level A criteria. Level AAA includes all requirements from Levels A and AA.
Level A – Minimum Baseline
Level A includes the minimum accessibility requirements.
It covers the most fundamental accessibility barriers: providing text alternatives for images, ensuring keyboard access to all interactive elements, avoiding content that causes seizures and allowing users to extend time limits.
A site failing Level A is effectively unusable for many people relying on assistive technologies such as screen readers and alternative input devices.
Level AA – The Australian Standard
Level AA is the standard for accessibility compliance in Australia.
It addresses the most common accessibility barriers: colour contrast ratios, visible focus indicators so users navigate clearly, consistent navigation, form error identification and content reflow on small screens.
The AHRC and most Australian Government policies expect Level AA as a minimum requirement.
Level AAA – Specialist Standard
Level AAA is the most stringent tier, including success criteria such as sign language interpretation for video, extended contrast ratios and advanced support for people with cognitive and learning disabilities.
Level AAA is generally recommended only for certain government services and organisations serving disability communities directly.
Practical guidance: Non-profits, corporates and SMEs should set Level AA as their target, possibly implementing selected Level AAA criteria where they strongly support their audience or risk profile.
Our WCAG 2.2 Level AA Checklist
This checklist is organised under the four WCAG principles to help teams plan remediation and audits.
Detailed technical testing still needs specialist input, but this gives you a solid starting framework.
Perceivable
- Text colour contrast: A minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text, alongside a 3:1 ratio for user interface components and graphical objects.
- Text resizing and reflow: Text can be resized up to 200% without loss of content or functionality, and page layouts reflow down to 320 pixels in width without requiring two-dimensional scrolling.
- Text alternatives: Meaningful alt text for informational images, and null/empty attributes for purely decorative graphics.
- Multimedia alternatives: Synchronised captions and audio descriptions for pre-recorded video.
- Adaptable presentation: Visual cues and meaning are not conveyed solely by colour, shape, size or auditory indicators.
Operable
- Keyboard operability: All interactive functionality is operable via keyboard alone (e.g., Tab, Shift+Tab, Enter, Space, and arrow keys) with no keyboard traps.
- Focus visibility and placement: A clearly visible keyboard focus indicator that is never fully obscured by sticky banners, headers or modal overlays.
- Logical focus order: Sequential navigation through links, buttons and form controls follows a logical reading path.
- Bypass blocks: Mechanisms such as “Skip to main content” links or ARIA landmark roles allow users to jump past repeated navigation menus.
- Minimum target size: Pointer and touch targets have an interactive area of at least 24×24 pixels, unless inline within text or spaced sufficiently apart.
- Pointer gestures and dragging: Any action completed by multi-point gestures or dragging can also be completed using a single pointer tap or click.
Understandable
- Predictable navigation and layout: Navigation menus, component order and repeated user interface elements remain consistent across all pages.
- Input and focus stability: Moving keyboard focus to an element or entering data does not trigger unexpected context shifts (such as automatically submitting a form or redirecting pages).
- Language specification: The default human language of the page (and any inline changes in language) is programmatically declared in the HTML.
- Labels and input guidance: Form controls include descriptive visual labels, placeholder guidance and clear instructions before submission.
- Error identification and suggestions: Form errors are identified in text, pinpoint the exact field and provide actionable suggestions for correction rather than relying solely on colour changes.
- Redundant entry and authentication: Information previously entered in a multi-step process is auto-populated or remembered and logins do not rely on cognitive tests without accessible alternatives.
Robust
- Name, role and value: Every user interface control (native or custom ARIA) programmatically exposes its name, role, state and current value to assistive technologies.
- Form control association: Labels, instructions, error descriptions and required/invalid states are programmatically linked to their corresponding inputs.
- Status messages: Dynamic content updates (such as “Search results updated” or “Item added to cart”) are announced to screen readers via live regions without forcibly shifting keyboard focus.
WCAG 2.2 adds new Level A and AA criteria around focus not being obscured, easier authentication, reduced reliance on dragging gestures and improved help mechanisms.
WCAG 2.2 includes new success criteria for mobile accessibility as well. The guidelines cover navigation, forms and images comprehensively.
For the full technical text, refer to the W3C WCAG 2.2 specification.
Australian Government Policies
WCAG sits within a broader Australian Government policy stack. Here is how the pieces fit together.
Digital Service Standard (DSS) v2.0 (December 2023) requires Commonwealth agencies to ensure that all websites, web apps and major digital transactions apply the latest version of WCAG and “leave no one behind”. In 2026, this means WCAG 2.2 Level AA.
Australian standards enforce accessibility requirements and incorporate WCAG criteria into digital services across all federal agencies.
The Digital Inclusion Standard (DIS) came into effect for new government services from January 2025 and for existing services from mid-2025.
It reinforces inclusive, accessible digital services and requires agencies to report their progress. The DIS explicitly references WCAG conformance and inclusive design principles.
AS EN 301 549:2024 is the Australian standard adoption of European accessibility requirements for ICT products and services.
It references WCAG and applies beyond websites to software, documents, mobile apps and hardware in government procurement.
Other policies: Digital Experience Policy, Australian Government Architecture and “Digital Sourcing Consider First”, collectively require agencies to plan for accessibility and WCAG compliance from the earliest procurement and design stages.
Territory governments align their own digital policies with these federal standards, most referencing WCAG Level AA as a minimum.
Digital Accessibility as a Moral, Commercial and SEO Advantage
Accessibility is more than “just compliance”. It is a lever for inclusion, customer satisfaction and digital performance.
Digital accessibility is a legal, commercial and ethical requirement in Australia.
The Moral Case
Around 5.5 million Australians live with disability, plus many more with temporary or situational impairments.
Accessible design ensures they are not excluded from banking, donations, education, healthcare and other essential digital services.
Inaccessible digital content can damage a brand’s reputation and consumer trust.
The Commercial Case
Users who encounter inaccessible forms, navigation or checkout flows will abandon and often never return.
Accessible websites improve user experience for everyone, not just those with disabilities. Investing in WCAG compliance directly protects revenue and reduces support overheads.
WCAG compliance can also reduce future costs associated with redesigning inaccessible digital assets.
The SEO Case
Improving accessibility can enhance search engine optimisation.
Many WCAG techniques overlap with good technical SEO such as semantic headings, alt text for images, fast and mobile-friendly layouts that all help search engines understand and rank your content better.
Structured data and clean HTML support both accessibility and discoverability.
Implementing WCAG in Website Design
The goal is to incorporate WCAG 2.2 Level AA into every stage rather than treating it as a bolt-on. A holistic approach works best.
Start With An Audit
Commission a WCAG 2.2 Level AA audit to establish a baseline.
Accessibility audits should combine automated tools and manual testing for effectiveness – automated tools can only detect certain accessibility barriers, while manual testing provides a more comprehensive accessibility assessment.
User testing with individuals relying on assistive technologies uncovers barriers missed by automated tools. The audit should produce a prioritised remediation plan.
Integrate Into Design
Colour palettes should be chosen for contrast. Typography and spacing should be designed for readability.
Focus order should be mapped during wireframing, with clear consideration of mobile gestures and touch target sizes across a wide range of devices.
Develop Accessibly
Web developers should use semantic HTML, avoid keyboard traps, structure headings correctly, use ARIA sparingly and test with screen readers and keyboards on desktop and mobile.
Content must be interpreted reliably by a diverse range of user agents and authoring tools.
Train Internal Teams
Internal content teams need to write meaningful content, maintain heading hierarchy in CMS editors, provide transcripts and captions, and avoid uploading inaccessible PDFs where HTML alternatives are possible after launch.
Using various inputs and plain language ensures content is accessible to the widest audience.
Monitor Continuously
Continuous monitoring of accessibility is essential as new content can introduce barriers.
Organisations should publish an accessibility statement to detail their compliance efforts and gaps.
Don’t forget that compliance extends to all digital touchpoints including mobile apps and downloadable documents.
Choosing Accessible Platforms & Vendors
Choosing the right technology stack makes WCAG compliance dramatically easier. Here is a concise buyer’s checklist.
- Ask for proof: Request whether vendors have tested their product against WCAG 2.2 Level AA. Ask for accessibility statements or conformance reports.
- Evaluate platforms carefully: Core platforms like WordPress, Shopify and WooCommerce can support accessibility but themes, plugins and custom code often introduce accessibility barriers if not carefully selected.
- Insist on accessibility-ready components: Themes, form builders and widget libraries should support keyboard navigation, correct ARIA use and sufficient colour contrast. Test these accessibility features before committing.
- Choose the right agency: Work with agencies that demonstrate accessibility expertise and provide other resources like ongoing testing, not just vague “best practice” promises.
What About WCAG 3.0?
While WCAG 2.2 is the current benchmark, the W3C is already actively developing WCAG 3.0.
This upcoming version features a different structure and conformance model that will move away from the A, AA and AAA levels in favour of new, flexible reporting tiers (Bronze, Silver and Gold) and a broader focus on specific functional user needs across various digital platforms.
However, there is no need to pause or delay your current accessibility efforts. WCAG 3.0 is still in the working draft phase and will not replace or deprecate WCAG 2.2 for several years.
Achieving WCAG 2.2 Level AA conformance remains the legal and practical standard in Australia, and doing so will provide your organisation with a solid, future-proof foundation for whenever WCAG 3.0 is officially released.
How We Reach & Maintain WCAG Compliance
White Peak Digital is a web design and conversion optimisation agency with a 100% Australian-based team that helps organisations across Australia achieve and maintain WCAG 2.2 compliance.
WCAG accessibility audits: A structured website audit of your current site or eCommerce store against WCAG 2.2 that includes prioritised issues, risk commentary in plain language and practical remediation recommendations.
Accessible design and development: New builds or redesigns on WordPress, Shopify or WooCommerce that meet agreed accessibility standards and WCAG standards, optimised for speed, SEO and conversion.
We can also address older websites that may have accumulated technical debt across a variety of legacy website platforms such as Joomla, Drupal and BigCommerce.
Technical SEO migrations: When migrating or scaling websites, our technical SEO team ensures changes do not introduce new accessibility issues and uses data-driven insights to align improvements with measurable business outcomes.
Ongoing care plans and training: Regular accessibility health checks, support for internal teams and guidance on maintaining WCAG conformance as your site evolves.
Frequently Asked Questions
Is WCAG 2.2 Level AA legally mandatory for private businesses in Australia?
WCAG is not directly written into the DDA, but the AHRC and courts use WCAG as the benchmark for what is “reasonably” accessible.
Failing to meet WCAG 2.2 Level AA can significantly increase legal risk.
A person who cannot use your site due to accessibility barriers can lodge a disability discrimination complaint, and WCAG conformance will usually be considered when assessing that complaint.
There are no separate accessibility laws naming WCAG explicitly, but it functions as the accepted technical standard in practice.
Does WCAG compliance only apply to websites or also to apps and documents?
WCAG applies to web content broadly, including websites, web applications and web-delivered documents.
Related standards like AS EN 301 549:2024 extend accessibility expectations to software, mobile apps, PDFs and other ICT products.
Organisations should consider all digital touchpoints (website, portal, learning platform, mobile apps and downloadable files) within their accessibility program.
How often should we review our site for WCAG compliance?
Conduct an annual accessibility review at a minimum.
High-traffic or high-risk services such as payments, healthcare, government or major fundraising campaigns should be checked quarterly.
Embed accessibility checks into regular release cycles and content publishing workflows rather than waiting for a large, infrequent audit.
Can automated tools alone guarantee WCAG compliance?
No. Automated tools are useful for catching obvious issues like missing alt text or low contrast, but they typically cover only 30-40% of WCAG success criteria in our experience.
Genuine WCAG conformance requires human review, including keyboard-only testing and testing with screen readers.
Many issues affecting cognitive accessibility and complex user journeys can only be found through manual testing.
What does it cost to make an existing site WCAG compliant?
Costs vary depending on site size, technology stack and current accessibility maturity.
Many SMEs can significantly improve compliance with a focused audit and remediation plan targeting high-impact templates and journeys.
Investment in accessibility often pays back through reduced legal risk, better SEO and improved conversion performance.
