ADA compliance means your website works for people with disability, in line with the Americans with Disabilities Act. The Act names no technical standard, so courts and regulators point to WCAG, the Web Content Accessibility Guidelines. Meet WCAG, document the work, and you hold a defensible position.
That sounds simple. The detail is where owners get caught, so let’s walk through it.
What ADA compliance actually means
The Americans with Disabilities Act is a US civil rights law from 1990. It bans discrimination by places of public accommodation. For two decades, courts have read that phrase to cover websites, not just physical shops. Title III is the part that applies to private business.
Here is the catch. The Act itself says nothing about code, contrast or alt text. So there is no line in the statute you can point to and tick off. Instead, judges and the Department of Justice lean on WCAG as the working benchmark. The Department of Justice guidance says web content should be accessible, and treats WCAG as the reference for what that means.
So ADA compliance, in practice, is WCAG conformance plus a record that you did the work. No certificate exists. No government body stamps your site. Anyone selling you an official “ADA certified” badge is selling air, and you should walk away.
Who does ADA compliance apply to?
Short answer: most sites that serve the public. Retail, property, hospitality, finance, education and health all sit in scope, because each runs a service the public uses. A booking page, a product catalogue, a member login, a contact form. If a customer can act on your site, a customer with disability should be able to act on it too.
The audience is larger than owners picture. In Australia, the Bureau of Statistics puts the number near 5.5 million people, about 21% of the population. Many rely on a screen reader, keyboard or magnifier to get through a page. These customers reach you online more, not less, because getting somewhere in person is often harder for them. Shut them out of a form and you have shut out real revenue, not an edge case.
Where WCAG fits in
WCAG is published by the World Wide Web Consortium, the group that sets web standards. The current version is WCAG 2.2, released in 2023. It rests on four ideas. Your content should be perceivable, operable, understandable and robust. In plain terms: people can see or hear it, use it with a keyboard or screen reader, make sense of it, and rely on it in their assistive tech.
WCAG sorts its rules into three conformance levels. Most owners aim for the middle one.
| Level | What it means | Who targets it |
|---|---|---|
| A | The floor. Basic barriers removed, such as keyboard access and image alt text | A starting point, rarely enough on its own |
| AA | The working standard. Adds colour contrast, clear labels, resize and reflow | Most businesses, and the level courts and regulators cite |
| AAA | The stretch. Sign language for video, higher contrast, stricter reading rules | A few pages, hard to hit across a whole site |
Level AA is the practical target. It is the bar named in most settlements, the one the WebAIM survey measures against, and the one your competitors are judged by too.
How common are failures? More common than owners expect. The WebAIM Million scans a million home pages each year. In 2024 it found detectable WCAG failures on 95.9% of them, at an average of 56.8 errors per page. Those are only the faults a scanner can catch by itself, so the real figure runs higher.
What about Australia?
Here the law changes, but the target barely moves. An Australian business is not bound by the ADA, which is US law. Your duty comes from the Disability Discrimination Act 1992. It makes discrimination in the provision of a service unlawful, and your website counts as a service.
The Australian Human Rights Commission is the body that hears complaints, and it has pointed to WCAG for years. So a Sydney owner and a US owner end up building to the same standard, by different legal routes. The well known local case is Maguire v SOCOG, where a blind user won a complaint over an inaccessible Olympics site in 2000. Old, but the principle held, and it still shapes advice across New South Wales today.
Honestly, the overlap surprised me the first time I mapped it. Owners brace for two rulebooks and find one technical answer. If you trade in both markets, WCAG 2.2 Level AA covers you on both sides of the Pacific.
A website owner’s ADA compliance checklist
Right, the practical part. You do not need to read WCAG cover to cover. Start with the failures that block real people and show up most in scans. Here is a checklist you can hand to a developer, mapped to what each item means.
| Check | What it means | Why it matters |
|---|---|---|
| Text contrast | Body text stands out from its background | Low contrast is the top failure on the web, on four in five pages |
| Image alt text | Every meaningful image carries a short text description | A screen reader reads the alt text aloud, or reads nothing at all |
| Form labels | Each field has a label tied to it in the code | Without one, a user cannot tell what to type where |
| Keyboard access | Every task works without a mouse | Many people tab through a page and cannot use a pointer |
| Visible focus | The active element shows a clear outline | Keyboard users need to see where they are |
| Headings | Structure uses real heading tags in order | Screen readers jump by heading to skim a page |
| Link text | Links describe where they go, not “click here” | Users pull up a list of links out of context |
| Video captions | Recorded video carries accurate captions | Deaf and hard of hearing users depend on them |
| Resize and reflow | Text scales to 200% without breaking the layout | Low vision users zoom in to read comfortably |
| Error messages | Forms say what went wrong and how to fix it | Vague errors trap people at the last step |
Work top down. Contrast and alt text alone tend to clear a large share of scanner errors in the first pass. Then move to keyboard and focus, which need a person, not a tool. An automated scan finds maybe a third of real issues, so pair it with hands-on testing. For the full method, see our website accessibility audit guide.
One warning before you spend a cent. Skip the overlay widgets that promise instant compliance. They sit on top of broken code, they load a third party script, and they rarely fix the source fault. A run of lawsuits in the United States has named sites that used them. Repair the markup first, then decide if a widget still adds anything.
One more item that is not code at all. Publish an accessibility statement. Name the standard you work to, give a contact for help, and date your last check. It will not fix a broken form, but it shows intent, and that record helps if a complaint ever lands.
What we found on a real audit
Numbers beat theory, so here are ours. A medical group, All Health, asked us to check every page of their site. We worked through 37 pages, one at a time, with no sampling. The result was blunt. We logged 213 WAVE errors, an average score of 4.1 out of 10, and not one page meeting Level AA.
The item that stopped us was the booking form. A keyboard user could reach it and then fail to submit it. To anyone using a mouse, the page looked fine. That gap is the whole problem in one screen. It reads as working, and it quietly shuts people out.
In our own testing, we retest after each fix rather than trust the first pass. One client assumed a contrast tweak was cosmetic. It cleared a stack of errors on every template at once, because the same colour ran site wide. So we keep a dated before-and-after on file, which becomes your evidence if a complaint ever reaches the Commission or a court. A score on its own proves nothing.
The full breakdown sits in our ADA compliance case study. The sector was healthcare, yet the faults were ordinary. The same short list turns up on retail, property and services sites too. If your work is health specific, we go deeper in ADA compliance for medical websites.
The relief for most owners is the cost curve. The cheap fixes, contrast and alt text, remove a large slice of the risk early. The work we do on ADA and AHRC compliance starts there, then moves to the harder, human-tested faults that a scanner walks straight past.
FAQ
What is ADA compliance?
It means your website works for people with disability, in line with the Americans with Disabilities Act. The Act names no code standard, so courts and regulators treat WCAG as the benchmark. In practice, ADA compliance is WCAG conformance plus a dated record of the work.
Is ADA compliance a legal requirement for websites?
For US businesses open to the public, courts have applied Title III to websites for years, so the duty is real. There is no official certificate, though. You show good faith by meeting WCAG and keeping a dated audit trail.
What WCAG level should I aim for?
Level AA. It is the level named in most settlements and the one regulators cite. Level A is too thin on its own, and Level AAA is hard to hit across a whole site. AA is the sensible target for most owners.
Does ADA compliance apply in Australia?
The ADA is US law, so it does not bind an Australian business. Your duty comes from the Disability Discrimination Act 1992, with the Australian Human Rights Commission handling complaints. The technical answer is the same, since both routes point at WCAG.
How do I check if my website is ADA compliant?
Start with a free scan using a tool like WAVE to catch contrast, alt text and label faults. Then test with a keyboard and a screen reader, since tools miss roughly two thirds of issues. A proper audit maps each fault to a WCAG rule and rates it by fix effort.
Key takeaways
ADA compliance means your website works for people with disability under the Americans with Disabilities Act. The Act names no standard, so WCAG is the working benchmark, and Level AA is the target most owners should meet. No certificate exists, only conformance plus a record of the work. In Australia the Disability Discrimination Act 1992 and the Australian Human Rights Commission set the same practical bar by a different route. Start with contrast and alt text, then test with a keyboard and screen reader, and keep a dated audit trail as your evidence.
Want a scoped check rather than a badge that means nothing? That is the work we do in ADA and AHRC compliance, page by page, with a fix list you can act on.
Sources
- W3C, WCAG 2.2: https://www.w3.org/TR/WCAG22/
- WebAIM, The WebAIM Million annual accessibility report: https://webaim.org/projects/million/
- US Department of Justice, ADA and web accessibility: https://www.ada.gov/
Updated August 2026. Written by Sheetal Dhadial, founder of SIAGB, an AI-native consultancy in Sydney.
Ready to put this into practice?
Let's Talk
