Skip to main content
Online PDF Editor Team

How to Make a PDF Accessible (PDF/A, WCAG, 508 Compliance)

Make PDFs accessible for screen readers — tagged PDF, reading order, alt text, PDF/UA, PDF/A. Compliance guide for government, enterprise, education.

make pdf accessiblepdf accessibilitypdf/uawcag pdfsection 508pdf/a
Screen reader software reading an accessible PDF document

Why PDF Accessibility Matters

1 in 4 adults in the US has a disability (CDC). Screen readers, Braille displays, voice control — they all need tagged, structured PDFs. An inaccessible PDF is a barrier: unreadable, unnavigable, unusable.

Legal drivers:

  • Section 508 (US Federal): Federal agencies + contractors must make ICT accessible. PDFs included.
  • ADA Title II/III: State/local gov, public accommodations — digital access required.
  • WCAG 2.1/2.2 AA: International standard. Courts reference it.
  • EN 301 549 (EU): European accessibility standard. PDF/UA referenced.
  • PDF/UA (ISO 14289): The PDF-specific accessibility standard. "Universal Accessibility."

Non-compliance = lawsuits, contract loss, excluded users. Proactive accessibility = broader reach, better SEO, future-proof archives.

Standards: PDF/UA, WCAG, Section 508, PDF/A

{`// Accessibility Standards Map

| Standard          | Scope                    | PDF-Specific? | Legal Force (US)     |
|-------------------|--------------------------|---------------|----------------------|
| PDF/UA (ISO 14289)| PDF accessibility        | YES           | Referenced by 508    |
| WCAG 2.1/2.2 AA   | Web content (incl. PDF)  | No (general)  | ADA, 508 reference   |
| Section 508       | US Federal ICT           | References PDF/UA | Law (federal)    |
| PDF/A (ISO 19005) | Archival                 | No            | Often required w/ UA |
| EN 301 549        | EU ICT                   | References PDF/UA | Law (EU)         |`}

PDF/UA is the "how" for PDFs. WCAG/508 are the "what" (legal requirements). PDF/A is "keep it forever" — often paired with UA for archival accessibility.

What Makes a PDF Accessible?

1. Tagged PDF (Structure Tree)

Every content element tagged:

,

,

,
, ,
, . Screen readers navigate by tags, not visual layout.

2. Reading Order

Tag order = reading order. Must match visual flow (left-to-right, top-to-bottom). Multi-column, sidebars, pull quotes — all must linearize logically.

3. Alt Text for Images

Every

needs /Alt text. Decorative images: empty alt (/Alt ()) or artifact tag. Complex charts: long description in /ActualText or linked appendix.

4. Fonts & Unicode Mapping

All fonts embedded. ToUnicode CMaps present for every font — maps glyph IDs to Unicode. No "symbol font" hacks.

5. Metadata

  • /Lang in catalog (document language)
  • /Title, /Author, /Subject, /Keywords
  • XMP metadata with accessibility flags

6. Form Fields

Interactive fields: /TU (tooltip = accessible name), tab order logical, required fields marked.

7. Security Permissions

If encrypted: Content Extraction for Accessibility (/E bit) MUST be allowed. Screen readers need to extract text.

8. No Flashing / Scripts / Multimedia That Traps Focus

JavaScript, embedded video, 3D — must not break keyboard navigation.

How to Create Accessible PDFs

Best Practice: Author Accessibly, Export Tagged

Don't create a PDF then fix it. Create accessibly in source:

  • Word: Use Styles (Heading 1, Heading 2, Normal). Alt text on images (Format Picture → Alt Text). Tables: Header Row repeat. File → Save As → PDF → Options → "Document structure tags for accessibility" ✓
  • Google Docs: Headings via Styles. Alt text (Right-click image → Alt text). File → Download → PDF (tags included).
  • InDesign: Articles panel for reading order. Object Export Options → Alt text. Export → PDF (Print) → "Create Tagged PDF" ✓
  • LaTeX: tagpdf package, hyperref with pdfa options. Compile with LuaLaTeX.

Scanned Documents → OCR + Tagging

Scan at 300 DPI → OCR (Acrobat Pro, ABBYY, OCRmyPDF) → Auto-tag (Acrobat: Tools → Accessibility → Autotag Document) → Manual verify/fix reading order, alt text, tables.

Fixing Existing PDFs (Remediation)

You have an inaccessible PDF. Options:

Adobe Acrobat Pro (Gold Standard)

  1. Tools → Accessibility → Autotag Document
  2. Reading Order Tool (fix order, tag types)
  3. Set Alternate Text (batch alt text for figures)
  4. Table Editor (tag headers, scope)
  5. Full Check (Accessibility Checker) → fix all issues
  6. Save as PDF/UA (File → Save As Other → PDF/UA)

PDF-XChange Editor (Windows, Freemium)

Tools → Accessibility → similar workflow. Free tier works for basic remediation.

axesPDF / PAC / CommonLook (Specialized)

Enterprise remediation tools. Automated + manual. Expensive. For high-volume compliance.

Our Toolkit — Not a Remediation Tool (Honest Gap)

We don't do tagging, reading order, alt text, or PDF/UA validation. Our tools (merge, split, compress, convert, protect, watermark, page numbers) operate on page content streams — they preserve existing tags if present, but don't create or fix them.

Workflow: Remediate in Acrobat Pro → use our tools for final assembly (merge chapters, add page numbers, compress, protect). Our Merge PDF preserves bookmarks/outlines. Compress PDF Low level linearizes (helps screen reader streaming).

Testing Accessibility

  1. Acrobat Pro Accessibility Checker: Tools → Accessibility → Full Check. Reports every PDF/UA failure.
  2. PAC (PDF Accessibility Checker): Free (Windows). Validates PDF/UA-1/2. Detailed report.
  3. Screen reader test: NVDA (free, Windows) + PDF. JAWS (paid). VoiceOver (macOS). Listen — does it make sense?
  4. Reflow test: Ctrl+4 (Acrobat) — content reflows to single column. Readable?
  5. Contrast check: Text/background ≥ 4.5:1 (WCAG AA). Tools: Colour Contrast Analyser.

How Our Tools Fit In

Post-remediation assembly line:

  • Merge PDF — combine accessible chapters (preserves tags, merges outlines)
  • Add Page Numbers — Bates/standard numbering (drawn as content, tagged as artifact)
  • Compress PDF Low — linearize (Fast Web View) for screen reader streaming
  • Protect PDF — AES-256 with Content Extraction ALLOWED (screen reader access)
  • Watermark PDF — classification stamps (tagged as artifact, not read)

FAQ

How do I make a PDF accessible?

Author accessibly in Word/InDesign (styles, alt text, table headers) → export tagged PDF. Or remediate existing PDF in Acrobat Pro (Autotag → Reading Order → Alt Text → Full Check).

What is PDF/UA?

ISO 14289 — Universal Accessibility for PDF. The technical standard for accessible PDFs. Tagged, reading order, alt text, Unicode mapping, metadata, permissions.

Is PDF/A the same as accessible PDF?

No. PDF/A = archival (self-contained, fonts embedded, no encryption). PDF/UA = accessibility. Often combined: PDF/A-2u or PDF/A-3u (u = Unicode/UA compliant).

How do I check if a PDF is accessible?

Acrobat Pro: Tools → Accessibility → Full Check. PAC (free, Windows). Screen reader test (NVDA/JAWS/VoiceOver).

Can I make a PDF accessible online for free?

Limited. Some server tools claim "auto-tag" but quality is poor. Real remediation needs Acrobat Pro or specialized tools. Our toolkit doesn't do tagging/remediation.

What is Section 508 compliance for PDFs?

Federal standard requiring accessible ICT. For PDFs: effectively means PDF/UA compliance. Test with Acrobat Full Check + screen reader.

Do screen readers read PDFs?

Only if tagged. Untagged PDF = screen reader reads raw text stream (wrong order, no headings, no table structure, no alt text). Tagged PDF = navigable, structured.

Can I password-protect an accessible PDF?

Yes — but MUST allow "Content Extraction for Accessibility" (permissions bit). Our Protect PDF allows this by default when you set permissions.

Building accessible documents? Remediate in Acrobat Pro, then assemble with our toolkit: Merge, Page Numbers, Compress, Protect. Free. Private. Client-side.