What Is ADA Website Compliance?
ADA website compliance means making your website usable by people with disabilities, consistent with the Americans with Disabilities Act. The ADA itself never mentions websites, but the Department of Justice has long taken the position that business websites are covered, and courts largely agree. In practice, compliance means meeting WCAG 2.1 Level AA, the technical standard regulators and courts reference most, covering things like alt text, color contrast, keyboard access, and properly labeled forms.
- Detectable failures
- About 96% of the top one million homepages had detectable WCAG failures (WebAIM Million report)
- Most common failure
- Low-contrast text, found on roughly 80% of tested homepages (WebAIM Million report)
- Lawsuit volume
- Roughly 4,000+ web accessibility lawsuits have been filed in US courts annually in recent years (UsableNet year-end reports)
- Government standard
- The 2024 DOJ rule for state and local governments adopts WCAG 2.1 Level AA (US Department of Justice, Title II rule)
ADA Website Compliance, Defined #
The Americans with Disabilities Act, passed in 1990, prohibits discrimination against people with disabilities in places of public accommodation. ADA website compliance is the practice of making your website work for those users: people who are blind and browse with screen readers, people with low vision who need strong contrast and zoomable text, people with motor disabilities who navigate by keyboard or voice, and people who are deaf and need captions. Because the ADA predates the commercial web, it contains no technical checklist for websites. That gap has been filled in practice by the Web Content Accessibility Guidelines, known as WCAG, at conformance Level AA. When a business says its site is ADA compliant, what it almost always means, and what courts and settlement agreements almost always require, is conformance with WCAG 2.1 AA, increasingly with an eye toward the newer WCAG 2.2.
Does the ADA Really Apply to Websites? #
The Department of Justice has said for years that it does. Title II of the ADA covers state and local governments, and in 2024 the DOJ finalized a rule explicitly requiring their websites and mobile apps to meet WCAG 2.1 AA on a phased timeline. Title III covers private businesses that serve the public, and while no equivalent regulation spells out a technical standard for them yet, the DOJ has repeatedly stated in guidance and court filings that Title III applies to business websites. Federal courts have mostly agreed, though circuits differ on details such as whether a website must connect to a physical location. For a practical business owner, the debate is largely academic: the enforcement history, settlement patterns, and DOJ position all point the same direction, and WCAG 2.1 AA is the benchmark that consistently satisfies them.
What Is WCAG, and What Does Level AA Mean? #
The Web Content Accessibility Guidelines are published by the W3C, the standards body behind the web itself. WCAG organizes accessibility into four principles, content must be perceivable, operable, understandable, and robust, and grades conformance at three levels: A, AA, and AAA. Level AA is the widely accepted target: strong enough to be genuinely usable, achievable enough for real-world sites. WCAG 2.1 AA includes success criteria like minimum contrast ratios of 4.5 to 1 for normal text, full keyboard operability, visible focus indicators, text alternatives for images, labels on form fields, and content that reflows on mobile. WCAG 2.2, published in 2023, adds nine criteria, including easier-to-see focus indicators and less painful authentication. Regulators still reference 2.1 AA most, but building to 2.2 AA today is sensible future-proofing, since the newer criteria address real friction users hit constantly.
What Are the Most Common Failures? #
The same handful of problems dominate every audit and most lawsuits. 1) Missing alt text, so screen readers announce nothing useful for images, including product photos and image buttons. 2) Low contrast text, the single most common failure on the web, especially gray-on-white body copy. 3) Keyboard traps and unreachable controls, menus and modals that only work with a mouse. 4) Unlabeled form fields, where a screen reader user hears edit text with no clue what to type. 5) Missing document structure, pages without proper headings or landmarks. The fixes are usually simple in code.
<img src="blue-ceramic-mug.jpg"
alt="Blue ceramic coffee mug, 12 oz" />
<label for="email">Email address</label>
<input type="email" id="email" name="email"
autocomplete="email" required />The Demand-Letter Reality, Without the Scare Tactics #
Here are the documented facts. Several thousand web accessibility lawsuits are filed in US courts each year, with New York, Florida, and California federal and state courts hosting most of them, and industry trackers consistently report that e-commerce sites are the most frequently targeted category. A larger volume of demand letters never becomes public lawsuits and typically settles for amounts commonly reported in the four to five figures plus remediation commitments. Small businesses do receive these letters, and repeat plaintiffs and law firms drive much of the volume. That is the reality; here is the perspective. The odds for any single small site remain modest, and the same fixes that reduce legal exposure make your site work better for the roughly one in four US adults the CDC reports as having a disability. Treat accessibility as customer experience with legal alignment, not as lawsuit panic.
Do Accessibility Overlay Widgets Actually Work? #
Overlay widgets are third-party scripts, often sold as one line of code for instant compliance, that add a toolbar for adjusting contrast, text size, and similar settings, sometimes with automated fixes underneath. They are genuinely controversial. Hundreds of accessibility practitioners have signed an open letter advising against relying on them, many blind users report that overlays interfere with the screen readers they already use, and companies using overlays have still been sued, with industry trackers documenting hundreds of such cases per year. In 2025 the FTC's settlement with one overlay vendor over compliance claims underscored the marketing problem. A fair summary: overlays can offer minor convenience features, but they do not repair broken code underneath, and no responsible practitioner treats them as equivalent to remediation. If a vendor promises full ADA compliance from a single script, that promise is not supported by the record.
How Do You Actually Fix a Website? #
Real remediation follows a repeatable path. 1) Audit: combine automated scanning, which catches perhaps a third of issues like missing alt text and contrast failures, with manual testing by keyboard and screen reader, which catches the rest. Our free ADA Compliance Checker is a fast way to run the automated pass and see where your site stands. 2) Prioritize: fix the pages that matter most first, homepage, navigation, product pages, forms, and checkout, and the failures that block tasks entirely before cosmetic ones. 3) Remediate in code: alt text, labels, headings, contrast tokens, focus states, and keyboard handlers, fixed at the template level so every page inherits the repair. 4) Verify with real assistive technology, not just tools. 5) Maintain: add accessibility checks to your content workflow so new blog posts and products do not reintroduce old failures.
What Does an Accessibility Statement Do? #
An accessibility statement is a public page describing your site's conformance target, usually WCAG 2.1 AA, known limitations, and a way for users to report barriers, such as an email address or phone number. It is not legally required for private businesses, but it earns its keep three ways. First, it gives a frustrated user a direct channel to you before they contact a law firm, and settlement patterns suggest responsiveness matters. Second, it documents good-faith effort, which counsel can point to if a dispute arises. Third, it forces internal honesty: writing down your conformance status requires actually knowing it. Keep the statement accurate and modest. Claiming full compliance while your checkout fails keyboard testing is worse than acknowledging ongoing work. Pair the statement with a feedback loop someone actually monitors, and update it whenever you complete a meaningful round of remediation.
When to Get Help, and a Necessary Caveat #
Handle the basics yourself: run our free ADA Compliance Checker, fix alt text and obvious contrast problems, and test your main pages with only a keyboard. Bring in professionals when the audit surfaces structural issues, custom components that need rebuilding, an inaccessible checkout, or when you have received a demand letter and need remediation done quickly and documented properly. Our ADA compliance services cover full audits with assistive-technology testing, code-level remediation on WordPress, Shopify, and custom sites, and ongoing monitoring so fixes stay fixed. For a broader picture of your site's health alongside accessibility, our free Website Grader is a sensible companion check. One important caveat: this article is general information, not legal advice, and the regulatory landscape continues to evolve, so for questions about your specific legal exposure, talk to an attorney experienced in ADA matters.
FAQ
Is there a law that says my website must meet WCAG 2.1 AA?
For private businesses, not explicitly. The DOJ's 2024 rule adopting WCAG 2.1 AA applies to state and local governments under Title II. For businesses under Title III, no technical standard has been codified yet, but DOJ guidance, court decisions, and settlement agreements consistently point to WCAG 2.1 AA, making it the practical benchmark to build against.
My website was built recently. Is it automatically accessible?
No. New does not mean accessible, and the WebAIM Million study finds detectable WCAG failures on about 96% of leading homepages. Modern themes and builders still ship low-contrast palettes, unlabeled icon buttons, and mouse-only menus. The build date matters far less than whether accessibility was tested during the build. A quick scan and a keyboard-only walkthrough will tell you quickly.
How much does it cost to make a small-business site accessible?
It varies with the site's condition. Fixing alt text, contrast, and labels on a small template-based site is often modest, sometimes a few hours of work. Full remediation of a large or custom site with an inaccessible checkout can run into thousands of dollars. An audit first is the right sequence, because it converts a vague fear into a priced, prioritized list.
Will an overlay widget protect me from lawsuits?
The documented record says no. Industry trackers report hundreds of lawsuits each year filed against companies whose sites run overlay widgets, and accessibility practitioners broadly advise against relying on them as a compliance strategy. Overlays do not repair the underlying code that screen readers and keyboards depend on. Genuine remediation of templates and components is what actually reduces both barriers and exposure.
Does ADA compliance apply to PDFs and videos on my site?
Yes, content counts, not just page templates. Videos should have accurate captions, and audio-heavy content benefits from transcripts. PDFs need proper tagging, reading order, and text alternatives, or better, offer the same information as an accessible web page. Menus, forms, and brochures posted as scanned images are among the most common content-level barriers small-business sites carry.
Where should I start today?
Three steps this week: run your homepage and highest-traffic pages through our free ADA Compliance Checker, unplug your mouse and try to browse and complete a form using only the Tab and Enter keys, and fix the missing alt text and gray-on-white text the scan surfaces. Those steps address the most-cited failures and give you an honest baseline for planning the rest.
Was this helpful?