If you run a business in Australia with any kind of digital presence, accessibility law applies to you. The DDA, WCAG, compliance obligations — it all sounds complex, but it doesn't have to be. Here's a clear, no-jargon guide to what's actually required, what the real risks are, and what practical steps you can take today.
The Basics: DDA, AHRC & WCAG Explained
Disability Discrimination Act 1992 (DDA)
Australia's federal law prohibiting discrimination against people with disabilities. It covers employment, education, accommodation, and crucially — the provision of goods, services, and facilities. Your website, app, online booking system, PDF price list, email newsletter: all services under the DDA.
Australian Human Rights Commission (AHRC)
The AHRC issues guidelines explaining how the DDA applies in practice. In April 2025, they released completely updated Guidelines on Equal Access to Digital Goods and Services — the first major rewrite since 2014. While these guidelines don't have direct legal force, they're taken into account when the Commission assesses complaints.
WCAG 2.2
The Web Content Accessibility Guidelines are the internationally recognised technical standard. The 2025 AHRC guidelines formally adopt WCAG 2.2 Level AA as the minimum benchmark. It's structured around four principles — content must be Perceivable, Operable, Understandable, and Robust. Level AA includes 55 specific, testable success criteria.
Who Needs to Comply
The DDA applies to all organisations — government and private sector, large and small, for-profit and not-for-profit. There is no size threshold or industry exemption. If you provide goods, services, or facilities through digital channels to people in Australia, the DDA covers you.
Retail & e-commerce · Professional services (law, accounting, consulting) · Healthcare & telehealth · Education & online learning · Hospitality & tourism · Banking & finance · Real estate · Government at all levels · Not-for-profits
For government suppliers: the AS EN 301 549 standard (incorporating WCAG 2.2) is now embedded in Commonwealth procurement requirements. Demonstrating accessibility compliance is becoming a prerequisite for public sector contracts.
What Are the Actual Risks
AHRC Complaints: Anyone can file a complaint with the Australian Human Rights Commission. The AHRC investigates and attempts resolution through conciliation.
Federal Court: If conciliation fails, complainants can escalate to the Federal Court. Recent cost protection reforms have lowered the financial barrier to doing so.
Compensation: Courts can order up to AUD $100,000 per violation, determined by severity and impact.
Lost customers: One in five Australians lives with disability. Nearly 5 million Australians face barriers from poor digital design. That's not a niche — it's a significant portion of your revenue.
Top 10 Accessibility Issues on Australian Websites
Based on testing thousands of Australian websites, these are the issues we see most frequently:
Missing or Poor Alt Text
Images without alternative text are invisible to screen reader users. The most common WCAG failure — and one of the easiest to fix.
Insufficient Colour Contrast
Text without enough contrast is hard to read for low-vision users and anyone on a phone in sunlight. WCAG requires 4.5:1 for normal text.
Missing Form Labels
Form fields without associated labels leave screen reader users facing blank fields with zero context about what to enter.
Keyboard Navigation Failures
Sites that only work with a mouse block people who navigate with keyboards due to motor disabilities, injuries, or preference.
Broken Heading Structure
Headings create a navigable outline for screen readers. Skipped levels, missing headings, or headings used only for visual size break navigation.
Vague Link Text
"Click here" and "Read more" are meaningless out of context. Links should describe their destination: "View pricing plans" not "Click here."
Auto-Playing Media
Auto-playing audio/video disrupts screen readers, stresses users with cognitive disabilities, and surprises everyone in quiet environments.
Missing Language Declaration
Without a lang attribute, screen readers may read English text with French pronunciation or other mismatched speech engines.
Inaccessible PDFs
Documents without proper tagging, reading order, and structure represent a major accessibility gap for most organisations.
Focus Indicators Removed
Removing the visible focus ring for aesthetic reasons makes keyboard navigation impossible to follow. WCAG 2.2 strengthened these requirements.
Your Compliance Roadmap
A realistic, step-by-step approach that works for businesses of any size:
Audit Your Current State
Run an automated accessibility scan. This identifies common issues — missing alt text, contrast failures, form problems, heading issues. Automated tools catch roughly 30–50% of WCAG issues. Pair with manual checks: keyboard navigation, screen reader testing, PDF review.
Prioritise Issues
Focus on impact (access-blocking issues first), frequency (high-traffic pages first), and WCAG level (Level A before Level AA). Start with homepage, key service pages, contact page, and checkout flows.
Fix the Quick Wins
Add alt text. Fix colour contrast. Add form labels. Ensure keyboard focus is visible. Set page language. Make link text descriptive. Many of these can be done by content editors — no developer required.
Address Structural Issues
Fix heading hierarchy. Ensure all interactive elements work with keyboard. Add ARIA labels where needed. Fix navigation menus for keyboard and screen reader access. Ensure error messages are announced.
Address Documents & Media
Audit published PDFs and fix or replace inaccessible ones. Add video captions. Provide audio transcripts. Create accessible document templates for future use.
Build Into Your Process
Add accessibility to design briefs and QA. Train content editors. Review accessibility when updating the site. Publish an Accessibility Statement. Prevention is always cheaper than remediation.
What About Accessibility Overlays
You may have encountered companies selling JavaScript widgets that promise to "make your website accessible" with a single line of code. These are accessibility overlays.
The 2025 AHRC guidelines are clear: automated tools are not a substitute for properly designed, inclusive systems. Overlays may address some surface-level issues, but they don't fix underlying structural problems, they can interfere with assistive technology, and they're widely criticised by the disability community.
Genuine accessibility means fixing the actual code and content — not adding a widget on top.
Quick Reference: Key Standards & Laws
| Standard / Law | What It Is | Key Requirement |
|---|---|---|
| DDA 1992 | Australia's disability discrimination law | No discrimination in goods, services, and facilities |
| WCAG 2.2 Level AA | International web accessibility standard | 55 testable success criteria across 4 principles |
| AHRC Guidelines 2025 | How the DDA applies to digital services | WCAG 2.2 AA minimum, broad digital scope |
| AS EN 301 549 | ICT accessibility standard (procurement) | Aligns with WCAG 2.2, required for government contracts |
| DSS 2.0 | Digital Service Standard for government | Latest WCAG + "leave no one behind" |
| PDF/UA (ISO 14289) | PDF accessibility standard | Tagged structure, reading order, alt text |
Frequently Asked Questions
Not necessarily. Accessibility isn't always included in standard web development unless specifically requested and tested. Many modern websites look great but have significant accessibility gaps under the surface.
The DDA applies regardless of business size. That said, the effort required scales with your digital presence. A small business with a simple website might need just a few hours of work. The key is demonstrating genuine effort toward accessibility.
At minimum, after any significant website update. Ideally, run a comprehensive check quarterly and include accessibility in your routine content review process. Automated monitoring tools can help catch issues as they appear.
Yes. Under the DDA, individuals can file complaints with the AHRC and, if unresolved, escalate to the Federal Court. This has happened in Australia — the Maguire v SOCOG case in 2000 confirmed websites are a "service" under the DDA. Recent reforms have also lowered the cost barriers for complainants.
Level A covers the most basic requirements. Level AA (the recommended minimum in Australia) adds criteria around contrast, resizing, and navigation. Level AAA is the highest standard but is generally aspirational rather than a baseline requirement. The 2025 AHRC guidelines set Level AA as the minimum.
Automated testing catches many common issues but can't evaluate everything — things like reading order, alt text quality, and the actual experience of navigating with a screen reader require human judgment. Automated tools are an excellent starting point and ongoing monitoring tool, but pairing with manual review gives you the fullest picture.
The businesses that move on accessibility now will be ahead of the curve. The ones that wait will find themselves scrambling as awareness, complaints, and expectations continue to grow.