How to Create Accessible PDFs: A Practical WCAG 2.2 Guide (2026)

Most PDFs you meet in the wild are inaccessible. A blind reader points a screen reader at them and gets gibberish; a low-vision user enlarges the text and watches the layout shatter. Making a PDF accessible is not hard - it is mostly the discipline of three habits applied consistently. This guide walks through what WCAG 2.2 actually expects from a PDF, how to add the structure that screen readers need, and the small final checks that turn a regular PDF into one that everyone can use.

Who this is for

You are publishing PDFs as part of your job - government, education, healthcare, a regulated industry - and accessibility is required. Or you are publishing PDFs as part of running a public-facing business and you want to do right by every reader. Either way, the underlying skills are the same: structure your source document well, export thoughtfully, run a quick verification pass, and ship.

What WCAG 2.2 actually requires from a PDF

WCAG 2.2 AA is the global de-facto standard for digital accessibility. Applied to PDFs, the practical checklist boils down to seven things:

• Tags. Every meaningful element (heading, paragraph, list, table, link) is marked with a tag so assistive technology knows what it is.
• Reading order. The order tags are read by a screen reader matches the visual reading order.
• Alt text. Every image, chart and diagram has descriptive alternative text.
• Contrast. Text contrasts the background at 4.5:1 (3:1 for large text).
• Selectable text. No scanned-image-of-text without an OCR layer on top.
• Document language. The document carries a language tag so screen readers use the right voice.
• Title and bookmarks. A meaningful title in metadata, and bookmarks for long documents.

Start with the source document, not the PDF

A PDF inherits accessibility from its source. A clean Word document with proper Heading 1/2/3 styles, structured lists, and alt text on every image produces a tagged, accessible PDF on first export. A Word document where every heading is "Bold 18 pt" produces a PDF where the screen reader cannot tell anything from anything.

The two minutes you spend assigning real styles in Word/Google Docs save thirty minutes of post-hoc tagging in Acrobat. If you do nothing else from this guide, do this.

Tagging an existing untagged PDF

1. Open the PDF in our PDF editor or in Adobe Acrobat Pro.
2. Run the auto-tag pass. This adds tags based on visual layout - imperfect, but a much better starting point than untagged.
3. Open the Tags panel and walk through the tag tree. Re-tag mis-identified elements (a heading marked as paragraph, a list mis-tagged as separate paragraphs).
4. For every image, set the alt text. For decorative images add an "artifact" tag so screen readers skip them.
5. Verify reading order using the Reading Order tool. The order should match the visual flow you intend, not the order text was placed on the page.
6. Save and run the accessibility checker (Acrobat) or our built-in lint pass.

Writing good alt text

Alt text is the single biggest accessibility lever. Three rules cover 80 percent of cases:

• Describe the meaning, not the appearance. "Bar chart showing 2025 revenue increased 32 percent over 2024" not "two blue bars side by side".
• Be brief. Aim for 100 to 200 characters. Long alt text becomes painful at screen-reader speeds.
• Avoid "image of" or "photo of". The screen reader already announces the element type.

Reading order: the silent killer

A PDF tagged in the wrong reading order is worse than untagged: it confidently feeds the reader nonsense. The most common mistake is when text in a multi-column layout reads left-to-right across the whole page (mixing columns) rather than down column 1, then down column 2.

The fix is the Reading Order tool in our PDF editor or Acrobat. Number the regions in the order you want them read; the screen reader follows that order regardless of visual position.

Final checks before shipping

• Run the accessibility checker. Address every error before publishing.
• Open with a real screen reader. NVDA on Windows or VoiceOver on Mac. Listen to the first two pages. If anything makes you cringe, fix it.
• Zoom to 200 percent. The text should reflow or remain readable. Hard-baked layout breaks this.
• Tab through interactive elements. Form fields, links, buttons should follow logical order with visible focus.
• Check colour contrast. Use the built-in contrast checker for every text-on-background combination.

Standards beyond WCAG 2.2

PDF/UA is the formal ISO standard for accessible PDFs. It is essentially a strict superset of WCAG's PDF requirements with mandatory structural rules. If you publish under a contract that requires PDF/UA compliance, use a tool that explicitly produces and verifies PDF/UA-1 output (Acrobat Pro is the practical default).

Section 508 (US federal), EAA (EU), and AODA (Ontario) all reference WCAG. Compliance with WCAG 2.2 AA generally satisfies all three.

Conclusion

Accessible PDFs are not a Photoshop-level dark art. They are mostly the discipline of using real heading styles in your source document, writing thoughtful alt text, and spending five minutes verifying reading order. Apply those three habits and every PDF you publish from now on will work for every reader.

Pick the most recent PDF you exported from Word. Open it in our PDF editor, run the auto-tag pass, fix any reading-order issues, and re-save. You have just made one document accessible. Do it for the next ten and accessibility becomes part of your normal workflow.

Frequently asked questions