Skip to main content
guide8 min readUpdated: January 2025

Serial Filers and the ADA Enforcement Gap: Why Disabled Users Bear the Burden

Understand the accessibility enforcement gap in ADA Title III. Why enforcement falls to disabled users, and why serial filers highlight systemic accessibility failures.

The Fundamental Problem: No Federal Enforcement Mechanism

Most federal civil rights laws include federal enforcement. When a business violates the Civil Rights Act, the Department of Justice can investigate and bring enforcement actions. When businesses violate OSHA regulations, federal inspectors check compliance. But ADA Title III, which covers public accommodations, has a peculiar design: there is no federal enforcement agency actively ensuring compliance. The Department of Justice can investigate complaints after the fact, but does not conduct proactive audits or inspections. The answer: you do. People with disabilities. If a website is inaccessible, the enforcement mechanism is entirely individual: There is no government-funded accessibility auditor. There is no federal inspector checking websites. There is no proactive enforcement. It all depends on individual users identifying barriers and pursuing remedies. This creates what accessibility advocates call an "enforcement gap":

1

A person with a disability encounters the barrier

2

They document it (if they have resources and technical knowledge)

3

They contact the website owner

4

If the owner refuses, they can sue individually

5

Or they file a complaint with the DOJ, hoping investigation eventually occurs

6

Thousands of websites remain inaccessible

7

Most website owners never face consequences

8

Many aren't even aware their sites are inaccessible

9

No mechanism exists to systematically improve web accessibility

10

Compliance is entirely optional without individual pressure

What Are Serial Filers and Why Do They Exist?

A "serial filer" refers to a person with disabilities who files accessibility complaints against multiple websites, often many websites over time. Some file against dozens or even hundreds of different website operators. Serial filers exist because: Serial filers are not:

1

Barriers Are Everywhere: Inaccessible websites are ubiquitous. A person using a screen reader will encounter dozens of broken websites in a single day of normal internet use

2

No Alternative Enforcement: Since the government doesn't proactively enforce, individual complaints are the only mechanism that creates pressure

3

Accessibility Advocates Use Legal Tools: People committed to accessibility access use the legal system because it's the only tool available

4

Systemic Pattern: When the same barriers repeat across websites (missing alt text, keyboard traps, poor contrast), they file similar complaints

5

Pattern-Based Filing: Some strategically target specific types of violations (e.g., e-commerce sites that all use the same template with similar barriers)

6

Being frivolous or vexatious (they're filing against legitimately inaccessible sites)

7

Filing against the same company repeatedly (they typically target different businesses)

8

Filing fake or exaggerated claims (barriers are real)

9

Making up violations (accessibility standards are technical and verifiable)

10

Gaming the system (they're using the legal system as designed when no other option exists)

How the Serial Filer Stigma Harms Disabled Users

As serial filing has become visible, website operators and some legal observers have pushed back, framing individual enforcement as a problem: This framing ignores who's actually being harmed: The "serial filer" backlash creates a system where disabled users have MORE barriers, not fewer: Because there's no government enforcement, a disabled person who wants to use an inaccessible website faces a choice: This places an enormous burden on disabled people. You shouldn't need to become a lawsuit party to access a retail website or bank account. The serial filer narrative reframes accessibility discrimination as a problem with disabled people, not with website owners: When disabled users know they'll be labeled "serial filers" or frivolous complainers: The most important point: multiple filers against different websites is NOT evidence of frivolous litigation. It's evidence that:

1

"Serial filers are abusing the legal system"

2

"These are frivolous lawsuits for quick settlements"

3

"We can't afford to defend ourselves against individual complaints"

4

"This is why we need WCAG to be clarified" (implying the current law is too broad)

5

Website owners respond to serial filers by becoming defensive and resistant to complaints

6

Rather than fixing accessibility, they hire lawyers to fight claims

7

They may retaliate against people who complain

8

The costs of litigation discourage individual complaints

9

Result: barriers remain, often for years, while legal battles continue

10

Accept the barrier and go without the service

11

Become a litigant and hire an attorney

12

These are the only options available

13

There is no middle ground where a government agency fixes the problem

14

Instead of asking "Why are so many websites inaccessible?" we ask "Why are so many disabled people suing?"

15

Instead of demanding government enforcement, we demonize disabled people for using the legal system

16

This deflects from the real problem: widespread accessibility discrimination

17

It becomes another form of disability discrimination dressed as concern about legal abuse

18

They're less likely to file complaints about barriers they experience

19

They self-censor to avoid being seen as "that person who sues"

20

They internalize the stigma and blame themselves instead of the website

21

Fewer complaints are filed, so barriers persist unchecked

22

Website owners have even less pressure to improve

23

Widespread accessibility discrimination exists

24

Most website owners are not voluntarily complying

25

The enforcement gap is real and harmful

26

Without individual legal action, barriers would be even more endemic

27

The legal system is working as designed when no federal enforcement exists

The Real Problem: Systemic Enforcement Failure

In other civil rights contexts, federal enforcement creates pressure for compliance: These agencies don't wait for individuals to file complaints. They conduct audits, inspections, and investigations. This creates systematic pressure for compliance. For web accessibility, the approach is different: Some argue the enforcement gap exists because: None of these justify the complete absence of proactive federal enforcement.

1

Housing discrimination: HUD investigates fair housing complaints

2

Employment discrimination: EEOC investigates and can bring enforcement actions

3

Voting access: DOJ investigates voting rights violations

4

Workplace safety: OSHA inspects workplaces proactively

5

No federal inspectors audit websites

6

No proactive investigations for compliance

7

The DOJ responds to complaints but has limited resources

8

No systematic data collection on accessibility failures

9

Result: Website owners have minimal pressure to comply voluntarily

10

"There are too many websites to audit" — But that's an argument for MORE resources, not less enforcement

11

"Technology changes too fast" — Yet accessibility standards remain relatively stable

12

"It's unclear what compliance means" — WCAG provides clear guidance

13

"Websites are private property" — They're public accommodations when they serve the public

The Real Cost: Disabled Users Navigate More Barriers

The enforcement gap creates a terrible paradox for disabled users: In a typical day using the web, a disabled person might encounter: For each barrier, the disabled user has limited options: accept discrimination, file a complaint and hope for investigation, or hire a lawyer and become a litigant.

1

The Problem: Inaccessible websites are ubiquitous

2

The Reason: Most website owners face no consequences for non-compliance

3

The Mechanism: No federal enforcement agency ensures compliance

4

The Result: Individual disabled people must litigate to access basic services

5

The Backlash: Those who do litigate are stigmatized as "serial filers"

6

The Outcome: Fewer disabled people file complaints, so even fewer websites improve

7

A retailer's website with missing product descriptions (can't purchase)

8

A bank's site with keyboard traps (can't access accounts)

9

A healthcare provider's portal without captions (can't understand instructions)

10

Government websites that are technically required to be accessible but aren't

11

Social media platforms with poor compatibility with screen readers

Why "Serial Filers" File Against Similar Barriers

Many inaccessible websites share the same barriers because: Some disability rights advocates strategically file complaints against patterns of violations: This is not frivolous. It's highlighting systemic accessibility failures that a federal enforcement agency would address proactively.

1

They use similar templates or platforms with the same accessibility problems

2

Common mistakes repeat across the web (missing alt text, poor contrast, keyboard traps)

3

Most developers don't prioritize accessibility

4

Accessibility standards aren't widely taught or followed

5

E-commerce sites using the same shopping platform

6

Financial institutions with similar barriers

7

Websites using inaccessible design frameworks

8

This draws attention to systemic problems, not just individual sites

What Real Accountability Would Look Like

Effective accessibility compliance would require: With real federal enforcement: Without federal enforcement, the current system relies on: This is not a sustainable or just system.

1

A federal agency with authority and resources to audit websites

2

Regular proactive inspections of high-traffic websites

3

Clear penalties for non-compliance (not just lawsuits)

4

Technical guidance and resources to help sites achieve compliance

5

Public reporting on compliance across industries

6

Disabled users wouldn't need to become litigants

7

Website owners would know compliance is expected and enforced

8

Most barriers would be fixed before disabled users encountered them

9

Individual complaints would supplement, not replace, enforcement

10

There would be no "serial filer" problem because barriers would be rare

11

Disabled users identifying barriers (unpaid enforcement labor)

12

Disabled users contacting website owners (free compliance consulting)

13

Disabled users suing when owners refuse to comply (litigation at individual expense)

14

Stigmatizing those who do sue as "frivolous" or "serial filers"

Why Individual Enforcement Matters (Until the System Changes)

Until the federal government enforces web accessibility, individual complaints are the only mechanism that creates pressure for change. People who file multiple complaints are: Many serial filers work with disability organizations and are motivated by: They're not motivated by getting rich on settlement money. They're motivated by making the web accessible. Instead of stigmatizing "serial filers," we should:

1

Asserting their legal rights under disability rights law

2

Exercising the enforcement mechanism available to them

3

Creating pressure for compliance when no federal agency will

4

Setting precedent that accessibility discrimination has consequences

5

Advocating for broader systemic change

6

Personal experience of discrimination

7

Commitment to accessibility as a civil right

8

Desire for systemic change

9

Making examples of businesses that refuse compliance

10

Demand federal enforcement resources

11

Hold website owners accountable for intentional non-compliance

12

Support disability advocacy organizations bringing strategic cases

13

Recognize that multiple complaints indicate systemic failure, not individual abuse

14

Reframe the debate from "too many lawsuits" to "too little enforcement"

Document Systemic Barriers

Barriers you encounter aren't isolated. They're part of a systemic problem. Get an audit identifying specific WCAG violations for your records.

Put This Knowledge Into Practice

Use A11yScan to test your website against WCAG standards automatically.

Start Free Scan

Frequently Asked Questions

Why does web accessibility matter?

Web accessibility ensures people with disabilities can perceive, understand, navigate, and interact with websites. It also reduces legal risk and improves user experience for everyone.

What is WCAG?

WCAG (Web Content Accessibility Guidelines) are international standards published by the W3C that define how to make web content more accessible to people with disabilities.

More Resources

checklist

Complete WCAG 2.1 AA Checklist for Web Accessibility

statistics

Web Accessibility Lawsuit Statistics 2024: Complete Analysis

guide

ADA Website Requirements 2024: Complete Compliance Guide

tutorial

Complete Screen Reader Testing Guide for Accessibility

statistics

2024 Accessibility Lawsuit Trends: What the Data Shows

guide

2025 Accessibility Litigation Predictions: What to Expect

guide

What to Do If You Receive an Accessibility Demand Letter | A11yscan

guide

Why WCAG Accessibility Overlays Fail | A11yscan

guide

Accessibility as Enterprise Risk Management: 2024-2025 Analysis

guide

Accessibility Statement: Legal & User Importance

statistics

ADA Website Lawsuits Surge 37% in 2025: Legal Risks, Trends, and Business Impact | A11yscan

guide

The ADA & Your Website: Legal Requirements in 2025

guide

ADA Title III & Web Accessibility: What You Need to Know | A11yscan

guide

Alt Text That Actually Works: Writing for Screen Readers

guide

AODA: Accessibility for Ontarians with Disabilities Act | A11yscan

guide

AODA: Accessibility for Ontarians with Disabilities Act | A11yscan

guide

ARIA Labels & Semantic HTML: Building for Screen Readers

guide

Accessibility Conformance Reports (ACRs): Legal Guide

guide

The CEO\'s Guide to ADA Compliance - A11yscan Blog

guide

Corporate Legal Risk: Your Website Might Be Your Biggest Liability

guide

How to Document Website Accessibility Barriers

guide

E-Commerce Accessibility: Why Your JavaScript Catalog Is Breaking Millions of Sales

guide

Focus Management & Tab Order: Fixing Keyboard Navigation

guide

Forms & Input Accessibility: The #1 ADA Violation

guide

Remediation vs. Retrofit vs. Rebuild: Strategic Accessibility

guide

Restaurant Websites & Accessibility: Why Beautiful Menus Fail

guide

Accessibility Audits: What a Proper Audit Includes

guide

TikTok\'s Captions: How Social Media Accidentally Normalized Accessibility

checklist

The 10-Point WCAG Pre-Launch Checklist - A11yscan Blog

statistics

WCAG Lawsuit Legal Terms: Standing, Nexus, Harm & Damages

guide

California Web Accessibility Laws: Unruh Act, AB 434, AB 1757 | A11yscan

guide

Color Contrast: The Foundation of Visual Accessibility

guide

Designing for Blind Users: Screen Reader Accessibility

guide

Designing for Cognitive Disabilities: Clear & Simple Navigation

guide

Designing for Deaf Users: Audio Accessibility

guide

Designing for Low Vision Users: Vision Accessibility

guide

Designing for Motor Disabilities: Keyboard & Switch Access

guide

Designing for Neurodivergent Users: Accessibility Beyond Disability

guide

Your Rights as a Person with Disabilities: Web Accessibility Protections

guide

Div Soup: Why Pretty But Broken Websites Cost More Than You Think | A11yscan

guide

How to Document and Report Web Accessibility Issues

guide

European Accessibility Act (EAA): EU Digital Accessibility Requirements | A11yscan

guide

Finding Legal Support for Web Accessibility Claims

guide

Florida Web Accessibility Laws: ADA Title III, Section 508, and Florida Standards | A11yscan

guide

Keyboard Navigation: Making Your Site Usable Without a Mouse

guide

Defending Against Accessibility Claims: Good Faith Strategies

statistics

Major 2024 Accessibility Settlements: Case Studies and Lessons

guide

Maps & Data Visualizations Accessibility: Charts, SVG, Colorblindness

guide

Mobile Accessibility: Why 40% of Your Users Can\'t Use Your Site on Mobile | A11yscan

guide

NYCHRL: New York City Digital Accessibility Rights Law | A11yscan

guide

PDF Accessibility: Tagging, Forms, OCR & Legal Requirements

guide

Platform Liability: When Third Parties Create Accessibility Barriers

guide

You Used a Template. Your Site Is Still Broken. Your Liability Is Still Real. | A11yscan

guide

SEO and WCAG: How Accessibility and Search Rankings Are Linked | A11yscan

guide

The Silver Economy & Web Accessibility: Why Seniors Need Better Website Design | A11yscan

guide

Temporary Disabilities & Accessibility: Broken Mice, Injured Arms, Lost Glasses | A11yscan

guide

Understanding Your Rights as a User Requiring Web Accessibility Features

guide

Video & Multimedia Accessibility: Captions, Descriptions, Transcripts

guide

Understanding WCAG 2.1 Levels: A vs AA vs AAA

guide

WCAG 2.1 vs 2.2: What Changed and Why It Matters for Your Compliance | A11yscan

guide

You Sell Products, Not Websites. But Your Website Still Needs to Be Accessible. | A11yscan

Ready to Improve Your Accessibility?

Start with a free accessibility scan and get actionable insights immediately.

Start Free Accessibility Scan