Guide

Web Accessibility for Australian Businesses: A Complete Guide

A practical guide to web accessibility for Australian organisations: what it is, why it matters, your obligations under the DDA, and how to make progress.

Skip to contents

Web Accessibility for Australian Businesses: A Complete Guide

Everything Australian organisations need to understand about web accessibility — obligations, benefits and practical next steps.

What is web accessibility?

Web accessibility means designing and building websites, apps and digital documents so people with disability can perceive, understand, navigate and interact with them. It covers a wide range of disabilities, including visual, auditory, physical, speech, cognitive and neurological disabilities.

In practice, accessibility is about removing barriers. Examples include:

  • Ensuring screen reader users can navigate with headings, landmarks and meaningful link text
  • Providing sufficient colour contrast and text resizing for people with low vision
  • Making all functionality available via keyboard for people who cannot use a mouse
  • Providing captions, transcripts and audio descriptions for people who are Deaf or hard of hearing
  • Avoiding content and interactions that can trigger seizures or disorientation

Accessible design is not a separate layer you add at the end. It is a way of working that influences research, design, content, development and testing.

Why accessibility matters in Australia

1. People and inclusion

  • Around one in five Australians live with disability (ABS 2022 SDAC).
  • Many more experience temporary or situational impairments: a broken arm, glare on a mobile screen, or trying to watch video in a noisy environment.
  • As the population ages, more people will rely on accessible digital services to participate fully in work, education and community life.

When your digital products are inaccessible, you are effectively closing the door on a large part of your potential audience.

In Australia, digital accessibility is primarily a discrimination issue, not a technical one.

  • The Disability Discrimination Act 1992 (DDA) makes it unlawful to discriminate on the basis of disability in the provision of goods, services and facilities.
  • This has applied to websites and digital services since the landmark Maguire v SOCOG (2000) case, where the Sydney Olympic Games website was found to be unlawfully inaccessible to a blind user.
  • Complaints under the DDA can be made to the Australian Human Rights Commission (AHRC), and may lead to conciliation, enforceable undertakings or, in some cases, Federal Court action.

Government bodies and publicly funded organisations often have additional obligations, such as:

  • Whole-of-government digital service standards and accessibility policies
  • Procurement rules requiring WCAG conformance for purchased systems
  • Sector-specific regulations (for example, in education, transport or banking) that reference accessibility.

3. Business benefits

Beyond compliance, accessibility delivers tangible benefits:

  • Larger audience and market reach – more people can use and complete key tasks on your site.
  • Better user experience for everyone – clearer content, predictable navigation and robust interactions help all users, not just people with disability.
  • Improved SEO and performance – semantic HTML, text alternatives and fast, well-structured pages are rewarded by search engines.
  • Reduced support costs – fewer users get stuck or need to call for help.
  • Stronger brand and reputation – demonstrating inclusion and social responsibility builds trust with customers, staff and regulators.

The standard: WCAG 2.2 Level AA

Most Australian organisations use the Web Content Accessibility Guidelines (WCAG) as the benchmark for accessibility.

  • WCAG 2.2 is the current version of the standard.
  • Level AA is the level most commonly referenced in Australian government policy, procurement and international legislation.

WCAG is organised around four principles. Content must be:

  1. Perceivable – information and user interface components must be presented in ways users can perceive (for example, text alternatives for images, captions for video, sufficient contrast).
  2. Operable – users must be able to operate the interface (for example, keyboard access, enough time to read and use content, no content that causes seizures).
  3. Understandable – information and operation of the interface must be understandable (for example, clear language, predictable navigation, helpful error messages).
  4. Robust – content must be robust enough to work reliably with current and future user agents, including assistive technologies.

WCAG is technology-agnostic. It applies to websites, web apps, intranets, extranets and many mobile experiences that use web technologies.

What web accessibility covers

Accessibility touches every part of your digital presence:

  • Code and structure – semantic HTML, headings, landmarks, form labels, focus order, ARIA where appropriate.
  • Visual design – colour contrast, text size and spacing, responsive layouts, focus indicators, avoiding relying on colour alone.
  • Content and copy – clear language, descriptive link text, meaningful headings, logical content structure, accessible documents.
  • Media – captions, transcripts, audio descriptions, accessible media players.
  • Interaction design – keyboard and switch access, clear states and feedback, avoiding complex gestures or time-limited tasks.
  • Documents and downloads – accessible PDFs, Word, PowerPoint and other formats, or providing accessible HTML alternatives.

Where Australian organisations should start

Most teams find it helpful to treat accessibility as a program of work, not a one-off project.

1. Get a clear picture of your current state

Begin with an accessibility review of your key digital products:

  • Identify critical user journeys (for example, sign-up, login, search, checkout, application forms, booking flows).
  • Assess these journeys against WCAG 2.2 Level AA.
  • Include both expert evaluation and user testing with people with disability where possible.

The outcome should be a prioritised list of issues, grouped by:

  • Severity – how badly the issue blocks or hinders users
  • Reach – how many users are likely to be affected
  • Legal risk – whether the issue creates a clear barrier to access under the DDA

2. Fix the most important journeys first

Focus on:

  • High-traffic, high-value tasks (for example, payments, applications, bookings, account management)
  • Content and services that are essential for compliance, safety or entitlements

Addressing these areas first reduces both user impact and legal exposure while building internal capability.

3. Embed accessibility into your delivery process

To make progress sustainable:

  • Add accessibility criteria to design and development checklists
  • Include accessibility acceptance criteria in user stories and definition of done
  • Integrate automated checks into your CI/CD pipeline, while recognising they only catch a subset of issues
  • Provide training for designers, developers, content authors and product owners
  • Update procurement processes to require WCAG 2.2 AA conformance for third-party tools and platforms

4. Plan for ongoing governance

Accessibility is not “set and forget”. New content, features and campaigns can introduce new barriers.

Establish:

  • A clear accessibility policy and ownership
  • Regular audits of key journeys
  • A way for users to report accessibility issues and get support
  • Metrics and reporting to track progress over time

Accessibility and different types of disability

Your users may:

  • Use screen readers, screen magnifiers or braille displays
  • Navigate entirely by keyboard, switch device or voice control
  • Need captions, transcripts or visual cues instead of audio
  • Rely on simple language, consistent layouts and clear instructions
  • Be sensitive to motion, flashing content or cluttered interfaces

Designing with these needs in mind leads to interfaces that are more resilient and easier to use for everyone.

Accessibility beyond websites

In Australia, the same principles apply across your digital ecosystem:

  • Websites and web apps – public sites, portals, intranets, extranets
  • Native mobile apps – using platform accessibility APIs and guidelines
  • Documents – PDFs, Word, PowerPoint and other formats
  • Kiosks and terminals – ticketing, check-in, self-service devices
  • Emails and marketing campaigns – templates, images, headings, links

If a digital channel is part of how you provide goods, services or information, it is likely to be in scope of the DDA.

Practical next steps for Australian organisations

  1. Identify your priority products and services – which websites, apps and documents are most important for customers and most exposed legally.
  2. Commission an accessibility review – focusing on WCAG 2.2 Level AA and real user journeys.
  3. Create a remediation roadmap – with clear owners, timelines and success measures.
  4. Train your teams – so designers, developers and content authors can prevent new issues.
  5. Update policies and procurement – to embed accessibility requirements into how you buy and build.
  6. Engage people with disability – in research, co-design and testing.

Accessibility is an ongoing commitment, but each improvement you make opens your services to more people and reduces risk.

Web accessibility for Australian organisations

Web accessibility is the practice of designing and building digital products so people with disability can perceive, understand, navigate and interact with them. In Australia, it is not optional: it is how you ensure a substantial part of your potential audience can actually use what you have built.

According to the Australian Bureau of Statistics 2022 Survey of Disability, Ageing and Carers (SDAC), 5.5 million Australians — 21.4% of the population, more than one in five — live with disability. When digital products are not accessible, those people encounter barriers that can prevent them from completing transactions, accessing services, reading important information or participating in what your organisation offers. In most cases, they simply leave.

This guide explains what accessibility means in practice, why it matters commercially and legally, what your obligations are under Australian law, and how to make practical progress.

---

What web accessibility actually means

Accessibility is not just a checklist; it is about people and their real tasks:

  • A person who is blind can complete a purchase using a screen reader.
  • A person with low vision can read your content using browser text scaling.
  • A person with a motor disability can navigate your site entirely by keyboard.
  • A person who is deaf can access the information in your video through captions.
  • A person with a cognitive disability can understand your forms and recover from mistakes without frustration.

The internationally recognised standard for digital accessibility is the Web Content Accessibility Guidelines (WCAG), currently at version 2.2. WCAG is organised around four principles: content must be perceivable, operable, understandable and robust. It defines three levels of conformance — A, AA and AAA — with Level AA being the level most Australian organisations, regulators and procurement requirements point to.

Meeting WCAG 2.2 Level AA does not guarantee a perfect experience for every user, but it removes the most common and significant barriers and provides a defensible, evidence-based demonstration that you have taken your obligations seriously.

Accessibility is also not binary; it exists on a spectrum. Organisations that have done nothing are at genuine risk. Organisations that are making systematic progress, and can demonstrate that progress, are in a materially better position than those that are not.

---

Why accessibility matters for Australian organisations

Your customers

The ABS 2022 SDAC reports that 5.5 million Australians live with disability. This does not include the millions more who experience temporary impairments (such as a broken arm or recovery from surgery), situational constraints (such as bright sunlight or a noisy environment), or older Australians whose vision, hearing and motor function have declined with age.

The overlap between accessibility and general usability is substantial: when you fix an accessibility barrier, you almost always improve the experience for a much wider group.

From a business perspective, inaccessible digital products exclude customers who are ready and willing to transact. They rarely complain; they simply go elsewhere and tend not to return. Accessible products capture that audience.

The Disability Discrimination Act 1992 (DDA) makes it unlawful to discriminate against a person on the basis of disability in the provision of goods, services and facilities. Since the landmark case of Maguire v SOCOG (2000), the DDA has been applied to digital services.

In that case, the Human Rights and Equal Opportunity Commission found that the Sydney 2000 Olympics website discriminated against Bruce Maguire, a blind man, by failing to provide accessible content. SOCOG was ordered to remediate its site and ultimately to pay Maguire $20,000 in damages.

More recently, in Innes v State of Queensland (Queensland Health) [2018] FCCA 2763, the Federal Circuit Court ordered Queensland Health to pay $10,000 in damages and make its website accessible after Graeme Innes — a former Disability Discrimination Commissioner — successfully argued that inaccessible documents on the site constituted unlawful discrimination.

These cases establish that digital accessibility is within the DDA’s scope. Australian government bodies are also generally required to meet WCAG standards under Commonwealth and state government policies.

For organisations expanding overseas, equivalent obligations apply:

  • UK: Equality Act 2010 and Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 (PSBAR).
  • US: Americans with Disabilities Act (ADA), under which over 3,100 federal web accessibility lawsuits were filed in 2025 alone (Seyfarth Shaw).

Your reputation and staff

Organisations that are visibly committed to accessibility are increasingly favoured by:

  • Customers who value inclusion.
  • Staff who want to work somewhere with a genuine social conscience.
  • Partners and clients who make accessibility a procurement requirement.

The reputational cost of being publicly called out for an inaccessible digital product is disproportionate, particularly when the underlying issues are preventable.

---

How to make practical progress

Accessibility is not a one-off project with a finish line. Organisations that do it well treat it as an ongoing capability built into how they design, build and maintain digital products.

A sensible starting point typically involves five steps:

  1. Understand where you are today
  2. Identify your highest-priority user journeys
  3. Bring people with lived experience of disability into your testing
  4. Establish clear accessibility requirements for future work
  5. Monitor accessibility over time

IncluD supports each of these steps:

  • IncluD Verify – expert accessibility reviews and audits.
  • IncluD Lived – testing with people with lived experience of disability.
  • IncluD Monitor – ongoing monitoring of accessibility over time.
  • IncluD CoLab – practical advisory support embedded in your delivery teams.

If you are unsure where to begin, a readiness conversation with the IncluD team is a practical first step.

---

Frequently asked questions