The Disability Discrimination Act 1992 (the DDA) is the main federal law protecting people with disability from discrimination in Australia. It was written long before most organisations had websites, but it still applies to them. Here’s what it means in practice, without the legal jargon.
What the DDA says
The DDA makes it unlawful to treat someone less favourably because of their disability in areas of public life, including work, education, accommodation and access to premises. The part that matters most for websites is the provision of goods, services and facilities.
If you provide a service, and your website or documents are part of how people find, use or pay for that service, then an inaccessible website can be a barrier that shuts people with disability out.
Who it applies to
Almost everyone who provides goods or services to the public: businesses of any size, not-for-profits, NDIS providers, schools, and all levels of government. There’s no exemption just for being small, although size and resources can be relevant to the defence below.
Does the DDA mention websites or WCAG?
No. The Act itself doesn’t name any technical standard. Instead, the Australian Human Rights Commission, which handles DDA complaints, publishes guidance on what it expects. Its Guidelines on equal access to digital goods and services, published in April 2025, say organisations should conform with WCAG 2.2 at a minimum of Level AA. They also say PDFs should meet the PDF/UA standard, and that the Australian Standard AS EN 301 549 should be used when buying technology. The guidelines replaced the Commission’s 2014 advisory notes, which pointed to the older WCAG 2.0. In practice, WCAG 2.2 AA is the measuring stick you’ll be compared against if a complaint is made.
The website case everyone mentions
In 2000, a blind man, Bruce Maguire, complained that the Sydney Olympics website couldn’t be used with his screen reader. The Human Rights and Equal Opportunity Commission (now the Australian Human Rights Commission) found that the organising committee had discriminated against him and ordered it to pay damages. It’s still the landmark example that inaccessible websites can breach the DDA.
How complaints work
- Complaint: a person who’s been affected lodges a complaint with the Australian Human Rights Commission.
- Conciliation: the Commission tries to resolve it between both parties. Most complaints are settled here, often with an agreement to fix the problem, sometimes with compensation.
- Court: if it can’t be resolved, the person can take the matter to the Federal Court or Federal Circuit and Family Court.
Beyond the legal risk, a complaint usually means rushed fixes, legal costs and time lost. It’s far cheaper to find and fix the problems before anyone is shut out.
What about “unjustifiable hardship”?
The DDA includes a defence where making something accessible would cause unjustifiable hardship, taking into account things like cost, benefit and the organisation’s resources. It’s a narrow defence that you’d have to prove. It’s not a general excuse, and it’s hard to rely on for a website, where accessibility is usually achievable, especially when it’s built in from the start.
Showing you’re taking it seriously
- Get an audit against WCAG 2.2 AA so you know where you stand
- Fix the highest-impact issues first, and keep a record of what you’ve done
- Publish an accessibility statement with a way for people to report problems
- Consider a Disability Action Plan. Organisations can lodge one with the Australian Human Rights Commission, and it can be taken into account if a complaint is made
- Train the people who publish your content, so new pages and documents stay accessible
Wondering whether you can get your website “DDA certified”? Read Is there such a thing as DDA certification?
Common questions
Does the DDA apply to my website?
If your website, app or online forms are part of how you provide goods, services or information to the public, yes. That includes booking, buying, applying, enquiring and finding information.
Does it apply to small businesses and not-for-profits?
Yes. There is no exemption for small organisations. What counts as unjustifiable hardship takes your size and resources into account, but this is decided case by case.
Can I get my website DDA certified?
No. There is no official DDA certificate or badge. Read Is there such a thing as DDA certification? for what you can get instead.
Does the DDA cover PDFs and Word documents?
Yes, if people need them to use your services. The Commission’s guidelines say PDFs should meet the PDF/UA standard, and that accessible formats such as web pages are often better. Our guide on how to make an accessible PDF explains how.
Will an accessibility widget or overlay make my site compliant?
No. Overlay tools change how a page looks, but they don’t fix the underlying code, and many screen reader users find they make sites harder to use. The reliable way is to test your site and fix the problems at the source.
What should I do first?
Find out where you stand. Work through our free website accessibility checklist, then get an accessibility audit against WCAG 2.2 AA so you know exactly what to fix.
This guide explains the general picture. It isn’t legal advice for your situation. If you’re dealing with a complaint, talk to a lawyer.
For more on the standards themselves, read Does your website meet Australia’s accessibility standard? and What’s new in WCAG 2.2.
See what the evidence looks like in our sample audit report.