Website Accessibility: What Australian Businesses Need to Know

Most Australian businesses have not thought seriously about website accessibility. Some have heard of it and assumed it only applies to government sites. Neither assumption is correct, and both carry real risk.

Here is what WCAG actually is, what Australian law says, and what fixing it looks like in practice.

WCAG 2.1 AA Without the Jargon

WCAG stands for Web Content Accessibility Guidelines. It is published by the W3C, the same international body that sets web standards. The guidelines describe how to make web content usable by people with a range of disabilities, covering visual, auditory, physical, speech, cognitive, and neurological conditions.

There are 3 conformance levels: A, AA, and AAA. Level AA is the standard that governments, healthcare organisations, and most compliance requirements point to. It is achievable for most websites without exotic technology. AAA is the highest level and some of its criteria are intentionally aspirational.

The guidelines are organised around 4 principles. Content must be perceivable (users can access it through at least one sense), operable (users can interact with all controls and functions), understandable (content and interfaces are clear), and compatible (content functions correctly with assistive technologies). Those 4 principles generate 50 success criteria at Level AA.

In practice, the failures that actually matter and that audits surface most often are concentrated in a much smaller set of issues.

The Australian Legal Context

This is not the US, and the ADA (Americans with Disabilities Act) does not apply here. Australian businesses operate under the Disability Discrimination Act 1992, which makes it unlawful to discriminate against a person with a disability in access to goods and services. The Australian Human Rights Commission has issued guidance confirming that websites fall within the scope of the DDA.

The WCAG guidelines are referenced in the Australian Government's web accessibility requirements, and government agencies at all levels are required to meet WCAG 2.1 AA. For private businesses, the DDA creates a legal obligation that is less prescriptive but real. Complaints can be lodged with the Australian Human Rights Commission. Litigation is possible and has occurred.

The risk is higher in sectors that serve broad public audiences, healthcare, finance, retail, education. If you serve customers online and some of those customers have disabilities, access barriers on your site are a legal exposure.

The Most Common Failures

In every accessibility audit we have run, the same failures appear repeatedly.

Missing alt text. Images without alternative text descriptions are invisible to screen readers. A decorative image can have an empty alt attribute (alt=""). An informative image needs a description that conveys its meaning. A graph showing revenue growth needs alt text that describes what the graph shows, not just "a graph."

Poor colour contrast. WCAG AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. Light grey text on a white background fails this consistently. So do thin light fonts on pale backgrounds. There are free tools that check any colour combination against the standard.

Unlabelled form fields. A text input with placeholder text that says "Your name" looks fine visually. But if the input has no associated <label> element, a screen reader user navigating the form by keyboard does not know what the field is for. Placeholder text disappears when you start typing. Labels do not.

Keyboard navigation gaps. Every interactive element on a site needs to be reachable and operable by keyboard alone. Users who cannot use a mouse rely on the tab key to move through the page. If a dropdown menu only opens on hover, keyboard users cannot access it. If a modal dialog traps keyboard focus inside it and pressing Escape does not close it, keyboard users are stuck.

Missing focus indicators. When a keyboard user tabs to a button or link, there needs to be a visible indicator showing which element is focused. Many designs remove the default browser focus outline because it is considered unattractive, and replace it with nothing. That is a failure.

Our Process for the St Rose Hospital Build

St Rose Hospital's website was 70 pages. Every page audited against WCAG 2.1 AA. That is not a task you can do at the end of a project. It needs to be embedded in the build process from the start.

We established an accessibility baseline before writing the first line of CSS. Heading hierarchy was defined: one <h1> per page, logical order from H2 downward, no headings used for visual sizing. Colour palette was checked before design sign-off. Every form in the system was built with explicit labels from the beginning, not retrofitted later.

During development we ran every page state through three tools: Lighthouse (built into Chrome DevTools), axe (browser extension), and WAVE (a visual overlay tool that highlights issues directly on the page). These tools catch a significant proportion of WCAG AA failures automatically. They do not catch everything. Manual keyboard navigation testing is essential. Automated tools cannot verify that a modal is logically structured for a screen reader the way a human testing it can.

At 70 pages, the audit process is methodical. We worked through the site in sections, fixing issues as they were found rather than accumulating a remediation backlog. Finding an accessibility failure during build costs minutes. Finding it during a formal audit after launch costs significantly more.

How to Audit Your Own Site

Three free tools are sufficient for an initial audit.

Lighthouse: Open Chrome DevTools (F12), go to the Lighthouse tab, run an audit on Accessibility. It gives you a score and a list of specific failures with documentation on how to fix each one.

axe DevTools: Browser extension available for Chrome and Firefox. Run it on any page and it highlights accessibility violations with severity levels. The free version is comprehensive for WCAG 2.1 AA checking.

WAVE: Web Accessibility Evaluation Tool at wave.webaim.org. Enter any public URL and it returns a visual overlay of the page with icons marking issues. Useful for getting a quick picture of where problems are concentrated.

Start with your most visited pages and your most critical conversion paths. A site with 200 pages needs to be prioritised: fix the homepage, the contact page, the service pages, and any pages that drive direct revenue first.

If your site is in a regulated sector or you serve a broad public audience, a professional audit is worth the investment. We include accessibility auditing in our website builds. We can also audit existing sites independently of a rebuild.