Most organizations first learn that their PDFs are an accessibility problem when a demand letter arrives in the mail. These letters allege that inaccessible documents on your website deny people with disabilities equal access, and they ask you to fix the problem — usually alongside a request to settle. This article explains the demand-letter playbook, why PDFs are such a common target, and the concrete steps that lower your exposure before a letter ever shows up.
This is general information, not legal advice.
The demand-letter playbook
A demand letter is a pre-litigation tool. Rather than filing a lawsuit immediately, a plaintiff's firm sends a letter describing an accessibility barrier its client encountered and inviting the business to resolve the matter. The structure is fairly consistent:
- The allegation. A person with a disability — often a screen-reader user — tried to use your website or a document on it and couldn't.
- The legal hook. The letter cites the ADA (and sometimes state laws like California's Unruh Act) and frames the barrier as a denial of equal access.
- The standard. It points to WCAG 2.1 Level AA as the benchmark for what "accessible" means, because there is no separate federal technical rule for private businesses under ADA Title III.
- The ask. Remediate the barriers, and resolve the claim — frequently including attorneys' fees.
The volume here is not trivial. Industry trackers report that thousands of digital accessibility lawsuits and demand letters are filed each year, and document-level barriers are an increasingly common thread.
What demand letters typically allege
PDF-related letters tend to allege a recognizable set of failures, because these are the barriers a screen reader hits immediately:
- Scanned or image-only documents that contain no machine-readable text at all.
- Untagged PDFs with no structure, so a screen reader cannot determine headings, reading order, or relationships.
- Missing alternative text on images, charts, and logos.
- Inaccessible forms — fields with no labels, no keyboard support, or a broken tab order.
- Tables without header associations, so data is read as a meaningless stream.
In other words, the letter describes the exact experience a user has when a document was exported without any accessibility work.
Why PDFs are an easy target
PDFs draw claims out of proportion to their visibility for a few structural reasons:
- They're often overlooked. Accessibility projects tend to focus on the main website's HTML and forget the brochures, statements, and applications linked from it.
- They fail uniformly. A PDF exported from a design tool without tagging fails the same way across thousands of sites, which makes barriers cheap to find at scale.
- They're high-stakes content. Menus, bills, benefit notices, and application forms are exactly the documents people need to use — so a barrier there is both common and consequential.
- There's no Title III safe harbor. Because no regulation defines "accessible enough," the uncertainty itself increases settlement pressure.
The settle-versus-litigate calculus
When a letter arrives, businesses weigh two paths, and the right answer depends entirely on the specific facts — which is why this decision belongs with your attorney.
| Factor | Pushes toward settling | Pushes toward litigating |
|---|---|---|
| Cost | Litigation and counsel can be expensive and slow | A weak or boilerplate claim may not survive scrutiny |
| Time | Settlement resolves the matter quickly | Fighting sets a precedent for future letters |
| Remediation | You likely need to fix the documents either way | The fix may already be underway or complete |
| Reputation | Quiet resolution avoids attention | Some organizations choose to defend on principle |
Note that remediation is usually required either way — settling rarely means you can leave the documents as they are. That reframes the question: since you'll almost certainly fix the PDFs regardless, the real leverage is in fixing them before a letter forces your hand.
We are deliberately not putting dollar figures on settlements or litigation here. Costs vary enormously by jurisdiction, the number of documents, and the facts of the case, and any specific number would be misleading.
Concrete steps to reduce exposure
The good news is that the same work that defends against a demand letter also makes your documents genuinely usable for the roughly 1 in 4 U.S. adults living with a disability. A focused program looks like this:
1. Run a prioritized audit
Inventory the PDFs on your public site and rank them by exposure: how many people rely on them and how central they are to your services. A menu, an application form, and a billing statement matter more than a five-year-old press release.
2. Remediate the highest-risk documents first
Fix tagging, reading order, alt text, table headers, and form labels — starting with the documents at the top of your priority list. For the mechanics of doing this well, see how to remediate an inaccessible PDF. A practical, plain-English starting point is our ADA PDF compliance checklist.
3. Publish an accessibility statement
State your commitment to accessibility and give users a clear, working way to report a problem. A real contact channel routes complaints to your team instead of to a plaintiff's firm. A statement is not a legal shield on its own, but it demonstrates good faith.
4. Monitor on an ongoing basis
Inaccessible PDFs creep back in every time someone publishes a new file. Treat monitoring as continuous, not one-time — check new documents before they go live.
5. Train the people who create documents
Most accessibility failures are introduced at the source. Teaching the staff who build menus, forms, and reports the basics — real headings, alt text, selectable text, proper tables — prevents new barriers far more cheaply than fixing them later.
For the complete legal and technical context behind all of this, the PDF accessibility and ADA compliance guide is the pillar that connects these pieces.
Key takeaways
- A demand letter is a pre-litigation request: it alleges a barrier, cites the ADA and WCAG 2.1 AA, and asks you to fix and settle.
- PDFs are an easy target because they're overlooked, fail uniformly, and carry no Title III safe harbor.
- The settle-versus-litigate decision is fact-specific — but remediation is usually required either way, so fixing documents early is the real leverage.
- A prioritized audit, remediation, an accessibility statement, ongoing monitoring, and staff training together move you from easy target to hard one.
- Costs and lawsuit counts vary widely; treat any specific figure with caution and get advice on your own situation.
