PDF Accessibility: WCAG, ADA, Section 508 (2026)

You're publishing a government document, a university syllabus, an annual report, or a healthcare form. Someone using a screen reader needs to read it. Right now, your PDF is a wall of pictures of text — the screen reader sees nothing useful, the content is invisible to a portion of your audience, and your organisation may be in violation of accessibility laws.

This guide covers what makes a PDF accessible, the steps to convert an inaccessible PDF into one that screen readers can navigate, and how to verify the result meets WCAG / Section 508 / ADA standards.

Why PDF accessibility matters

Several distinct reasons:

• Legal compliance. US federal agencies (Section 508), UK public bodies (PSBAR 2018), EU public sites (EN 301 549), and ADA (private companies) require accessible digital content. Non-compliant PDFs are a source of lawsuits and audit findings.
• Real users. Roughly 1-2% of any audience uses assistive technology — screen readers, screen magnifiers, voice control, switch devices. For 1000 readers, that's 10-20 people who need the PDF to work.
• SEO and discovery. Search engines extract text from accessible PDFs more reliably. Inaccessible image-only PDFs are invisible to Google.
• Future-proofing. Future you (or your replacement) will edit the PDF. Accessible structure makes edits easier.

The cost of making a PDF accessible is small (15-30 min per document with the right workflow). The cost of NOT doing so can be high.

What "accessible" means for a PDF

An accessible PDF has six layers of structure that an inaccessible PDF lacks:

A PDF can have ALL of these missing (image-only scan), some (text-PDF with no tags), or all (proper accessible PDF).

Quick check: is your PDF already accessible?

Before fixing, check the current state:

In Adobe Acrobat Reader (free)

1. Open the PDF.
2. View → Show/Hide → Navigation Panes → Tags (or Ctrl+Shift+T).
3. The Tags panel appears on the left.

What you see tells you the state:

• "No Tags Available" → not accessible, needs work from scratch
• A tag tree with elements like <H1>, <P>, <L> → has structure, may need refinement
• Just <Document> with no nested tags → minimally tagged, almost certainly broken

Using Adobe's Accessibility Checker

Adobe Acrobat Pro has a built-in checker:

1. All Tools → Prepare for Accessibility → Accessibility Check.
2. Run with default settings.
3. Review the report — issues appear in a panel showing what's missing.

Common issues the checker flags: missing tags, no document title, no language specified, untagged form fields, missing alt text on images.

Using a free online checker

• PAC (PDF Accessibility Checker) — free desktop tool from PDF/UA organisation
• WAVE accessibility tool — extension version flags some issues for PDFs
• AXES PDF QuickCheck — free, browser-based

These give a similar overview to Acrobat Pro at no cost.

The accessibility workflow

Step 1: Start with a tagged source

The easiest accessible PDF comes from a properly structured Word document. Word automatically generates tags when exporting:

• Use Word's Heading 1, Heading 2 styles for headings (NOT just bold + larger font)
• Use Word's list style for bulleted/numbered lists (NOT manually typed bullets)
• Add alt text to images: right-click image → View Alt Text → write a description
• Set the document language: Review → Language → Set Proofing Language
• Add a document title: File → Info → Properties → Title

When you export to PDF (File → Save As → PDF), check Document structure tags for accessibility in the Options dialog. The result is a tagged PDF with most structure carried over.

This is the highest-quality path. Always start from a structured source if possible.

Step 2: For untagged PDFs — add tags

If the PDF was created without tags (scanned, generated from an unstructured tool), add them:

In Adobe Acrobat Pro

1. All Tools → Prepare for Accessibility → Autotag Document.
2. Acrobat analyses the page and adds tags automatically.
3. Review the resulting tag tree — autotag is approximate; expect to refine.

Manually (Acrobat Pro)

1. Open the Tags panel.
2. Right-click in the Tags panel → Add tag to selection.
3. Select content on the page, choose tag type (Heading, Paragraph, etc.).
4. Repeat for every content block.

This is tedious for long documents — autotag first, then manually fix what autotag got wrong.

Using free tools

• PDFix Free — free tool for adding basic tags
• PAC + Acrobat Reader — Reader can't add tags but can verify, then use a free tagging tool

Step 3: Fix the reading order

Tags determine what elements are; reading order determines what order assistive tech reads them.

To check and fix in Acrobat Pro:

1. All Tools → Prepare for Accessibility → Reading Order.
2. Numbered overlays appear on each page showing the reading order.
3. Click any element to change its order.
4. For multi-column documents, ensure column 1 reads top-to-bottom before column 2 starts.

Common reading order problems:

• Multi-column docs read left-to-right across columns instead of column-by-column
• Text wrapping around an image reads the image alt text in the wrong place
• Tables read row-by-row vs column-by-column inconsistently
• Footnotes read in the wrong place

Manual fix is unavoidable for complex layouts.

Step 4: Add alt text to images

Every image needs alt text describing what it shows (in 125 characters or less, generally):

In Acrobat Pro:

1. Right-click an image → Tag → Image (if not already tagged).
2. Right-click again → Properties.
3. Add Alternate Text describing the image.

Examples of good alt text:

For purely decorative images (page borders, separators), mark as Artifact so the screen reader skips them entirely.

Step 5: Set document metadata

Three fields matter:

1. Document title — File → Properties → Description → Title
2. Document language — File → Properties → Advanced → Language
3. Author (optional but recommended) — same dialog

Set these even for short documents. Screen readers announce the title when opening; the language tells the reader how to pronounce.

Step 6: Tag form fields (if any)

PDF forms have fields (text inputs, checkboxes, radios). Each needs a label that describes what it's for:

In Acrobat Pro:

1. Open the Forms panel.
2. Right-click each field → Properties.
3. Add a Tooltip that describes the field (e.g., "First name").
4. The screen reader uses the tooltip as the field's label.

Without tooltips, the screen reader announces "edit field" with no context. With tooltips, the user knows what to type.

Step 7: Add bookmarks for long documents

For documents over ~10 pages, bookmarks let users jump to sections:

1. View → Show/Hide → Navigation Panes → Bookmarks.
2. Add a bookmark for each major heading: select the text, right-click → New Bookmark.

In Acrobat, you can also generate bookmarks from headings: Bookmarks → Options → New Bookmarks from Structure.

OCR for scanned PDFs

If your PDF is a scan (image-only), it has no text at all. Screen readers see nothing.

Step 1 for any scanned PDF: run OCR.

1. Use a tool like PDFGrover's OCR PDF or Adobe Acrobat's built-in OCR.
2. The OCR engine recognises text and creates a searchable text layer behind the images.
3. The PDF now has actual text — accessibility tools can work on it.

After OCR, follow the steps above to add tags, alt text, etc.

OCR accuracy is 90-99% on clean text, lower on poor scans. Always proofread the OCR output before considering the PDF accessible.

WCAG, Section 508, ADA — what each requires

These standards overlap heavily. Quick summary:

WCAG 2.1 AA (international standard)

• Perceivable: alt text, captions, structure
• Operable: keyboard accessible, navigable
• Understandable: clear language, predictable
• Robust: works with assistive tech

For PDFs, AA = tagged, alt text, reading order, language, color contrast.

Section 508 (US federal)

• Adopts WCAG 2.0 AA (and aligns with 2.1 AA)
• Specific PDF requirements: tagged, accessible forms, document language, bookmarks for long docs

ADA (US private sector)

• No specific technical standard, but courts increasingly cite WCAG 2.1 AA as the de facto requirement
• Title III (public accommodations) → applies to commercial websites and digital content

EN 301 549 (EU public)

• Adopts WCAG 2.1 AA + additional ICT requirements

In practice: meeting WCAG 2.1 AA satisfies all of the above. That's the target.

Verifying accessibility — the test

After fixing, verify:

Test 1: Keyboard navigation

1. Open PDF in Acrobat Reader.
2. Use only Tab key to navigate (no mouse).
3. Confirm focus moves through every interactive element (links, form fields, bookmarks).
4. Confirm focus order makes sense.

Test 2: Screen reader test

1. Use NVDA (free, Windows), VoiceOver (built-in macOS), or JAWS.
2. Open the PDF.
3. Listen to a few pages of the document being read aloud.
4. Confirm:
   • The document title is announced
   • Headings are announced as headings
   • Lists are announced as lists with item count
   • Tables are read row-by-row coherently
   • Images are described via alt text
   • No "graphic" announcements with no description

If you hear "graphic" with no description, that image is missing alt text. If headings are read as plain text, tag them as headings.

Test 3: Automated checker

1. Run PAC, Adobe's checker, or AXES PDF QuickCheck.
2. Review the report.
3. Fix any flagged issues.

Automated checkers catch ~30% of issues. Human screen-reader testing catches the rest.

Common mistakes

Treating "searchable PDF" as accessible. A searchable PDF has text but may have no tags. Search engines can extract text; screen readers still struggle without structure.

Skipping alt text on charts and graphs. A chart's data is the point — describe what the chart shows, not just "bar chart". Otherwise the screen reader user gets no information.

Heading tags on visual headings only. Every heading (H1, H2, H3) in your document outline needs an H tag. Don't tag a paragraph that "looks like a heading" because it's bold.

Forgetting to set the document language. Screen readers default to system language and pronounce other languages with the wrong accent.

Color contrast issues. Light grey text on white background fails WCAG. Use a contrast checker — text needs 4.5:1 ratio against background (3:1 for large text 18pt+).

Tagged PDF without correct reading order. Tags say what each element is; reading order says what order to read them in. Both matter.

Inaccessible forms. Form fields without tooltips are useless to screen reader users. Add a tooltip to every field.

Treating accessibility as an afterthought. Easier and cheaper to start with a structured source (good Word doc) than to retrofit a flat PDF.

When to use a paid accessibility service

For high-stakes documents (legal filings, government regulations, insurance forms):

• Hire a certified accessibility consultant ($500-2000 per document) to remediate and certify.
• Use commCommonLook (commercial PDF/UA tool, $$) or PDFix Pro for batch processing.
• Use Acrobat Pro's Make Accessible action wizard — guided workflow.

For typical web-published documents (blog posts as PDF, training materials, internal docs), free/low-effort fixes suffice.

Quick reference

Summary

PDF accessibility is about adding structure (tags, reading order, alt text, language) on top of the visible page content. Screen readers and assistive tech use the structure; visible appearance stays unchanged.

Start from a structured source (well-formatted Word doc) when possible — that's the easiest path. For existing PDFs, add tags via Acrobat's autotag, refine manually, add alt text and bookmarks, set metadata, verify with a screen reader.

For organisations publishing many PDFs, build accessibility into your authoring workflow rather than retrofitting after — the cost difference is 10x to 100x.

PDFGrover's OCR PDF creates the searchable text layer needed before tags can be added — a prerequisite for any accessibility work on scanned PDFs. PDF Metadata Editor sets document title, language, and author fields needed for compliance. For full WCAG remediation (tags, reading order, alt text), Adobe Acrobat Pro or specialist accessibility tools are needed; PDFGrover focuses on the prep steps.