Skip to main content

Accessible Word Document vs PDF: Where to Start

The short answer: start with the Word file. An accessible Word document, with real headings, alt text, built-in lists, simple tables and a set language, exports to a tagged PDF that needs only a final check. Fix the PDF directly only when you have no source file, when the PDF was scanned, or when it contains forms or complex layouts.

Teams often ask us whether to make the Word version or the PDF version accessible. After 9+ years of document work, our answer is almost always the same: fix the source, and the PDF follows.

Why start with Word?

  • It is faster. Styles, alt text and lists take minutes in Word and much longer in a PDF editor.
  • It lasts. The next time the document is updated, the accessibility is still there. Fixes made only in the PDF are lost on the next export.
  • Anyone can do it. Content editors can learn it in a short training session. PDF remediation needs specialist tools and skills.

What carries over from Word to PDF

When you export correctly, these become PDF tags that screen readers use:
– Headings built with Heading styles become H1, H2, H3 tags.
– Alt text on images becomes the alternate text in the PDF. Decorative images become artifacts.
– Lists built with the Bullets and Numbering buttons become list tags.
– Tables with a marked header row become tables with header cells.
– Links keep their text and destination.
– Document title and language carry into the PDF properties.

What does not carry over well: text boxes, floating images, manual spacing with tabs, and tables used for layout. Fix those in Word first.

How to export a tagged PDF from Word

  1. Run Review > Check Accessibility and fix the errors.
  2. Set the document title: File > Info > Properties > Title.
  3. Choose File > Save As > PDF, then Options.
  4. Make sure “Document structure tags for accessibility” is checked, and create bookmarks from headings.
  5. Save, then open the PDF and check it.

Avoid “Print to PDF”. It produces an untagged file and throws the work away.

When you need to fix the PDF itself

  • No source file: only the PDF exists.
  • Scanned documents: the page is an image. It needs OCR, then tagging.
  • Forms: fillable fields need labels, tooltips and a logical tab order.
  • Designed layouts from layout software, with columns, sidebars or infographics, often need reading order corrections.

These cases are worth doing properly, ideally by someone experienced with PDF tagging.

How to check the result

  • Run the accessibility check in Adobe Acrobat.
  • Look at the Reading Order and the Tags panel: does the structure match the visible document?
  • Read the first pages with a screen reader such as NVDA or VoiceOver.
  • Confirm the title shows in the window bar and the language is set.

Automated checks catch part of the issues. A short manual pass with a screen reader catches the rest.

For a step-by-step on headings, fonts, tables and links, see our document accessibility guide. If you have a backlog of files, our document accessibility team can help.

FAQ

Is an accessible PDF required, or is an accessible Word file enough?

Publish the format your users need. Many organizations publish a tagged PDF and offer the Word file on request. Both should be accessible.

Why does my PDF fail the check even though Word passed?

Usually because of export settings (tags were not included), “Print to PDF”, or elements like text boxes and floating images that do not tag cleanly.

Can I make a scanned PDF accessible?

Yes, with OCR and tagging, but recreating it from a source file is often faster and gives a better result.