Website accessibility used to be a niche compliance topic. In 2026, it’s a mainstream business risk and a genuine opportunity — and it’s one of the few major areas of website best practice that most Australian small business sites still get wrong.
Here’s what accessibility actually means, why it’s a legal issue in Australia (not just a “nice to have”), what the current WCAG 2.2 standard requires and a practical checklist you can work through on your own site.
Why accessibility isn’t optional in Australia
Around 5.5 million Australians — 21% of the population — live with disability, according to the Australian Institute of Health and Welfare. That includes people with vision impairment, motor impairments that affect mouse use, hearing loss and cognitive or learning disabilities. If your website is hard to navigate with a keyboard, hard to read with a screen reader, or relies on colour alone to convey information, you’re locking out a meaningful share of your potential customers before they’ve even seen what you sell.
It’s also a legal question. Under the Disability Discrimination Act 1992 (Cth), providing a service — including a website — in a way that discriminates against people with disability is unlawful. This isn’t theoretical: in the landmark case Maguire v Sydney Organising Committee for the Olympic Games (2000), a blind complainant successfully argued that SOCOG’s website breached the DDA by failing to provide alt text on images and accessible results tables. The Commission ordered the site fixed and later awarded $20,000 in compensation when the fixes weren’t fully made. That case is over two decades old and it’s still the reason Australian government and enterprise sites take accessibility seriously.
More recently, the Australian Human Rights Commission released new Guidelines on Equal Access to Digital Goods and Services (April 2025), explicitly extending DDA obligations to modern digital products — websites, apps, AI tools and self-service systems — across banking, retail, hospitality and essential services. Disability Discrimination Commissioner Rosemary Kayess has been clear that this covers ordinary commercial websites, not just government portals.
None of this means every small business is about to be sued. It does mean accessibility complaints are a real and rising risk and — just as importantly — that an accessible site is simply a better-performing one: cleaner code, better SEO and a smoother experience for every visitor, not just those using assistive technology.
What “WCAG compliant” actually means
The Web Content Accessibility Guidelines (WCAG), published by the W3C, are the international standard that Australian courts, the AHRC and government policy all point to. They’re organised around four principles, often remembered as POUR:
- Perceivable — information must be presentable in ways people can perceive (text alternatives for images, captions for video, sufficient colour contrast).
- Operable — all functionality must work via keyboard, not just a mouse, with no content that traps or disorients users.
- Understandable — text is readable, pages behave predictably and forms clearly explain errors.
- Robust — content works reliably across browsers and assistive technologies, including screen readers.
Guidelines are rated at three conformance levels — A, AA and AAA. In practice, WCAG Level AA is the benchmark almost everyone works to: it’s what the Australian Government’s Digital Service Standard requires of federal sites and it’s the level referenced in most accessibility legal claims internationally.
What’s new in WCAG 2.2
WCAG 2.2 became the current version of the standard, adding nine new success criteria on top of 2.1. The additions that matter most for a typical small business website are:
- Target Size (Minimum) — clickable buttons and links should be at least 24×24 CSS pixels, with enough space around them. This mostly affects mobile menus, icon buttons and tightly packed navigation.
- Dragging Movements — anything that currently requires a drag gesture (image sliders, sortable lists) needs a tap or click alternative.
- Focus Not Obscured — when someone tabs through your site with a keyboard, the focus indicator (the highlighted outline) can’t be hidden behind a sticky header or cookie banner.
- Consistent Help — if you offer a help link, chat widget, or contact option, it needs to appear in the same place across pages.
- Redundant Entry — multi-step forms (like checkout or bookings) shouldn’t make users re-enter information they’ve already provided in the same process.
- Accessible Authentication — login and account creation shouldn’t rely purely on tasks like solving a puzzle or transcribing a code image, without an easier alternative.
The most common accessibility failures we see on small business sites
Most of the accessibility problems on Australian small business websites aren’t exotic — they’re the same handful of issues repeated across page after page:
- Missing or lazy alt text on images (blank, or just the filename like “IMG_2043.jpg”).
- Low colour contrast — light grey text on white backgrounds, or brand colours that look great but fail contrast ratios for body text.
- Forms without proper labels, so a screen reader can’t tell a user what a field is actually asking for.
- Heading structure that skips levels or is used purely for visual styling rather than to describe page structure (h1 → h4, no h2 or h3 in between).
- Content that only works with a mouse — dropdown menus, sliders, or “click here” interactions with no keyboard equivalent.
- Video without captions and PDFs uploaded as scanned images with no readable text layer at all.
- Link text like “click here” or “read more” repeated dozens of times, which is meaningless out of context to a screen reader user jumping between links.
A practical starting checklist
You don’t need to solve everything at once. A sensible, low-cost first pass looks like this:
- Run an automated scan — free tools like WAVE (wave.webaim.org) or the Lighthouse accessibility audit built into Chrome DevTools will catch roughly a third of issues in minutes: missing alt text, contrast failures, missing form labels and heading problems.
- Test keyboard navigation manually — put the mouse away and tab through your homepage, main menu and one form. If you can’t reach or operate something, a screen reader user can’t either.
- Check colour contrast on your actual brand palette, not just body copy — many logo and accent colours fail AA contrast when used for text or buttons.
- Add real alt text to product photos, team headshots and infographics — describe what the image conveys, not just what it is.
- Caption video content you host or embed, including social clips repurposed onto the site.
- Be cautious with “accessibility overlay” plugins that promise instant compliance via a widget. Several have faced legal and advocacy criticism for papering over — rather than fixing — the underlying code and some have themselves been the subject of accessibility lawsuits.
A full WCAG 2.2 AA audit and remediation is a proper project — usually done alongside a redesign, a maintenance engagement, or a dedicated accessibility review — but the steps above will meaningfully reduce your exposure and improve the experience for every visitor in an afternoon or two.
Frequently asked questions
Is website accessibility legally required in Australia?
Yes, indirectly. There’s no single “Website Accessibility Act,” but the Disability Discrimination Act 1992 prohibits discrimination in the provision of services and this has been found by the Human Rights Commission to include websites. The AHRC’s 2025 Guidelines on Equal Access to Digital Goods and Services confirm this applies to ordinary commercial digital products, not just government sites.
Do small businesses really get complaints or legal action over this?
It’s far less common than for large enterprises and government agencies, but complaints to the AHRC can be lodged against any business and the reputational and customer-experience cost of an inaccessible site is real regardless of legal risk. Larger and higher-traffic sites carry more exposure, which is worth factoring in as your business grows.
What’s the difference between WCAG 2.1 and WCAG 2.2?
WCAG 2.2 is the current version of the standard and is fully backwards-compatible with 2.1 — everything in 2.1 still applies, plus nine additional success criteria covering things like target size, focus visibility and easier authentication.
Can a plugin make my WordPress site accessible automatically?
Not on its own. Overlay and widget-based tools can help with some surface-level issues, but genuine accessibility depends on how the site is actually built — semantic HTML, proper labelling, colour choices and keyboard support. Treat plugins as a supplement to good build practice, not a substitute for it.
Where should I start if I only have a small budget?
Run a free automated scan, fix the alt text and contrast issues it surfaces and test your main navigation and one key form with a keyboard only. Those three steps address a large share of the most common failures at effectively no cost.
Building accessibility in from the start
The businesses that handle this well don’t treat accessibility as a one-off audit — they build it into how their site is designed and maintained, the same way they’d handle page speed or mobile responsiveness. If you’re planning a rebuild, a redesign, or want a WCAG 2.2 review of your current site, that’s exactly the kind of thing we help Melbourne and Australian businesses get right from the ground up.
