Accessibility Requirements for Australian Websites

The Legal and Practical Reality of Web Accessibility in Australia

Roughly 4.4 million Australians — about 17.8% of the population — live with some form of disability, according to the Australian Bureau of Statistics 2022 Survey of Disability, Ageing and Carers. That figure includes people with vision impairment, hearing loss, cognitive disabilities, and mobility limitations. Every one of them is a potential customer. Every one of them is trying to use the internet to find local services, book appointments, make purchases, and get information.

Yet most Australian small business websites are built without a single accessibility consideration. No alt text on images. Colour contrast that fails even the most basic test. Forms that can't be navigated by keyboard. PDFs that screen readers can't parse. These aren't aesthetic oversights — they are, in many cases, legal exposures.

This guide is the definitive reference on accessibility requirements for Australian websites. It covers the legal framework, the technical standards, the compliance process, the real costs, and the practical steps any business owner or web designer needs to take. Whether you run a café in Brisbane, a physiotherapy clinic in Melbourne, or a law firm in Sydney, this article applies to you.

The Legal Framework: What Australian Law Actually Says

The Disability Discrimination Act 1992 (DDA)

The primary federal law governing web accessibility in Australia is the Disability Discrimination Act 1992 (Cth). The DDA makes it unlawful to discriminate against a person on the grounds of disability in a wide range of areas, including access to services and facilities provided to the public.

The Australian Human Rights Commission (AHRC) has explicitly confirmed that websites and digital services are covered under the DDA. If your website is inaccessible to a person with a disability — and they can demonstrate they were unable to access a service that a non-disabled person could access — you may be in breach of the Act. Complaints are lodged with the AHRC and can proceed to the Federal Court.

Importantly, the DDA operates on a complaints-based model. The Australian government does not proactively audit private sector websites. However, that does not make non-compliance safe. Any person who encounters a barrier on your website can file a formal complaint, triggering conciliation proceedings and potentially litigation.

Advisory Notes from the AHRC

In 2014, the AHRC published its World Wide Web Access: Disability Discrimination Act Advisory Notes. These notes confirm that:

• Websites operated by Australian entities that provide services to the public must be accessible to people with disabilities.
• The recommended standard for compliance is the Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium (W3C).
• Both public sector and private sector organisations are subject to the DDA.

While the Advisory Notes are not legally binding regulations in themselves, they represent the AHRC's official position on what constitutes compliance. Any Federal Court proceeding would almost certainly reference WCAG conformance as the benchmark.

Government Sector: The WCAG Mandate

For Australian government agencies at the federal level, web accessibility is not advisory — it is mandatory. The Digital Service Standard administered by the Digital Transformation Agency (DTA) requires that all government websites and digital services meet WCAG 2.1 Level AA as a minimum. Most state governments have adopted equivalent requirements.

Private sector businesses are not under the same mandatory obligation, but the government standard provides the clearest signal of what courts and regulators consider reasonable compliance.

Notable Australian DDA Web Accessibility Cases

The landmark Australian case establishing web accessibility obligations was Maguire v SOCOG [2000] HREOCA 16. Bruce Maguire, a blind man, filed a complaint against the Sydney Organising Committee for the Olympic Games because the official Sydney 2000 Olympics website was not accessible to screen reader software. The Human Rights and Equal Opportunity Commission ruled in his favour. SOCOG was ordered to pay $20,000 in damages.

This case, decided over two decades ago, remains the foundational precedent. It confirmed unambiguously that websites are subject to the DDA and that WCAG (then version 1.0) is the applicable standard.

Understanding WCAG: The Technical Standard That Governs Compliance

What Is WCAG?

The Web Content Accessibility Guidelines (WCAG) are the internationally recognised technical standard for web accessibility, published and maintained by the World Wide Web Consortium (W3C). The guidelines are organised around four core principles, commonly remembered by the acronym POUR:

• Perceivable: Information and interface components must be presentable in ways users can perceive — e.g. text alternatives for images, captions for video.
• Operable: Interface components and navigation must be operable — e.g. keyboard navigation, no content that triggers seizures.
• Understandable: Information and the operation of the interface must be understandable — e.g. readable text, predictable navigation, error identification.
• Robust: Content must be robust enough to be reliably interpreted by assistive technologies — e.g. valid HTML, name/role/value for custom components.

WCAG Versions: 2.0, 2.1, and 2.2

Version	Released	Key Additions	Australian Government Minimum
WCAG 2.0	2008	Foundational 61 success criteria	Superseded
WCAG 2.1	2018	17 new criteria; mobile, low vision, cognitive	Current minimum (AA)
WCAG 2.2	2023	9 new criteria; focus appearance, target size, auth	Recommended best practice
WCAG 3.0	In development	New scoring model, broader scope	Not yet applicable

As of 2026, the operative standard for Australian compliance purposes is WCAG 2.1 Level AA. WCAG 2.2 was published in October 2023 and is increasingly referenced in best practice guidance, though not yet a formal government mandate. Forward-thinking organisations are beginning to implement WCAG 2.2 now to avoid future retrofitting.

Understanding Conformance Levels: A, AA, and AAA

Each WCAG version defines three levels of conformance:

• Level A: The minimum level. Addresses the most critical barriers. Non-compliance at this level likely constitutes direct discrimination under the DDA.
• Level AA: The standard adopted by the Australian government and widely recognised as the baseline for reasonable compliance. Addresses the majority of barriers faced by users with disabilities.
• Level AAA: The highest level. Not generally required as a blanket standard — some criteria may be impossible to satisfy for all content types — but specific AAA criteria may be relevant in context.

For private Australian businesses, targeting WCAG 2.1 Level AA is the appropriate goal. It provides meaningful protection against DDA complaints and genuinely improves usability for a broad range of users.

The 13 Key WCAG 2.1 AA Requirements Every Australian Business Website Must Address

WCAG 2.1 Level AA encompasses 50 success criteria. The following are the most commonly failed and most practically relevant for small and medium business websites in Australia:

1. Text Alternatives (1.1.1): Every non-text content element — images, icons, infographics — must have descriptive alt text. Decorative images should have empty alt attributes (alt="").
2. Captions for Video (1.2.2): Pre-recorded video content that includes audio must have synchronised captions. This includes embedded YouTube or Vimeo videos on your site.
3. Colour Contrast — Normal Text (1.4.3): Text must have a contrast ratio of at least 4.5:1 against its background. This is one of the most commonly failed criteria.
4. Colour Contrast — Large Text (1.4.3): Large text (18pt or 14pt bold and above) requires a minimum contrast ratio of 3:1.
5. Resize Text (1.4.4): Text must be resizable up to 200% without loss of content or functionality.
6. Images of Text (1.4.5): Avoid using images to convey text. Use actual HTML text instead, styled with CSS.
7. Reflow (1.4.10, WCAG 2.1): Content must not require horizontal scrolling at 320px wide viewport width. This is critical for mobile accessibility.
8. Non-text Contrast (1.4.11, WCAG 2.1): User interface components (buttons, form fields) and informational graphics must have a contrast ratio of at least 3:1 against adjacent colours.
9. Keyboard Accessibility (2.1.1): All functionality must be operable via keyboard alone. Users who cannot use a mouse must be able to navigate, submit forms, and interact with all content.
10. Focus Visible (2.4.7): Any keyboard-focusable interface component must have a visible focus indicator. Do not suppress the default browser focus outline without providing a visible alternative.
11. Page Titles (2.4.2): Each page must have a descriptive title that identifies its topic or purpose.
12. Labels for Inputs (1.3.1, 3.3.2): Every form field must have a programmatic label. Placeholder text alone does not satisfy this requirement.
13. Language of Page (3.1.1): The primary human language of each page must be declared in the HTML lang attribute (e.g. lang="en-AU").

Who Is Most at Risk: Industries with Elevated Compliance Obligations

While the DDA applies to all businesses offering services to the public, certain industries carry elevated risk and heightened ethical obligations around accessibility:

Health and Medical Practices

Healthcare providers — GPs, allied health clinics, specialists — serve patients across every demographic, including older Australians, who have higher rates of disability. A patient who cannot navigate your online booking system because of a vision impairment is being denied access to healthcare. If you operate websites for health and wellness practices, accessibility must be treated as a clinical and legal obligation, not an afterthought.

Legal Services

Law firms have a particular obligation given that their clients may be seeking legal redress precisely because of discrimination or disadvantage. An inaccessible law firm website is an ironic and legally exposed position. Well-structured websites for law firms should incorporate full WCAG 2.1 AA compliance as standard practice.

Childcare and Education

Childcare operators serve families across a wide spectrum, including parents with disabilities who need to research services, complete enrolment forms, and communicate with staff online. Websites for childcare centres must be navigable by all parents, including those using screen readers or keyboard-only navigation.

Hospitality and Retail

Cafés, restaurants, and retailers offering online menus, reservations, or e-commerce are providing services to the general public and are clearly subject to the DDA. For example, a café using inaccessible PDFs for their menu — which is extremely common — may be breaching their obligations to customers with visual impairments. Businesses like ZenPacks Australia, which serves hospitality and food service clients, demonstrate that even B2B platforms in this sector need to consider accessibility across their digital touchpoints.

Government Contractors and Funded Organisations

If your business holds a government contract or receives government funding, your website accessibility obligations may be explicit contractual requirements, not merely implied by the DDA.

How to Audit Your Website for Accessibility: A Practical Step-by-Step Process

1. Run an automated scan. Start with free automated tools. Google's Lighthouse (built into Chrome DevTools) provides an accessibility score and highlights common failures. WAVE (wave.webaim.org) is a free browser extension that overlays visual indicators of accessibility errors. axe DevTools offers a free browser extension with more detailed results. Note: automated tools typically catch 30–40% of WCAG issues. They are a starting point, not a final audit.
2. Check colour contrast manually. Use the WebAIM Contrast Checker (webaim.org/resources/contrastchecker) to test specific colour combinations. Input your brand's hex codes for text and background colours.
3. Keyboard navigation test. Close your mouse. Navigate your entire website using only the Tab, Shift+Tab, Enter, and arrow keys. Can you reach every link, button, and form field? Is the focus indicator always visible?
4. Screen reader test. Use NVDA (free, Windows) or VoiceOver (built into macOS and iOS) to navigate your website. Does the page make logical sense when read aloud? Are images described? Are form labels read correctly?
5. Check all images for alt text. Right-click any image in your browser and inspect its HTML. Every meaningful image should have a descriptive alt attribute. Logos should describe the logo. Decorative images should have alt="".
6. Review forms. Every form field needs a visible label element that is programmatically associated with its input via a matching for/id pair. Check your contact form, booking form, and newsletter signup.
7. Check document accessibility. If you link to PDFs — menus, brochures, price lists — open them in Adobe Acrobat and run the built-in accessibility checker. Better still, convert the content to HTML pages.
8. Conduct a manual expert review or commission an audit. For comprehensive compliance, engage a certified accessibility specialist to conduct a manual audit against WCAG 2.1 AA. This typically costs $1,500–$5,000 for a small business website, depending on complexity.

The Real Cost of Web Accessibility: Remediation vs. Building Right the First Time

This is the section most articles skip. The economics of accessibility are not what most business owners expect.

The Cost of Retrofitting an Inaccessible Site

The single most expensive accessibility mistake is building an inaccessible website and then being forced to remediate it. Retrofitting WCAG 2.1 AA compliance onto a poorly built site can cost more than the original build.

Scenario	Estimated Cost	Notes
Build accessible from scratch (small business site)	$500–$3,000	Lowest cost; best outcome
Accessibility audit (5-page site)	$800–$2,500	Manual review by specialist
Remediation of existing site (minor issues)	$500–$2,000	Alt text, contrast fixes, label fixes
Remediation of existing site (structural issues)	$2,000–$8,000+	Theme or code rebuild may be needed
DDA complaint conciliation	$5,000–$20,000+	Legal fees + remediation + potential damages
Federal Court accessibility litigation	$50,000–$200,000+	Rare but possible; includes legal representation

The lesson is straightforward: investing in accessibility at the design and build stage costs a fraction of what it costs to fix later — and a tiny fraction of what a DDA complaint could cost.

Accessibility Overlays: Why They Are Not a Compliance Solution

So-called "accessibility overlay" tools — JavaScript plugins that claim to make your website instantly compliant — are widely marketed and widely misunderstood. Products like AccessiBe, UserWay, and AudioEye promise WCAG compliance via a single script installation. They are not a substitute for genuine accessibility.

The National Federation of the Blind (USA), leading accessibility researchers, and over 900 signatories to the Overlay Fact Sheet (overlayfactsheet.com) have documented that overlays fail to fix the majority of WCAG issues, can actively interfere with assistive technologies, and do not provide legal protection under disability discrimination law. The AHRC has not endorsed overlay tools as a compliance mechanism.

Using an overlay and claiming compliance would be a weak defence against a DDA complaint. Genuine accessibility requires genuine implementation.

Accessibility and SEO: The Business Case Beyond Legal Compliance

Many accessibility improvements directly benefit search engine optimisation — a convergence that makes the business case for accessibility even stronger.

• Alt text: Descriptive alt attributes help Google index your images and improve image search visibility. Google's own documentation confirms that alt text is a primary signal for image understanding.
• Semantic HTML: Proper use of heading hierarchy (H1 → H2 → H3), landmark elements (nav, main, footer), and list elements helps both screen readers and Googlebot parse page structure. Google Search Console data consistently shows that well-structured pages earn richer results.
• Page titles and meta descriptions: WCAG requires descriptive page titles (2.4.2). These are the same elements that drive click-through rates in search results.
• Captions and transcripts: Video captions provide Google with additional indexable text, improving the discoverability of video content.
• Mobile accessibility and Core Web Vitals: Many WCAG 2.1 criteria relating to reflow, text spacing, and target size align with Google's Core Web Vitals requirements that affect search ranking. PageSpeed Insights directly measures factors that intersect with accessibility.
• Readable, plain language: WCAG 3.1 guidance on readable language (clear writing, avoiding jargon) aligns with what Google rewards in terms of user engagement signals.

Accessibility is not a cost centre. It is an investment that simultaneously reduces legal risk, expands your potential customer base, and strengthens your organic search performance.

Platform-Specific Accessibility Considerations for Australian Small Businesses

The website platform you choose has a significant impact on how achievable WCAG 2.1 AA compliance is in practice.

Platform	AU Monthly Cost (approx.)	Accessibility Out of the Box	Notes for AU Businesses
Wix	~$17/mo	Moderate	Wix has invested in accessibility but theme/template choice matters greatly; editor can introduce inaccessible markup
Squarespace	~$16/mo	Moderate–Good	Templates are generally well-structured; limited control over focus states and ARIA attributes
Shopify	~$39/mo	Moderate	Accessibility varies heavily by theme; Dawn theme (default) has reasonable accessibility; third-party apps often introduce violations
WordPress (self-hosted)	$10–$30/mo hosting	Variable	Full control; accessible themes available; page builder plugins (Elementor, Divi) frequently generate inaccessible markup
Custom-built HTML/CSS/JS	Hosting only	Excellent (if built correctly)	Maximum control; accessibility depends entirely on developer skill and process

The key insight: no platform guarantees accessibility by default. Compliance is always a function of how the platform is configured, what theme or template is used, and how content is added. A developer who understands WCAG can build an accessible site on any of the above platforms. A developer who ignores accessibility can break it on any of them.

Writing an Accessibility Statement for Your Australian Website

Publishing an accessibility statement is a recognised best practice and signals good faith to both users and regulators. While not legally required for private sector sites, it is strongly recommended. A proper accessibility statement should include:

• A commitment to accessibility and which standard you are targeting (WCAG 2.1 Level AA)
• Known limitations and areas still being improved
• Contact information for users who experience accessibility barriers
• An accessible alternative for any content that cannot currently be made accessible (e.g. "If you cannot access our PDF menu, please call us on [number] and we will read it to you")
• Date of last review

The accessibility statement should be linked from the footer of every page of your website and should itself be fully accessible.

Ongoing Accessibility Maintenance: This Is Not a One-Time Fix

Accessibility is not a project you complete and forget. It is an ongoing operational commitment. Every time you:

• Add a new image without alt text
• Embed a video without captions
• Install a new plugin or widget
• Change your brand colours
• Add a new form
• Upload a PDF

...you create a potential new accessibility failure. A structured approach to ongoing maintenance — including accessibility checks as part of the content publishing workflow — is essential. Consider engaging a website care plan ($24.95 + GST/month) that incorporates regular accessibility monitoring alongside security updates, performance checks, and content management.

Frequently Asked Questions About Accessibility Requirements for Australian Websites

Is my small business website legally required to be accessible in Australia?

Yes. The Disability Discrimination Act 1992 (Cth) applies to all businesses that provide services to the public, including via websites. There is no small business exemption. The Australian Human Rights Commission has confirmed that website inaccessibility can constitute unlawful discrimination under the DDA. While the government does not proactively audit private sector sites, any person who experiences a barrier on your website can file a formal complaint with the AHRC. That complaint can result in conciliation, and if unresolved, Federal Court proceedings. The landmark case is Maguire v SOCOG [2000], which established this principle over two decades ago.

What is the minimum WCAG level I need to meet in Australia?

For private sector businesses, there is no formally legislated minimum — the DDA does not specify a WCAG level in the statute. However, the AHRC's Advisory Notes recommend WCAG as the compliance standard, and WCAG 2.1 Level AA is the level adopted by all Australian government agencies under the Digital Service Standard. In any DDA complaint or litigation, WCAG 2.1 Level AA would almost certainly be the benchmark applied. Targeting Level AA is the appropriate goal for all Australian businesses. Level A alone would likely be insufficient to demonstrate reasonable compliance.

Does the DDA apply to websites built on platforms like Wix, Squarespace, or Shopify?

Yes. The DDA obligation attaches to the business operating the website, not the platform provider. If your Wix or Squarespace website is inaccessible, you bear the legal exposure — not Wix or Squarespace. Platform accessibility features reduce the effort required to achieve compliance, but they do not guarantee it. You are responsible for the content you publish, the theme you choose, the plugins you install, and the overall accessibility of the user experience your site delivers.

What are the most common accessibility failures on Australian small business websites?

Based on widely published audit data from WebAIM's annual survey of the top 1 million websites and anecdotal experience with Australian SMB sites, the most common failures are: (1) missing or inadequate alt text on images; (2) insufficient colour contrast between text and backgrounds; (3) missing form input labels; (4) no keyboard navigation support; (5) inaccessible PDFs (menus, price lists, brochures); (6) videos without captions; (7) missing page titles or duplicate page titles; and (8) content not reflowing correctly at mobile viewport widths. These are all fixable, and most can be addressed without a complete rebuild.

Can I use an accessibility overlay tool to achieve compliance?

No. Accessibility overlay tools — JavaScript plugins that claim to automatically fix WCAG issues — are not a reliable compliance mechanism and are not endorsed by the AHRC or disability advocacy organisations. Independent research and the testimonies of users with disabilities consistently show that overlays fail to correct the majority of WCAG failures and can actively worsen the experience for screen reader users. Using an overlay would not constitute a meaningful defence against a DDA complaint. Genuine WCAG compliance requires genuine implementation in the underlying code and content of your website.

How much does it cost to make my website accessible?

It depends entirely on the current state of your site and the platform it is built on. If you are building a new site, specifying WCAG 2.1 AA compliance from the outset adds minimal cost when done by a competent developer — often less than $500 in additional development time for a standard small business site. If you are retrofitting an existing site, a professional accessibility audit costs $800–$2,500 for a small site, and remediation can range from a few hundred dollars for minor fixes to $5,000+ if structural issues require rebuilding templates or themes. The cheapest path is always to build accessibly from the beginning.

Does my website need to be accessible if I only serve local customers face-to-face?

Yes. Even if your primary customer acquisition is through foot traffic or word of mouth, if your website is publicly accessible — meaning anyone can visit it — it is subject to the DDA. A customer with a disability who visits your website to find your opening hours, location, phone number, or prices and cannot access that information due to an accessibility barrier may have a valid complaint. The DDA does not require that your website be the primary or exclusive service delivery channel — it requires that the service you offer via the website be accessible to people with disabilities.

What is an accessibility statement and do I need one?

An accessibility statement is a page on your website that declares your commitment to accessibility, identifies the standard you are targeting (WCAG 2.1 Level AA), lists any known limitations, and provides contact details for users who encounter barriers. It is not a legal requirement for private sector Australian websites, but it is strongly recommended. It demonstrates good faith, helps users with disabilities know what to expect, and provides an accessible alternative pathway when automated solutions fall short. Government agencies are required to publish accessibility statements. Following this practice as a private business signals that you take your DDA obligations seriously.

A Note on Accessibility for Tradespeople and Service Businesses

It would be easy to assume that web accessibility is a concern only for large organisations with complex digital ecosystems. That assumption is wrong. A plumber's contact form that can't be submitted by keyboard. An electrician's service page with images of compliance certificates published as non-accessible JPEGs. A quote request form with unlabelled fields. These are real accessibility failures on real small business websites across Australia.

Tradies and service businesses — from electricians like APX Trade Group in Sydney through to sole-trader operators across every state — interact with customers online who may be elderly, have low vision, or rely on assistive technology. Building a website that works for all of them is not a significant technical challenge. It is a matter of knowing the requirements and implementing them correctly from the start.

Summary: What Australian Businesses Must Do

1. Understand that the Disability Discrimination Act 1992 applies to your website regardless of your business size or industry.
2. Target WCAG 2.1 Level AA as your compliance standard.
3. Conduct an initial accessibility audit using automated tools (Lighthouse, WAVE) supplemented by manual keyboard and screen reader testing.
4. Prioritise fixing the most common and highest-impact failures: alt text, colour contrast, form labels, keyboard navigation, and PDF accessibility.
5. Build accessibility into your content publishing process — not as a retrofit but as standard practice.
6. Publish an accessibility statement linked from your site footer.
7. Avoid accessibility overlay tools as a compliance strategy.
8. Engage ongoing maintenance to catch new accessibility issues introduced through content updates and plugin changes.

If you are building a new website or rebuilding an existing one, weauto builds professional, accessible websites for Australian small businesses from $99 + GST, delivered in 5 business days — with accessibility considerations built into every build.

Related reading

• Seo For Tradies How To Get Found On Google
• Website For Cleaning Business
• Plumber Website Cost