In 2025, UsableNet, a company that tracks these cases, counted more than 5,000 lawsuits in the US over websites and apps that people with disabilities couldn’t use. 64% of them, nearly two in three, were against companies making less than $25 million a year. Seven in ten were against online stores. And being sued once doesn’t make you safe: 1,427 of those suits hit companies that had already been sued before.
The reason small sites get hit is simple. The most common problems are easy to find with free tools, they show up on almost every page, and in some states the law sets a price for each one. In California, the Unruh Civil Rights Act sets a minimum of $4,000 per offense, plus the other side’s attorney’s fees.
The good news: the failures behind most of these cases are well known, and most of them take minutes to fix.
#The 7 most common failures at a glance
The percentages come from WebAIM’s February 2026 scan of the top one million home pages. It found automatically detectable failures on 95.9% of them. Two of the failures below can’t be measured by an automated scan, so they have no number, but they show up in lawsuits all the time.
| Failure | How common | Who it blocks | Fix in minutes |
|---|---|---|---|
| Low-contrast text | 83.9% of home pages | Low-vision and older visitors | Darker text, at least 4.5:1 |
| Images without alt text | 53.1% | Blind people using screen readers | Describe the image; alt="" if decorative |
| Form fields without labels | 51% | Screen-reader and voice-control users | A label tied to every field |
| Checkout that needs a mouse | Not measurable by scans | Keyboard and switch users, blind users | Real buttons, visible focus, test with Tab |
| Videos without captions | Not measurable by scans | Deaf and hard-of-hearing people | Captions on every video with speech |
| Empty links and buttons | 46.3% / 30.6% | Screen-reader and voice-control users | Give every icon a name |
| No page language | 13.5% | Screen-reader users | <html lang="en"> |
#1. Low-contrast text

Still from our reel “Your website can get you sued”.
What it is. Light gray text on a white background, white text on a pale photo, a faint placeholder inside a form field. It looks elegant in a design file. It is the single most common failure on the web: 83.9% of home pages had it in WebAIM’s 2026 scan.
Why it matters. People with low vision, older visitors and anyone reading a phone outside in the sun simply can’t read it. If they can’t read the price or the shipping terms, they can’t buy.
The fix:
- Normal text needs a contrast ratio of at least 4.5:1 against its background. Large text (about 24px, or 19px bold) needs 3:1. This is WCAG 2.2 criterion 1.4.3.
- Buttons, input borders and focus outlines need at least 3:1 against what’s around them (1.4.11).
- Check your colors with a contrast checker (WebAIM has a free one, and Chrome DevTools shows the ratio when you inspect text). Usually the fix is one darker gray in your theme.
#2. Images without alt text

Still from our reel “Your website can get you sued”.
What it is. Alt text is the short description a screen reader reads out in place of an image. Without it, a blind visitor hears “image”, or worse, the file name: “IMG_4471 dot JPG”. More than half of home pages (53.1%) had at least one image missing it.
Why it matters. On a store, the product photo often is the product information: color, shape, what’s included. On a button made from an image, a missing alt means the button has no name at all.
The fix:
- Every image that carries meaning gets an
altthat says what it shows or does:alt="Blue ceramic mug, 12 oz", notalt="product image". - Purely decorative images get an empty
alt="", so screen readers skip them. Don’t leave the attribute out. - If an image is a link or a button, the alt describes where it goes or what it does:
alt="Cart", notalt="cart icon". - Text inside images (banners, promo graphics) must be repeated in the alt, or better, be real text.
#3. Form fields without labels

Still from our reel “Your website can get you sued”.
What it is. A field that only has gray placeholder text, or a label that looks right on screen but isn’t connected to the field in the code. A screen reader lands on it and says “edit text, blank”. 51% of home pages had at least one.
Why it matters. Sign-up, contact, search and checkout are all forms. If someone can’t tell which box is the email and which is the card number, they can’t finish.
The fix:
- Give every field a visible label connected in the code:
<label for="email">Email</label>with<input id="email">, or wrap the input inside the label. - A placeholder is not a label. It disappears when you start typing and is usually low contrast.
- Errors must say what is wrong in text (“Enter a card number with 16 digits”), not just turn the field red.
- Add
autocomplete(email,name,cc-number) so browsers and assistive tech can fill the fields for people.
#4. A checkout that needs a mouse

Still from our reel “Your website can get you sued”.
What it is. Many people can’t use a mouse: blind people, people with tremors or limited hand movement, people using a switch or voice control. They move through a page with the keyboard (Tab, Shift+Tab, Enter, Space, arrows) or with tools that act like one. Custom dropdowns, size pickers, date pickers, cookie banners and “Buy now” buttons built from a plain div often can’t be reached or pressed that way. Scanners can’t fully detect this. You have to try it.
Why it matters. If the keyboard can’t reach the pay button, the sale doesn’t happen. The best-known US case, Robles v. Domino’s, started exactly like this: a blind customer couldn’t order a pizza on the website or app.
The fix:
- Use real
<button>and<a href>elements. They work with the keyboard for free. Adivwith a click handler doesn’t. - Never remove the focus outline (
outline: none) without putting a clearly visible one back. People need to see where they are. - Make sure Tab moves in a logical order, that nothing traps the focus, and that pop-ups close with Esc and return the focus to where it was.
- Test it: put the mouse away and buy something on your own site, from the home page to the confirmation.
#5. Videos without captions

Still from our reel “Your website can get you sued”.
What it is. A product video, a hero video or a recorded webinar with speech and no captions.
Why it matters. Deaf and hard-of-hearing visitors miss everything that’s said. So does anyone watching with the sound off, which on a phone is most people.
The fix:
- Add captions to every pre-recorded video with speech (WCAG 1.2.2). YouTube, Vimeo and most video hosts let you upload or edit them.
- Auto-generated captions are a start, not the finish. Read them once and fix names, prices and numbers.
- For audio-only content like a podcast, publish a transcript.
- Don’t autoplay video with sound, and give any moving video a pause button.
#6. Empty links and buttons
What it is. An icon with no text: the magnifying glass for search, the cart, the hamburger menu, social media icons, the “X” that closes a pop-up. On screen they are obvious. To a screen reader they are “link” or “button”, with nothing after it. WebAIM found empty links on 46.3% of home pages and empty buttons on 30.6%.
Why it matters. If the cart button has no name, a blind shopper can’t find the cart. Voice-control users can’t say “click cart” either.
The fix:
- Give icon-only buttons a name:
<button aria-label="Open cart">, or visually hidden text inside the button. - Make link text say where it goes. “Shipping policy” works on its own; “click here” doesn’t.
- If an SVG icon sits next to visible text, hide the icon from screen readers with
aria-hidden="true"so it isn’t read twice.
#7. No page language, and headings out of order
What it is. A page with no lang attribute on the <html> tag (13.5% of home pages), and headings picked for their size instead of their place in the page.
Why it matters. The lang attribute tells a screen reader which voice and pronunciation to use. Without it, a Spanish page can be read with an English voice, and it’s very hard to follow. Headings are how screen-reader users skim: they jump from heading to heading the way you scan with your eyes.
The fix:
- Set the language on every page:
<html lang="en">, orlang="es"on your Spanish pages. If a paragraph is in another language, mark it with its ownlang. - Use one H1 that says what the page is about, then H2 and H3 in order, without skipping levels for styling. One H1 isn’t a strict WCAG rule, but it’s the clearest structure.
- Style headings with CSS, not by picking a smaller or bigger heading tag.
#Why overlay widgets won’t save you

Still from our reel “Your website can get you sued”.
Accessibility overlays are scripts you paste into your site. They add a floating icon with options like bigger text or high contrast, and some promise to fix your site automatically with AI. They’re tempting: one line of code, a monthly fee, a “compliant” badge.
The evidence says otherwise:
- The FTC case. In January 2025, the US Federal Trade Commission announced that accessiBe, one of the best-known widget makers, would pay $1 million to settle charges that it misrepresented its AI tool’s ability to make any website compliant with WCAG. The FTC also alleged that accessiBe passed off reviews and articles it had influenced as independent opinions. The order became final in April 2025 and bars the company from making those compliance claims without evidence.
- The lawsuits. In UsableNet’s 2025 data, lawsuits against companies that already had a widget installed add up to more than 1,400 over the year (1,416, adding up its monthly figures). Its conclusion: widgets usually don’t fix the code-level problems underneath. UsableNet sells accessibility services itself, so read that with some care. But the FTC case points the same way.
The reason is technical. A widget runs on top of your page after it loads. It can’t reliably know what your product photo shows, which label belongs to which field, or why your custom checkout button ignores the keyboard. Those fixes belong in the code. A widget can sit on top of an accessible site, but it can’t be the fix.
#Where the law applies
United States: the ADA and state laws
- ADA Title III prohibits disability discrimination by businesses open to the public. The Department of Justice’s position, repeated in its March 2022 guidance, is that this covers what businesses offer on the web. The DOJ hasn’t issued a technical standard for private business websites. It calls the Web Content Accessibility Guidelines (WCAG) “helpful guidance”. In practice, lawsuits and settlements usually measure sites against WCAG Level AA, but WCAG itself isn’t the law for private businesses.
- Online-only businesses are a gray area. A federal appeals court held in 2019 that the ADA covered Domino’s website and app, because they were tied to its restaurants. Other courts, including a California appeals court in 2022, have said a website on its own isn’t covered. Lawsuits keep coming either way, and fighting one costs far more than fixing the site.
- Under the federal ADA, a private plaintiff can’t win money damages, only a court order to fix the site plus attorney’s fees. Money comes from state laws.
- California’s Unruh Civil Rights Act treats an ADA violation as an Unruh violation and sets damages of at least $4,000 per offense, plus attorney’s fees. Whether every visit counts as a separate offense is disputed: in the Domino’s case, the federal court limited the damages to a single $4,000. New York is the other big state for these suits; UsableNet says it leads the country in filings.
European Union: the European Accessibility Act
- Since 28 June 2025, the European Accessibility Act (Directive 2019/882) applies to a list of services provided to consumers, including e-commerce: websites and apps where consumers buy things. Each EU country enforces it through its own national law.
- Microenterprises providing services are exempt: fewer than 10 people and annual turnover or balance sheet of no more than €2 million. Products are a different story, and the exemption doesn’t cover them.
- Germany implements it through the Barrierefreiheitsstärkungsgesetz (BFSG). Offering a service that doesn’t meet the requirements can be fined up to €100,000. Lesser violations, like missing information, go up to €10,000.
- If you sell to consumers in the EU from outside it, assume the rules apply to you. How authorities will enforce them against sellers based abroad is still unclear.
Dominican Republic
- Ley 5-13 on disability (2013) sets a national policy of universal accessibility that includes information and communication technologies, and makes the national disability council (CONADIS) responsible for promoting accessible electronic access.
- NORTIC B2, issued in 2017 by the government’s technology office (OPTIC, now OGTIC) with CONADIS, sets web accessibility requirements for government portals.
- We couldn’t confirm any rule that requires private websites in the Dominican Republic to be accessible, or any penalty for them. Some private companies have adopted NORTIC B2 voluntarily; the savings and loan association APAP was the first, in 2019.
- If you sell to customers in the US or the EU, their rules travel with them.
#The checklist we use on every client site
These are the checks we run before any site we build goes live. Each one is testable, and none of them needs a paid tool:
- Contrast. Body text is at least 4.5:1 against its background; large text at least 3:1. No light gray on white.
- Controls are visible. Buttons, field borders and the focus outline are at least 3:1 against their background.
- Images. Every meaningful image has alt text that says what it shows or does; decorative images use
alt=""; text in images is repeated in the alt. - Forms. Every field has a visible label tied to it in the code. Placeholders are never the only label.
- Errors. Error messages say in words what to fix, next to the field, and never rely on color alone.
- Keyboard. You can reach and use every link, menu, pop-up and button, and finish the whole checkout, with Tab, Enter, Space and Esc only. Nothing traps the focus.
- Focus. A clearly visible focus outline on everything you can tab to.
- Video. Every video with speech has checked captions; no video autoplays with sound.
- Names. Every icon button and link has a name a screen reader can read (
aria-labelor hidden text); no “click here”. - Structure. One H1 per page, headings in order, and the page language set in
<html lang>. - Zoom. The page still works at 200% zoom and on a 320px-wide screen, with nothing cut off or overlapping.
- Test, don’t trust a widget. Lighthouse or axe shows no accessibility errors on the home page, a product or service page, and checkout, and a person has done the manual checks below.
How to test in 10 minutes
- Automated scan (2 minutes). In Chrome, open DevTools, go to Lighthouse and run the Accessibility audit. Or install the free axe DevTools extension. Run it on your home page, one product page and checkout. Automated tools only catch part of the problems, so a perfect score isn’t the end.
- Keyboard only (3 minutes). Put the mouse away. Press Tab from the top of the page and try to buy something. Can you always see where you are? Can you open the menu, pick a size, close the cookie banner and reach the pay button?
- Zoom (1 minute). Zoom the browser to 200%, and narrow the window to phone width. Text should reflow, not get cut off or overlap.
- Screen reader (4 minutes). On Windows, install NVDA (free). On a Mac, press Cmd+F5 to turn on VoiceOver; on an iPhone, it’s under Settings › Accessibility. Close your eyes, or don’t look, and listen: jump between headings (H in NVDA, VO+Cmd+H in VoiceOver), then tab through a form. Does every image, field and button make sense?
If something fails, write it down with the page and what you pressed. That list is your fix list, and most items on it will be small.
#How Altamar can help
If you want a second pair of eyes, one of our engineers can go through your site with you: run the checklist, walk the checkout with a keyboard and a screen reader, and tell you what to fix first. If it’s a quick fix, we’ll show you how to do it yourself. Book a free call.
#References
All checked on November 12, 2026.
- WebAIM, The WebAIM Million: the 2026 report on the accessibility of the top 1,000,000 home pages (February 2026 scan): webaim.org
- UsableNet, 2025 Year-End Digital Accessibility Lawsuit Report (data from January 1 to December 15, 2025): usablenet.com · plain-text version
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2: w3.org; Understanding contrast (minimum): w3.org; Easy checks: w3.org
- US Department of Justice, Guidance on Web Accessibility and the ADA (March 18, 2022): ada.gov
- 42 U.S.C. §12188, ADA Title III remedies: law.cornell.edu
- Robles v. Domino’s Pizza, 913 F.3d 898 (9th Cir. 2019): ca9.uscourts.gov; BCLP on the Unruh damages ruling in the same case: bclplaw.com
- Martinez v. Cot’n Wash (Cal. Ct. App. 2022), Norton Rose Fulbright summary: nortonrosefulbright.com
- California Civil Code §51 and §52 (Unruh Civil Rights Act): §51 · §52
- FTC, proposed order against accessiBe (January 3, 2025) and final order (April 22, 2025): ftc.gov
- Directive (EU) 2019/882, the European Accessibility Act: eur-lex.europa.eu; Article 4, microenterprise exemption: legislation.gov.uk; European Commission overview: commission.europa.eu
- Germany, BFSG §37 (fines, in German): gesetze-im-internet.de
- Dominican Republic, Ley 5-13 sobre Discapacidad (in Spanish): drlawyer.com; NORTIC B2:2017 (in Spanish): dgjp.gob.do; Law Office of Lainey Feingold, country summary: lflegal.com; APAP and NORTIC B2 (in Spanish): elnuevodiario.com.do
- NV Access, NVDA screen reader: nvaccess.org






