ADA and WCAG compliance for US websites in 2026: what the law requires, the WCAG 2.1 AA standard, common failures, and how to cut legal risk.
ADA and WCAG Compliance for US Websites: What You Need in 2026
If your business serves US customers, your website is almost certainly expected to be accessible to people with disabilities — and the legal exposure for ignoring that is real, growing, and easy to underestimate. Thousands of web accessibility lawsuits and demand letters are filed in the US every year, and most target small and mid-sized businesses, not just enterprises. This guide explains what the ADA actually requires of websites, where WCAG fits in, and what compliance looks like in practice without the fear-mongering or the legalese. It is not legal advice — for that, talk to counsel — but it will tell you what most US businesses genuinely need to do.
The ADA and your website: what the law actually says
The Americans with Disabilities Act (ADA) became law in 1990, long before websites mattered. Title III of the ADA prohibits discrimination by “places of public accommodation” — businesses open to the public. The catch: the ADA’s text does not mention websites and does not spell out a technical standard. Over the past decade, US courts have increasingly held that a business’s website is covered by Title III, especially when it connects to a physical location or is central to how the business serves customers.
The practical upshot is that you are operating in a space where the obligation is clear but the exact technical bar is set by case law and settlements rather than a single statute. That uncertainty is precisely why plaintiffs’ firms have been so active: businesses settle rather than litigate an ambiguous standard.
Where WCAG comes in
Because the ADA does not define a technical standard, courts, the Department of Justice, and settlement agreements have coalesced around one: the Web Content Accessibility Guidelines (WCAG), published by the W3C. WCAG is the de facto benchmark for US web accessibility.
- WCAG 2.1 Level AA is the standard most settlements and guidance reference today. It is the practical target to aim for.
- WCAG 2.2, published in late 2023, adds criteria (for example around focus visibility and dragging movements) and is the direction the bar is heading.
- Level AA, not AAA, is the realistic compliance goal. AAA is aspirational and not expected for general business sites.
WCAG is organized around four principles, often abbreviated POUR: content must be Perceivable, Operable, Understandable, and Robust. Almost every accessibility failure traces back to violating one of those four.
What about Section 508 and DOJ rules?
Two related rules cause confusion, so it is worth being precise:
- Section 508 applies to federal agencies and many of their contractors. If you sell to the US government, this is directly relevant; it also adopts WCAG as its baseline.
- The 2024 DOJ rule under ADA Title II formally adopted WCAG 2.1 AA for state and local government entities. It does not bind private businesses directly, but it signals where federal thinking is going — toward WCAG 2.1 AA as the explicit standard.
For a typical private US business, Title III plus the WCAG 2.1 AA benchmark is the frame that matters.
The most common failures that get sites sued
You do not need to memorize WCAG to dramatically cut your risk. A small set of issues accounts for the majority of complaints:
- Missing image alt text — screen readers cannot describe images without it.
- Poor color contrast — low-contrast text fails users with low vision and is one of the most cited violations.
- No keyboard navigation — every function must work without a mouse. Inaccessible menus, modals, and carousels are repeat offenders.
- Unlabeled forms — inputs without proper labels make checkout and contact forms unusable with assistive tech.
- Missing focus indicators — keyboard users need to see where they are on the page.
- Video without captions — media needs text alternatives.
How to know where you stand
Accessibility is testable, which means you can replace anxiety with evidence:
- Automated scans (axe, WAVE, Lighthouse) catch roughly 30–40% of issues in minutes. Useful, but never sufficient on their own.
- Manual testing — navigating the whole site by keyboard, and using a screen reader like VoiceOver or NVDA — catches the issues automation cannot.
- A professional audit against WCAG 2.1 AA gives you a prioritized remediation list and documentation that demonstrates good-faith effort, which matters if you ever receive a demand letter.
One important caution: so-called accessibility “overlay” widgets that promise instant compliance with a line of JavaScript are widely criticized by accessibility experts and have themselves been named in lawsuits. They are not a substitute for building the site correctly.
Build it in, do not bolt it on
The cheapest path to accessibility is to treat it as a requirement from the first wireframe, not a fix after launch. Accessible design overlaps almost entirely with good design: clear contrast, logical structure, predictable navigation, and forms that explain themselves. Teams that bake the UX design process and accessibility together ship sites that are both compliant and genuinely better to use — and they avoid the far higher cost of retrofitting. When you scope a project, accessibility should be a line item in the brief, the same way performance is. For where that sits in overall budgets, see our breakdown of UI/UX design cost.
The bottom line
For US websites in 2026, the working standard is WCAG 2.1 Level AA, the legal frame is ADA Title III, and the risk is concrete enough that “we will get to it later” is an expensive bet. The good news: accessibility is testable, fixable, and mostly just good engineering and design done with care. Fix the high-frequency failures first, audit against WCAG, and build it into new work from the start. If you want help auditing or building an accessible site that holds up, talk to our team.
