WCAG accessibility guidelines as an industry standard, not the law

WCAG — the Web Content Accessibility Guidelines — is a technical standard. It is published by the World Wide Web Consortium, and the industry references it voluntarily. It carries no enforcement power on its own. Understanding it as an industry standard, separate from the legal obligation that gives it force in Australia, clarifies a distinction that gets flattened in most commentary. WCAG is the “what.” A country’s own law is the “why it matters.”

WCAG, the World Wide Web Consortium, and the two things that are easy to conflate

	WCAG	The Disability Discrimination Act (Australia)
What it is	A technical specification: testable success criteria for accessible content	A federal anti-discrimination law
Who publishes or enforces it	The W3C’s Web Accessibility Initiative publishes it; no one enforces it directly	Complaints handled by the Australian Human Rights Commission, escalating to the courts
Does it name a specific law?	No — it is jurisdiction-agnostic by design	Yes — it is the source of the actual legal obligation in Australia
What “Level AA” means	A defined conformance tier within the WCAG specification	Referenced, not created, by Australian guidance as the practical benchmark

The legal detail — including that the Australian Human Rights Commission’s April 2025 guidance names WCAG 2.2 Level AA, and that the DDA carries no small-business exemption — is covered fully on website accessibility obligations in Australia. This page is about WCAG’s status as an industry reference point, not the legal exposure itself.

Why the industry adopted the WCAG accessibility guidelines voluntarily, before any law required it

WCAG’s first version was published in 1999. That was well before most jurisdictions had settled how their anti-discrimination or equal-access laws applied to websites at all. Development teams and standards-conscious agencies adopted it as a practical, testable benchmark for what “accessible” concretely meant. The alternative was building to no defined standard whatsoever. That voluntary adoption is why WCAG became the default reference point international law and guidance later pointed to. Each jurisdiction did not have to independently invent its own technical criteria.

How the WCAG web content accessibility guidelines work as a specification: success criteria, conformance level and AAA

It defines success criteria — testable statements like “text has a contrast ratio of at least 4.5:1 against its background.” These are organised under four principles: perceivable, operable, understandable, robust. They are graded into three conformance levels, A, AA and AAA. Version 2.2 is the current recommendation, published by the W3C as a formal Recommendation in October 2023. Each version is additive. 2.2 does not remove criteria from 2.1; it adds further ones. That is why a supplier working “to WCAG 2.0” is working to an outdated subset, rather than a different but equally valid standard. One example of an additive criterion is the long-standing requirement that prerecorded audio and video carry captions or an equivalent alternative. This success criterion has been present since the original guidelines, and carried forward, unchanged in substance, through every version since.

Where the industry-standard framing genuinely matters

WCAG carries no enforcement mechanism of its own. A supplier claiming to build “WCAG compliant” sites is making a claim you cannot verify against any external register, the way you might check a trade licence. What you can verify is whether specific, testable criteria are actually met — covered in practical terms on what automated scanners can and cannot find. The specification itself, unlike a professional licence, has no external body confirming anyone’s claimed adherence to it.

Why a global standard still needs a local legal answer

WCAG being the same specification worldwide is precisely why it cannot tell you what your legal obligation is — that comes entirely from your own jurisdiction’s law. Australia does not have a standalone “web accessibility act”; it has the Disability Discrimination Act, a law about discrimination generally, applied to websites through the same reasoning used for physical premises. WCAG is the technical yardstick a business can point to when demonstrating it has taken accessibility seriously; it is not itself the source of the obligation, and no Australian statute names it directly.

Why WCAG’s version history matters more than it seems

WCAG has progressed through several versions since 1999 — 1.0, 2.0, 2.1, and now 2.2. Critically, each version is additive. It does not remove or replace earlier success criteria; it adds further ones on top. A supplier confidently stating they build “to WCAG” without naming a version is not describing a fixed, stable target. They could genuinely mean anything from the 1999 baseline to the current 2.2 recommendation, and the practical gap between those is substantial. Naming the version is not a technicality. It is the difference between a specific commitment and a vague one.

How WCAG interacts with other technical standards bodies, in the European Union and elsewhere

WCAG sits alongside other W3C accessibility specifications. WAI-ARIA is the most relevant to modern, heavily interactive websites; it defines how custom interactive components communicate their role and state to assistive technology. WCAG also underpins standards published by other bodies, rather than competing with them. The European Union’s EN 301 549, for example, incorporates WCAG’s success criteria directly, rather than defining a separate set. A site can follow WCAG’s content-level guidance closely while still getting WAI-ARIA implementation wrong on custom components. That is one reason a comprehensive accessibility approach references more than WCAG alone, even though WCAG remains the primary, most widely cited standard.

Why an industry standard without an enforcement body still matters commercially

Some industry standards carry real enforcement. A licence can be revoked. A certification can be audited. WCAG has neither mechanism directly. Its practical force comes from being the standard courts, regulators and industry bodies point to when assessing whether a service is reasonably accessible. That gives it real weight, despite having no independent enforcement arm of its own — a distinction covered from the legal-obligation side on website accessibility in Australia.

What to do next

If a supplier tells you they build to “WCAG standards,” ask which version and which level, in writing, and treat it as a technical claim to be tested rather than a compliance certificate to be trusted. The legal side of the obligation — what actually applies to your business under Australian law, and that there is no small-business exemption — is set out in full on website accessibility obligations in Australia.

Building to a named version and level correctly is ongoing technical work, not a one-off setting — see development as an ongoing engagement for where that sits as a purchase.