Website accessibility in Australia: the standard is can they finish the task

Australia never wrote a web accessibility statute. What it wrote was the Disability Discrimination Act 1992 (Cth), which makes discrimination on the ground of disability unlawful in areas of public life, including the provision of goods, services and facilities. Nothing in it mentions HTML. It did not need to: in 2000 the Human Rights and Equal Opportunity Commission found that the Sydney Olympics ticketing website unlawfully discriminated against a blind complainant, and awarded $20,000 in damages. That decision, Maguire v Sydney Organising Committee for the Olympic Games (No 2), is where the Web Content Accessibility Guidelines first became the measure an Australian website is judged by, and the Commission still cites it as the authority.

The current guidance replaced a note that had stood since 2014. In April 2025 the Australian Human Rights Commission published its Guidelines on equal access to digital goods and services, issued under section 67(1)(k) of the Act. They are explicit that they are not legally binding and should be read with the Act itself. What they are is the Commission's stated view of what compliance looks like, prepared with technical and disability advisory groups, which makes them the document any complaint or conciliation would be argued around. Treat them as the benchmark, not as an optional style guide.

The Web Content Accessibility Guidelines are a W3C standard, currently at version 2.2, published in October 2023. They are organised under four principles, and the plainest way to read them is as four questions about a person trying to use your page. Conformance comes in three levels: A is the floor, AA is the level Australian guidance and government policy both use, and AAA contains criteria that cannot reasonably apply to all content. When someone says a site is compliant without naming a level, they have not said anything.

Level AA is not exotic. It is a few dozen testable statements, most of which are decisions a developer makes once: text has enough contrast against its background, every control can be reached and operated with a keyboard, focus is visible, form fields have real labels, images that carry meaning have alternative text, video has captions, the page has a language set, and nothing important is conveyed by colour alone. Our website design guide covers where these sit in a build; the point here is that almost none of them cost anything if they are decided before the design is signed off.

Everyone providing goods or services in Australia is bound by the Act. What differs is how specific the written obligation on top of it is, and how likely you are to be asked for evidence. Government has a mandatory standard; procurement has an Australian Standard; telecommunications has a code; everyone else has the Act and the Commission's guidelines.

WebAIM has tested the home pages of the top one million websites every year since 2019, running a real browser and evaluating the page after scripts and styles have applied. In February 2026, 95.9 per cent of those pages had detected failures against WCAG 2.2 Level A or AA. That figure had improved slightly every year for six years and then went backwards, up from 94.8 per cent. Detected errors rose to 56.1 per page, a ten per cent jump in twelve months. Because only automatically detectable failures are counted, the true rate of conformance is lower than the four per cent the numbers imply, not higher.

The interesting part is why it reversed. The average home page carried 1,437 elements in February 2026, 22.5 per cent more than a year earlier, and 133 ARIA attributes, up 27 per cent. Pages using ARIA averaged 59.1 errors against 42 for pages without it. ARIA exists to make complex components accessible, so that correlation is not a case against it; it is a case against complexity added faster than anyone tests it. WebAIM attributes the trend to heavier reliance on third-party frameworks and libraries and to AI-assisted coding. Carousel, lightbox and slider libraries in particular were associated with 20 to 60 per cent more errors than average.

For an Australian business the practical read is simple. The failures are not exotic and they are not expensive. Low contrast text sits on 83.9 per cent of home pages and is a decision made in a brand palette. Missing alternative text sits on 53.1 per cent and is a content habit. Unlabelled form fields sit on 51 per cent and are usually the result of a designer removing the label because the grey hint text inside the field looked tidier. None of these needs a rebuild. All of them need someone to be responsible for them.

We hold our own site to the standard we sell, and we test it the same way. The result was instructive enough to publish. Our pages scored 96 out of 100 for accessibility, with a single warning about heading order, while four real barriers were live. Three of them could not have been found by reading the HTML, because they did not exist until the page had run.

The largest was the scroll animation. Content faded in as you scrolled, using a helper that combines opacity with visibility: hidden at zero opacity. That is a common convenience and it is a genuine accessibility failure: visibility: hidden removes an element from the accessibility tree entirely. Every heading and paragraph below the fold was invisible to a screen reader until a sighted scroll happened to reveal it. The tool reported the symptom, headings not in a sequentially descending order, because the only headings it could see were the two that had already animated in.

If you do nothing else, do the six. They are 96 per cent of what is detectable, they are all decisions rather than projects, and every one of them is verifiable by someone who is not a developer.

Beyond the six, the two that catch most Australian sites are video and custom components. Video needs captions, and captions that were auto-generated and never corrected are not captions. Custom components need a name, a role and a state that assistive technology can read, which is why the plainest advice in the standard is still the best: use the real HTML element before you build your own. If you are commissioning a build, put WCAG 2.2 Level AA in the brief and ask for evidence of a keyboard pass and a rendered-page test, not a screenshot of a score.

Accessible markup and machine-readable markup are close to the same thing. Alternative text tells a screen reader and an image crawler what an image shows. A single, sensible heading order tells a screen reader user how to navigate and tells a search engine how the page is organised. Descriptive link text is both a WCAG requirement and the anchor text that carries meaning. Captions and transcripts turn video into text that can be indexed and quoted. A page language attribute tells an assistive technology how to pronounce a word and tells a search engine which market the page is for.

The connection matters more now that answers are being assembled rather than listed. An AI assistant reading your page is doing something close to what a screen reader does: taking the structure at face value and extracting what it can name. A heading that only exists after an animation runs is a heading that a system reading the rendered page may never see, which is exactly the failure we found on our own site. Our AI citation guide covers the wider entity work, and our conversion checklist covers what happens once a person can actually use the page.

If you want the honest version: accessibility is not a project you finish. It is a property of how you build, and it decays every time someone adds a component in a hurry. The organisations that hold it are the ones that made it a checklist item rather than an annual audit.

For most Australian small and medium businesses, clearing the common failures on an existing site is days of work, not a rebuild. The palette, the alt text, the form labels and the link names are content and CSS decisions. What costs money is a bespoke component that was built without a name or a role, or a video library with no captions, and even those are cheaper than the alternative of doing it again after a complaint. Building it in from the start costs nothing extra at all: it is a set of constraints on a design, agreed before the design is approved.

Where most agencies bill the auditing, the checking and the technical passes by the hour, our Snowball SEO platform does that heavy lifting, so more of the budget goes to the design, the writing and the photography and video that make the site worth visiting. If you want the work done rather than described, our websites and landing pages service builds to WCAG 2.2 Level AA as a default rather than an extra, and our conversion optimisation service picks up where usability and accessibility meet. Our website cost guide covers how Australian agencies price a build.