One does not have to be a technician to see that digital accessibility under the Disability Discrimination Act is no niche matter. The reality for organisations in Australia is they are required to make reasonable provision so those with a disability can use their online services, be it an app, website, form or booking system. The fact a service is now online does not negate the terms of the 1992 Act.
The Act will not hand you a universal checklist for your site nor dictate which version of WCAG has to be followed. Yet the Web Content Accessibility Guidelines are the technical standard of choice for mitigating discrimination risk and opening up access. For practical guidance, see Australian website accessibility guidelines. For a proper grounding on the 1992 Act one should consult the Australian Human Rights Commission.
In this guide Rhys Parker lays out the legal landscape in Australia and what WCAG entails in the real world. He covers where organisations tend to stumble and how to put together a process for digital accessibility that will stand up in 2026. There is no legal obfuscation here and no suggestion an automated scan is a panacea.
Digital Rights Under Australian Law
By way of the Disability Discrimination Act, people are shielded from discrimination on account of disability in employment, education, accommodation and when it comes to goods and services. An application or website is often the means by which a customer will get in touch with an organisation, make a payment or book in; in that sense the digital service is part of the goods and services on offer.
Consequently if a site is not amenable to a screen reader, makes a nuisance of keyboard users or relegates key information to colour alone, a person may find he cannot do what another customer can. That is not some ornament of digital inclusion but a question of independent participation.
Who Requires Digital Access?
Assistive technology is employed in its many forms by people with disability: from screen magnification and readers to speech recognition, switch devices and alternative keyboards. Some will require more time to get through an online task or want transcripts and captions and plain language.
Then there are the statistics. In Australia about a fifth of the population have a disability, hardly an edge case. And that does not account for situational impediments like bad internet, an eye problem or a broken arm.
What the DDA Demands of a Website
You will not find a line in the Disability Discrimination Act to the effect that all Australian sites must be in conformance with WCAG 2.2 AA. The law is concerned with whether the service is usable and if the organisation has done what is reasonable to stave off discrimination.
An automated checker can give a false sense of security while barriers remain. Or an organisation might have a few defects it is addressing in a risk-based fashion. Compliance is a matter of conduct and making the necessary adjustments, not putting a PDF certificate on the wall.
Online Services
When a charity, school, health provider, government or private enterprise puts essential services online and the channel is not accessible, complaints are likely. Be it for banking, ticketing, shopping or to put in an application. If an inaccessible form is the only option to register or lodge a complaint, a person with disability is put at a distinct disadvantage and the risk to the organisation is greater.
The Duty to Make Reasonable Adjustments
To allow for participation a process or service is altered. This could mean extending a deadline, having staff on hand to help while a site is being put right, or taking a phone application. It is not unreasonable simply because it is costly or adds to the administration. One has to weigh the cost and resources against the barrier and the adjustment’s efficacy. Unjustifiable hardship is a legal concept but it is not an excuse to be lax on accessibility.
Some Guidance for Australia
The W3C’s Web Content Accessibility Guidelines are where any business would do well to start. They set out success criteria for content that is robust, operable and easy to understand. While WCAG is not an Act of Parliament in this country, it is a sound technical standard for giving practical shape to anti-discrimination obligations. WCAG 2.2 Level AA is a target of which many organisations make sensible current use, with the understanding that one’s legal duties are circumstantial.
The Four Core Accessibility Principles
Content must be perceivable: provide captions on video, enough colour contrast and text for images of substance so users can take in the information. Interfaces should be operable by all, with keyboard navigation among the input methods available. As for being understandable, there is to be no ambiguity in the instructions or behaviour; error messages are to be of some use and navigation consistent. Robustness means the content will stand up to assistive technology as well as any browser or mobile device. One might think these are technicalities until a customer is at an impasse on a payment screen over an error message he cannot access. At that point they are very human indeed.
WCAG Versions And Targets
In the course of accessibility audits, policy making and procurement one will still see WCAG 2.1 cited with frequency. Version 2.2 has refinements to offer, success criteria for better focus appearance, accessible authentication and alternatives to dragging for instance.
It is something an organisation ought to put on record as to what conformance level and version it is after. Telling a developer or a customer “we adhere to WCAG” does not inspire confidence. A proper statement will name the standard and the level, note any exceptions and how testing is done and give a way to report any barriers.
WCAG And The DDA
Separate out the roles and the link between WCAG 2.2 and the Disability Discrimination Act is plain. The DDA is the source of the wide ranging legal requirement, WCAG the technical means to find and put an end to digital obstacles.
Compliance with Level AA may be put forward as evidence of reasonable steps but it is no shield from the law. Then there is the matter of the content itself, third-party systems, documents, the conduct of mobile devices and whether a person can see a task through from beginning to end.
| Area | What To Check | Why It Matters |
|---|---|---|
| Keyboard access | Menus, pop-ups and the like function without a mouse, for the benefit of those with motor impairments or who use assistive technology. | Supports people with motor disabilities and many assistive technology users |
| Screen readers | Blind or low-vision users need to be able to make sense of the page and operate it, so headings, labels and status must be right. | Helps blind and low-vision users understand and operate the page |
| Colour and contrast | So as to be distinguishable to someone with a colour vision deficiency, text and graphics have to be clear. | Reduces barriers for people with low vision or colour vision deficiency |
| Forms | Leave no room for doubt in required fields or errors so as not to put a stop to a booking or application. | Prevents users being blocked during applications, payments and bookings |
| Media and documents | Do not let important PDFs or videos without captions keep essential information in a format of one kind only. | Ensures essential information is not locked into one format |
What Organisations Need
To be in compliance with the DDA a website has to be looked at in its entirety, the homepage is not enough. All the world and an accessible front page will not save you if the customer is thwarted by a payment gateway or form at the next turn. Put yourself in the position of the user: can he locate the service, put in his particulars, put right any mistakes, make the payment and get in touch if something goes wrong?
Barriers That Should Be Dealt With
There are all too common issues: no alt text, CAPTCHA that is not accessible, links of the “read more” variety, time limits, poor visibility of focus, headings put there for looks, flashing, low contrast or unlabeled form fields. A scanned PDF is beyond a screen reader.
Do not neglect the mobile side either. Responsive design is not the same as accessible design for all the marketing copy would have you believe; zooming can make things run together and cramped controls are a problem even if the desktop keyboard works fine.
Risks In Third-Party Tech
An external supplier may run your chat tool or document system but the responsibility for the service is yours. Make sure contracts have the necessary provisions for testing, remediation and escalation. I have seen teams go over a new platform and the cost is not what comes as a shock, it is to find the system will not show a status update to a screen reader or properly label a field. Best to ascertain such limitations before you have signed and the launch is upon you.
Auditing
An audit will supply an organisation with the facts on barriers, provided the approach is sound. Automated tools will pick up on missing labels or a structural defect but they are not to be trusted to tell you if a process is befudding or if the user can get the job done with a screen reader. Have someone with a disability and experience of the technology put the site through its paces. Let them try to find a service and then recover from an error. You will see where it breaks down.
A Process Based On Risk
Make a start on the journeys that have the most impact: from account set up and applications to payments, scheduling an appointment, lodging a complaint or accessing emergency information. For every issue put down on record note the owner who will see to it, what it means for the user, the fix in prospect and when retesting is due.
Barriers of any kind that impede completion, put private data at risk, compromise safety or are part of essential services must be given priority. A matter of cosmetic spacing can be left for later. But do not relegate a payment form unusable by keyboard users to the “one day” drawer with the rest of the mystery cables.
Delivery should have accessibility built in
From procurement and content planning through to design review, development, QA and release management, make room for it. Have developers put the site to the test with an accessibility tree and keyboard only; let content teams employ plain language, links that are descriptive and headings that mean something.
An accessibility statement is needed to lay out the organisation’s aims, how to complain, any limitations you are aware of and an alternative way to get in touch. See that it is reviewed as the service evolves. There is little point in having a statement if it is out of date, it conveys a false sense of confidence in an experience that is not there.
The legal side of complaints
In Australia a website that is not accessible can be the subject of a complaint if disability barriers stand in the way of equal access to one’s goods or services. This may be done with the organisation itself, via the Australian Human Rights Commission or some other dispute process as circumstances dictate.
A prompt and practical response is the way to go. It is no defence to say the site is technically modern when it cannot be used. Find out what was put in the way of the person, put forward an accessible option on the spot, put aside the evidence and make a plan for remediation that is realistic.
What tends to be overlooked
Accessibility is too often regarded as a project for launch day. Yet defects will be reintroduced when a supplier alters a form component or marketing puts in an unlabelled pop-up or an editor uploads a PDF that is not accessible. Nor does a single scan make for full compliance. You have to evaluate against your WCAG criteria of choice and even then there are legal questions it will not settle. Be forthright on what has been tested and what is still a work in progress.
2026 Compliance Checklist
For those looking for a place to begin with digital accessibility in Australia this checklist is of use. Not to be taken as legal advice, it serves to make broad intentions into work that can be held to account.
- Put all public facing material on the table: websites, apps, third party services, forms, video and documents.
- Select a target level and WCAG version and document why.
- Run critical user journeys past screen readers, mobile and keyboard navigation.
- Combine manual testing with people with disability and automated scans.
- Where support, payments or applications are concerned, remove the barriers. In the meantime an accessible substitute should be offered.
- There is training to be had for customer service as well as the writers, editors, designers and procurement staff.
- Your statement of accessibility should be published with a contact method that works. Make sure contracts with suppliers and acceptance testing have the right terms.
- And after a major release retest, leaving a trail of the decisions made and the remediation.
Planning in a sensible manner
Should time be limited to a day, put your efforts into the three principal customer journeys in preference to going over every page. The homepage, search, the main form, a payment, the confirmation and how one makes contact are where you will want to be. It is better evidence than a spreadsheet of such size as to be never opened again. While accessibility is something any organisation should be doing, a complex service is no place for a one-man beginner’s project. A small business might put in hand to a well-defined audit and some unambiguous alternatives; for the bigger organisations it means having ownership of the matter spread over customer service, legal, procurement, content and technology.
One has to make allowances for supplier delays, retesting and the time needed to put things right. A simple matter of correcting content is done in minutes, but an inaccessible booking system could be months to replace. Put down in the budget for remediation, staff training and user testing as well as an expert review, do not have the whole of it go on an audit report.
Frequently Asked Questions
Is The DDA Applicable To Websites?
The Disability Discrimination Act 1992 will apply to a website or digital service if it is in the business of providing information, goods or services. How that is determined in law is a function of the circumstances, the barrier and the organisation in question.
What Is Required Of A Website?
For an Australian organisation there is an onus to have accessible digital services and to make reasonable adjustments. WCAG is the technical framework of choice for most, yet the DDA does not hand out a uniform checklist for all websites.
Are You Legally Bound By WCAG?
Not as such, the DDA is not generally WCAG. It can be called for under a contract or sector obligation, or by way of policy, and serves as evidence of good practice. But the facts of the service are what dictate legal duties.
Which Level Of WCAG?
WCAG Level AA is the usual target from a practical standpoint, covering a wide array of barriers without insisting on every optional enhancement. One should have the scope, version, exceptions and how testing is to be done on record.
Making A Website Compliant
This involves mapping out the important user journeys and putting them through an automated and manual audit, using assistive technology to test, then retesting once the high-risk barriers have been fixed and alternatives put in place. An accessibility statement should be in order and the work treated as part of normal operations.
Can There Be A Complaint?
A person is within his rights to take up an issue with the organisation or file a complaint with the Australian Human Rights Commission for instance. A prompt response and a usable alternative will mitigate the harm if nothing else, though the obligation remains.
The Australian Standard
Do not look for an “Australian website standard” in lieu of the DDA. In the course of a project or per the contract, WCAG 2.1 or 2.2 will be the practical reference for assessing digital accessibility.
DDA Versus WCAG
The former is anti-discrimination law in Australia, the latter a W3C technical standard. The DDA lays out the responsibility, WCAG is how an organisation goes about measuring the technical side of it.
Service And Accessibility
At the end of the day, the point of the Disability Discrimination Act in Australia is to let people use a service in an independent and dignified fashion. WCAG 2.2 AA is a fine goal but you need responsible follow-through, accessible content and customer support to be in true compliance.
If one wants to be accessible in 2026 in a way that is measurable and not so rough for everyone, the sensible thing is to focus on the journeys of consequence, have real people do the testing, remove what stands in the way of completion and keep your records.