Is WCAG legally required in Australia?

Overview

What the law actually says

Section 24 of the Disability Discrimination Act makes it unlawful for anyone who provides goods, services or facilities, whether for payment or not, to discriminate on the ground of disability: by refusing to provide the service, in the terms or conditions of providing it, or in the manner in which it is provided. Websites, apps and digital documents are services within that section. The Act covers both direct discrimination (section 5) and indirect discrimination (section 6), where a requirement that looks neutral disadvantages people with disability, which is exactly how an inaccessible checkout or PDF form behaves. The main defence is unjustifiable hardship, and it is harder to make out than most organisations assume.

So the honest answer to "is WCAG legally required" is that the DDA does not prescribe a technical standard at all. It prohibits an outcome. WCAG is how everyone, including the Commission and the courts, measures whether that outcome has occurred.

Where WCAG gets its legal weight

In April 2025 the Australian Human Rights Commission published its Guidelines on equal access to digital goods and services, replacing the Advisory Notes it had maintained since the early 2000s. The Guidelines state that organisations should conform with WCAG 2.2 at a minimum of Level AA, and they extend that expectation beyond websites to mobile apps, SaaS platforms, kiosks, AI systems and wearables. They are issued under section 67(1)(k) of the DDA. They are not legally binding, but the Commission can consider them when handling complaints, which makes them the closest thing Australia has to an official statement of what compliance looks like.

What has happened when it was tested

Australia decided the first web accessibility case in the world. In Maguire v Sydney Organising Committee for the Olympic Games (No 2) [2000] HREOCA 31, Bruce Maguire, who is blind and uses a refreshable braille display, complained that the official Olympics website was inaccessible. The Commission held the website was a service under section 24, found unlawful discrimination, and rejected SOCOG's unjustifiable hardship defence, including its attempt to shift responsibility to its technology contractor. SOCOG was ordered to make the site accessible by 15 September 2000. It did not, and in a further decision the Commission awarded Mr Maguire $20,000 in compensation. The AHRC still cites the case as upholding the applicability of WCAG under the DDA.

Later matters have tended to settle rather than run to judgment. In 2014 Gisele Mesnage, a blind screen reader user, brought proceedings against Coles under the DDA over its online shopping site; the case settled in February 2015 with Coles agreeing to improve the site's accessibility. A complaint by Graeme Innes and Nadia Mattiazzo about the Commonwealth Bank's touch screen EFTPOS terminals reached a settlement in the Federal Court, with the bank agreeing to upgrade the terminals' software and train staff and customers. Most matters never become public at all: they resolve in confidential conciliation at the Commission, usually with a commitment to remediate.

The volume is not trivial. In the 2023 to 2024 year the Commission received 1,164 complaints under the DDA, its largest jurisdiction at 43% of all complaints received, and goods, services and facilities was the largest single area with 521 complaints.

How a complaint actually works

1. A written complaint goes to the AHRC. It is free, no lawyer is needed, and anyone affected can lodge one.
2. The Commission investigates and conciliates. Most matters resolve here. Typical outcomes are an agreement to remediate, sometimes with training, a statement or compensation.
3. If conciliation fails, court becomes available. Once the complaint is terminated, the complainant can apply to the Federal Court or the Federal Circuit and Family Court of Australia within 60 days.

The practical consequence: by the time a complaint lands, the cheapest path is nearly always to fix the problem. Organisations that already hold an independent audit and a dated remediation plan are in a much stronger position in conciliation than those starting from nothing.

Where WCAG is explicitly required

• Australian Government. The Digital Experience Policy applies to Commonwealth entities. Its Digital Inclusion Standard requires services to comply with the DDA and the latest version of WCAG, currently WCAG 2.2, with Level AA as the baseline set by the Australian Government Style Manual. It applies to new public facing services from 1 January 2025 and to existing public facing services from 1 January 2026, with agencies reporting to the DTA.
• State governments. NSW requires all government digital products and services, internal and external, to meet the current version of WCAG to Level AA, and other states take similar positions in their own policies.
• Procurement. Australian government ICT procurement uses AS EN 301 549:2024, the Australian adoption of the European accessibility standard, which incorporates WCAG. Suppliers inherit accessibility obligations through tenders and contracts, which is why conformance evidence such as a VPAT or Accessibility Conformance Report is increasingly requested. See our supplier checklist for what evaluation teams ask for.

What this means for your organisation

Whether or not a statute names you, the measuring stick is the same: WCAG 2.2 Level AA. ExceedAbility recommends the same sequence the AHRC's good practice guidance points to: commission an independent WCAG 2.2 AA audit, remediate by severity, publish an honest accessibility statement with a working contact route for access problems, and keep evidence of testing and progress. That is also precisely what conciliation tends to ask of a respondent, so doing it early costs less than doing it under a complaint.