Almost every organization publishes PDFs — applications, statements, forms, reports, syllabi — and almost every organization is covered by some accessibility law that reaches those documents. But the specific law, the deadline, and the level of legal exposure vary enormously depending on what sector you are in. This guide is a sector-by-sector tour of who must make their PDFs accessible, under which laws, which documents carry the most risk, and what to do about it. This is general information, not legal advice.
The thread running through every industry is the same: accessibility serves real people. Roughly 1 in 4 U.S. adults lives with a disability, and many rely on screen readers, magnification, or keyboard navigation to read the documents you publish. An untagged PDF can be completely silent to a screen reader — which is why regulators and courts increasingly treat inaccessible documents as a denial of service rather than a technical oversight.
At a glance: who is covered and by what
The table below summarizes the landscape before we walk through each sector in detail. The standards listed are the benchmarks regulators and courts actually use, not necessarily what the underlying statute names.
| Industry | Main laws | Typical PDFs at risk | Accessibility standard |
|---|---|---|---|
| Government (state/local) | ADA Title II; Section 508 (federal) | Forms, permits, notices, meeting agendas, reports | WCAG 2.1 AA |
| Education (higher-ed & K-12) | ADA Title II; Section 504; Section 508 | Syllabi, course packs, library scans, enrollment forms | WCAG 2.1 AA |
| Healthcare | HHS Section 504 rule; ADA (II & III) | Intake/consent forms, after-visit summaries, EOBs, benefit notices | WCAG 2.1 AA |
| Financial services | ADA Title III; EAA (Europe) | Statements, disclosures, contracts, applications | WCAG 2.1 AA |
| Legal & professional services | ADA Title III; Section 508 (if contracting) | Engagement letters, filings, client forms, reports | WCAG 2.1 AA |
| Retail & e-commerce | ADA Title III; EAA (Europe) | Receipts, manuals, catalogs, coupons, return forms | WCAG 2.1 AA |
A useful mental model: government and government-funded sectors face explicit regulations with hard deadlines, while private businesses face enforcement through lawsuits and demand letters that use WCAG as the de facto standard even though no statute names it.
Government: explicit rules, hard deadlines
State and local government is the sector where the legal question is most settled. ADA Title II covers state and local agencies, courts, libraries, transit authorities, and the programs they run, requiring that people with disabilities have an equal opportunity to participate in and benefit from public services.
On April 24, 2024, the Department of Justice published a Title II rule that, for the first time, sets a concrete technical standard — WCAG 2.1 Level AA — and applies it not just to web pages but explicitly to conventional electronic documents: PDF, Word, Excel, and PowerPoint. After an April 2026 interim final rule, the deadlines are:
| Covered entity | Population served | Deadline |
|---|---|---|
| State / local government | 50,000 or more | April 26, 2027 |
| State / local government | Under 50,000 | April 26, 2028 |
| Special district governments | Any size | April 26, 2028 |
Federal agencies sit under a separate regime: Section 508 of the Rehabilitation Act, whose Revised Standards (the "508 Refresh," effective January 2018) incorporate WCAG 2.0 Level A and AA by reference and reach federal contractors and vendors through procurement.
- Who's covered: state/local agencies (Title II), federal agencies and their contractors (Section 508).
- Typical PDFs at risk: permit and benefit applications, public notices, meeting agendas and minutes, budget and annual reports, tax forms.
- Practical exposure: a fixed regulatory deadline. The question is no longer whether government PDFs must meet WCAG 2.1 AA, but whether you will be ready in time. See our ADA & PDF accessibility guide for the full legal background.
Education: high volume, high scrutiny
Education is one of the most actively scrutinized sectors, and for a structural reason: institutions publish enormous volumes of PDFs created by thousands of decentralized authors — faculty syllabi, scanned course packs, library digitizations, financial-aid forms, and admissions paperwork.
Public colleges, universities, and K-12 districts are covered by ADA Title II and therefore fall under the 2024 rule and its 2027/2028 deadlines. They are also covered by Section 504 of the Rehabilitation Act, which prohibits disability discrimination by recipients of federal funding — and nearly every public institution receives federal funds.
- Who's covered: public universities, community colleges, and K-12 districts (Title II + Section 504); federally funded private institutions (Section 504).
- Typical PDFs at risk: syllabi, lecture handouts, scanned readings, library archives, enrollment and financial-aid forms, IEP and 504 plan documents.
- Practical exposure: the Department of Education's Office for Civil Rights (OCR) actively investigates complaints and negotiates resolution agreements, often after a single student complaint. The sheer document volume makes manual remediation impractical. We cover the institutional playbook in higher-ed & K-12 PDF accessibility.
Healthcare: a 2027 deadline most providers haven't noticed
Healthcare faces a regulation that many providers are not yet aware applies to them. On May 9, 2024, the Department of Health and Human Services published a final rule under Section 504 requiring WCAG 2.1 AA for the web and mobile content of recipients of HHS funding — which sweeps in most hospitals, clinics, and providers that bill Medicare or Medicaid.
After a May 2026 extension, the deadlines are:
| Recipient size | Deadline |
|---|---|
| 15 or more employees | May 11, 2027 |
| Fewer than 15 employees | May 10, 2028 |
On top of the HHS rule, the ADA applies independently — Title II to public hospitals and Title III to private providers as places of public accommodation.
- Who's covered: providers billing Medicare/Medicaid, hospitals, clinics, and HHS-funded health programs.
- Typical PDFs at risk: intake and consent forms, after-visit summaries, explanations of benefits (EOBs), benefit and coverage notices, patient-portal documents.
- Practical exposure: accessible forms are especially critical here — a patient who cannot independently complete a consent or intake form is denied meaningful access to care. See healthcare PDFs & the HHS Section 504 rule for the details.
Financial services: regulated everywhere, sued frequently
Financial institutions are doubly exposed. In the U.S., banks, credit unions, lenders, and insurers are places of public accommodation under ADA Title III, and they generate exactly the kind of personalized, recurring documents that attract complaints. In Europe, the European Accessibility Act brings banking services and their customer-facing documents under explicit regulation.
There is no DOJ technical regulation for Title III — the agency has declined to issue one — so enforcement runs through private lawsuits and demand letters, which use WCAG 2.1 AA as the accepted benchmark.
- Who's covered: banks, credit unions, lenders, insurers, investment firms (U.S. Title III; EU under the EAA).
- Typical PDFs at risk: monthly statements, disclosures and privacy notices, loan and account applications, contracts, tax documents (1099s, etc.).
- Practical exposure: statements and disclosures are templated and reused across thousands of customers, so a single inaccessible template becomes a scalable target. We break this down in accessible PDFs for financial services.
The European overlay: the EAA
The European Accessibility Act (Directive (EU) 2019/882) carries obligations from June 28, 2025 and covers a range of consumer products and services — including banking, e-commerce, and transport — along with their customer-facing documents such as bank statements, invoices, and contracts. The technical benchmark is the harmonized standard EN 301 549, which incorporates WCAG 2.1 AA. Microenterprises (fewer than 10 employees) providing services may be exempt. Any organization serving European customers should read the EAA & global PDF laws.
Legal & professional services: covered by the work they do
Law firms, accountants, consultancies, and other professional-services firms are places of public accommodation under ADA Title III, so the client-facing documents they produce can carry an accessibility obligation. Many also acquire a second obligation through their clients: a firm that contracts with a federal agency, or produces deliverables for one, can be pulled into Section 508 requirements through procurement.
- Who's covered: law firms, accounting and consulting firms, agencies, and other professional-services providers (Title III; Section 508 when serving federal clients).
- Typical PDFs at risk: engagement letters, client intake forms, contracts, court filings, advisory reports and deliverables.
- Practical exposure: generally lower volume than retail or education, but each document is high-stakes and client-specific. Firms that deliver inaccessible work product to a government client can find it rejected on procurement grounds.
Retail & e-commerce: the most-litigated sector
Retail and e-commerce sit at the center of U.S. digital accessibility litigation. As places of public accommodation under ADA Title III, online and brick-and-mortar retailers generate a constant stream of consumer-facing documents, and industry trackers report that thousands of digital accessibility lawsuits are filed each year — a growing share referencing inaccessible PDFs alongside the website itself.
European retailers face the EAA in addition, which explicitly covers e-commerce services and the documents that accompany them (invoices, receipts, contracts), benchmarked against EN 301 549 / WCAG 2.1 AA.
- Who's covered: online and physical retailers, marketplaces, and e-commerce platforms (U.S. Title III; EU under the EAA).
- Typical PDFs at risk: receipts and invoices, product manuals and spec sheets, downloadable catalogs, coupons and promotions, return and warranty forms.
- Practical exposure: high. Automated scanning makes it cheap for plaintiffs to find non-compliant documents at scale, and a reused template can become a single point of failure across thousands of files.
What "accessible" means in every sector
Although the laws differ, the technical target is remarkably consistent across industries: a PDF that conforms to WCAG 2.1 AA. In practice that means the document has:
- Tags — an invisible structure tree of headings, paragraphs, lists, and tables that tells assistive technology what each element is.
- Correct reading order — the logical order a human reads, not the order objects were drawn.
- Alt text — text alternatives for meaningful images; decorative images marked as artifacts.
- Sufficient color contrast — and never color alone to convey information.
- Accessible forms — labeled fields, logical tab order, and clear instructions.
- Metadata and language — a document title and specified language.
The related ISO standard PDF/UA (ISO 14289) defines how these features are implemented inside the file, while WCAG defines what accessibility means at the content level — they are complementary. Whatever your sector, the document-level work is the same; only the deadline and the enforcement mechanism change.
Key takeaways
- Almost every sector is covered by some accessibility law that reaches PDFs — the difference is the specific law, the deadline, and the enforcement mechanism.
- Government, education, and healthcare face explicit regulations with hard 2027/2028 deadlines (ADA Title II, Section 504, the HHS Section 504 rule); financial services, legal, and retail face enforcement primarily through lawsuits and demand letters.
- WCAG 2.1 AA is the common benchmark across nearly every regime, including the European Accessibility Act's EN 301 549.
- Education and retail are the highest-volume targets, healthcare's deadline is the most overlooked, and financial services are exposed on both sides of the Atlantic.
- Regardless of industry, the technical work is the same: tags, reading order, alt text, contrast, accessible forms, and metadata — so prioritize the documents people actually use and build accessibility into your workflow.



