There is no way to guarantee you will never receive a demand letter — but you can systematically make your organization a much harder target by making your documents genuinely usable. The same work that reduces legal exposure also serves the roughly 1 in 4 U.S. adults living with a disability. This article lays out a practical, prioritized prevention plan: find your public PDFs, fix the riskiest ones first against a recognized standard, give users a real way to ask for help, and keep new documents from reintroducing the problem.
This is general information, not legal advice. Think of what follows as risk reduction, not a promise of immunity.
Start with the standard you're aiming at
Before fixing anything, know the target. Across U.S. and EU frameworks, the recurring technical benchmark is WCAG 2.1 Level AA — it underpins the ADA Title II rule for government documents (PDF, Word, Excel, PowerPoint), the HHS Section 504 rule for federally funded recipients, and Europe's EN 301 549 under the EAA, and courts use it as the de facto benchmark for private businesses under Title III. For PDFs specifically, PDF/UA (ISO 14289) defines how accessibility is implemented inside the file — tags, reading order, structure, metadata — while WCAG defines what accessible means at the content level. Aim for WCAG 2.1 AA at minimum, implemented through PDF/UA-conformant structure.
The prevention plan, in priority order
Work the list top to bottom. Each step lowers exposure on its own, and the early steps deliver the most risk reduction per hour spent.
| Priority | Step | Why it reduces risk |
|---|---|---|
| 1 | Inventory every public PDF | You can't protect documents you don't know you're publishing |
| 2 | Rank documents by traffic and risk | Concentrates effort where a barrier is most likely to be hit and most consequential |
| 3 | Scan/audit against WCAG 2.1 AA | Turns "we think it's fine" into evidence of what actually fails |
| 4 | Remediate or replace top documents | Removes the barriers that demand letters allege |
| 5 | Publish an accessibility statement | Gives users a path to your team instead of to a plaintiff's firm |
| 6 | Respond fast to requests | A quick accessible alternative defuses many complaints |
| 7 | Train content creators | Stops new barriers at the source |
| 8 | Monitor continuously | Keeps regressions from creeping back in |
1. Inventory your public PDFs
You cannot protect what you cannot see. Crawl your site and list every linked PDF, including the ones buried in old news posts, resource libraries, and footer links. Note where each is linked from and roughly how often it's accessed. The goal is a single source of truth for what the public can actually download from you.
2. Prioritize by traffic and risk
Not all documents carry equal exposure. Rank them so remediation effort lands where it matters most. The highest-risk documents are usually those people must use to transact or exercise a right:
- Applications and forms — job applications, enrollment, benefits requests.
- Statements and bills — financial statements, invoices, account summaries.
- Notices — benefit notices, legal notices, policy changes.
- Policies and disclosures — terms, privacy notices, required disclosures.
A current, high-traffic application form matters far more than a five-year-old press release. Fix the top of the list first.
3. Scan and audit against WCAG 2.1 AA
Run each prioritized document through an accessibility check. Automated scanning catches the high-frequency failures fast — and these are precisely the ones demand letters allege:
- Image-only/scanned pages with no machine-readable text.
- Untagged content, so a screen reader can't determine headings or reading order.
- Missing alt text on images, charts, and logos.
- Tables without header associations, read as a meaningless stream of cells.
- Form fields without labels or with a broken tab order.
Automated tools won't catch everything — judgment calls like meaningful alt text and logical reading order need human review — but they reliably surface the structural failures that make a document an easy target.
4. Remediate the highest-risk documents — or replace them
For each top document, either fix it or replace it with accessible HTML. Remediation means adding the structure a screen reader relies on:
- Tags and reading order so content is announced in a logical sequence.
- Alt text for every meaningful image.
- Table headers associated with their data cells.
- Form field labels, keyboard support, and a sensible tab order.
Often the better move is to replace the PDF with an accessible web page — especially for content that changes (rates, hours, policies). HTML is generally easier to keep accessible than a re-exported PDF. For the full workflow, see how to remediate an inaccessible PDF, and use our ADA PDF compliance checklist as a plain-English worklist.
5. Publish an accessibility statement with a feedback channel
State your commitment to accessibility and give users a clear, working way to report a barrier — an email or form that routes to a team that actually responds. A statement is not a legal shield by itself, but it demonstrates good faith and, crucially, gives a frustrated user a path to you rather than to a plaintiff's firm.
6. Fix accessible alternatives fast on request
When someone reports that they can't use a document, treat it as urgent. Provide an accessible version — a remediated PDF, an HTML page, or even an accessible Word file — quickly. A fast, helpful response resolves many situations before they escalate, and it reflects the good-faith posture your accessibility statement promises.
7. Train the people who create documents
Most failures are introduced at the source, every time someone exports a new file. Teach the staff who build forms, reports, and notices the basics: real heading styles, alt text, selectable (not scanned) text, properly structured tables, and labeled form fields. Documents that are born accessible are far cheaper than documents fixed under pressure.
8. Monitor continuously
Accessibility is not a one-time project. New PDFs go up constantly, and old ones get re-uploaded. Check new documents before they go live, re-scan periodically, and keep your inventory current so a regression doesn't quietly become next year's demand letter.
Set expectations: risk reduction, not a guarantee
No checklist makes you lawsuit-proof. A determined plaintiff can still send a letter, and facts vary. What this plan does is shrink the attack surface — fewer barriers, evidence of good faith, a real feedback loop, and a process that keeps new documents clean. That combination moves you from easy target to hard one. For the broader legal and regulatory context, the pillar guide on PDF lawsuits and the new regulations connects these pieces.
Key takeaways
- Inventory first, then prioritize by traffic and risk — applications, statements, forms, notices, and policies sit at the top.
- Scan against WCAG 2.1 AA to replace guesswork with evidence, then remediate or replace the riskiest documents.
- Publish an accessibility statement with a working feedback channel and respond fast when someone asks for an accessible alternative.
- Train content creators and monitor continuously so new PDFs are born accessible and regressions don't creep back.
- This is risk reduction, not a guarantee — but it reliably moves you from an easy target to a hard one.
