← toolkit.bot

PDF Accessibility Audit Checklist for EAA 2026 — What to Check and How to Fix It

If your organization distributes PDFs to EU users, the European Accessibility Act (EAA) is now in active enforcement. PDFs are the single most common accessibility failure in corporate, government, and publishing document workflows — and most organizations have no systematic process for auditing them.

This checklist covers the 8 criteria that determine whether a PDF meets WCAG 2.2 AA, why PDFs routinely fail each one, and the fastest remediation path for each failure type.

Why PDF Accessibility Audits Matter Under EAA 2026

The EAA entered enforcement on June 28, 2026. It applies WCAG 2.2 AA to digital documents distributed in EU markets by organizations with 10+ employees or €2M+ annual revenue. PDFs — annual reports, product documentation, e-learning materials, publications — are squarely in scope.

Unlike website accessibility, PDF accessibility is rarely audited proactively. Most organizations do not know what percentage of their PDF inventory is non-compliant. This checklist gives compliance managers a structured starting point.

The 8-Point PDF Accessibility Audit Checklist

1. Document Structure and Heading Hierarchy (WCAG 1.3.1)

What to check: Does the PDF have tagged headings (H1, H2, H3) that reflect the visual hierarchy? Open the Tags panel in Adobe Acrobat and confirm heading tags are present and correctly nested.

Common failure: Most PDFs exported from Word or InDesign without explicit accessibility settings contain no heading tags. Text that looks like a heading is styled visually but carries no semantic role.

Impact: Screen reader users cannot navigate by headings. For a 40-page compliance report, this means a blind user must listen to the entire document sequentially.

Fastest fix: Convert to EPUB3 using toolkit.bot. The converter detects heading structure from font size, weight, and position cues and rebuilds it as semantic HTML5 headings — no manual tagging required.

2. Reading Order (WCAG 1.3.2)

What to check: Enable "Read Out Loud" in Acrobat (View → Read Out Loud → Activate) and listen to the document. Does the content play back in logical order, or does it jump between columns, mix footnotes into body text, or read sidebars mid-paragraph?

Common failure: Multi-column layouts are almost always read incorrectly. Acrobat reads across the full page width before moving down, so two-column text is read as alternating fragments from each column.

Impact: Every user relying on a screen reader or text-to-speech tool encounters garbled content. This is a WCAG 1.3.2 failure and an EAA non-compliance.

Fastest fix: Convert to EPUB3. HTML5 source order is explicit — the converter preserves correct reading sequence and eliminates column ambiguity.

3. Alternative Text for Images (WCAG 1.1.1)

What to check: Right-click each image in Acrobat → Properties → Tag tab. Confirm an "Actual Text" or "Alt" attribute is set. Decorative images should be marked as Artifact.

Common failure: Images are inserted without alt text. Figures, charts, and diagrams have no programmatic description. Logos are unlabeled.

Impact: Screen reader users get no information from images. For documents with charts conveying regulatory data, this is a critical compliance gap.

Fastest fix: For images where alt text exists in the source PDF, toolkit.bot carries it through to the EPUB3 output. For images lacking alt text, post-conversion manual addition in a text editor (the EPUB3 file is HTML — edit with any editor) or Sigil is faster than editing a PDF.

4. Hyperlink Descriptions (WCAG 2.4.4)

What to check: Are hyperlinks labeled with meaningful text, or do they display bare URLs ("https://example.com/document/12345/page/7") or generic text ("click here")?

Common failure: PDFs generated from Word documents often contain URLs as link text. Screen reader users hear an entire URL read aloud with no context.

Impact: Navigation by links — a standard screen reader workflow — becomes unusable when all link text is either a URL or "click here."

Fastest fix: Correct in the source document before conversion. If the source document is no longer available, edit the EPUB3 output directly — changing link text in HTML takes seconds.

5. Table Structure (WCAG 1.3.1)

What to check: Does each data table have header cells (TH tags in PDF tag structure) identifying columns and rows? Use Acrobat's Table Editor (Tools → Accessibility → Table Editor) to inspect.

Common failure: Tables are tagged as TD cells throughout, with no header cells. Simple presentation tables (price lists, comparison grids) are the most common failure.

Impact: Screen reader users cannot determine which column or row a data cell belongs to. A regulatory comparison table becomes incomprehensible.

Fastest fix: toolkit.bot detects table header rows from visual formatting and emits correct HTML5 <th> elements in the EPUB3 output. Complex tables with merged cells may need manual review after conversion.

6. Document Language Declaration (WCAG 3.1.1)

What to check: File → Properties → Description tab in Acrobat. Is a language set in the "Language" field? If blank, the PDF has no language declaration.

Common failure: Most PDFs exported from Microsoft Office or Google Docs do not carry language metadata unless explicitly set. This is a trivial fix in the source document but rarely done.

Impact: Screen readers cannot select the correct pronunciation model. A French document without a language declaration will be read with English phonetics by default.

Fastest fix: EPUB3 requires a language declaration in package metadata. toolkit.bot sets this automatically from the detected document language — this failure disappears in conversion.

7. Content Reflow at 400% Zoom (WCAG 1.4.10)

What to check: Open the PDF, zoom to 400%, and scroll horizontally. Does content require horizontal scrolling to read? For a standard widescreen monitor, content should reflow to a single column at 400% zoom.

Common failure: All fixed-page PDFs fail this test. PDF pages have fixed dimensions — zooming enlarges content but does not reflow it. This is inherent to the format, not a configuration issue.

Impact: Users with low vision who rely on high zoom levels cannot read PDFs without constant horizontal scrolling. This is arguably the most pervasive accessibility failure in all PDF documents.

Fastest fix: This cannot be fixed in PDF. The document must be converted to a reflowable format. EPUB3 passes WCAG 1.4.10 by design — text wraps at any zoom level.

8. Color Contrast (WCAG 1.4.3)

What to check: Use a color contrast analyzer (Colour Contrast Analyser is free) on body text. Normal text requires a 4.5:1 contrast ratio against its background. Large text (18pt+ or 14pt bold) requires 3:1.

Common failure: Light grey text on white backgrounds. Branded PDFs using corporate color palettes that were chosen for aesthetics rather than accessibility. Watermarks behind text that reduce effective contrast.

Impact: Users with low vision or color blindness cannot read insufficient-contrast text.

Fastest fix: Must be corrected in the source document. If the PDF is the only available version, recreate it with sufficient contrast before converting to EPUB3.

Audit Priority: Which Documents to Remediate First

Most organizations cannot audit every PDF simultaneously. Prioritize by:

The Fastest Remediation Path for Most PDFs

For the majority of structured PDFs (reports, publications, documentation), conversion to EPUB3 resolves 6 of the 8 checklist items automatically:

Items requiring source document correction (alt text for images, color contrast) must be addressed before or after conversion — but those are the minority of failures in most document types.

To convert: upload at toolkit.bot/pdf2epub — free, no account required, approximately 30 seconds per document. Validate the output with ACE by DAISY to generate a formal WCAG 2.2 AA conformance report.

Start your PDF accessibility audit — convert free at toolkit.bot, then validate with ACE by DAISY.

Convert a PDF Free →

For High-Stakes Documents

Legal filings, regulated publications, certified VPAT documentation, and high-distribution public-facing content warrant human review after automated conversion. The toolkit.bot Premium Verification service provides expert human review, formal WCAG 2.2 AA assessment, and documentation suitable for regulatory submission. Request premium review →

For accessibility teams managing EAA compliance workflows, see our dedicated guide at toolkit.bot/for/accessibility-teams →

Related guides