Here’s a fact that should embarrass us: in 2026, the vast majority of Australian websites are still unusable for people with disabilities. Not hard to use—actually unusable.

We’re not talking about some obscure technical standard that only affects a tiny number of people. According to the Australian Bureau of Statistics, about 4.4 million Australians (roughly 18% of the population) live with some form of disability. Many of them rely on assistive technologies like screen readers to access the web.

And most websites break these tools completely.

The Numbers Don’t Lie

WebAIM’s annual accessibility analysis consistently shows that around 96% of home pages have detectable WCAG (Web Content Accessibility Guidelines) failures. Let that sink in. We’re not talking about minor issues—these are fundamental problems like missing alt text on images, poor colour contrast, or forms that can’t be navigated with a keyboard.

In Australia, the situation isn’t any better. A 2025 study by the Australian Human Rights Commission found that 87% of government websites failed basic accessibility tests. Government websites. The ones that are explicitly required to be accessible under the Disability Discrimination Act.

If the public sector can’t get this right, what hope do we have for everyone else?

Why It Matters

Let’s get concrete about what this means. If you’re using a screen reader and encounter a form with unlabelled fields, you literally can’t tell what information goes where. If you have low vision and a website uses grey text on a slightly lighter grey background (I’m looking at you, minimalist design trends), the content is invisible to you.

If you navigate by keyboard because you can’t use a mouse, and the website doesn’t show you where focus is, you’re clicking around blindly hoping to hit the right spot.

These aren’t edge cases. These are daily realities for millions of Australians trying to do basic things like book a doctor’s appointment, pay a bill, or apply for a job.

The economic impact is real too. According to a report from the Australian Network on Disability, people with disabilities and their families represent over $150 billion in combined spending power. Businesses that ignore accessibility are literally turning away customers.

Why Progress Is So Slow

So if this is such an obvious problem, why hasn’t it been fixed?

The main reason is that accessibility gets treated as a checkbox exercise, not a core requirement. It’s something you think about after the site is built, if at all. By then, fixing problems is expensive and disruptive, so it gets pushed to “phase two” (which never happens).

There’s also a fundamental knowledge gap. Most developers don’t learn about accessibility in their training. It’s not part of most bootcamp curriculums. It’s not emphasised in computer science degrees. You might get a lecture or two if you’re lucky.

And honestly, most developers never use a screen reader or try to navigate a site with only a keyboard. If you haven’t experienced these challenges firsthand, it’s easy to think of accessibility as someone else’s problem.

The Legal Pressure Is Building

For years, Australian businesses could ignore accessibility without much consequence. That’s changing.

The Disability Discrimination Act has always technically required accessible websites, but enforcement was patchy. Now we’re seeing more complaints to the Australian Human Rights Commission and more court cases. In 2024, Coles faced legal action over accessibility issues with their online shopping platform.

The writing’s on the wall: accessibility is becoming a legal risk, not just a nice-to-have feature.

What Actually Works

The good news is that building accessible websites isn’t actually that hard if you do it from the start.

Semantic HTML gets you most of the way there. Use actual button elements for buttons. Use heading tags in logical order. Use labels for form fields. This stuff isn’t complicated—it’s just doing HTML properly instead of making everything a div.

Colour contrast is about choosing readable colour combinations. There are free tools that check this in seconds. There’s no excuse for grey-on-grey text.

Keyboard navigation means making sure someone can tab through your site logically and see where they are. Again, not rocket science.

The key is baking this into your process from day one. Include accessibility in your design mockups. Test with a keyboard during development. Run automated accessibility checkers (though these only catch about 30% of issues). Get real users with disabilities to test when you can.

The Automated Testing Trap

A lot of organisations run automated accessibility tests and think they’re done. They’re not.

Automated tools are useful for catching obvious problems like missing alt text or heading structures. But they miss a lot. They can’t tell if your alt text is actually meaningful. They can’t tell if your site makes logical sense to someone using a screen reader. They can’t evaluate if your interactive widgets behave sensibly.

You need human testing. Ideally, you need testing by actual users with disabilities. There are organisations in Australia that can help with this, like Vision Australia and Media Access Australia.

The Government’s Role

The public sector needs to lead on this. If government websites aren’t accessible, they’re failing in their basic duty to serve all citizens equally.

The Digital Transformation Agency has published guidelines, which is good. But guidelines without enforcement don’t change much. We need regular accessibility audits of government websites with public reporting and consequences for non-compliance.

And we need better procurement standards. When governments buy software or contract for website development, accessibility should be a hard requirement, not a preference.

What Needs to Change

First, accessibility needs to be taught properly in every web development course. Not as an optional module, but as a core competency. You shouldn’t be able to graduate as a developer without understanding semantic HTML and ARIA attributes.

Second, we need better tools built into development workflows. Accessibility linters should be as common as code formatters. Design tools should flag contrast issues automatically.

Third, organisations need to stop treating accessibility as a project and start treating it as a standard practice. You don’t have a “make the site work in Chrome” project—you just build sites that work in Chrome. Same should go for screen readers.

The Business Case

Beyond the moral and legal arguments, there’s a straightforward business case for accessibility.

Accessible sites are generally better for everyone. Clear navigation helps all users. Good contrast is easier to read for people without vision impairments too. Keyboard navigation makes power users happy.

Accessible sites perform better in search engines because the semantic structure that helps screen readers also helps search crawlers. Google can’t see your images either—it relies on alt text just like visually impaired users do.

And as the population ages, more and more users will need accessibility features. Vision and motor skills decline with age. Building accessible sites now is building for your future audience.

Time to Get Serious

Australia’s digital accessibility crisis won’t fix itself. It requires a sustained effort from developers, designers, business leaders, and policymakers.

The technology is there. The guidelines exist. What’s missing is the will to make it a priority.

We’ve got 4.4 million Australians who deserve better. It’s time to deliver.