ADA Lawsuit Payouts: 5 Real Case Examples and What Drives the Cost
ADA lawsuit payouts from 5 real website cases: Target, Netflix, H&R Block, Domino's and Fashion Nova. Who got paid, how much, and what drives the cost.
Contributor, AccessBell
Anton Stewart contributes to AccessBell’s guides on web accessibility, WCAG and accessibility testing.
Every article Anton Stewart works on follows our editorial process: requirements are checked against the primary source, such as the W3C’s Web Content Accessibility Guidelines, and each article shows a review history so you can see what changed and when.
Spotted an error in one of our guides? Tell us and we will review it.
ADA lawsuit payouts from 5 real website cases: Target, Netflix, H&R Block, Domino's and Fashion Nova. Who got paid, how much, and what drives the cost.
ADA lawsuits in 2026: the filing numbers, four recent website cases (Moscot, Cuddle Clones, Fashion Nova, Missouri) and what each teaches a business that is sued.
How to fix your website after an ADA complaint or lawsuit: what to fix first, code examples for the most common failures, manual testing and how to prove the fix.
How to check if your website is ADA compliant: run an automated WCAG scan, then test keyboard use, zoom, forms, contrast and captions by hand. A step-by-step guide.
How to create a website accessibility report: what to include, the W3C report template, VPAT and ACR formats, and how to generate a report from scan results.
ADA website accessibility explained: who the ADA covers, whether websites count, the WCAG standard, and how AccessBell helps you find and fix issues behind lawsuits.
The European Accessibility Act for technical teams: who it covers, EN 301 549 and WCAG requirements, exemptions, national rules and a compliance checklist.
WCAG 1.2.1 Audio-only and Video-only (Prerecorded) explained simply: transcripts for podcasts, alternatives for silent video, and how to test your media.
WCAG 1.2.2 Captions (Prerecorded) explained simply: what good captions include, why auto-captions fall short, how to add a caption file and how to test.
WCAG 1.2.3 Audio Description or Media Alternative (Prerecorded) explained simply: describing what videos show, the two ways to comply and how to test.
WCAG 1.3.1 Info and Relationships explained simply: why headings, lists, tables and form labels must be in the code, with fixes and how to test.
WCAG 1.3.3 Sensory Characteristics explained simply: why instructions cannot rely only on shape, size, position or sound, with examples and how to test.
WCAG 1.4.2 Audio Control explained simply: the 3-second rule for autoplaying sound, the pause, stop and volume controls required, and how to test.
WCAG 2.1.1 Keyboard explained simply: why every feature must work without a mouse, the controls that most often fail, how to fix them and how to test.
WCAG 2.1.2 No Keyboard Trap explained simply: how keyboard traps happen in widgets and embeds, why modal dialogs are not traps and how to test for them.
WCAG 2.1.4 Character Key Shortcuts explained simply: why single-key shortcuts trip up voice and keyboard users, the three ways to comply and how to test.
WCAG 2.2.1 Timing Adjustable explained simply: session timeouts and other time limits, the turn off, adjust and extend options, exceptions and how to test.
WCAG 2.3.1 Three Flashes or Below Threshold explained simply: why flashing can cause seizures, the three-per-second rule and how to check video and animation.
WCAG 2.4.1 Bypass Blocks explained simply: skip links, landmarks and headings that let keyboard and screen reader users jump past repeated menus.
WCAG 2.4.12 Focus Not Obscured (Enhanced) explained simply: how it differs from 2.4.11, who it helps, CSS scroll-padding fixes and how to test for it.
WCAG 2.4.2 Page Titled explained simply: how to write unique, descriptive page titles, what to do in single-page apps and how to test your titles.
WCAG 2.4.3 Focus Order explained simply: why keyboard focus must follow a logical order, the tabindex and dialog mistakes that break it and how to test.
WCAG 2.4.4 Link Purpose (In Context) explained simply: why "click here" and "read more" fail, how to write link text that works and how to test it.
WCAG 2.5.1 Pointer Gestures explained simply: why pinch, swipe and multi-finger gestures need a single-tap alternative, with examples and how to test.
WCAG 2.5.2 Pointer Cancellation explained simply: why actions should happen on release, not on press, how people cancel accidental taps and how to test.
WCAG 2.5.3 Label in Name explained simply: why a control’s accessible name must contain its visible text, how voice control relies on it and how to test.
WCAG 3.1.1 Language of Page explained simply: why every page needs a lang attribute, which language code to use and how to check it in seconds.
WCAG 3.3.1 Error Identification explained simply: how to show form errors in text, tie them to fields, announce them and test your error messages.
WCAG 3.3.9 Accessible Authentication (Enhanced) explained: how it differs from 3.3.8, why image and personal-photo logins fail, fixes and how to test yours.
A practical guide to keyboard accessibility testing: what to check, the exact keys to use, and a component-by-component reference table mapped to WCAG.
WCAG 1.1.1 Non-text Content explained simply: how to write alt text for every kind of image, icon, chart and CAPTCHA, with code examples and a test routine.
WCAG 1.2.9 Audio-only (Live) explained simply: what counts as live audio, who it helps, how to add real-time captions or transcripts, and how to test it.
WCAG 1.3.2 Meaningful Sequence explained simply: why reading order matters, how CSS and layout tables break it, how to fix it and how to test your pages.
WCAG 1.4.1 Use of Color explained simply: why color cannot be the only cue, fixes for links, forms, charts and status icons, and how to test your pages.
WCAG 1.4.3 Contrast (Minimum) explained simply: the 4.5:1 and 3:1 ratios, what counts as large text, the exceptions, fixes and how to test your colors.
WCAG 1.4.8 Visual Presentation explained simply: the five rules for readable blocks of text, who they help, the CSS to meet them and how to test your pages.
WCAG 2.2.2 Pause, Stop, Hide explained simply: what moving and auto-updating content needs, the 5-second rule, carousel fixes and how to test your pages.
WCAG 2.2.3 No Timing explained simply: why time limits exclude people, the two exceptions, how it differs from 2.2.1, and how to remove timers from your site.
WCAG 2.5.8 Target Size (Minimum) explained simply: the 24 by 24 pixel rule, the spacing test, the five exceptions, CSS fixes and how to check your site.
WCAG 3.2.2 On Input explained simply: what counts as a change of context, who it helps, how to meet it with examples and code, and how to test your forms.
WCAG 3.3.2 Labels or Instructions explained simply: visible labels, format hints, grouped fields and required markers, with code examples and a test routine.
WCAG 3.3.8 Accessible Authentication (Minimum) explained: why password recall and CAPTCHAs fail, the four exceptions, login fixes and how to test yours.
WCAG 4.1.3 Status Messages explained simply: what counts, how to announce it with role status, alert, progressbar or aria-live, form errors and how to test.
Here's what you should know about WCAG 2.2: the nine new success criteria, what changed since WCAG 2.1, whether you must conform, and how to test your site.
What automated accessibility testing catches, what needs a human, and how to combine both into a repeatable process for finding and fixing WCAG issues.
A practical WCAG 2.2 AA checklist: the nine new success criteria, the one that was removed, and how to test your website against each requirement.
The free scan shows the issues on one public page. A 3-day free trial then monitors up to 500 URLs per domain and lets you apply fixes you approve, such as alt text, button names and the page language. Nothing is applied until you approve it.
Pro is a 3-day free trial, then $29 per domain per month or $199 per year. You add a card at checkout and are not charged until the trial ends. Cancel before then and you will not be charged.
Not ready for a subscription? A Page Report is $19 for one page, and a Domain Audit is $79 for up to 500 pages.