Website Accessibility in Australia: WCAG Guide
By BudgetByte Editorial Team • Published on 04/10/2026
Why Accessibility Belongs on Your Website Checklist
Want an accessible website from day one? We build with semantic HTML, keyboard-friendly forms and readable contrast as standard. Get a quote or see our services.
An accessible website is one that people with disability can use. That includes people who are blind or have low vision and use screen readers or magnification, people who are Deaf or hard of hearing, people who can't use a mouse, and people with cognitive or learning disabilities. It also helps older users, people on small phone screens in bright sunlight, and anyone with a temporary injury.
For Australian businesses, website accessibility isn't just a nice extra. This guide explains the legal background, what the WCAG standard asks for in plain English, the most common problems we see on small business sites, and how to check your own.
This article is general information, not legal advice.
The Legal Background in Australia
The Disability Discrimination Act 1992 (DDA) makes it unlawful to discriminate against people with disability when providing goods, services and facilities. The Australian Human Rights Commission (AHRC) has published guidance making clear that this applies to websites and online services, and it points to the Web Content Accessibility Guidelines (WCAG) as the benchmark.
Australian Government websites are expected to meet WCAG at Level AA. There is no separate certification scheme for private businesses. But if someone can't use your website because of their disability, they can make a complaint to the AHRC. Beyond the legal side, an inaccessible website simply turns away customers.
For a broader look at the legal side of running a website, see our guide to website legal requirements in Australia.
WCAG in Plain English
WCAG is published by the World Wide Web Consortium (W3C). Version 2.2 is the current recommendation, and it builds on 2.0 and 2.1. It has three conformance levels: A (minimum), AA (the usual target), and AAA (the highest, not expected for whole sites).
WCAG is organised around four principles, often remembered as POUR:
Perceivable
People must be able to perceive the content. That means text alternatives for images, captions for video, enough colour contrast, and content that still makes sense when zoomed or resized.
Operable
People must be able to use the interface. Everything should work with a keyboard, focus should be visible, there should be enough time to complete tasks, and nothing should flash in a way that could trigger seizures.
Understandable
Content and interfaces should be clear and predictable. Use plain language, label forms clearly, explain errors, and make navigation consistent.
Robust
The site should work reliably with assistive technologies. In practice, that means well-structured, standards-based code.
The Most Common Accessibility Problems on Small Business Sites
In our experience reviewing Australian small business websites, the same issues come up again and again.
Missing or unhelpful alt text
Images that carry meaning (a photo of your completed work, a chart, an icon button) need alt text describing them. Decorative images should have empty alt text so screen readers skip them. "IMG_4521.jpg" or "image" isn't helpful.
Low colour contrast
Light grey text on a white background, or white text on a pale photo, is hard for many people to read. WCAG AA sets minimum contrast ratios for text, and free contrast checkers will tell you if you pass.
Forms without labels
Placeholder text that disappears when you start typing is not a label. Each field needs a visible, programmatically connected label. Error messages should say what's wrong and how to fix it, not just turn the box red.
Keyboard traps and invisible focus
Try navigating your site with the Tab key. Can you reach every link, button and form field? Can you see where you are? Can you open and close the mobile menu, pop-ups and booking widgets?
Headings used for styling
Screen reader users often jump between headings to scan a page. Headings should follow a logical order (one H1, then H2s and H3s) and not be chosen just because of their font size.
Vague link text
"Click here" and "read more" repeated across a page don't tell a screen reader user where the link goes. Use descriptive link text such as "View our bathroom renovation projects."
Video without captions
Captions help Deaf and hard of hearing users, and also anyone watching with the sound off. Auto-generated captions are a start, but review them for accuracy.
PDFs that aren't accessible
Menus, price lists and forms published only as scanned PDFs can't be read by screen readers. Put key information on the web page itself.
How to Check Your Own Website
You don't need specialist training to find the most obvious problems.
- Keyboard test. Put your mouse away and use Tab, Shift+Tab, Enter and the Space bar to go through your home page, a service page and your contact form.
- Zoom test. Zoom your browser to 200%. Is everything still readable without horizontal scrolling?
- Automated check. Run a free tool such as WAVE or the accessibility audit in Chrome's Lighthouse. These catch some issues (missing alt text, low contrast, missing labels) but not all.
- Screen reader test. Try VoiceOver on a Mac or iPhone, TalkBack on Android, or NVDA on Windows. Listen to how your home page and contact form are read out.
- Content check. Read your key pages aloud. Is the language plain? Are headings meaningful? Are instructions clear?
Automated tools are a starting point, not a pass mark. A site can score well and still be difficult to use.
Accessibility and SEO Overlap
Many accessibility basics also help search engines understand your site: descriptive headings, alt text, meaningful link text, clear page titles, and fast, well-structured code. That isn't the main reason to do it, but it's a useful bonus. Our article on website design in Australia covers other foundations of a well-built small business site.
Building Accessibility In From the Start
Fixing accessibility after launch is possible, but it's far easier to build it in:
- Choose a design with strong contrast and readable font sizes.
- Use real text instead of text inside images.
- Make sure every interactive element is a proper button or link.
- Test forms, menus and pop-ups with a keyboard before launch.
- Write alt text as you add images.
- Caption videos before publishing.
- Include accessibility in your website brief so every designer quoting knows it's expected.
An Accessibility Checklist for Your Next Update
- Every meaningful image has descriptive alt text. Decorative images have empty alt.
- Text meets WCAG AA contrast requirements.
- All functionality works with a keyboard, and focus is visible.
- Forms have visible labels and clear error messages.
- Headings follow a logical order.
- Link text makes sense out of context.
- Videos have accurate captions.
- Pages work at 200% zoom and on small screens.
- Key information isn't locked inside images or scanned PDFs.
- An accessibility statement explains how people can contact you if they have trouble.
Frequently Asked Questions
Is website accessibility a legal requirement in Australia?
The DDA prohibits disability discrimination in providing services, and the AHRC's guidance applies this to websites. There's no certification you must hold, but an inaccessible site can lead to a complaint, and it shuts out potential customers.
Which WCAG level should a small business aim for?
Level AA is the usual target and the level referenced for Australian Government websites. Level AAA is generally not expected across a whole site.
Can an accessibility plugin or overlay make my site compliant?
Overlay tools that add a toolbar or try to fix issues automatically don't fix underlying problems in the code and content, and some users find them make things harder. It's better to fix the site itself.
How much work is it to make an existing site accessible?
It depends on how the site was built. Some issues, such as alt text, labels and contrast, are quick fixes. Others, such as inaccessible menus or page builders that produce messy code, may be better solved with a rebuild.
Talk to Us About Accessible Design
If you'd like an accessibility review of your current site, or a new site built with accessibility as standard, contact BudgetByte.
Related guide: NDIS Provider Website Design Guide
Related guide: Childcare Website Design: What Parents Want
Related guide: Multilingual Websites for Australian Business
About BudgetByte Editorial Team
The BudgetByte Editorial Team specializes in local SEO and high-performance web development strategies tailored for Australian trades and agencies.
Need a Local Website Built Fast?
We serve small businesses and tradesmen across Australia with premium, affordable web design.
