DDA and healthcare accessibility: the precedents designers should know

27 June 2026

Accessibility & health literacy Accessibility & Regulation

Australia's Disability Discrimination Act names no technical standard, but three closed cases, thirty years apart, show what a digital service has to get right - and each maps onto a common health-product screen.

Not legal advice This article describes closed cases and their general pattern for design education. It is not legal advice and not a compliance verdict on any product. Check current guidance and seek qualified advice for compliance decisions.

The Disability Discrimination Act 1992 (DDA) makes it unlawful to discriminate against a person with disability in the provision of goods, services and facilities - written in general terms, decades before most health services went digital, and naming no version of any accessibility standard. What counts as meeting it has instead been shaped by individual complaints, three of which are settled, closed and instructive for anyone building a digital health product today.

A general law, no named standard

Section 24 of the DDA covers goods, services and facilities. It does not mention websites, apps or WCAG (the Web Content Accessibility Guidelines), because it predates all three. Complaints are lodged with the Australian Human Rights Commission under the Australian Human Rights Commission Act 1986, which sets out a complaint, a conciliation stage run by the Commission, and, if conciliation fails or the complaint is terminated, the option to apply to the Federal Court or Federal Circuit Court. Most complaints resolve at conciliation and are never tested in open court, which is one reason there are few full judgments to cite even though complaints are common.

1. Maguire v SOCOG (2000) - the website is a service

Bruce Maguire, who is blind, complained that the Sydney Olympics website was inaccessible with a screen reader: images carried no alternative text, the results tables published during the Games could not be read, and navigation between the schedule and the sports index did not work. On 24 August 2000 the Human Rights and Equal Opportunity Commission found the Sydney Organising Committee for the Olympic Games had directly and indirectly discriminated against Maguire under sections 5, 6 and 24 of the DDA. It rejected the Committee's argument that fixing the site would be an unjustifiable hardship, on evidence that the fixes were achievable within weeks at modest cost, and Maguire was ultimately awarded $20,000 in damages. The finding that mattered beyond this one case: a website is a service under the Act, and building it to work for sighted users only is what makes it discriminatory, not any single missing feature.

2. Mesnage v Coles (2014) - a redesign can remove access that already existed

Gisele Mesnage, who is blind and shops using a screen reader, had used Coles' online grocery ordering successfully until a 2013 site redesign removed the features that made it work. Afterwards, placing a single order could take her as long as eight hours: she could not reliably select a delivery time, and navigation broke in ways sighted shoppers never encountered. When a direct complaint to Coles and a complaint to the Australian Human Rights Commission did not resolve the problem, the matter proceeded toward the Federal Circuit Court - among the first web accessibility matters to reach that court - and was settled before judgment, with Coles committing to rebuild the site to meet WCAG 2.0 and to involve accessibility specialists in the process. The lesson for a product team: accessibility is not a one-off milestone. A later redesign can silently discriminate against users a product previously served well.

3. The Commonwealth Bank EFTPOS case (2016-2019) - a self-service terminal is a service too

Nadia Mattiazzo and Graeme Innes, both blind, complained that Commonwealth Bank's Albert EFTPOS terminals had no tactile buttons, so a blind customer could not enter a PIN privately or reliably. The complaint was lodged with the Human Rights Commission in 2016; when it was not resolved, a Federal Court case followed in 2018. The bank settled in January 2019, agreeing to add an audio-guided accessibility mode through headphones and to work with the Australian Banking Association on accessibility principles for the sector; disability advocates called the fix an incomplete first step, not a full solution. The pattern here is different from a website: the barrier was a physical self-service device with a digital interface behind it, the same category as a hospital check-in kiosk or a pharmacy pick-up terminal.

What ties the three together

None of these cases was about healthcare, and that is the point worth naming directly: the DDA does not carve out a separate, lighter rule for health services. A patient portal is a website, in the same legal category as the Olympics site. An online appointment-booking flow is a service, in the same category as online grocery ordering. A self-service check-in kiosk in a clinic is a facility, in the same category as a bank's EFTPOS terminal. Every one of these closed cases turned on the same underlying fact: a digital-only path existed with no equivalent way for a blind user to complete the same task, and the organisation had the means to fix it.

What this means for a health product

A patient portal login or results page is, in DDA terms, exactly the kind of "website" Maguire's case addressed - alt text, navigable structure and readable data tables are not optional extras.
A redesign needs an accessibility check before launch, not just at the original build. Coles' case shows that removing existing access is treated the same as never providing it.
A self-service kiosk (check-in, pharmacy pick-up, triage terminal) needs a non-visual, non-fine-motor way to complete the same task, not just a compliant screen behind an inaccessible physical interface.
Conciliation, not court, is where most of these matters are actually resolved - which means the cost of getting it wrong is rarely a headline judgment, but a real, direct negotiation with an affected user.