The lawsuit arrived on a Tuesday morning. A plaintiff’s attorney filed a demand letter claiming the company’s website violated the Americans with Disabilities Act because screen readers couldn’t navigate it properly. The company had never considered accessibility, had no documentation of any efforts, and faced a settlement demand of $15,000 plus attorney fees.
They paid because fighting it would cost more. This happens to small and mid-sized businesses daily across the United States.
WebAIM’s analysis of one million home pages found that 95.9% had detectable WCAG failures. The most common issues: missing alternative text for images affecting 55% of pages, empty links at 50%, missing form labels at 46%, and insufficient color contrast at 81%.
Web accessibility lawsuits under ADA Title III reached over 4,000 federal filings annually in recent years, with additional thousands in state courts.
For the Business Owner
Do I actually need to worry about this, or is it just something big companies deal with?
You run a small business. You have a website that someone built three years ago. You’ve never thought about accessibility because you assumed it was a concern for government agencies and Fortune 500 companies.
Here’s the uncomfortable reality: plaintiff’s attorneys specifically target small businesses because you’re easier to settle with than large corporations with legal teams.
Understanding Your Legal Exposure
The ADA applies to places of “public accommodation,” and courts have increasingly interpreted this to include commercial websites. The legal theory is that your website is an extension of your business. If your physical location must be accessible, so must your digital presence.
California, New York, and Florida see the highest volume of accessibility lawsuits. If your business operates in these states or your website is accessible to residents there, you face higher risk. But no state is exempt.
Small businesses are not exempt by size. There’s no “too small to sue” threshold. Plaintiff’s attorneys often target smaller businesses because they lack resources for prolonged litigation and settle quickly.
The good news: documented good-faith efforts at accessibility significantly reduce legal exposure. Courts and settlement negotiations favor businesses that can show they’ve tried to comply.
Perfect compliance is expensive. Reasonable effort is not. Reasonable effort provides significant legal protection.
What “Good Faith” Compliance Looks Like
Run a free accessibility scan on your website using tools like WAVE, axe DevTools, or Lighthouse. These catch obvious issues: missing alt text, color contrast problems, form labels. Fix the issues they identify. Document that you did so.
Add an accessibility statement to your website. This page describes your commitment to accessibility, what standards you’re working toward, and how users can report problems. Include contact information for accessibility feedback.
Address the highest-impact issues first. Missing image alt text, empty links, form fields without labels, and color contrast problems affect the most users and trigger the most automated detection.
Get a professional accessibility audit if you can afford one. Audits cost $1,500-$10,000 depending on site complexity. The audit itself is evidence of good faith even if you haven’t fixed everything it identifies.
Doing something is dramatically better than doing nothing. Start with free tools and fix what they find.
Cost Reality Check
DIY accessibility improvements using free tools: $0 plus your time. For a simple website, expect 4-20 hours depending on your technical comfort level.
Professional remediation for a typical small business website: $2,000-$8,000 depending on site size and issue complexity. Ongoing monitoring adds $500-$2,000 annually.
Overlay tools that claim to make sites accessible with one line of code: $500-$1,500 annually. These tools are controversial. Accessibility advocates generally criticize them as inadequate. Some plaintiff’s attorneys specifically target sites using overlays.
Settling a lawsuit: $5,000-$50,000 plus your own legal fees. Attorney fees alone often run $5,000-$15,000 even for quick settlements.
Fixing your website costs less than getting sued. This isn’t complicated math.
Sources:
- WebAIM Million Report: webaim.org
- ADA lawsuit statistics: UsableNet, Seyfarth Shaw annual reports
- Settlement ranges: Published case data and legal industry surveys
For the Web Developer
What are the actual technical requirements, and how do I prioritize implementation?
You’ve been asked to “make the website accessible” without clear budget, timeline, or specification of what “accessible” means. The client expects this to be a simple task. You know it’s more complex than they understand.
WCAG 2.1 Level AA is the standard most referenced in legal documents and settlements.
Technical Requirements Overview
WCAG 2.1 Level AA is the practical compliance target for most commercial websites. It includes Level A requirements plus additional criteria that address common assistive technology needs.
The Perceivable principle requires that all content be presentable in ways users can perceive. This means alternative text for images, captions for videos, sufficient color contrast, and content that doesn’t rely solely on color to convey meaning.
Technical implementation: ensure all img tags have meaningful alt attributes. Contrast ratios must meet 4.5:1 for normal text and 3:1 for large text.
The Operable principle requires that all functionality be usable via various input methods. This means keyboard navigation for all interactive elements and visible focus states.
Technical implementation: ensure all interactive elements are reachable via tab key, focus states are visible, and skip links exist for main content.
The Understandable principle requires that content and interface be comprehensible. This means readable text, predictable behavior, and input assistance.
Technical implementation: use proper heading hierarchy, label all form fields, provide error messages that explain what went wrong.
The Robust principle requires that content work across different browsers and assistive technologies. This primarily means proper semantic HTML and ARIA usage.
Prioritized Implementation Approach
Start with automated testing to identify the largest issue categories. Tools like axe DevTools, WAVE, or Lighthouse catch 30-50% of WCAG violations.
Priority 1 issues are most frequently cited in lawsuits: missing alt text on images, forms without proper labels, insufficient color contrast, keyboard traps, and missing page language declaration.
Priority 2 issues affect significant user groups but are less commonly cited: missing skip links, improper heading hierarchy, videos without captions, and focus order that doesn’t match visual order.
Priority 3 represents full compliance but lower litigation risk: cognitive accessibility features, advanced ARIA patterns, and enhanced navigation features.
Test with keyboard only first. If you can’t use the site without a mouse, neither can many assistive technology users.
Testing and Validation
Automated testing catches about 30% of accessibility issues. Essential tools include axe DevTools browser extension, Lighthouse for quick audits, and pa11y for command-line testing in CI/CD pipelines.
Manual testing catches issues automation misses: logical reading order, meaningful alt text content, appropriate heading use, and context-dependent issues. Plan 2-4 hours of manual review for every 10 pages.
Screen reader testing validates real-world usability. NVDA is free for Windows. VoiceOver is built into Mac and iOS. At minimum, navigate your key user flows with a screen reader.
User testing with actual disabled users reveals issues no testing tool catches. Organizations like Fable and AccessWorks connect you with disabled testers.
Automated tools find issues. Manual testing finds problems. User testing finds failures.
Sources:
- WCAG 2.1 specification: W3C
- Automated testing limitations: Deque Systems research
- Screen reader usage statistics: WebAIM survey
For the Marketing Manager
How do I explain accessibility requirements to leadership and get budget approved?
Your CEO thinks accessibility is a “nice to have” feature you can address eventually. Your legal team hasn’t flagged it because they don’t know enough about web technology to understand the risk. You’re stuck between knowing there’s a problem and lacking authority to fix it.
Here’s how to build the business case in terms leadership responds to.
Building the Business Case
Lead with legal risk quantification. “Our website currently violates ADA accessibility standards that have been the basis for over 4,000 federal lawsuits annually. Companies in our industry have faced settlements ranging from $10,000 to $75,000 plus legal fees.”
Add competitive differentiation. An accessible website reaches 15-20% more potential customers, including the 61 million American adults living with disabilities and their families who consider accessibility in purchasing decisions.
Frame investment efficiency. “Proactive remediation costs $3,000-$8,000. Reactive defense after a demand letter costs $15,000-$50,000. The question isn’t whether to address accessibility but whether to address it before or after we’re forced to.”
Connect to brand values if your company claims to value inclusion, diversity, or customer service. Inaccessible websites contradict those stated values.
Presenting the Options
Create three options with clear trade-offs.
Option 1, minimal: DIY improvements using free tools. Cost is internal time only. Risk reduction is moderate. Legal protection comes from documented effort, not comprehensive compliance.
Option 2, moderate: professional audit plus remediation of critical issues. Cost is $5,000-$15,000. Risk reduction is significant. Legal protection is strong.
Option 3, comprehensive: full audit, complete remediation, ongoing monitoring, and training. Cost is $15,000-$30,000 initially plus $2,000-$5,000 annually. Risk reduction is maximum.
Recommend Option 2 for most situations. It provides substantial protection at reasonable cost.
Managing Ongoing Compliance
Accessibility isn’t a one-time project. Every new page, feature, or content update can introduce new issues. Build accessibility checkpoints into your content and development workflows.
Train content creators on accessibility basics: meaningful alt text, proper heading structure, descriptive link text, caption requirements for video.
Schedule quarterly accessibility scans to catch regressions. New plugins, theme updates, and content changes introduce new issues over time.
Accessibility is ongoing maintenance, not a one-time fix. Budget accordingly.
Sources:
- Disability statistics: CDC disability prevalence data
- Legal settlement data: UsableNet annual reports
- Market opportunity research: Various accessibility ROI studies
The Bottom Line
Website accessibility is a legal requirement for most commercial websites under current ADA interpretation. The majority of websites fail to meet minimum standards, creating legal exposure that plaintiff’s attorneys actively exploit.
The path forward is clear: assess your current state using free tools, address obvious issues, document your efforts, and consider professional remediation if budget allows.
You don’t need a perfect website. You need a documented effort to make it accessible.
Sources:
- WebAIM Million Report: webaim.org
- WCAG 2.1 Guidelines: W3C
- ADA lawsuit statistics: UsableNet, Seyfarth Shaw annual reports
- Remediation cost benchmarks: Industry surveys and vendor data