DDA compliance and WCAG AA in Australia

The Disability Discrimination Act 1992 (Cth) makes it unlawful to discriminate against a person on the basis of disability in the provision of goods, services and facilities. Web services count. This page covers how the DDA applies to digital services, what the Australian Human Rights Commission has said in published guidance, and the small number of decided cases that shape the practical compliance bar.

The legal framing

The DDA does not name "websites" or "WCAG" in its primary text, but Section 24 (goods, services and facilities) and the AHRC's published Advisory Notes treat web accessibility as falling within the Act's scope. The 2014 World Wide Web Access: Disability Discrimination Act Advisory Notes confirm this and recommend WCAG 2.0 Level AA as the operating standard for Commonwealth and most State Government services. WCAG 2.1 has been in widespread Australian regulatory use since 2018, and 2.2 is increasingly the working baseline in new tender frameworks.

The case law

The most-cited Australian decision remains Maguire v Sydney Organising Committee for the Olympic Games (2000), where the Human Rights and Equal Opportunity Commission found that an inaccessible Olympics website constituted unlawful discrimination. The decision established that complainants do not need to prove malicious intent; functional inaccessibility alone is sufficient.

Subsequent matters have largely settled before formal hearings, often via undertakings to remediate. Decided settlements have involved retail e-commerce, financial services, and government customer-service portals. The Australian Human Rights Commission publishes settled-matter summaries that are useful precedent reading even where the cases did not produce binding judgments.

What the AHRC actually expects

From the published Advisory Notes and the Commission's outreach work:

• WCAG 2.0 AA is the documented minimum, with 2.1 and 2.2 increasingly expected in modern services.
• An accessibility statement is recommended on the site, including a contact path for accessibility issues and a target response time.
• Reasonable adjustment provisions in the DDA mean a site that does not meet AA must offer alternative ways to access the underlying service (phone, in-person, accessible form). Pure web-only services with accessibility gaps carry higher risk.
• Complaints are usually resolved at the conciliation stage. Most matters never reach a hearing.

Practical implications

For most Australian organisations, DDA compliance work translates to a small set of operational commitments:

1. Adopt WCAG 2.2 AA as the documented standard.
2. Audit the site annually against that standard.
3. Publish an accessibility statement covering scope, current status, known gaps, and a contact path.
4. Maintain a remediation roadmap that addresses identified gaps within a reasonable timeframe.
5. Have a non-digital path for users who cannot use the digital service.

The procurement angle is increasingly material. Most Commonwealth tenders, several State Government frameworks, and a growing list of enterprise procurement processes now require WCAG 2.2 AA conformance evidence as part of the bid. Failure to demonstrate it can be a disqualifying factor.

Document hosting and the DDA

If your site hosts PDFs, those count. PDFs uploaded to government and advocacy sites must meet PDF/UA accessibility standards to be DDA-compliant. Our PDF accessibility guide covers the production workflow.