An accessible PDF starts in Word, not after export. Use real heading and list styles, add useful text alternatives, keep tables simple, set the document language and title, then run Word's Accessibility Checker. Export a tagged PDF and inspect that exact file before publishing it.
Use the PDF Accessibility Checker after export to confirm five basic signals: tagged status, title, declared language, extractable text, and bookmarks. It is a first-pass check, not a repair tool or compliance certificate.
Accessible Word-to-PDF checklist
- Structure the Word source with built-in styles.
- Describe meaningful images and mark decoration appropriately.
- Use simple tables with identified header rows.
- Set useful links, a document title, and the correct language.
- Resolve Word Accessibility Checker findings that apply.
- Export a tagged PDF instead of flattening it through Print to PDF.
- Check the exported PDF, then complete manual review.
1. Build Structure with Word Styles
Choose Word's built-in Title, Heading 1, Heading 2, and Heading 3 styles according to the document hierarchy. Do not make a heading by only enlarging or bolding ordinary text. Screen readers and PDF exporters use semantic styles to understand the outline.
- Keep heading levels logical: move from Heading 1 to Heading 2, then Heading 3 without choosing a level for its appearance alone.
- Use real lists: create bullets and numbered lists with Word's list controls rather than typed dashes or numbers.
- Keep the layout readable: use paragraphs, columns, and spacing controls instead of repeated tabs, spaces, or empty lines.
2. Give Visuals a Useful Alternative
Add concise alternate text to an image, chart, or diagram when it communicates information. Describe its purpose in context rather than repeating a caption word for word. Mark purely decorative visuals as decorative so they do not add noise for screen-reader users.
| Visual | Good decision | Avoid |
|---|---|---|
| Product photo | Describe the feature the reader needs to notice | “Image” or the filename |
| Chart | State the trend or conclusion and provide the data nearby | Listing colors without explaining meaning |
| Divider or flourish | Mark it decorative | Adding meaningless alternate text |
3. Keep Tables Simple
Use tables for data, not page layout. Identify the first row as a header row, keep the grid predictable, and avoid merged, split, or nested cells when a simpler structure can communicate the same information. Complex relationships may still need manual checking after export.
4. Set Links, Title, and Language
- Links: write an anchor that explains the destination, such as “read the accessibility policy,” instead of “click here.”
- Title: give the file a descriptive document title, not only a filename. After export, you can inspect or correct basic title metadata with the PDF Metadata Editor.
- Language: set the primary document language and mark passages that switch languages when your Word version supports it. The declared PDF language helps assistive technology choose pronunciation rules.
- Navigation: a meaningful heading outline can support bookmarks in the exported PDF, especially for long reports.
5. Run Word's Accessibility Checker
In current desktop versions of Word, open Review → Check Accessibility. Review each finding in context. Microsoft says the checker explains why a flagged issue may matter and suggests a way to resolve it. A clean automated report is helpful, but it cannot judge every reading-order, wording, or document-purpose decision.
Microsoft's Word accessibility guide covers the checker, headings, alternate text, links, color, and table practices across supported Word editions.
6. Export a Tagged PDF
Use Word's PDF Save As or Export workflow and keep the option that preserves document structure tags for accessibility enabled when it is available. Menu labels vary by platform and Word version, so review the PDF options rather than assuming the default.
Avoid Print to PDF for an accessible master. A print workflow can flatten or discard semantic structure, links, bookmarks, and other interactive information. Export from the accessible source, save a new PDF, and keep the Word file as the maintainable master.
Adobe's accessible PDF creation guidance likewise recommends adding accessibility features in the authoring application. Adobe notes that automatic tagging can misread complex layouts, so export is not the final test.
7. Check the PDF You Will Publish
- 1. Open the PDF Accessibility Checker.
- 2. Upload the final exported PDF, not the Word source or an earlier draft.
- 3. Review tagged status, title, language, extractable text, and bookmarks.
- 4. If a signal is missing, correct the source when possible, export again, and recheck the new file.
- 5. Use the PDF Validator separately if the file also has structural or parsing problems.
What PDFCheck Can and Cannot Verify
| Signal | What the report tells you | What still needs review |
|---|---|---|
| Tagged status | Whether the PDF reports tags | Whether tags are correct and complete |
| Title | Whether title metadata is present | Whether the title is meaningful |
| Language | Whether a primary language is declared | Whether changes of language are marked |
| Extractable text | Whether enough text can be extracted | Whether words and reading sequence are accurate |
| Bookmarks | Whether bookmark outlines are present | Whether navigation is complete and logical |
PDFCheck cannot confirm reading order, alt-text quality, table semantics, or compliance. It also does not change the Word document or repair the PDF. Use its report to prioritize the next check.
Turn a Failed Signal into the Right Fix
| Finding | Best first fix | Then |
|---|---|---|
| Not tagged | Apply Word styles and use tagged PDF export | Inspect the tag tree and reading order manually |
| Missing title | Set a descriptive title in the source or PDF metadata | Recheck the exact final copy |
| Missing language | Set the document's primary language | Review language changes in mixed-language content |
| No usable text | Export from a digital source or use OCR for scans | Verify recognition and reading order; see the scanned PDF guide |
| No bookmarks | Build a logical heading outline in Word | Check bookmark labels and destinations |
Finish with Manual Review
Read the exported PDF in sequence, inspect the tag tree and heading hierarchy, confirm that alternate text explains meaningful visuals, verify table headers and cell relationships, test link purpose, and check keyboard navigation. For an image-only export, first determine whether text exists with the PDF Text Extractor, then use OCR and review its output.
The W3C WCAG 2.2 techniques include PDF-specific examples for text alternatives, reading order, artifacts, OCR, headings, forms, language, title, tables, and lists. Section508.gov also publishes a PDF testing and remediation resource collection.
Standards Context without Overclaiming
WCAG provides broader accessibility success criteria, while PDF/UA describes accessible PDF structure. ISO's ISO 14289-2:2024 overview says PDF/UA-2 specifies how PDF 2.0 is used to construct accessible digital documents; it does not define the conversion or remediation process. Read Understanding PDF standards for the role of PDF/A, PDF/X, and PDF/UA.
Final Release Checklist
- The Word source uses semantic headings, lists, links, tables, and image alternatives.
- Word's Accessibility Checker findings were reviewed, not merely dismissed.
- The PDF was exported with structure tags rather than printed to a flattened copy.
- The exact release file has title, language, text, tags, and useful navigation signals.
- Reading order, alternate text, tables, links, and assistive-technology behavior were manually checked.
For a deeper explanation of the automated first pass, read PDF Accessibility Checker Online: WCAG and PDF/UA Basics.