Effectively yes, though not in the way most people expect. There is no Australian statute that says "your website must meet WCAG".

What exists is the Disability Discrimination Act 1992, which makes it unlawful to discriminate in the provision of goods, services and facilities, and that has been applied to websites.

So the obligation is broad and outcome-based, and the Web Content Accessibility Guidelines are the practical measure everyone uses to show you have met it.

If your site cannot be used by someone with a disability, the absence of a WCAG law is not a defence.

This one gets waved away a lot, usually with "we are not government, so it does not apply to us". That is the single most common misreading of how the DDA works.

What the DDA actually says

The Disability Discrimination Act 1992 makes it unlawful to discriminate against a person on the ground of disability in the provision of goods, services and facilities. It does not mention websites, because it was written in 1992. It does not need to. The obligation attaches to the service, and a website is how most businesses now provide theirs.

The landmark Australian case is Maguire v Sydney Organising Committee for the Olympic Games, heard by the Human Rights and Equal Opportunity Commission in 2000. A blind complainant could not use the official Olympics website. The complaint succeeded. That is the precedent Australian web accessibility has rested on ever since, and it involved a private organising committee, not a government department.

The Australian Human Rights Commission publishes advisory notes on web accessibility under the DDA, which point to the Web Content Accessibility Guidelines as the way to meet the obligation. The Commission's guidance is advisory, which people sometimes read as optional. It is better read as the measure a court or a conciliation process will reach for when deciding whether you discriminated.

Where WCAG comes in

WCAG is a technical standard from the W3C, organised into levels A, AA and AAA. Level AA is the working benchmark almost everywhere, including Australian practice.

For federal government services, the requirement is explicit: the Australian Government's Digital Service Standard requires digital services to be accessible, with WCAG as the measure. If you sell to government, or you are a supplier inside a government service, this reaches you contractually even though the DDA reaches you anyway.

For everyone else the standard is not legislated, it is evidentiary. Meeting WCAG AA is how you demonstrate you did not discriminate.

The bit that has changed: AI is writing your pages now

Here is where this becomes a live problem rather than a 2015 problem.

A lot of website content is now generated, and generated content fails accessibility in specific, repeatable ways. Not because the writing is bad, but because accessibility lives in the structure and the attributes, which is exactly what a content tool tends to treat as decoration.

The failures we see most:

  • Images with empty or meaningless alt text. A generated alt="image" is worse than nothing, because it passes an automated check while telling a screen reader user nothing.
  • Heading levels used as sizes. An H4 chosen because it looked right, inside a page with no H2. Screen reader users navigate by heading structure, so this breaks the page's table of contents.
  • Link text that says "click here" or "read more". Generated repeatedly, on the same page, so a user listing the links hears "read more" nine times.
  • Colour used as the only way to convey meaning. A red chip meaning overdue, with nothing else that says overdue.
  • Contrast failures in generated components, especially light grey secondary text, which is the single most common automated finding on any site.
  • Forms with placeholder text instead of labels. The placeholder disappears when typing starts and is frequently not read as a label at all.

None of this is exotic. All of it is cheap to fix while the page is being built, and tedious to fix across 200 pages afterwards.

The internal systems people forget

The DDA is about discrimination in employment as well as in services. An internal portal, a timesheet tool, a training platform or an intranet that an employee with a disability cannot use is an employment problem as much as a website one.

This is worth a thought if you have been building internal tools quickly with AI assistance, because internal tools rarely get an accessibility review and often get built fastest.

What automated testing will and will not find

Run an automated checker and you will catch contrast, missing alt attributes, missing form labels and some structural problems. That is genuinely worth doing and it is the cheapest pass available.

It will not catch whether the alt text is accurate, whether the heading structure makes sense, whether the page can be operated by keyboard alone, or whether a screen reader user can actually complete your booking flow. Those need a person. The gap between "passes an automated scan" and "usable" is where most of the real exposure sits, and it is the part a generated page is most likely to fail.

What we do on client builds

Structure first, at build time. Headings in real order, labels on form fields, alt text written by whoever knows what the image is for, and focus states that are visible. Doing this during the build costs close to nothing. Retrofitting it is a project.

Keyboard test every interactive thing. Menus, modals, carousels, booking widgets, video players. If you cannot tab to it and operate it, it is not finished. This catches more real problems than any scanner.

Never let colour carry meaning alone. Every status that has a colour also has a word or a shape.

Check the generated pages as well as the template. A perfectly accessible template filled with generated pages carrying "click here" links is still a failing site. That is the check that gets skipped.

If you are building or rebuilding on HubSpot, structure matters earlier than people expect, which is part of why we wrote the complete guide to HubSpot CMS integration architecture.

And if AI is producing content across your business, accessibility belongs in the rules you set for it. We covered writing those in who signs off on AI, a one page AI policy you can actually use.

In short

No Australian law names WCAG, and that does not help you. The Disability Discrimination Act 1992 makes discrimination in providing a service unlawful, websites have been held to that standard since the Maguire case in 2000, and WCAG AA is how you show you met it.

The new pressure is generated content, which fails in structural ways an automated scan half catches. Fix it at build time, test with a keyboard, and check the pages rather than only the template.

Frequently asked questions

Is web accessibility a legal requirement in Australia? There is no statute naming WCAG, but the Disability Discrimination Act 1992 makes it unlawful to discriminate in providing goods, services and facilities, and that has been applied to websites since Maguire v SOCOG in 2000. The obligation applies to private businesses as much as to government.

What WCAG level should an Australian business meet? Level AA is the working benchmark in Australian practice and is what accessibility guidance and government requirements point to. Level A is insufficient in practice and AAA is not expected of most sites.

Does the DDA apply to internal systems? Yes. The Act covers discrimination in employment as well as in services, so an internal portal, intranet or training platform that an employee with a disability cannot use creates exposure.

Will an automated accessibility checker make my site compliant? No. Automated tools catch contrast, missing alt attributes and missing form labels, which is a useful first pass. They cannot judge whether alt text is accurate, whether headings are logical or whether a task can be completed by keyboard or screen reader.

Sources

  • Disability Discrimination Act 1992, for the prohibition on discrimination in the provision of goods, services and facilities.
  • Digital Service Standard, Australian Government, for the accessibility requirement on government digital services.
  • Maguire v Sydney Organising Committee for the Olympic Games, HREOC 2000, the Australian precedent applying the DDA to a website. Cited by name because the Commission's site blocks automated retrieval.

Rebuilding a site, or shipping generated pages onto one? Talk to us and we will tell you what would fail.