PDF Accessibility Remediation: Complete Guide for WCAG Compliance

PDFs are everywhere — contracts, reports, invoices, government forms, white papers. And most of them are completely inaccessible to screen reader users. A study by WebAIM found that PDFs are the single most common accessibility barrier reported by screen reader users, ahead of CAPTCHA, Flash content, and missing alt text. The problem is that creating an accessible PDF requires deliberate effort. Unlike HTML, which has built-in semantics (headings, lists, links), a PDF is essentially a visual layout format. Without proper tagging, a screen reader sees nothing but a wall of unstructured text — or worse, reads content in the wrong order.

What Makes a PDF Accessible

An accessible PDF meets these criteria:

• Tagged structure: headings, paragraphs, lists, tables, and figures are semantically tagged (like HTML)
• Correct reading order: content is read in a logical sequence, not in the visual layout order
• Alternative text: all images and graphics have descriptive alt text
• Bookmarks: long documents have a bookmark structure matching the heading hierarchy
• Accessible forms: form fields have labels, tab order is logical, and validation messages are programmatic
• Language: the document language is specified (and language changes within the document are marked)
• Searchable text: no image-only text (scanned documents must be OCR'd)
• Color contrast: text meets WCAG 2.2 AA contrast ratios (4.5:1 for normal text, 3:1 for large text)

Creating Accessible PDFs from Source

The best approach is to create accessibility at the source — in Word, InDesign, or whatever tool generates the PDF.

Microsoft Word to PDF

Word is the most common source. If you use Word's built-in styles (Heading 1, Heading 2, Normal, List Bullet), the PDF export preserves the tag structure. Here's the checklist:

1. Use built-in heading styles (don't just bold text and increase the font size)
2. Add alt text to all images (right-click > Edit Alt Text)
3. Use Word's table tools (Insert > Table) — don't draw tables with borders
4. Mark the header row in tables (Table Properties > Row > Repeat as header)
5. Set the document language (Review > Language)
6. Add a title (File > Properties > Title)
7. Export with "Create Bookmarks using Headings" checked
8. Use "Save as PDF" or "Export" (not "Print to PDF" — it strips tags)

This alone gets you 70-80% of the way to an accessible PDF. The remaining 20-30% may require Adobe Acrobat Pro for fine-tuning.

Adobe InDesign to PDF

InDesign is powerful for accessible PDF creation but requires more manual work. Use paragraph styles mapped to PDF tags (Export Tagging in Style Options), set the Articles panel for reading order, and export with "Create Tagged PDF" checked. InDesign gives you the most control — but also the most opportunities to get it wrong.

Remediating Existing PDFs

Most PDFs in the wild are not tagged. Remediating them requires Adobe Acrobat Pro or a specialized tool.

Adobe Acrobat Pro Workflow

1. Run the Accessibility Checker: Acrobat > Accessibility > Full Check. This identifies missing tags, alt text, reading order issues, and more.
2. Add tags: Acrobat > Accessibility > Autotag Document. Auto-tagging gets you started but always needs manual review.
3. Fix reading order: Acrobat > Accessibility > Reading Order tool. Click on each content block to set its tag type (heading, paragraph, figure, table) and drag to reorder.
4. Add alt text to images: Right-click tagged images > Properties > Alternate Text. Write a concise description of the image content.
5. Fix tables: Use the Table Editor to identify header cells (TH) vs data cells (TD) and set scope attributes.
6. Set document properties: File > Properties > Title (clear and descriptive), Language, and Initial View (show bookmarks panel).
7. Re-run the checker to verify fixes.

Alternative Tools

• PAC (PDF Accessibility Checker): free tool for testing PDF accessibility against PDF/UA and WCAG. Best free checker available.
• CommonLook PDF GlobalAccess: commercial plugin for Acrobat with superior table remediation and auto-tagging.
• axesPDF: commercial tool for creating and remediating accessible PDFs, popular in the EU.
• Equidox: cloud-based remediation with AI-assisted tagging. Good for high-volume remediation.

Scanned PDFs: The OCR Challenge

Scanned PDFs are images — no text at all. A screen reader literally sees nothing. You must run OCR (Optical Character Recognition) first to convert the image to searchable text, then tag the result.

Adobe Acrobat Pro's OCR (Scan & OCR > Recognize Text) handles most scanned documents well. For large volumes, ABBYY FineReader offers batch processing with better accuracy on degraded scans.

After OCR, the document still needs full remediation (tagging, reading order, alt text). OCR creates the raw text — it doesn't create accessibility.

PDF/UA: The Accessibility Standard

PDF/UA (ISO 14289-1) is the international standard for accessible PDFs. It goes beyond WCAG by specifying requirements specific to the PDF format: tag structure, artifact marking, font embedding, and character mapping.

Meeting PDF/UA generally means you also meet WCAG 2.2 AA for document accessibility. The PAC checker tests against PDF/UA and provides a detailed compliance report.

Common Mistakes

• "Print to PDF": this creates a flat image-like PDF with no tags. Always use "Export" or "Save as PDF" from the source application.
• Decorative images without artifact marking: if an image is decorative (backgrounds, dividers), mark it as an artifact — don't just leave the alt text empty.
• Tables used for layout: use tables for data only. Layout tables confuse screen readers and violate WCAG.
• No tab order in forms: form fields must have a logical tab order matching the visual layout. Test with the Tab key.
• Color-only information: highlighting in red doesn't work for colorblind users. Use bold, icons, or text labels in addition to color.