PDF & Document Accessibility

A PDF created by simply exporting from Word, printing to PDF, or scanning a physical document is almost always inaccessible. Here's why:

• Scanned PDFs are images. A scanned document is a picture of text — a screen reader sees a blank page. OCR (optical character recognition) must be applied AND structural tags added.
• Untagged PDFs have no structure. Screen readers need tagged PDFs — documents where headings, paragraphs, lists, tables, and form fields are marked up semantically. An export from Word without tag remapping typically produces a poorly-tagged or untagged PDF.
• Reading order may be wrong. PDFs with multi-column layouts, sidebars, or complex formatting often have a logical reading order that doesn't match the visual order. Screen readers announce content in tag order, not visual order.
• Images lack alt text. Images embedded in PDFs need alt text just like images on web pages.
• Forms are not interactive. PDF forms must have tagged, labeled form fields — not static images of forms.
• Tables lack header markup. Data tables must have header rows and cells marked so screen readers can announce "Column: Price, Row: HVAC Inspection" rather than just the cell value.

Section 508 (federal contractors and agencies)

Section 508 of the Rehabilitation Act requires that electronic documents — including PDFs — published or provided by federal agencies and federal contractors be accessible. The technical standard references WCAG 2.1 and PDF/UA (ISO 14289). PDFs published on federal agency websites or provided as deliverables on federal contracts must be tagged, with proper reading order, alt text, and accessible forms.

ADA / WCAG (businesses and state/local government)

WCAG includes techniques for PDF accessibility (PDF Techniques). Courts have found businesses liable under the ADA for inaccessible PDFs linked from their websites — particularly service agreements, menus, applications, and informational guides. The W3C's PDF Techniques document is the authoritative reference.

DOJ Title II (municipalities and schools)

The 2024 DOJ Title II final rule explicitly covers "electronic documents" including PDFs. Government entities must ensure all PDFs they publish — meeting agendas, zoning documents, enrollment forms, budget reports, public notices — are accessible by their compliance deadline.

For documents created in Word or Google Docs

1. Use heading styles (Heading 1, Heading 2) in your source document — not manually bolded text.
2. Add alt text to images before exporting.
3. Mark table headers in the source document.
4. Set document language in Word's document properties.
5. Export with "Best for electronic distribution" in Word's PDF export options (not "Print to PDF" which discards tags).
6. Check in Adobe Acrobat using the Accessibility Checker — fix remaining issues.

For scanned documents

1. Apply OCR in Adobe Acrobat.
2. Use the "Auto-Tag Document" tool as a starting point.
3. Manually verify and correct the tag tree, reading order, and alt text.

PDF/UA compliance

PDF/UA (Universal Accessibility, ISO 14289) is the international standard for accessible PDFs, referenced by Section 508 and increasingly by courts. A PDF/UA compliant document passes automated PDF/UA validation tools like PAC (PDF Accessibility Checker).

Trades businesses

Service agreements, estimate PDFs, maintenance plan documents, and rebate forms published to your website must be accessible. The risk is lower than for municipalities, but if a user files an ADA complaint about an inaccessible PDF on your site, you are exposed.

K–12 schools

Schools publish enormous volumes of PDFs — enrollment forms, student handbooks, IEP-related documents, class schedules, lunch menus, newsletter PDFs, budget documents, board meeting agendas. Under Section 504 and the 2024 DOJ Title II rule, all of these must be accessible. Schools that use automated PDF generation tools must verify those tools produce accessible output.

Municipalities

Municipal PDFs are often legacy documents scanned from paper originals — almost always inaccessible. Meeting agendas, zoning ordinances, public hearing notices, permit applications, RFP documents, budget reports — all must meet accessibility standards under the Title II rule. Municipalities with large document archives face significant remediation work.