ADA Website Compliance: A Complete Guide to Making Your Website Accessible
ADA Website Compliance: A Complete Guide to Making Your Website Accessible
The Americans with Disabilities Act was signed in 1990 — before the web existed. It never mentions websites, URLs, or digital content. And yet ADA website compliance is one of the most active areas in digital accessibility law today, with courts consistently holding that websites of businesses serving the public must be accessible to people with disabilities. If your business has a website and serves customers, this applies to you. Here’s what it means and how to get it right.
(This article is general information, not legal advice. Your ADA obligations depend on your specific circumstances — consult qualified legal counsel.)
What ADA Website Compliance Means
ADA website compliance means making your website usable by people with disabilities — including those who are blind, have low vision, are deaf or hard of hearing, have motor impairments, or have cognitive disabilities. In practical terms, it means conforming to the Web Content Accessibility Guidelines (WCAG) at a level that courts and regulators have established as the expected standard.
The ADA itself sets no technical specification for websites. What’s happened instead is that courts, DOJ settlements, and regulatory guidance have converged on WCAG 2.1 Level AA as the benchmark — and WCAG 2.2 Level AA is increasingly the expected target.
How the ADA Applies to Websites
Two parts of the ADA are relevant:
Title III covers “places of public accommodation” — businesses that serve the public, including retailers, restaurants, banks, healthcare providers, hotels, and entertainment venues. Courts have applied Title III to the websites and mobile apps of these businesses, reasoning that an online presence is an extension of the business itself. The landmark case — Robles v. Domino’s Pizza — established that a website and app connected to a physical business can fall under Title III, and the Supreme Court declined to hear the appeal.
Title II covers state and local government entities. In April 2024, the DOJ published a rule requiring all web content and mobile apps of state and local governments to conform to WCAG 2.1 Level AA, with phased compliance deadlines (the first, for larger entities, has already passed as of 2026).
For private businesses, there is no equivalent Title III regulation naming WCAG — but WCAG is the standard applied in virtually every settlement, consent decree, and court-ordered remediation. For a comprehensive look at how these requirements come together, BarrierBreak’s ADA compliance guide covers the landscape in detail.
ADA Website Accessibility Requirements: What WCAG Covers
WCAG organizes its requirements under four principles:
Perceivable — users must be able to perceive all content. This includes text alternatives for images, captions for video, sufficient color contrast, and content that works when text is resized.
Operable — all functionality must be available via keyboard, navigation must be consistent and predictable, and users must have enough time to interact with content.
Understandable — text must be readable, forms must behave predictably, and errors must be identified and explained clearly.
Robust — content must be compatible with current and future assistive technologies, including screen readers, magnifiers, and voice control.
Get BarrierBreak’s stories in your inbox
Join Medium for free to get updates from this writer.
At Level AA, WCAG includes approximately 50 success criteria. The ones that appear most frequently in ADA compliance testing include:
- 1.1.1 — text alternatives for all non-decorative images
- 1.2.2 — captions for pre-recorded video
- 1.4.3 — minimum color contrast ratios
- 2.1.1 — all functionality keyboard-accessible
- 2.4.7 — visible focus indicators
- 3.3.1 / 3.3.2 — error identification and labels on forms
How to Make a Website ADA Compliant
A practical compliance path has five steps:
1. Run an ADA website audit
An ADA accessibility audit evaluates your website against WCAG using three testing layers: automated scanning (fast, catches code-level issues), manual expert testing (catches judgment-based issues like meaningful alt text and logical reading order), and assistive technology testing (confirms real users can actually complete tasks). Automated tools alone catch a minority of real barriers.
2. Prioritize by user impact
Not all issues carry equal weight. Barriers that prevent core tasks — logging in, completing a purchase, submitting a form — come before cosmetic issues. Fix what blocks users first.
3. Remediate the issues
Fix accessibility barriers in your code: add meaningful alt text, repair keyboard navigation, label form fields, ensure sufficient contrast, add captions to video, correct heading structure. Fix root causes in shared components rather than patching page by page.
4. Maintain an accessibility statement
An accessibility statement documents your conformance target (typically WCAG 2.1/2.2 Level AA), your current status, any known limitations, and how users can contact you with accessibility issues. It demonstrates good faith and gives users a path to report barriers.
5. Build accessibility into your process
An ADA-compliant website today can become non-compliant with the next release if accessibility isn’t part of how your team designs, develops, and tests. Embed accessibility in your definition of done, train your team, add automated checks to your pipeline, and audit periodically.
Organizations that want a structured approach often work with accessibility specialists — the team at BarrierBreak combines ADA compliance testing, remediation, and training as a continuous programme rather than a one-time project.
Common ADA Website Compliance Mistakes
- Assuming an overlay widget makes you compliant. Overlays are widely criticized and rarely achieve real WCAG conformance.
- Auditing once and never again. Products change; accessibility regresses without ongoing testing.
- Automated testing only. Scanners catch a fraction of barriers; manual and AT testing are essential.
- Waiting for a demand letter. Reactive compliance costs more — legally and technically — than proactive.
- Confusing ADA with WCAG. The ADA is the law; WCAG is the technical standard courts use to measure compliance. Both matter, differently.
Conclusion
ADA website compliance means making your website usable by people with disabilities, measured against WCAG 2.1/2.2 Level AA as the standard courts and regulators apply. The ADA may predate the web, but its application to websites is well-established. Audit your site with combined automated, manual, and assistive technology testing; remediate by user impact; maintain an accessibility statement; and build accessibility into your ongoing development process. Do that, and you protect your users, reduce legal risk, and build a website that genuinely serves everyone.
FAQ
Does the ADA apply to my website? If your business serves the public — retail, healthcare, banking, hospitality, entertainment, professional services — courts have consistently applied ADA Title III to websites. State and local government websites are explicitly covered under the 2024 Title II rule.
What technical standard makes a website ADA compliant? WCAG 2.1 Level AA is the standard applied in virtually all ADA settlements and enforcement actions. WCAG 2.2 Level AA adds further criteria and is increasingly expected. The ADA text doesn’t name a standard, but WCAG is the de facto requirement.
What is an ADA website audit? A structured evaluation of your website against WCAG, combining automated scanning, manual expert testing, and assistive technology testing. The output is a report identifying barriers, mapping them to WCAG criteria, and providing remediation guidance.
Can an accessibility overlay make my site ADA compliant? Almost certainly not. Overlays are widely criticized by accessibility professionals and advocacy organizations. They sit on top of your existing code and often fail to address the underlying barriers. Genuine compliance requires fixing the source code.
How much does ADA compliance cost? It depends on the size and complexity of your site, the number of issues, and the depth of testing. There’s no single price — but proactive compliance is consistently cheaper than reactive remediation after a demand letter.
How often should I test for ADA compliance? After every significant update, and at least annually for a formal audit. Continuous automated monitoring between audits helps catch regressions early.
