Accessibility requirements for Australian government websites

Australian government websites are expected to meet WCAG 2.1 AA (moving to 2.2 AA) under the Digital Service Standard, sitting on top of the Disability Discrimination Act 1992, which has covered web content since the Sydney Olympics case in 2000. If you build, run or sell into government digital services, WCAG conformance is a requirement, not a preference.

The legal foundation: the DDA

The Disability Discrimination Act 1992 makes it unlawful to discriminate against people with disability in the provision of services — and the Australian Human Rights Commission established in Maguire v SOCOG (2000) that this includes websites. A blind user complained that the Sydney Olympics site was inaccessible; the Commission agreed and ordered fixes. That precedent has stood for a quarter of a century.

Two things follow. First, the DDA applies to every organisation serving the Australian public, not just government. Second, for government specifically, the AHRC’s own advice points to WCAG as the benchmark for what non-discriminatory web content looks like.

The policy layer: the Digital Service Standard

The federal Digital Service Standard requires government services to be accessible, with WCAG AA as the operative benchmark — 2.1 AA as the established baseline, and 2.2 AA the target as policies refresh. In practice this covers:

• Public websites and transaction services — the obvious surface.
• Internal and staff-facing systems — the DDA protects employees too; agencies increasingly hold intranets and internal tools to the same bar.
• Documents — PDFs published by agencies are content and are expected to be accessible, which is routinely where agencies struggle most.
• Procured software — anything an agency buys becomes part of its service. This is why accessibility clauses appear in tenders.

States and territories mirror this with their own policies (NSW, Victoria, Queensland and others all reference WCAG AA), so the practical answer is the same nationwide.

What this means for agencies

The uncomfortable operational truth: a passed audit at launch doesn’t keep a service conformant. Content publishing, CMS updates and vendor releases all drift. The agencies that hold the line treat conformance as monitoring, not certification:

1. Baseline every public service against WCAG AA — automated scanning across pages first, manual checks (keyboard, focus, screen reader, zoom) on key flows.
2. Fix by component and template, not page by page — government sites are template-heavy, which makes component-level fixes unusually high-leverage.
3. Scan continuously so new content and releases can’t silently reintroduce the common failures.
4. Keep evidence — scan history, manual check records and remediation logs are what you produce when an audit or complaint arrives.

What this means for vendors

If you sell software to Australian government, your product’s accessibility is assessed during procurement. Expect tenders to ask how you conform to WCAG 2.1/2.2 AA and to request evidence — increasingly in the form of an Accessibility Conformance Report (VPAT/ACR).

The vendors who win these evaluations aren’t the ones claiming perfection; they’re the ones with a current, honest report backed by real testing, plus a credible remediation roadmap for the gaps. “We’ve never been asked before” reads as risk; a dated ACR with specific remarks reads as competence.

Getting started

Whether you’re an agency team or a vendor selling in:

• Target WCAG 2.2 AA for new work — it’s a superset of 2.1 AA, so you can’t be caught behind a policy update (what changed in 2.2).
• Scan your highest-traffic services first and fix criticals — alt text, labels, contrast and heading structure clear the bulk of raw findings fast.
• Schedule the manual checks automation can’t judge: keyboard-only passes, focus behaviour, screen reader flows on your top transactions.
• Produce evidence as you go so the next tender, audit or complaint is a document-retrieval exercise, not a crisis.

Australia’s requirements aren’t exotic — they’re the same WCAG baseline as the rest of the world, enforced through the DDA and procurement. The differentiator is simply whether conformance is something you did once or something your service does continuously.

Frequently asked questions

What accessibility standard do Australian government websites have to meet?

WCAG 2.1 Level AA is the working baseline, required through the Digital Service Standard for federal services, with states and territories imposing equivalent requirements. Agencies are progressively moving to WCAG 2.2 AA as policies update, so new work should target 2.2.

Does the Disability Discrimination Act apply to websites?

Yes. The DDA has applied to web content since Maguire v SOCOG in 2000, when the Human Rights Commission found the Sydney Olympics website discriminated against a blind user. It covers both government and private organisations providing services to the Australian public.

Do vendors selling software to Australian government need to prove accessibility?

Increasingly, yes. Government buyers assess accessibility during procurement, commonly by asking for WCAG conformance evidence or an Accessibility Conformance Report (VPAT/ACR). No evidence often means no shortlist.

Is there a penalty for non-compliant Australian government websites?

Enforcement runs through DDA complaints to the Australian Human Rights Commission, which can lead to conciliation and Federal Court action. For agencies the bigger practical drivers are policy obligations, audit findings and the political cost of excluding citizens from essential services.