Australia doesn’t have a standalone law that says “your website must be accessible.” Plenty of public sector teams take that as licence to treat accessibility as a nice-to-have. That’s a mistake. Here’s the concrete case for acting anyway.

“It’s not the law” is technically true, and beside the point

There’s no dedicated Digital Accessibility Act in Australia. What exists instead is section 24 of the Disability Discrimination Act 1992 (DDA), which makes it unlawful to discriminate against someone with disability in the provision of goods, services or facilities, and this has been found to apply to websites. That’s a different legal shape to a prescriptive technical law, and it’s why some organisations reason their way into inaction: no named accessibility act, no explicit mandate, no urgency.

That reasoning holds up right up until someone lodges a complaint. The DDA doesn’t need a dedicated accessibility law to bite. It already can, and for government organisations specifically, the exposure is arguably higher than for private business, because a public body failing its own citizens is a harder story to defend than a private company falling short.

The regulator has already moved the bar

In 2026, Australian Human Rights Commission guidance shifted from recommending WCAG to affirming WCAG 2.2 Level AA as the minimum accessibility benchmark. That’s a meaningful change: if a DDA complaint about a government website were ever tested, WCAG 2.2 AA is now the clearest available signal of what “reasonable” looks like. Waiting for a more explicit law misses the point: the regulator has already told you where the bar sits.

You’ve probably already committed to this, on paper

This is the argument that tends to land hardest internally: most agencies are already bound by their own policy framework. The federal Digital Service Standard and Digital Inclusion Standard both require agencies to meet WCAG and build accessibility in from the start, and most state and territory governments have equivalent standards. In practice, the internal case for accessibility work often isn’t “here’s a new obligation.” It’s “here’s the gap between the standard you’ve already signed up to and what your website actually does.” That reframes accessibility from a discretionary spend to a compliance gap against your own stated policy.

The equity case, stated plainly

Around 5.5 million Australians, roughly one in five, live with disability. For a government website, that’s not a niche audience segment; it’s a substantial share of the citizens the service exists to serve, many of whom are trying to access entitlements, payments, or essential information they have every right to reach as easily as anyone else. An inaccessible government site isn’t just a legal exposure. It’s a failure of the basic purpose of a public service.

The reputational case

When an inaccessible government website makes the news, the story isn’t “a private company cut corners.” It’s “the public body responsible for this let people down.” Courts, the media and the public generally hold government organisations to a higher standard than private business precisely because they’re publicly funded and meant to serve everyone. That asymmetry cuts against slow-walking accessibility work, not in favour of it.

Making the case internally

This guide sets out the general policy and legal landscape. It isn’t legal advice for your organisation specifically. If a DDA complaint or dispute is already in play, that’s a conversation for a lawyer, not a website audit.

See how we work with government agencies, or read what a website accessibility audit covers.

Ready to see where the gap actually is?

A WCAG 2.2 AA audit gives you a concrete, prioritised picture of where your site stands: the kind of evidence that makes the internal case for you.

Book a WCAG accessibility audit