WCAG Explained: How Australia Set the World Precedent

In June 1999, a blind man named Bruce Maguire lodged a complaint about a website.

The site belonged to the Sydney Organising Committee for the Olympic Games. Maguire could not use it. He reads with a refreshable braille display, and large parts of the site, including the ticketing information, the schedule index and the results tables, had no text alternatives for him to read.

SOCOG argued it would cost roughly two million dollars and take more than a year to fix. Maguire’s advocates put the figure at thirty to forty thousand. The Human Rights and Equal Opportunity Commission found that SOCOG had unlawfully discriminated against him under section 24 of the Disability Discrimination Act, and ordered the site fixed before the Games opened. SOCOG only partially complied. In November 2000 the Commissioner awarded Maguire twenty thousand dollars in damages.

It was one of the first website accessibility complaints anywhere in the world, and it set the precedent that Australian anti-discrimination law applies to websites.

That was twenty six years ago. WebAIM’s annual analysis of a million home pages still finds detectable accessibility failures on roughly ninety five per cent of them.

So let us go through what the standard actually is, where it sits in Australian law, and what a small business should realistically do about it.

What WCAG actually is

WCAG stands for Web Content Accessibility Guidelines. It is published by the World Wide Web Consortium, the body that maintains the technical standards of the web. It is not a law and it was never written as one. It is a technical specification describing how to build digital content that people with disabilities can actually use.

The current version is WCAG 2.2, released in October 2023. Version 3.0 exists in draft form and has for years. Do not wait for it.

WCAG has three conformance levels:

Level A is the minimum. Fail these and significant groups of people simply cannot use your site at all.

Level AA is the working standard. It is what governments, courts, regulators and procurement processes reference around the world. When anyone says “WCAG compliant” without specifying, this is what they mean, and it is what we build every site to.

Level AAA is the highest tier. It is not realistic or even appropriate as a blanket target for most sites, and W3C says as much. Some AAA criteria are worth adopting selectively, such as video transcripts and clearer link text.

The four principles, in plain English

WCAG is organised around four principles, usually shortened to POUR. They are more useful than they sound, because they describe four genuinely different ways a website can lock someone out.

Perceivable. Can people take in the information at all? This covers alt text on meaningful images, captions on video, text that has enough contrast against its background, and content that still makes sense when someone zooms to two hundred per cent. If your only phone number is baked into a graphic, a blind visitor has no phone number.

Operable. Can people actually drive the interface? This covers keyboard access for everything, no keyboard traps, enough time to complete tasks, and touch targets big enough to hit. Plenty of people never use a mouse. If your dropdown menu only opens on hover, it does not exist for them.

Understandable. Is it predictable and clear? Consistent navigation, form fields labelled properly, error messages that say what went wrong and how to fix it, and the page language declared so screen readers pronounce your content correctly rather than reading English with a French accent.

Robust. Will it work with assistive technology, now and later? This is mostly about using proper semantic HTML rather than a pile of divs pretending to be buttons. Screen readers understand a real button. They do not understand a styled div that a developer attached a click handler to.

Where this sits in Australian law

This is where most articles get vague, so here is the actual position.

Australia has no legislation that says “your website must meet WCAG 2.2 AA.” Anyone telling you WCAG is the law is oversimplifying.

What we have is section 24 of the Disability Discrimination Act 1992, which makes it unlawful to discriminate against people with disability in the provision of goods, services and facilities. Australian courts and the Australian Human Rights Commission have consistently treated websites and digital services as falling inside that, starting with Maguire. The DDA is administered by the AHRC, and complaints go there first.

WCAG is the yardstick used to assess whether a service is accessible. In April 2025 the AHRC published updated guidelines on equal access to digital goods and services, recommending alignment with WCAG 2.2 Level AA and extending its coverage to newer territory including mobile apps, self-service machines, AI systems and biometric technologies.

For government, it is firmer. Federal agencies work to the Digital Inclusion Standard, whose fourth criterion is “make it accessible” and which references the DDA and the current version of WCAG directly. If you tender for government work, or work for anyone who does, you will be asked about this.

So the accurate framing for a private business is this. Failing WCAG is not itself an offence. Providing a service that a person with disability cannot use may be unlawful discrimination, and WCAG 2.2 AA is the standard by which that will be measured. Meeting it is how you demonstrate you have done what is reasonable.

Complaints are also cheaper and easier to lodge than most business owners assume. They start at the AHRC, not in a courtroom.

If you sell into Europe, this got sharper

Worth flagging for anyone running an online store, because it catches Australian businesses who assume EU law is a European problem.

The European Accessibility Act has been enforceable across all twenty seven EU member states since 28 June 2025. It applies to businesses selling covered products and services to EU consumers regardless of where the business is based. The law follows the customer, not the company. E-commerce is explicitly in scope, and the technical benchmark is EN 301 549, which incorporates WCAG at Level AA.

There is a microenterprise carve-out for service providers with fewer than ten employees and under two million euros in turnover, though the detail varies by member state. Enforcement is real: the first lawsuits were filed in France in late 2025.

If you have a Shopify or WooCommerce store that accepts orders from Europe, this is your problem now, not a hypothetical.

Who this is actually for

The number usually quoted is that around twenty one per cent of Australians, roughly five and a half million people, live with disability. That alone should settle the commercial argument.

But the framing of accessibility as a niche concern for a small group is the reason it keeps getting deprioritised, and it is wrong.

Consider who benefits from captions: deaf people, and also everyone watching video with the sound off in a waiting room, on a train, or in an open plan office, which is most video viewing.

Consider who benefits from high contrast text: people with low vision, and also everyone over fifty, everyone using a phone outdoors in Queensland sun, and everyone on a cheap screen with the brightness down to save battery.

Consider who benefits from keyboard access: people with motor impairments, and also power users, and anyone whose trackpad has just died.

Consider who benefits from a form that explains its errors clearly: everyone, without exception.

Accessibility is often described as designing for permanent disability. It is more accurate to say you are designing for permanent, temporary and situational limitation at once. A broken wrist is temporary. Holding a baby is situational. Both make one-handed operation the only option.

And Australia is ageing. The cohort that struggles most with small tap targets and low contrast text is also the cohort with the most disposable income.

What actually fails, and how cheap most of it is to fix

The failures found in large scale surveys are remarkably consistent year to year, and they are not exotic engineering problems:

Low contrast text is the most common by a wide margin. Missing alternative text on images. Empty links, usually icon links with no accessible name, so a screen reader announces “link” and nothing else. Form inputs without labels. Missing document language declaration. Empty buttons.

Every one of those is cheap. Most are minutes of work. The reason they persist is not cost, it is that nobody has looked.

Which is worth sitting with, because it reframes the whole issue. The barrier is not budget. It is that a business owner has never been told this exists, and the person who built their site never raised it.

A warning about overlay widgets

You will be sold accessibility overlays. These are the third party scripts that add a little accessibility icon to the corner of your site, opening a panel offering bigger text, higher contrast and a screen reader mode, usually for a monthly fee, usually promising compliance.

Be very careful here.

Overlays sit on top of your existing code. They cannot fix the underlying problems, because the problems are structural: an image with no alt text has no meaning for a widget to surface, and a div pretending to be a button is still a div. They have been the subject of legal action rather than protection from it, and a large number of blind and low vision users, along with many accessibility professionals, have publicly opposed them, some reporting that overlays actively interfere with the assistive technology they already use.

We do not install them, and we would push back on any client who asked us to. Buying a widget to avoid fixing your website is the digital equivalent of putting a ramp sticker on a set of stairs.

What to actually do

In order, from most to least useful.

Test with a keyboard. Put the mouse away. Tab through your homepage. Can you reach every link, button and form field? Can you see where you are at all times, or does the focus indicator disappear? Can you open the menu, use it, and get back out? Can you get trapped anywhere? This one test, which costs nothing and takes ten minutes, will find more real problems than any automated scan.

Run an automated scan, then treat the result with suspicion. Tools like WAVE, axe DevTools and Lighthouse are genuinely useful and will find your contrast failures and missing labels immediately. They also only catch somewhere around a third of actual barriers. A clean automated report does not mean an accessible site. It means the machine-detectable problems are gone.

Check your contrast. WCAG 2.2 AA requires 4.5 to 1 for normal body text, and 3 to 1 for large text and for interface components and meaningful graphics. WebAIM’s contrast checker is free and takes seconds per pair.

Write real alt text. Describe what the image conveys in context, not what is literally in frame. A photo of a finished driveway on a concreting site is better described as “stamped concrete driveway completed in Narangba” than “concrete”. Decorative images that add nothing should have empty alt attributes so screen readers skip them rather than announcing a filename.

Fix your forms. Every input needs a visible, programmatically associated label. Placeholder text is not a label; it vanishes the moment someone starts typing. Error messages need to say what is wrong and how to fix it, and they need to be announced, not just coloured red.

Never use colour alone to convey meaning. Around one in twelve men has some form of colour vision deficiency. If red means error, add an icon and words.

Try a screen reader once. VoiceOver is built into every Mac and iPhone; NVDA is free on Windows. Ten minutes of listening to your own homepage is uncomfortable and extremely clarifying.

Publish an accessibility statement. State the standard you work to, what you know is not yet conformant, and how someone can contact you if they hit a barrier. This is standard practice, it is expected under EU rules, and under the DDA it demonstrates good faith and an active remediation path rather than indifference.

The part nobody mentions: it helps your SEO

Accessible markup and machine-readable markup are largely the same thing.

Proper heading hierarchy helps screen reader users navigate, and helps search engines understand your page structure. Alt text helps blind users, and is how images get found and how AI systems describe your content. Captions and transcripts make video usable without sound, and make its content indexable, since a search engine cannot watch a video either. Semantic HTML tells assistive technology what each region is, and tells crawlers the same thing.

Screen readers and search crawlers are both machines trying to understand your page without seeing it. Build for one and you have largely built for the other.

The honest summary

WCAG 2.2 Level AA is achievable for a small business site. It is not a specialist project requiring a separate budget line, provided it is built in from the start rather than retrofitted, which is the expensive version.

Australia produced the world’s first major ruling on this in 2000, and then most of the country carried on as though it had not happened. The legal risk is real but modest for a small operator. The commercial cost of excluding a fifth of the population, plus everyone outdoors, everyone over fifty and everyone with a dead trackpad, is not modest at all.