In essence, the Disability Discrimination Act (DDA) is simple: those with a disability are to have the same online access to goods and services as anyone else. But the 1992 legislation reaches well beyond what one might see in a marketing plan or contract; it has bearing on any public-facing technology, be it a website, mobile app, software, email, cloud service or digital kiosk.
For Australian government and commercial entities, digital accessibility is an operational and customer-service duty as much as a legal one. While WCAG 2.2 Level AA makes for a sound technical standard, ticking the boxes will not of itself insulate an organisation from DDA risk. What matters is if the service can be used with comparable independence, with assistive technology and any reasonable adjustments called for. For a practical overview, see Australia’s website accessibility guidelines.
Rose Dunstan puts practical compliance into plain English in this guide to the law, the risks and the technology, and the course of action open to organisations in 2026. For all that an inaccessible digital service may not be as conspicuous as a lift out of order, it can leave a person just as stranded.
The Requirements of the Disability Discrimination Act
Under the 1992 Act, discrimination on the basis of disability is forbidden in the provision of goods and services. Since digital channels are the means by which most of these are purchased, booked, supported or managed, equal access is the result. One should not have to make a phone call, visit a store or put in a request for assistance because an organisation’s online offering is not compatible with their disability.
Equal Access at its Core
An anti-discrimination law rather than a technology standard, the DDA will look to see if a person has been put at an unreasonable disadvantage or treated less favourably. A blind individual who cannot put through an online payment, a Deaf person for whom a video is incomprehensible without captions, or someone whose dexterity is limited and cannot work a form with a keyboard or switch are cases in point. The provider may be obliged to effect a reasonable adjustment, whether that is to alter a form, put forward accessible documents or put right a process that is an impediment.
When Hardship Is Unjustifiable
There is room in the DDA for unjustifiable hardship but do not mistake this for a licence to have an inaccessible service. It is not enough to say the legacy platform is hard to change or that there is a cost to remediation. A proper assessment of the factors at play, including the resources of the organisation and the impact on those concerned, is preferable to a shrug and the hope of going unobserved.
Digital Services and Products in Scope
Obligations in Australia extend past the corporate homepage. Any technology in a public-facing service ought to be part of an accessibility risk assessment. It is what the service does and its use by the public that is relevant, not whether it was procured from a supplier, put in the cloud or made in house.
Technologies commonly in scope
Websites, apps, online shops, customer portals, booking systems, AI platforms, digital kiosks, information screens, emails and digital documents are all potentially covered. Particular care is warranted with complaint forms, learning or appointment systems, registration and payment pages since a problem at any point can cut off access to the whole service.
Responsibility is not ceded to a third party. Should a business go with a certain payment or CRM system, the onus is on them to see that the product is amenable to accessible use and that the contract has provisions for putting defects right.
Public and Internal
While the risk is most apparent in public-facing services, internal tools at the workplace can present disability discrimination issues. An employee or applicant using a recruitment portal, payroll or training platform may be affected. The question to ask is not whether the system is in public view but whether the user can get on with it free of a disability-related barrier. Such internal access needs to be viewed in the context of inclusive employment and workplace adjustments.
Websites, apps and the information they hold: a question of law
Do not make of websites and mobile applications mere decoration; they are service delivery channels. When a customer has to go to one in order to put in an order, book something, get at some information or run his account, any lapse in accessibility is a failure of service.
The guidelines for website accessibility in Australia are to be seen as sound advice on how to provide equal access, not some talisman that will ward off all manner of complaint. An automated scan may show a site in the clear but it could be a poor experience for the user in the end.
Barriers you are likely to come across
There are a number of familiar culprits: no alternative text, colour contrast that is substandard, PDFs that cannot be accessed, form fields without labels, error messages that do not make sense, content in motion, authentication issues, videos with neither captions nor transcripts and keyboard traps.
With a mobile app there can be more in the way of trouble. Screen-reader labels that are wrong, a focus order that is hard to follow, content that alters unannounced, gestures for which there is no substitute and controls of a size that is impractical.
For a website to be truly accessible in Australia it has to stand up to use on a range of operating systems, browsers, screen readers, magnification and voice control tools, as well as switch devices. A test on the desktop is only half the picture.
What is expected and what obtains
It is expected that accessibility is a matter of quality assurance to be put to bed before launch. The reality is that if the design is not right from the start it will be woven into your templates, vendor contracts, support procedures and content workflows, making late remediation costly.
One might think an accessible alternative is the answer. But to direct someone from a digital service he cannot use to a phone line can still mean expense and delay, a loss of privacy or having to rely on another.
WCAG 2.2 Level AA and AS EN 301 549:2024
As a technical measure of web and digital accessibility WCAG 2.2 Level AA is the norm. It is a middle ground between Level A and AAA (the three conformance levels of WCAG) and deals with a wide array of practical impediments without insisting on all the techniques of AAA.
Organisations in Australia would do well to look at Australian Standard AS EN 301 549:2024 where it is called for, in the evaluation of ICT in the form of hardware, software, websites and support services.
Making standards work as evidence
On an Australia project under WCAG 2.2 Level AA one should map requirements to the way a user actually goes about things: registering, searching, making a payment, downloading, altering details or getting in touch with support.
Standards are a means of demonstrating an organisation has given due thought to accessibility, though they are no substitute for manual testing, legal judgement, user research or reasonable adjustment.
| WCAG Level | Practical meaning | Use in compliance work |
|---|---|---|
| Level A | The minimum to begin with, covering the basics | Minimum starting point, not a complete accessibility target |
| Level AA | The common benchmark for digital services and websites, dealing with barriers that affect the many | Common benchmark for websites and digital services |
| Level AAA | The highest conformance, suitable for some content but not always feasible for a whole service | Useful for selected content, but not always achievable across an entire service |
The Australian Human Rights Commission has the information and guidance on disability rights and technology that pertains to discrimination. For a risk assessment or to resolve a dispute, organisations should take legal counsel and refer to the Commission’s disability rights guidance.
Duties in government procurement and the public sector
A tender or supplier agreement can make of accessibility a contractual obligation rather than a policy nicety. Procurement by government may call for accessible ICT, reporting on conformance, proof of testing and time for remediation, as well as support for assistive technology.
Rules vary between Commonwealth, state and local government so the procurement team is advised to see what applies to the entity and the project. There has to be a way of verifying the product is “accessible”, a generic claim will not do.
Put it in the contract
The documents should spell out the standard, who is footing the bill for any remediation, what the supplier has to put forward by way of evidence and the user journeys to be tested. Do not forget updates, plug-ins, integrations, outsourced support and content.
When a vendor comes to demonstrate, have him put aside the slide deck and do some real tasks. Put him to it with keyboard only, or navigating with a screen reader, or recovering from an error. That is where you will find out.
Ownership of internal digital tools
To concentrate on the public facing website and ignore the tools of the employee is an error. Inaccessible systems can have an impact on the day to day of work, on safety information, recruitment and promotion.
There is a division of responsibility: managers to deal with individual adjustments, content teams to put out information, technology to look after the platform, procurement to choose the supplier and leadership to set the tone.
Build accessibility into ownership
An accessibility owner should be put in place with the budget and authority to report. Make sure accessibility is part of the equation in everything from incident response and change management to project sign off and reviews of suppliers.
There is no substitute for training in the ways of accessible writing, form design and testing with assistive technology, as well as how to put together documents, headings, captions and image descriptions. One presentation a year will not put right a publishing process that is putting up new barriers on a weekly basis.
Legal Risks, Complaints and Enforcement
An individual faced with an inaccessible service has the option of going to the organisation with his or her concerns or lodging a complaint at the Australian Human Rights Commission. The latter can mean conciliation, negotiation and some information gathering. Should the issue remain unresolved, a claimant might take it further by way of legal action before the Federal Court or other court of jurisdiction. What ensues could be damages, legal costs, a change in policy or remediation, contingent on the facts and the legal route open to them.
The Merits of a Complaint
More often than not a complaint will reveal a host of broken buttons. It can be indicative of an organisation that has no accessibility policy, has been remiss in user testing, has turned a blind eye to reports or has left an inaccessible supplier to its own devices.
It is wise to have on file your accessibility decisions, audits, procurement checks, any reasonable adjustments made and records of remediation. While good record keeping is no surefire way of dictating a legal outcome, it goes some way to proving risks have been put in hand.
Making Access Better
An assessment should be done in a practical manner: do a technical review, test manually and get input from people with disability. You may use automated tools to spot patterns but they are not to be trusted when it comes to determining if a workflow is sensible or the content is comprehensible to a real person.
Concentrate on the important journeys first. With a day to spare, one would assess the likes of account set up, login, booking or purchase, payment, search, customer support and complaints; these tend to present the most in the way of customer impact and legal risk.
Compliance Checklist for Australia
- Websites, mobile apps, software, cloud services, kiosks, emails, documents and any internal tools employed in the course of delivering a service must be put under the microscope.
- Chart the critical user journeys and note where a person is likely to be put off, held up or put in the position of having to declare a disability.
- Put WCAG 2.2 Level AA to the test with screen readers, zoom, keyboard only and mobile features as well as the usual automated tools.
- Have those who make use of assistive technology put it through its paces and put down any barriers in plain English.
- Look over your forms, error messages, authentication, downloadable documents, alternative text, transcripts and captions.
- See what obligations for accessibility are laid down in government procurement requirements, contracts and with suppliers.
- For the barriers that stand in the way of an essential task being done, assign an owner and a deadline to see them fixed. In the interim there should be a reasonable adjustment process and a support channel that is fit for purpose.
- And after a redesign, an update to the platform or any new content, the testing needs to be done again.
Working Under Real Conditions
Services are not used in a lab. People are using them with children to look after, on the Stuart Highway or in a hurry to put in a form before the system times out. Accessibility work has to allow for that, as well as for poor connections, small screens, fatigue, cognitive load and a lack of confidence with technology.
Do not make a habit of putting a certificate in a drawer. Review your progress, document why you have made certain calls and prioritise the essentials so the service is of use to more people.
Some FAQs
The following are meant to dispel some of the confusion surrounding DDA website compliance and the law in Australia. They are a practical place to begin but not a replacement for counsel on a complex project or an active complaint.
Under the Disability Discrimination Act what are a business’s digital obligations?
Those in the provision of goods and services must ensure equal access and not discriminate. If the service is via an app or website, any disability related impediments ought to be identified and removed and the organisation must decide if any hardship put forward is truly without justification.
Is the DDA relevant to mobile apps and websites?
In many cases it is. The DDA is concerned with discrimination in the supply of goods and services, which is what a website or app may be doing. Hosting a service overseas or outsourcing it does not of itself insulate one from Australian legal risk.
What is the standard for 2026?
WCAG 2.2 Level AA is the benchmark of choice. AS EN 301 549:2024 is also of some relevance for ICT products and services. Do not mistake either for a legal safe harbour; actual user access and reasonable adjustments have to be factored in.
So what is WCAG 2.2 Level AA here in Australia?
It is the middle conformance level (A, AA, AAA) and a technical target rather than the language of the DDA. The requirements are wide ranging, from focus and contrast to keyboard access and adaptable content.
Risk of litigation for an inaccessible site?
Under the DDA an inaccessible service is an invitation to complaint and litigation. There may be direct engagement or AHRC conciliation, or it could end up in court. When a formal complaint is tabled, or a proceeding is threatened, a business would be well advised to act quickly, have its records in order and seek legal opinion.
AHRC guidelines cover what kind of digital product?
Anything public facing such as a website, kiosk, email, online document or cloud service. Internal tools warrant attention too if an applicant or employee is to be using them.
What does the Australian Government require of ICT procurement?
That will depend on the contract, the entity and the jurisdiction. Put the onus on the tender and contract for evidence of testing, the standard required and duties of remediation. Procurement teams should not take a supplier’s word for it but verify with independent testing and demonstration.
In Australia responsible service delivery means digital accessibility. Take the approach of involving users, mending the barriers to completion and having the evidence to show for it. Use WCAG 2.2 Level AA as your guide and start with the tasks and people most at risk of exclusion. It is a fairer way to do things and for the organisation much less of an ordeal than to find out about it in the context of a formal complaint.