In the United States, an inaccessible website is a legal liability under Title III of the Americans with Disabilities Act (ADA). Courts have increasingly ruled that websites are "places of public accommodation" subject to ADA requirements — and the number of filed lawsuits has grown every year. This isn't a niche concern for enterprise companies. Small US businesses are being targeted specifically because they're less likely to have legal defenses in place.
The ADA Accessibility Lawsuit Boom in the US
The Scale of the Problem
ADA web accessibility lawsuits filed in US federal courts have grown significantly year-over-year. The retail sector consistently receives the most filings, followed by food services, entertainment, travel, and financial services. The typical pattern: a law firm using automated scanning tools identifies accessibility violations on thousands of websites, then sends demand letters or files suits. Many small US businesses settle for $10,000–$50,000 plus legal fees — often more than the cost of fixing the accessibility issues in the first place.
Why Small US Businesses Are Being Targeted
Large enterprises have legal teams and compliance budgets. Small businesses often don't — making them easier targets for settlement demands. If your US business has a public-facing website serving customers, you are potentially exposed, regardless of your business size or industry.
What Is WCAG and What Does Compliance Mean?
WCAG 2.1 vs WCAG 2.2: What Changed
WCAG (Web Content Accessibility Guidelines) 2.1 has been the legal standard referenced by most US courts. WCAG 2.2 (published October 2023) added new success criteria around focus appearance, dragging alternatives, and target sizes. In 2026, most legal standards reference WCAG 2.1 AA, but building to WCAG 2.2 AA future-proofs your compliance.
The Four Principles: POUR
- Perceivable: Users must be able to perceive all content — including users who are blind (screen readers) or deaf (captions for video).
- Operable: All functionality must be operable via keyboard alone — not just mouse. Users with motor disabilities navigate via keyboard, switch controls, or voice input.
- Understandable: Content and navigation must be understandable — clear language, predictable behavior, helpful error messages.
- Robust: Content must be interpretable by assistive technologies — proper semantic HTML, correct ARIA usage, no reliance on CSS-only communication.
Level A vs AA vs AAA
Level A: Minimum accessibility — failing this means the site is effectively unusable for users with disabilities. Level AA: The legal standard referenced by most US courts, DOJ guidelines, and Section 508. This is your target. Level AAA: Enhanced accessibility — aspirational for most, required for specific government and healthcare contexts.
The 10 Most Common Accessibility Failures on US Websites
1. Missing Alt Text on Images
Screen readers read alt text to describe images to blind users. Images without alt text are invisible to these users — and missing alt text is the single most commonly cited violation in US accessibility lawsuits. Fix: add descriptive alt text to every informative image (alt="Product photo of blue running shoe, side view"). Decorative images get an empty alt attribute (alt="") — this tells screen readers to skip them.
2. Poor Color Contrast Ratios
WCAG 2.1 AA requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text (18px+ or 14px+ bold) against its background. Light grey text on white (#999999 on #FFFFFF has a 2.85:1 ratio — failing) is the most common violation. Check: WebAIM's Contrast Checker.
3. Form Inputs Without Proper Labels
Every form input must have a programmatically associated label — either a <label for="..."> element or an aria-label attribute. Placeholder text alone is not a label. When a user tabs to an unlabeled input, screen readers announce "edit text" with no context about what to enter. This is both a usability failure and a common legal citation.
4. No Keyboard Navigation Support
Every interaction on your site — navigation menus, modal dialogs, dropdown selects, tabs, accordions, date pickers — must be fully operable via keyboard alone. Tab to focus elements, Enter/Space to activate, Escape to close modals, arrow keys for menus. Common failure: modal dialogs that can be opened via keyboard but cannot be closed without a mouse (focus trap inside modal, Escape key not bound).
5. Videos Without Captions
All pre-recorded video with audio must have synchronized captions for users who are deaf or hard of hearing. Auto-generated captions (YouTube's CC, etc.) do not meet WCAG requirements — they must be reviewed and corrected for accuracy. Live video must have live captions (or a pre-approved alternative).
6. Links With No Descriptive Text
"Click here", "Read more", "Learn more" as standalone link text are accessibility failures. Screen reader users often navigate by tabbing through links — hearing "read more, read more, read more" gives no context about what each link leads to. Fix: "Read more about our US e-commerce development services" or use aria-label to provide context for visually-styled icon buttons.
7. No Skip Navigation Link
Keyboard users must tab through every navigation item before reaching page content — on a site with 15 nav items, that's 15 keystrokes before they can start reading. A "Skip to main content" link (typically visually hidden but visible on focus) allows keyboard users to skip navigation and jump directly to content. One-line HTML addition, significant accessibility impact.
How to Audit Your Website's Accessibility Right Now
Free Automated Tools
- WAVE (webaim.org/wave): Browser extension that overlays accessibility errors and warnings on your page. Excellent visual feedback for non-developers.
- axe DevTools (Chrome Extension): Integrates into Chrome DevTools, provides actionable WCAG-mapped violations with code references.
- Google Lighthouse: Run from Chrome DevTools → Lighthouse tab. The Accessibility score (0–100) gives an overall picture. Aim for 90+.
What Automated Tools Miss
Automated tools catch approximately 30–40% of WCAG violations. The rest require human testing. The most critical manual tests: keyboard-only navigation through your entire site, screen reader testing with NVDA (Windows, free) or VoiceOver (macOS/iOS, built-in), and cognitive accessibility review (clear language, error messages, consistent navigation).
How I Build Accessible Websites from the Ground Up
Semantic HTML as the Foundation
Proper semantic HTML provides accessibility without ARIA: <nav> for navigation, <main> for page content, <header>/<footer> for landmarks, <button> for clickable actions (not <div onClick>), correct heading hierarchy (one <h1> per page, logical <h2>/<h3> nesting). This foundation means screen readers can navigate your page structure without any additional code.
ARIA Roles for Complex Components
When HTML semantics aren't sufficient — for custom dropdown menus, tab panels, modal dialogs, tooltips — ARIA attributes communicate roles, states, and properties to assistive technologies. The ARIA authoring practices guide (ARIA APG) documents the correct patterns for every common interactive widget. Following these patterns means your custom React components work correctly with every screen reader.
Accessibility + SEO: The Double Win You're Missing
Many accessibility improvements directly benefit SEO: descriptive alt text is image SEO, semantic heading hierarchy is content structure that Google reads, meaningful link text improves internal linking quality, and fast-loading accessible pages have better engagement metrics. The US businesses that invest in accessibility aren't just reducing legal risk — they're building better-ranking websites. This also has a huge overlap with Google's Core Web Vitals standards. Get an accessibility audit for your site →