Topics: Website design & costs
Want this done for your business? Get a fixed quote or book a free 30-minute call.
Quick answer: Yes, the Disability Discrimination Act 1992 reaches the services and information you provide online, including your website. The Act doesn't name a technical standard, but the Australian Human Rights Commission's guidelines recommend WCAG 2.2 Level AA as the minimum, so that's the sensible target for any Australian business site.
Accessibility advice in Australia tends to come from two directions. Vendors sell a widget that promises instant compliance, and legal pages explain the Act without telling you what to fix. Neither helps much when you simply want to know whether your booking form works for someone who can't use a mouse.
This guide covers the legal context in plain terms, the faults that turn up most often on small business sites, and a routine you can run yourself in under an hour. Treat it as general information rather than legal advice; if you've received a complaint, speak to a lawyer.
Does the Disability Discrimination Act apply to your website?
In practice, yes. The DDA makes it unlawful to discriminate on the basis of disability when providing goods, services and facilities, and the Australian Human Rights Commission (AHRC) has long treated websites and apps as part of how businesses provide those services.
The principle was tested early. In Maguire v Sydney Organising Committee for the Olympic Games (2000), a blind man complained that the official Olympics website couldn't be used with his screen reader, and the complaint was upheld. Since then, the AHRC has published guidance on digital access, most recently its Guidelines for Equal Access to Digital Goods and Services.
How a dispute typically unfolds:
- A person lodges a complaint with the AHRC.
- The Commission tries to resolve it through conciliation, which is where most complaints end.
- If conciliation fails, the complainant can take the matter to the Federal Court or the Federal Circuit and Family Court.
The Act includes an "unjustifiable hardship" defence, but relying on it is a weak strategy for a website, where most fixes are modest. Accessibility matters most for businesses that serve people with disability directly or sell to government. If you're an NDIS provider, our guide to NDIS provider websites covers sector-specific expectations, and health, education and government suppliers often find accessibility written into their contracts.
Which WCAG version and level should Australian businesses aim for?
Aim for WCAG 2.2 Level AA. The Web Content Accessibility Guidelines are published by the W3C, and version 2.2 became a formal recommendation in October 2023. The AHRC's guidelines advise organisations to conform with WCAG 2.2 at Level AA as a minimum.
| Level | What it means | Should you target it? |
|---|---|---|
| A | The essentials: text alternatives, keyboard access, no seizure-inducing flashes | Required as part of AA |
| AA | Adds colour contrast, visible focus, consistent navigation, form errors you can understand and minimum target sizes | Yes, for every page |
| AAA | Stricter contrast, sign language for video, simpler reading levels | Selectively, where it helps your audience |
WCAG 2.2 builds on 2.1 with criteria that matter on small business sites: focus indicators that aren't hidden behind sticky headers, tap targets large enough to hit, logins that don't depend on memory puzzles, and forms that don't make people re-enter information they've already given.
What are the most common accessibility failures on small business sites?
Most failures are small, repeated and fixable in the design or template, not page by page.
| Failure | Who it affects | Fix |
|---|---|---|
| Low-contrast text, especially grey on white or text over photos | People with low vision, anyone outdoors on a phone | Check every colour pair; our guide to choosing accessible colours covers palettes that pass |
| Missing or useless alt text ("IMG_2041") | Screen reader users | Describe what the image shows or does; mark decorative images as decorative |
| Form fields with placeholder text but no label | Screen reader and voice control users | Visible labels tied to each field, plus clear error messages |
| Keyboard traps in pop-ups, menus and chat widgets | Keyboard and switch users | Every element reachable and escapable by keyboard |
| No visible focus outline | Keyboard users | A strong focus style, never outline: none without a replacement |
| Autoplaying video or rotating carousels | People with vestibular or attention disabilities | No autoplay with sound; pause controls on anything that moves |
| Menus, price lists or forms published only as PDFs | Screen reader and mobile users | Publish the content as a web page |
| Links that say "click here" or "read more" | Screen reader users scanning links | Link text that names the destination |
How can you check your site's accessibility yourself?
Run a short manual routine on your five most important pages: home, a key service page, contact, booking or checkout, and one long article. Automated scanners catch some issues, but many problems only show up when a person tries to use the page.
- Unplug the mouse. Use Tab, Shift+Tab, Enter, Space and Esc to reach every link, button and form field. Note anywhere you get stuck or can't see where you are.
- Run an automated scan. WAVE or axe DevTools in your browser will flag missing labels, empty links and contrast failures.
- Zoom to 200%. Text should reflow without overlapping or forcing sideways scrolling. Then repeat on a phone with large text switched on.
- Spot-check with a screen reader. VoiceOver is built into Macs and iPhones, TalkBack into Android, and NVDA is free for Windows. Listen to your headings and one form.
- Submit a form with mistakes. Error messages should say what went wrong and how to fix it.
- Check media. Videos need captions; audio needs a transcript.
- Write it down. A simple list of page, problem and severity becomes your designer's fix list.
Do accessibility overlay widgets make a site compliant?
No. Overlays are scripts that add a toolbar or attempt automatic repairs on top of your existing site. They don't change the underlying code, so the missing labels, keyboard traps and unlabelled buttons are still there for anyone using their own assistive technology. Some overlays also interfere with the screen readers and settings people already rely on, and many disabled users and accessibility specialists have criticised them publicly.
Budget instead for fixing the code. As we've argued before, accessibility is good business: the same work that helps a screen reader user also improves search visibility, mobile usability and conversion for everyone.
What should you ask your web designer to commit to?
Put WCAG 2.2 Level AA in the contract, along with how it will be tested. A verbal "yes, it's accessible" is worth very little at handover. Ask for:
- WCAG 2.2 AA conformance for all templates and components, stated in the scope
- A testing method that includes keyboard and screen reader checks, not only an automated score
- A colour palette checked for contrast before design sign-off
- CMS fields that make good practice easy, such as required alt text and a proper heading structure
- Accessible forms, including error handling and confirmation messages
- Web pages instead of PDFs for key content, or properly tagged PDFs where a file is unavoidable
- A short accessibility statement page with a contact for reporting problems
- A post-launch period during which accessibility defects are fixed at no charge
Accessible build practice belongs in every quote, not as an optional extra; our breakdown of website costs in Australia lists it among the standard inclusions. When you compare suppliers, our checklist for choosing a web design agency in Australia includes the questions to ask.
Frequently asked questions
Can a small business be taken to court over an inaccessible website in Australia?
It's possible. Disputes usually begin as a complaint to the AHRC, which attempts conciliation first, and only unresolved complaints can proceed to the Federal Court or the Federal Circuit and Family Court. The practical goal is to fix barriers before anyone needs to complain, and to respond quickly when someone reports a problem.
Is WCAG 2.2 required in Australia?
No law names WCAG 2.2 for private businesses. However, the AHRC's guidelines recommend WCAG 2.2 Level AA as a minimum, which makes it the clearest benchmark for showing you've taken reasonable steps. Government and corporate contracts may specify a version and level in writing.
Do accessibility widgets make my website compliant?
No. A widget sits on top of the page without repairing the code underneath, so the barriers remain for people using their own assistive technology. Spend the money on fixing templates, forms and content instead.
Are PDFs on my website covered by accessibility expectations?
Yes. Anything you publish to provide information or services is part of the experience, and PDFs are often the hardest format to make accessible. Publish key content such as menus, price lists and forms as web pages, and if a PDF is unavoidable, make sure it's properly tagged and readable by screen readers.
How often should I check my website's accessibility?
Run the quick keyboard and scan routine whenever you add a new page type, form or plugin, and at least once a quarter. Plan a fuller review every year or before any redesign, and keep the results so you can show progress over time.
Make your next build accessible from the start
Retrofitting accessibility costs more than designing it in. Our accessible website design work builds WCAG 2.2 AA into templates, forms and content from the first wireframe. If you'd like your current site reviewed or a new build quoted, see how GRWW in Australia works with local businesses, or send us your site and we'll reply with a fixed-price plan.