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.
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.
Avoid “Print to PDF”. It produces an untagged file and throws the work away.
These cases are worth doing properly, ideally by someone experienced with PDF tagging.
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.
Publish the format your users need. Many organizations publish a tagged PDF and offer the Word file on request. Both should be accessible.
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.
Yes, with OCR and tagging, but recreating it from a source file is often faster and gives a better result.
This website uses essential cookies to operate and, with your consent, statistics cookies (Google Analytics). For more details, see our Privacy Policy.