ADA Website Compliance Guide 2026
Everything you need to know about ADA website compliance — what the law requires, which violations trigger lawsuits, the WCAG 2.1 AA checklist, and exact code fixes for the most common issues.
Check your site right now — free
Get a lawsuit risk score and see every WCAG violation in under 60 seconds.
What is ADA website compliance?
The Americans with Disabilities Act (ADA), enacted in 1990, prohibits discrimination against people with disabilities in all areas of public life. Title III specifically covers “places of public accommodation” — and since 2010, federal courts have consistently ruled that commercial websites qualify.
This means any business that operates a public-facing website must ensure it is accessible to people who are blind, deaf, have motor disabilities, or have cognitive impairments. The technical standard courts use to assess compliance is WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the W3C.
Unlike building codes, there is no single federal rule specifying exactly which technical standard websites must meet. However, the Department of Justice issued a final rule in April 2024 formally adopting WCAG 2.1 AA as the compliance standard for state and local government websites, and private-sector courts have endorsed the same benchmark in the vast majority of ADA web-accessibility cases.
ADA lawsuit statistics 2026
ADA web accessibility lawsuits have grown every year since 2017. Serial plaintiffs and plaintiff law firms use automated scanners to identify non-compliant sites at scale, then send demand letters — often requesting $5,000–$20,000 to settle before a formal complaint is filed.
Even if a lawsuit is ultimately dismissed, legal fees for defending an ADA case average $8,000–$15,000. Proactive compliance is almost always cheaper than reactive defence.
Key risk factor: Having received a demand letter once does not protect you from future suits. Plaintiffs can sue again if violations reappear after a redesign or CMS update.
The 4 WCAG 2.1 principles (POUR)
WCAG 2.1 organises its 50+ success criteria under four core principles, often abbreviated as POUR.
Perceivable
All information and UI components must be presentable to users in ways they can perceive — including via screen readers and other assistive tech.
- Alt text on every meaningful image
- Captions on all pre-recorded video
- Colour is never the only way to convey information
- Text has at least 4.5:1 contrast ratio against its background
Operable
All UI components and navigation must be operable — users who cannot use a mouse must be able to complete every action using only a keyboard.
- All functionality available via keyboard alone
- No keyboard traps — users can always navigate away
- Visible focus indicator on every focusable element
- No flashing content faster than 3 flashes per second
Understandable
Information and the operation of the UI must be understandable — users must be able to comprehend content and know how to interact with forms.
- Page language declared in HTML lang attribute
- Form inputs have descriptive, associated labels
- Error messages identify the field and suggest a fix
- Consistent navigation across pages
Robust
Content must be robust enough to be interpreted by current and future assistive technologies, including screen readers and voice control software.
- Valid, well-formed HTML markup
- ARIA attributes used correctly
- Status messages conveyed without requiring focus
- Name, role, and value for all UI components
Top 6 violations that trigger ADA lawsuits
These issues appear in the majority of ADA web complaints. Fixing them eliminates most of your legal exposure.
Missing image alt text
CriticalWCAG 1.1.1Screen readers announce images by their alt attribute. Without it, blind users receive no information about the image content.
Exact fix
<!-- Before --> <img src="product-photo.jpg"> <!-- After --> <img src="product-photo.jpg" alt="Blue running shoes, size 10, side view">
Insufficient colour contrast
SeriousWCAG 1.4.3Text must achieve a 4.5:1 contrast ratio against its background (3:1 for large text). Low contrast makes text illegible for users with low vision.
Exact fix
/* Before — fails 4.5:1 ratio */ color: #999999; /* on white = 2.85:1 ❌ */ /* After — passes */ color: #767676; /* on white = 4.54:1 ✅ */
Form inputs without labels
CriticalWCAG 1.3.1 / 4.1.2Screen readers read out the label when a user focuses on an input. Inputs identified only by placeholder text are invisible to assistive technology.
Exact fix
<!-- Before --> <input type="email" placeholder="Enter email"> <!-- After --> <label for="email">Email address</label> <input type="email" id="email" placeholder="you@example.com">
Missing document language
SeriousWCAG 3.1.1The HTML lang attribute tells screen readers which language rules to use. Without it, text-to-speech software may mispronounce every word.
Exact fix
<!-- Before --> <html> <!-- After --> <html lang="en">
No keyboard focus indicator
SeriousWCAG 2.4.7Keyboard-only users (including people with motor disabilities) rely on a visible focus ring to know which element is active. Many sites remove it with outline: none.
Exact fix
/* Before — removes focus ring */
button:focus { outline: none; }
/* After — visible focus style */
button:focus-visible {
outline: 2px solid #3b82f6;
outline-offset: 2px;
}Empty or non-descriptive link text
SeriousWCAG 2.4.4Screen reader users often navigate by scanning a list of all links on the page. "Click here" or "Read more" provides no context about the destination.
Exact fix
<!-- Before --> <a href="/report.pdf">Click here</a> <!-- After --> <a href="/report.pdf">Download our 2026 Accessibility Report (PDF)</a>
Quick WCAG 2.1 AA checklist
Use this checklist for a manual review. Then run ADA Shield for automated detection of all 50+ criteria.
How to remediate violations
Most automated tools identify violations but leave you to figure out the fix. ADA Shield shows the broken HTML snippet alongside the corrected version so your developer can apply changes without interpretation.
Scan your URL
Paste your website URL. ADA Shield launches a real browser and runs axe-core against all WCAG 2.1 AA rules.
Review violations by risk
Violations are ranked by lawsuit risk — tackle critical issues (missing alt text, unlabelled inputs) first.
Apply the exact fix
Each violation includes the broken HTML and the corrected snippet. Copy, paste, and push to production.
For larger sites, prioritise pages that are most exposed to user traffic (homepage, product pages, checkout, contact) — these are the pages plaintiff attorneys scan first.
Ongoing monitoring — why one scan isn't enough
Every CMS update, theme change, plugin install, or new page publish can introduce new accessibility violations. A site that was compliant in January can have critical violations by March after a routine redesign.
ADA Shield's weekly monitoring scans your registered sites automatically, recalculates your risk score, and sends an email alert the moment your score worsens — giving you time to fix issues before a plaintiff attorney finds them.
What weekly monitoring catches that a one-time audit misses:
- New images uploaded without alt text
- Third-party widgets (chat, popups) that inject inaccessible HTML
- A/B test variants that fail contrast or keyboard requirements
- New product pages auto-generated from a CMS template
- Font or colour changes in a theme update that break contrast ratios
Ready to check your site?
Run a free scan in 60 seconds and get your lawsuit risk score with actionable, copy-paste fixes for every violation found.