One does not have to be a government body to be subject to Disability Discrimination Act digital accessibility obligations in Australia. Come 2026, any public-facing digital service – from a SaaS platform or customer portal to an online form, mobile app or website – is open to censure if it puts up unlawful barriers for people with disability.
There is a simple way to view it: organisations must regard digital accessibility as a duty of the Disability Discrimination Act 1992 and make WCAG 2.2 Level AA their technical standard. See Australian accessibility compliance guidelines for practical context. Do not think the law is appeased by an accessibility statement or some other ostentatious compliance badge; the internet has little time for such things.
Rhys McDonald has put together this guide to set out the Australian position and what a sensible accessibility programme entails, including how complaints are handled and what one ought to be checking. It is offered as general information rather than legal advice, since particular obligations will hinge on the organisation, the contract, the service and the circumstances.
The DDA Explained
Under the terms of the 1992 Disability Discrimination Act, or DDA, discrimination is made illegal in much of public life. The Act is there to protect those who need to make use of screen magnification, speech recognition, captions, alternative input methods or assistive technology of some kind to get at information and services.
For an organisation, grasping the DDA has the advantage of forestalling exclusion before any complaint or court matter gets under way. Should one want to know more about rights and discrimination under the Act, the Australian Human Rights Commission (AHRC) has official resources on the subject: Australian Human Rights Commission disability rights information.
What is covered
In providing goods and services, the DDA is applicable. These may be delivered via a digital channel where the organisation takes payment, puts out information, fields applications or deals with customers.
That said, an inaccessible site is not per se unlawful in all cases. The facts of the matter will dictate the answer: was an unreasonable barrier in place, was the person with disability dealt with less favourably, could a reasonable adjustment be made or is there a lawful exception?
Discrimination, direct or indirect
A business that will not extend an online service to a user of a screen reader is guilty of direct discrimination. Indirect discrimination is another matter, coming about when a blanket requirement is unreasonably disadvantageous to those with disability. Make every customer fill in a digital form they cannot access and there is no alternative, and you have a problem.
Online rules of the DDA
It is the service on offer that brings DDA duties into play in Australia, not whether the company styles itself a technology firm. A software house, council, health provider, university, retailer or bank would do well to give accessibility some thought.
If an accessibility issue stands in the way of someone putting in an application, getting support or closing a transaction, the organisation can expect to deal with the operational and legal fallout.
Do not forget they are services
Put simply, a website is your booking counter, front desk and application office in one. An app might be used for identity checks, transport, payments and account access. The medium of a screen does not absolve an organisation of its responsibilities.
The whole of the customer journey should be accessible. It is no good having a homepage that works but leaving the PDF receipt or account recovery process off limits. You might as well put a ramp at the front gate and a staircase in the dunny.
Making a reasonable adjustment
This is about altering a process so a person with disability can avail himself of a service. Be it human assistance, captions, an accessible format for information or taking an application over the phone because the online form is not an option.
Such an adjustment needs to be done in a timely and practical fashion and without making the individual have to put his medical affairs on the table or rehash the same access requirement with staff.
WCAG 2.2
For the majority of Australian organisations in 2026, WCAG 2.2 Level AA is the place to start. The Web Content Accessibility Guidelines offer success criteria that can be tested to see if your digital content is indeed usable for people with disability. WCAG is a matter of technical standards; the DDA is the law. One can lower risk and have a definitive target for development by conforming to the WCAG 2.2 Level AA in Australia, yet that is no shield against legal action. On the other hand, if there is a breach of a technical criterion it ought to be put in its proper context and not viewed as an open and shut case in court.
The Case for Level AA
Level A takes care of the basics. With Level AA you get controls that make a difference to access for a great many users, from those requiring captions and keyboard use to ones who need good colour contrast, focus indicators they can use and a navigation scheme they can rely on.
It is advisable for an organisation to put the target down in writing and make it part of the project brief, then test accordingly. Put off accessibility to the last week and one is likely to end up with costly rework and contrivances, not to mention a meeting an email would have sufficed for.
What WCAG Does Not Cover
For the most part WCAG is about web content and the like. But some software, devices and products will call for an eye to EN 301 549, what the procurement demands, sector obligations or platform guidance.
And while an automated tool will spot a missing label or a structural defect, it cannot tell you if the instructions are comprehensible or the journey is logical. So where one can, testing should be done with assistive technology and actual people.
Digital Services in Scope
Any digital service made available to the public be they customers, students, patients, staff or members of the community may fall under Australian requirements. Do not assume the main website is the only thing of consequence; map the service. That could mean mobile apps, SaaS, a customer portal, online booking, social media, kiosks, AI or any number of connected products. Even content from a contractor or third party can present a legal exposure.
Touchpoints to Consider
One must look at every instance where a person has to put in information, read it, follow directions or work a control. Menus, search, forms, authentication, payment, video, chat, error messages and account management all come into play.
With a mobile app in Australia both operating systems are to be covered. The native app may be different in kind from the site but the user wants the same result: to do the job on his own or have an alternative that works.
Dealing with Documents and Others
A PDF or spreadsheet, a scanned letter or application form can be a formidable barrier. There is no point in an accessible website if it sends the user to an inaccessible document and he is left there.
The same applies to third parties such as recruitment platforms, video hosts or payment screens. The contract should be explicit on testing and how defects are to be handled, and what the recourse is if the supplier is slow to act.
Duties of Government
Agencies of the Australian Government are bound by formal expectations in procurement and digital service. The Digital Service Standard and the ICT Procurement Standard are there to see that accessibility, security and quality are factored in.
But a government team should also think of the older device, the poor connection, the person with limited confidence in the digital realm or a disability. For a federal department it is more than a box to tick in the name of compliance; it is how a public service is delivered.
Evidence in Procurement
When agencies are procuring, a supplier’s word that something is “accessible” is not enough. Require the conformance report, the test results, any limitations and a plan for remediation, and evidence of testing with assistive tech. Make sure the standard and the release gates are defined in the paperwork; once the system is in production it is hard to demand repairs if the contract is ambiguous on the matter.
Real World Design
Involve people with disability in the review and design of a service. A page can be compliant on paper and still be a hindrance to the task at hand. Run through the usual scenarios – an emergency, a licence renewal, an application for help. Clear headings and plain English are of benefit to all.
Compliance for the Private Sector
For private business in Australia this is an operational duty that does not go away. A small concern can put in place a process for reporting barriers and respond to them in short order; it may be able to make headway by concentrating on the high-impact journeys first. A bigger entity will require audits, design standards and training. In either case the customer is no less due a service that is usable.
Put the customer’s priorities first: whether it is to put in an order, book something, open an account, file a complaint or get in touch with support, or simply to see when you are open. These are the journeys to be tested from end to end and nothing but a keyboard and browser zoom (as the case may be) and a screen reader should be employed in doing so.
I was reminded of this when I set about making online guides from my handwritten route notes; one can have a page that is all neatness and yet be exasperating to put to use. Vague link labels, a form that will not hold what has been put in or an absent heading are enough to make a two-minute affair into a bush track.
Workflows must have accessibility at their core
For content teams that means employing captions on video of consequence, alternative text for any image that conveys information, headings and link text that are descriptive. On the developer side there is the matter of form labels, error messages, semantic structure and the management of focus and the keyboard.
As for managers, ownership has to be allocated. In principle everyone will back accessibility but if no one is responsible for the defect queue, the budget, the testing timetable or how the customer is dealt with, then it will not work.
Legal and business risk
Non-compliance in digital accessibility has its costs in the way of legal exposure, harm to your reputation, sales forgone, procurement issues and support expenses that need not be incurred. It is also a barrier to people who require certain information at the time they do.
A complaint is not of itself a DDA breach on the part of the organisation, but it does call for a respectful response and a close investigation with the relevant records in hand, not a defensive one.
The escalation of complaints
An individual might come to the organisation with the grievance or lodge it with the Australian Human Rights Commission. The AHRC can bring the parties to conciliation in an attempt to settle things short of a court appearance. Should that not happen, the Federal Court is an option in the right circumstances; what transpires is a function of the law, the evidence and the facts. Legal counsel is advisable upon receipt of a formal complaint.
Reality and expectation
It is expected that an accessibility widget will put a website to rights. In fact an overlay will only go so far in accommodating some preferences, it is no substitute for proper testing, unambiguous content, captions, the right keyboard behaviour and an accessible structure. One might think accessibility is of concern to a few, but those with a broken mouse, poor connection, bright sun or age related impediments and the like will find accessible design of benefit as well.
Checking And Improving Access
To get a handle on access and improve it, a good audit will provide an organisation with a baseline and proof of reasonable steps having been taken. It looks at technical conformance and if a user can in practice get his important tasks done.
For Australia digital accessibility compliance a compact checklist such as the following is a sound place to start:
- Make an inventory of the websites, portals, apps, documents, third party tools and the like used in customer communications.
- Where appropriate have a written WCAG 2.2 Level AA target in place.
- See to it that there is adequate contrast, zoom, error recovery, test the headings, labels and the order of focus and the keyboard.
- Do the same with assistive technology and disabled users.
- Give precedence to any barriers which impede many users or essential functions.
- While you are addressing defects put out a contact method and alternatives that will work.
- And keep a record of the owners, remediation dates, limitations and what the tests show.
Testing plan based on risk
There is value in automated testing to put your finger on recurring defects in short order. But for task completion, language and focus behaviour a manual approach is required; user testing will turn up what a technical scan would overlook. And after a new template for the content management system, analytics tool, cookie banner or checkout is put in place, retest. What was acceptable half a year ago may not be now.
The Biggest Barriers Should Be Your Priority
| Area | What To Check | Why It Matters |
|---|---|---|
| Navigation | Keyboard use, headings and landmarks, menus that are consistent | A user should not have to rely on a mouse to get around the service |
| Forms | Labels, instructions for required fields, error messages of some utility | So people can put right any mistakes they make |
| Content | Accessible documents, captions, text alternatives and plain language | Information has to be presented in more than one sensory format |
| Mobile | Zoom, touch targets, orientation and screen reader gestures | The small screen and its controls are a barrier of a different kind |
| Support | Alternative channels, response times and contact details that can be seen | Help is needed when there are defects to be put to rights |
Compliance That Is Practical
When time is short, say you have a day, put first the customer journey whose failure does the most damage. Whether it is an essential application, account access, payment or booking, test it by hand and if you can have someone with a disability put it through its paces. Deal with the blockers and leave the cosmetic matters for later.
For an organisation in search of a defensible and user-centric process this is the way to go. But do not make of it a once-only exercise or a stand-in for legal counsel in the event of a contract dispute, a complaint or serious exclusion.
Evidence And Ownership
Have a register in place to document the retest result, target date, owner, severity and which users are affected by each barrier. Make sure accessibility is part of your staff training, release checklists, design briefs and agreements with suppliers.
There is no point in claiming perfection as a measure of good compliance. What it comes down to is recognising barriers and doing something about them, putting in place support and demonstrating that the whole service lifecycle is conducted with accessibility in mind.
Frequently Asked Questions
The following are put forward as practical guidance, not a legal opinion, to clear up some of the confusion over the 2026 Australian web accessibility laws; the facts will dictate the position.
What Are The New Laws On The Internet In Australia?
Do not think there is a new law to take the DDA’s place for digital accessibility. The Disability Discrimination Act 1992 is what organisations have to look at, together with any rules from the privacy, consumer, communications or procurement side of things. As requirements evolve, it is wise to verify what applies to your industry and service.
Is The DDA Applicable To Websites And Apps In Australia?
In some cases it is. Where a website or app puts goods or information before the public and in doing so erects a disability-related barrier, the DDA can come into play. One has to consider the service and the user’s situation, whether adjustments are possible and if an exception is in order.
Which Standard Do You Use For Accessibility In Australia?
WCAG is the technical reference of choice for a number of projects. WCAG 2.2 Level AA is a sensible goal for most, though the Digital Service Standard, EN 301 549 or the ICT Procurement Standard may be called for in government procurement or with certain products.
Are You Required To Meet WCAG 2.2 Level AA In Australia?
Not in the sense of a blanket rule for every site. It is a benchmark in common use but the law and the circumstances are what create obligations. Then again, a government policy or contract could make specific WCAG adherence mandatory.
Can There Be A Complaint Over An Inaccessible Website?
Certainly. The user can put the matter to the organisation or the Australian Human Rights Commission. While conciliation might settle it, there are legal ramifications if it does not. An organisation would do well to act quickly and sort out an alternative while remediation is being done.
Make Access The Norm
One does not need to make a special case of DDA 1992 compliance for a website. Handle it as you would any question of service quality: reliable support, testing, content that is clear and controls that work. The DDA is about equal access for people and WCAG 2.2 Level AA provides the teams with a technical steer.
A modest and steady approach is best. Get to know the service and your users, remove what stands in the way of an essential task, hold suppliers to account and put on record the improvements. In that manner the guidelines for Australian accessibility become routine and not just another paper left to collect dust next to the billy.