What does WCAG compliance mean in Australia?
WCAG compliance in Australia means your website conforms to the Web Content Accessibility Guidelines published by the W3C, usually to Level AA of the current version, WCAG 2.2. For private businesses it is the practical way to show you are not discriminating against people with disability online.
WCAG is not an Australian law. It is an international technical standard organised around four principles: content must be perceivable, operable and understandable, and the code must be dependable enough for assistive technologies to interpret. Each principle contains testable success criteria at three levels, A, AA and AAA. Level AA is the level Australian guidance points to, and it covers things like text contrast, keyboard access, visible focus, captions for video, labelled form fields, error messages people can understand, and content that works when zoomed.
The law sits underneath. The Disability Discrimination Act 1992 makes disability discrimination unlawful in many areas of life, and the Australian Human Rights Commission explains in its digital accessibility guidelines that this includes digital goods and services. So WCAG compliance in Australia is less about ticking a certificate and more about reducing the chance that a customer cannot book, buy, enquire or read because of how your site was built.
- Perceivable: text alternatives, captions, contrast, content that adapts
- Operable: keyboard access, enough time, no seizure risks, clear navigation
- Understandable: readable text, predictable behaviour, help with errors
- Fourth principle: code that assistive technologies can interpret reliably
Is WCAG compliance mandatory for Australian businesses?
No law names WCAG as mandatory for every private website, but the Disability Discrimination Act applies to businesses that provide goods and services, including online, and the Australian Human Rights Commission's guidance treats WCAG 2.2 Level AA as the minimum to aim for. In practice, that makes WCAG compliance in Australia the benchmark a complaint would be measured against.
Section 24 of the Act deals with the provision of goods, services and facilities, whether paid for or free. The Commission's 2025 guidelines on equal access to digital goods and services explain how that applies to websites, apps and digital documents, and state that organisations should conform with WCAG 2.2 at a minimum Level AA and consider appropriate Level AAA criteria. The guidelines describe themselves as helping organisations meet their obligations, and as the minimum they should aim for.
Government is different. The Commonwealth Digital Service Standard, version 2.0 released in December 2023, requires the latest version of WCAG for the services it covers, and state governments set their own policies. If you sell to government or deliver funded services, your contract may add accessibility requirements too. We are not lawyers; for a view on your specific obligations, speak to your own legal adviser.
The Commission's guidelines on equal access to digital goods and services set out its current position.
What happens if an Australian website is not accessible?
A person who cannot use your website because of disability can complain to the Australian Human Rights Commission under the Disability Discrimination Act, and the Commission's guidelines describe cases that began that way. The better outcome, for everyone, is fixing barriers before anyone has to complain.
The best-known Australian case is Maguire v Sydney Organising Committee for the Olympic Games in 2000. Mr Maguire, who is blind, complained that the Olympic website was not accessible to him. The organising committee argued that making it compatible with the W3C guidelines would impose unjustifiable hardship, and the Commission found that argument did not hold, because the benefit to vision-impaired people was considerable and the burden was modest. The Commission's current guidelines still cite that decision as upholding the relevance of WCAG under the Act.
Unjustifiable hardship is a real concept in the Act, assessed on all the circumstances, and the guidelines note it is up to the organisation claiming it to show why. For a typical business website built on a modern platform, most WCAG 2.2 AA fixes are ordinary development work, which makes a hardship argument hard to sustain. Your adviser can tell you how this applies to you; our job is to make the fixes affordable.
What changed in WCAG 2.2, and why it matters for Australian sites
WCAG 2.2, released in October 2023, added nine success criteria to WCAG 2.1 and removed one, 4.1.1 Parsing, which the W3C now describes as obsolete. Six of the new criteria sit at Level A or AA, so they are part of the target for WCAG compliance in Australia.
The new A and AA criteria focus on people with motor, cognitive and low-vision needs. Focus Not Obscured requires that a keyboard user's focused element is not completely hidden by sticky headers, cookie banners or chat widgets. Dragging Movements asks for a single-pointer alternative to anything that needs dragging, such as sliders or map pins. Target Size (Minimum) asks that pointer targets are at least 24 by 24 CSS pixels, or spaced so they do not crowd each other. Consistent Help asks that help options, like a phone number or chat link, appear in the same place across pages. Redundant Entry avoids making people type the same information twice in one process. Accessible Authentication (Minimum) removes the need to solve a memory or puzzle test to log in, unless an alternative is offered.
Older sites that met WCAG 2.1 AA commonly fail two or three of these: a sticky header covers focused links, tiny icon buttons sit too close together in a mobile menu, and a checkout asks for the delivery address again as the billing address with no "same as" option. These are usually quick fixes once found.
A WCAG 2.2 AA checklist for Australian business websites
Use this WCAG compliance checklist for Australia to find the barriers that affect most visitors, then confirm with a proper audit. It is not a substitute for testing every success criterion, but it catches the issues we find on almost every site.
- Every page has one clear H1 and headings in a logical order
- All meaningful images have alt text; decorative images are hidden from screen readers
- Text contrast is at least 4.5:1, or 3:1 for large text and interface parts
- Every function works with a keyboard alone, with a visible focus indicator
- Focused elements are never completely hidden by sticky headers or banners
- Form fields have visible labels, and errors say what went wrong and how to fix it
- Buttons and links have at least 24 by 24 CSS pixel targets or enough spacing
- Help and contact options sit in the same place on every page
- Video has captions; audio-only content has a transcript
- Pages work at 200% zoom and at narrow widths without sideways scrolling
- Link text makes sense out of context: no bare 'click here'
- Log-in does not rely on a puzzle or memory test without an alternative
- The page language is set, and dynamic updates are announced to screen readers
The W3C's summary of what is new in WCAG 2.2 explains the newer items with examples.
How a WCAG compliance audit works
A WCAG compliance audit for an Australian site samples your templates and key journeys, tests them against every WCAG 2.2 A and AA success criterion using automated tools and manual checks, and produces a prioritised list of issues with the fix for each. Automated scanning alone finds only a portion of real barriers, so manual testing is the core of the work.
We start by agreeing the scope: the home page, each distinct template, and the journeys that matter to your business, such as making an enquiry, booking an appointment, buying a product or downloading a document. For each item we run automated scanners, then test by keyboard, with screen readers on desktop and mobile, at 200 percent zoom, and in high-contrast modes. Custom components such as menus, tabs, carousels, date pickers and modal windows get extra attention, because they fail most often.
The report lists each issue with the page, the success criterion, how it affects users, a screenshot or code reference, a priority and the recommended fix. Issues that block a task, such as a checkout button that cannot be reached by keyboard, come first. Cosmetic items that technically fail but do not stop anyone come later. You get a summary you can share with management and a detailed list your developers, or we, can work through.
Blocker
Stops a user completing a key task: fix before anything else.
Serious
Makes a task very difficult or confusing: fix in the first round.
Moderate
Causes friction but has a workaround: schedule into the next sprint.
Minor
Technical failure with little impact: fix during routine maintenance.
For WCAG compliance in Australia, remediation means changing your site's code and content so each issue is actually resolved, then retesting to prove it. Fix shared templates and components first, because one fix to a header or form component can clear the same issue on hundreds of pages.
Typical fixes include rewriting a custom dropdown so it uses native elements or proper ARIA roles, adding labels and error announcements to forms, restructuring headings, adjusting brand colours to meet contrast ratios while keeping the look, adding skip links, correcting focus order in modal windows, writing alt text, and captioning videos. Content fixes, such as link text and PDF accessibility, often need your team's input because they depend on meaning.
After each batch we retest the affected pages with the same methods used in the audit and mark issues as resolved, partly resolved or needing your decision. Some issues sit in third-party tools, such as a booking widget or payment page. We report those to you with evidence you can send the vendor, and suggest alternatives if a vendor cannot fix them.
Do accessibility overlay widgets make a website WCAG compliant?
No overlay can make an inaccessible site conform on its own, because it does not change the underlying code that screen readers and keyboards rely on. Real WCAG compliance in Australia comes from fixing the site itself.
Overlays are scripts that add a toolbar for adjusting text size or contrast and try to patch issues automatically in the browser. Many disabled users already have these adjustments in their own devices and assistive technology, and automated patches cannot reliably judge things like whether alt text is meaningful or whether a custom widget announces its state correctly. Some users report that overlays interfere with their screen readers.
If you already pay for an overlay, it does not need to be removed on day one, but it should not be treated as the fix. We audit the site with the overlay switched off, fix the code, and then you can decide whether the overlay still adds anything. Most businesses find it no longer does.
Screen-reader and keyboard testing for WCAG compliance
WCAG compliance testing in Australia should use the tools people actually use: NVDA on Windows, VoiceOver on Mac and iPhone, TalkBack on Android, and a keyboard with no mouse. Each behaves slightly differently, and a component that works in one can fail in another.
Keyboard testing comes first because it is quick and reveals a great deal. Press Tab from the top of the page and watch: can you see where you are, does focus move in a logical order, can you open the menu, use the search, submit the form and close any pop-up with Escape? Then screen-reader testing checks what is announced: page titles, headings, landmarks, link and button names, form labels, error messages and changes that happen without a page reload.
Mobile testing matters for Australian sites because many customers browse and buy on phones. VoiceOver on iPhone and TalkBack on Android use gestures rather than keys, and they expose issues like tiny touch targets, content that only appears on hover, and carousels that trap focus. We record short screen recordings of failures so your team can see the problem, not just read about it. What we cannot provide in-house is testing by people with lived experience of disability; for larger or public services, we recommend adding that through a specialist panel.
Writing an accessibility statement for an Australian website
An accessibility statement tells visitors which standard you aim for, how you tested, what known issues remain and how to reach you if something does not work. The Australian Human Rights Commission's guidelines list providing an accessibility statement that explains how standards have been met among the practices that deliver equal access.
Keep it honest and specific. State the target, for example WCAG 2.2 Level AA, the date of the last review, the methods used, and any areas that do not yet meet the target, with an expected fix date if you have one. Give at least two ways to report a barrier, such as email and phone, and explain what happens next. Avoid claiming full compliance unless an audit supports it, and never use a statement to promise something the site does not do.
We draft the statement from the audit and remediation results, you review it, and ideally your adviser checks the wording. Link it from the footer of every page and update it whenever you finish a round of fixes or a new audit.
- Commitment and target standard
- Scope: which sites, apps or documents it covers
- How and when the site was tested
- Known limitations and planned fixes
- How to request content in another format
- Contact options and expected response time
How much does WCAG compliance cost for an Australian website?
The cost of WCAG compliance depends on the number of distinct templates and custom components, not the page count. Audits and fixes are quoted after we look at your site; accessible rebuilds with BtechWaleTech start from US$150, and local quotes vary widely depending on scope and testing depth.
A brochure site built on a few well-structured templates may need a day or two of fixes after the audit. A site on an old page builder with nested layouts, inaccessible sliders and dozens of custom forms may need so much work that a rebuild is cheaper and faster. An online store adds product filters, variant pickers, carts and checkout steps, each with its own accessibility traps; accessible store builds start from US$750. Web apps and portals with complex interactive screens start from US$900.
Remember the ongoing side. Every new page, blog post, PDF and plugin can introduce barriers, so part of the cost is training your editors and checking updates. Care after the two free months starts from US$120/mo. For a wider look at website budgets, see how much a website costs in Australia.
Fix the existing site or rebuild it accessibly?
On the road to WCAG compliance in Australia, fix the existing site when its templates are reasonably clean and the issues are mostly content, labels and contrast. Rebuild when the theme or builder generates inaccessible markup you cannot control, or when the site needs a redesign anyway.
A quick way to decide: count how many audit issues trace back to the theme, page builder or plugins you cannot edit. If most issues are in code you control, fixing is efficient. If most sit in a builder's output, every fix becomes a workaround that the next update may undo. In that case, rebuilding on clean templates with accessibility designed in usually costs less over two or three years.
A rebuild also lets you protect search rankings properly, with URL mapping and redirects, and improve speed at the same time. Our website redesign services page explains how we keep rankings through a rebuild, and WordPress website design covers building an editable site that stays accessible.
Which Australian businesses should prioritise WCAG compliance?
Every business benefits from WCAG compliance in Australia, but some should move first: organisations serving people with disability or older people, businesses selling online, anyone supplying government, and services people must use, such as health, finance, education and utilities.
NDIS providers and aged care services have audiences where accessibility is essential, not optional, and families checking a provider will notice when a site does not work with a screen reader or at large text sizes. Online stores risk losing sales at the checkout, where inaccessible forms stop customers completing a purchase. Suppliers to government may find accessibility written into tenders, and the Commission's guidelines suggest including accessibility in procurement documents when buying digital services.
Clinics, law firms, accountants and brokers handle enquiries and bookings that people need to make, sometimes urgently. If the only way to book is a form that cannot be completed by keyboard, you have a problem worth fixing this month, not next year. Our NDIS provider websites and aged care website design pages go deeper on those sectors.
Does WCAG compliance help SEO and AI search visibility?
WCAG compliance in Australia is not a ranking factor you can switch on, but many accessibility fixes overlap with what helps search engines and AI assistants understand a page. Clear headings, descriptive link text, text alternatives and clean HTML serve people and machines alike.
Search engines read the same structure a screen reader does. A page with one H1, logical subheadings, meaningful alt text and links that describe their destination is easier to interpret than one built from styled divs. Captions and transcripts turn video content into indexable text. Fast, stable pages help both users with cognitive or motor disabilities and your Core Web Vitals.
AI assistants that summarise pages tend to quote clear, self-contained passages under descriptive headings. Accessible content writing, which favours plain language and a logical order, happens to produce exactly that. So the work you do for WCAG compliance in Australia often pays off twice. Nobody can guarantee rankings, but a well-structured, accessible page gives you a better starting point.
Working with an accessibility team in India from Australia
For WCAG compliance work from India, you deal directly with the three developers who audit and fix your site, by WhatsApp, email and video call. There is no Australian office or local entity, invoices come from India, and quotes are in USD, paid by Wise, international wire or PayPal in stages set out in the written quote.
India is four and a half hours behind Sydney and Melbourne on standard time and five and a half in daylight saving, so calls land in your afternoon. Brisbane has the same gap all year, and Perth, two and a half hours ahead of India, can talk before lunch. Accessibility work suits this pattern: we fix and retest during our day and send you screen recordings and before-and-after notes to review during yours.
You keep control of the site. You invite us to your hosting, repository or CMS as users, and we work on a staging copy before anything reaches the live site. How you treat our invoice for tax is for your accountant.
First week
Scoping call, agreed list of templates and journeys, staging access, automated scans and the start of manual testing.
Second week
Audit report with priorities, a walkthrough call, blockers fixed on staging and retested, and a plan for the remaining issues.
Worked example: WCAG compliance for a regional physiotherapy clinic
This is a hypothetical scenario, not a client story. Say a physiotherapy clinic in Ballarat with two locations runs a WordPress site built on a page builder, with online booking through an embedded third-party widget, and a patient who uses a screen reader mentions they could not find the booking button.
The audit covers the home page, service page template, practitioner profiles, contact page, blog template and booking journey. It finds a mobile menu that cannot be opened by keyboard, a sticky header hiding focused links, low-contrast grey text, icon-only buttons with no names, a contact form without labels, and a booking widget whose date picker does not announce available times.
Most issues trace to the page builder, so the clinic chooses a rebuild on clean templates from US$150, finished in about two weeks, with colours adjusted to pass contrast while keeping the brand. The booking widget issue is documented with recordings and sent to the vendor, while the site adds a clearly labelled phone booking option next to it. The clinic publishes an accessibility statement listing the widget as a known limitation with the alternative.