Misconceptions about accessibility stop many organisations from starting — or lead them to underinvest once they do. Some of these myths are understandable; they reflect genuine uncertainties about scope, cost and technical complexity. Most of them are simply wrong. Here is what the evidence actually shows.

Myth: Accessibility is only for people with disability

Reality: Accessible design benefits a much wider group than its name suggests. Captions help people watching video in a noisy environment, not just people who are deaf. High contrast benefits people in bright sunlight, not just those with low vision. Keyboard navigation benefits power users and people with temporary injuries, not just those with motor disabilities. Clear, predictable forms help everyone — they just help people with cognitive disabilities the most.

The ABS 2022 SDAC found that 5.5 million Australians live with disability, but that figure does not capture the much larger number of people who benefit from accessible design situationally. When you invest in accessibility, you improve the product for everyone.

Myth: Accessibility is expensive

Reality: The cost of accessibility depends almost entirely on when it is addressed. Building accessibility into design and development from the start adds a modest overhead. Retrofitting accessibility onto an existing product — redesigning components, refactoring code, replacing content — is significantly more expensive. Responding to a DDA complaint or accessibility-related procurement failure is more expensive still.

The Maguire v SOCOG 2000 case is instructive: SOCOG initially argued it would cost $2.2 million and take 368 days to make their site accessible. The Commissioner accepted expert evidence that an accessible site would cost around $30,000 and take four weeks. The gap between the cost organisations fear and the cost of actually doing the work is almost always large.

Myth: Accessibility limits design

Reality: Accessibility and good design are not in competition. The constraints that accessibility introduces — sufficient contrast, readable typography, predictable interactions, clear visual hierarchy — are also the foundations of effective interface design. Many of the most elegant and well-regarded digital products are also highly accessible. The discipline required to meet WCAG often produces sharper, more coherent design.

Myth: Automated tools handle accessibility

Reality: Automated accessibility tools are useful for catching common, machine-detectable issues quickly — missing alternative text, insufficient contrast ratios, absent form labels. But they can only evaluate a portion of WCAG’s 87 success criteria. Whether alternative text is actually meaningful, whether a form flow is genuinely usable by a screen reader, whether content is understandable — these require human judgement. An automated scan is a starting point, not a conformance assessment.

Myth: Accessibility is just compliance

Reality: Conformance with WCAG is a floor, not a ceiling. The goal is genuinely usable digital products that work for the full range of people who might use them. Organisations that treat accessibility as a compliance exercise tend to produce products that technically pass automated checks while still excluding people with disability in practice. The organisations that do it well treat accessibility as a quality standard — something that makes their products genuinely better, not just legally defensible.

Myth: Once done, it stays done

Reality: Digital products change constantly. New features, updated components, content changes, third-party integrations — any of these can introduce new accessibility barriers. A product that was accessible at launch may not be accessible after six months of iterative development. Accessibility requires ongoing attention, not a one-time fix.

FAQ

Q: Is making a website accessible expensive?

It is usually far cheaper to design accessibility in from the start than to retrofit it later. The Maguire v SOCOG case provides a clear Australian example: expert evidence put the cost of an accessible site at approximately $30,000 — a fraction of the $2.2 million SOCOG initially claimed.

Q: Can automated tools check for accessibility?

Automated tools can catch some common issues, but they can only evaluate a portion of WCAG criteria. Confirming accessibility requires expert review and, ideally, testing with people who have lived experience of disability.

Q: Does WCAG conformance guarantee an accessible product?

Conformance with WCAG 2.2 Level AA removes the most common and significant barriers, but it does not guarantee a perfect experience for every user. It provides a strong, evidence-based foundation — not a ceiling.