Australia does not have a single dedicated website accessibility law for the private sector. Instead, accessibility obligations for online businesses flow primarily from the Disability Discrimination Act 1992 (DDA) — a broad anti-discrimination statute that the courts and the Australian Human Rights Commission (AHRC) have applied to web accessibility. Government websites face stricter, more explicit requirements under the Web Accessibility National Transition Strategy (NTS) and the Australian Government Digital Service Standard.
How the DDA applies to websites
The DDA prohibits discrimination against people with disabilities in the supply of goods, services, and facilities. The AHRC and the Administrative Review Tribunal have confirmed that this applies to websites — meaning that if your website is inaccessible to a person with a disability (for example, a blind person who cannot use a screen reader to navigate your site), you may be discriminating against them in the provision of services.
A landmark complaint decided in 2000 — Maguire v SOCOG — found that the Sydney Olympic Games website was discriminatory because it was inaccessible to blind users. While the web has changed enormously since then, the principle has not: websites that serve the public are expected to be accessible, and complaints under the DDA are a real enforcement mechanism.
Under the DDA, individuals can lodge complaints with the AHRC. If unresolved at that level, the complaint may proceed to the Federal Court. Most DDA web accessibility complaints are resolved through conciliation rather than litigation, but the risk of formal proceedings exists — particularly for large organisations with inaccessible websites.
WCAG 2.1 AA: the recommended standard
The AHRC's advisory note on web accessibility recommends conformance with WCAG 2.1 Level AA as the standard that discharges the DDA obligation for most website operators. This is the same standard required by most international frameworks. The key requirements at AA level include:
- Text alternatives for all non-text content (images, icons, buttons)
- Captions for all pre-recorded video content
- Keyboard accessibility — all functionality available without a mouse
- Sufficient colour contrast (4.5:1 ratio for normal text)
- Clear page structure using semantic HTML headings
- Forms with properly associated labels and clear error identification
- No content that flashes more than three times per second
- Consistent navigation and clear focus indicators
Practical steps for Australian businesses
For most online businesses, a pragmatic approach is: conduct an initial accessibility audit (automated tools such as Axe or WAVE give a useful first pass, but manual testing is essential for a complete picture); address the highest-impact barriers first — missing alt text, keyboard traps, and unlabelled form fields typically account for the majority of accessibility failures; publish an accessibility statement that describes your conformance target, any known exceptions, and how users can report accessibility issues; and commit to accessibility as part of your standard development process rather than a one-time remediation project.
For businesses that commission custom websites or web apps, include WCAG 2.1 AA conformance as a contractual requirement with your developer. Many accessibility problems that are expensive to fix post-launch are straightforward to address during the build if they are specified upfront.