How to ensure PDF accessibility: tips and tools?

Hi everyone,

I’m looking for advice on how to create accessible PDFs. Specifically, what are the best practices to ensure that the formatting and content remain accessible for all users? Could anyone share a checklist or some guidelines for creating accessible PDFs?

We’ve encountered an issue where converting Google Docs to PDFs sometimes disrupts the formatting, affecting accessibility. Are there any tools or resources you’d recommend to ensure accessibility during the conversion process?

Any tips on common mistakes to avoid would be greatly appreciated!

Looking forward to your feedback and suggestions!

@mpaulhac I’ve contacted our digital accessibility team for advice so hopefully will have something to share soon!

1 Like

Thanks a lot @anna.hughes! It’ll be great to have some advice on this. Looking forward to hearing what your team suggests!

Hi @mpaulhac, one way is to download the Google doc as Word, correct any formatting issues happening in the process, then convert it into PDF/A format. [Here](https://www.adobe.com/uk/acrobat/resources/document-files/pdf-types/pdf-a.html/) is some more info on the PDF/A format and why it is better than the standard PDF.

I’m sure there are other options too, just sharing what has worked well in some instances for me. Google online tools often have these issues of formatting problems and there isn’t an automatic fix that I have found so far. But I am also looking forward to hearing solutions from others!

1 Like

Here’s the advice from the Jisc accessibility team regarding accessible PDFs :slightly_smiling_face:

The most effective way to create an accessible PDF is to ensure the original document (e.g. Word or Excel) is properly structured before converting it. This should include:

  • Using correct heading styles (Heading 1, Heading 2, etc.)
  • Creating structured content using bulleted or numbered lists
  • Writing alt text for all meaningful images
  • Avoiding text boxes and floating elements that may disrupt reading order
  • When converting to PDF, always use Save As PDF or the Acrobat PDF

Before exporting, use the built-in Accessibility Checker in source documents (e.g. Word or Excel). This will highlight common accessibility issues. Also ensure that:

  • Tables have headers and first column styles applied
  • Hyperlinks use meaningful and descriptive text
  • Colour is not used as the only way to convey information
  • Text and background have sufficient contrast
  • The reading order flows logically
  • Images have alt text (if required)
  • Bookmarks are included for documents that are 20+ pages

It’s not recommended to fix tagging or structure directly in Adobe Acrobat Pro. This requires a licensed version of Acrobat Pro DC and can be complex and time-consuming. Getting it right at source is both quicker and more reliable. It also means you will have two accessible formats to offer.

Even when a PDF is created from a well-structured document, a manual check is still needed. At a minimum, you should:

  • Confirm the reading order is correct
  • Ensure all images include alt text
  • Check colour/contrast of text and background
  • Test the PDF with a screen reader (e.g. NVDA or VoiceOver)

External guidance from Microsoft:

I hope this is helpful!

3 Likes

Hi @Ursula_Rabar, thanks a lot for sharing your method – that’s really helpful!

I wasn’t aware of the difference with PDF/A, so the link is much appreciated. I’ll definitely give your approach a try :grinning_face_with_smiling_eyes:

Hi @anna.hughes, thank you so much for this detailed explanation – incredibly helpful!

There are definitely a few things here I hadn’t considered before, like using the built-in Accessibility Checker in Word. I also didn’t know about avoiding fixes directly in Acrobat Pro – that’s a useful heads-up.

I’ll go through the steps you outlined and try to incorporate them into my workflow.
Also, thanks for linking the Microsoft and Adobe guides – bookmarking those now!

If anyone has tips on how to do a quick but effective screen reader test (like a good starting point with NVDA or VoiceOver), I’d be really interested to hear.

My colleague has recommended this advice page: https://www.gov.uk/service-manual/technology/testing-with-assistive-technologies

1 Like

Some experience-based advice on creating UA compatible PDFs from Word:

Formatting

All formatting must be done using Word styles. Be aware that Word creates lists – bulleted, numbered – automagically, but they are coded as normal, hence useless in this context. Use the list styles offered.

Headings

Use headings by applying the relevant heading styles, not by applying formatting to text. And use headings to create a structure in the document. In the top menu choose View, then tick the Navigation Pane option. This will give you a navigation window on the left. Check that your headings look like a meaningful structure, and that heading levels follow each other in an intelligent manner. If you have blank lines there, one or more lines without text have been assigned a header style. Navigate to the line by clicking it in the pane, and change the style to Normal

Alternative text

All elements that are not running text needs an alternative text that explains what it shows, be it a table, a graph or a picture. This needs to explain what message the element conveys. The Table/Figure text that is to be shown below the element has another function; it is a label.

Table headers

Tables need a header. Right-click the table, in the pop-up menu choose Table properties, then Row and make sure the “Repeat as header row …” is ticked. That makes the row a header in the metadata. (If anyone has found a better way of doing it, please tell me!)

Spelling

Correct spelling and punctuation are also parts of Universal Access. While humans can correct for many misspellings, reading aids probably won’t be able to. So, check your text!

Tools

Use the Review – Check Accessibility tool actively and get rid of all comments. But be aware this tool may not discover all problems. The tool will e.g. not check if your alt texts are intelligible and useful, which is the object of the exercise.

Before you finish, use the File – Info menu to add a Title to your document.

Creating a PDF: I have experienced loss of alt texts using the Save as PDF option, and have started to use the Export – Create PDF/XPS Document option, ticking the Create bookmarks using Headings and PDF/A compliant options.

2 Likes

Yes, use Google docs for text creation, when that is done import to Word for formatting, structure, internal linking etc. E.g. to create captions for figures/tables, linking from text to headings/figures, creating Table of Contents if the document is long. Google Docs does not work for that kind of work, which you need if the document is long.

1 Like

Thanks a lot @janeriks for sharing these practical and well-explained tips! The point about using proper heading styles and checking the document structure with the Navigation Pane is a great reminder, it really helps ensure logical reading order and accessibility.

Also, I wasn’t aware that using “Save as PDF” could strip alt texts. I’ll definitely switch to “Export > Create PDF/XPS” with the bookmarks and PDF/A options, that’s a very helpful insight :folded_hands:

Really appreciate you taking the time to share this. It’s the kind of hands-on advice that makes a real difference!

1 Like

Thanks! I have been doing quite some UA work lately, and I have seen what mistakes I have made myself - despite being a seasoned word processor user. :grinning_face:

1 Like

That’s definitely relatable! :laughing: It might be worth thinking about putting together a short document that brings together all these practical tips and lessons learned. Could be a very handy resource for others here, something to think about!

1 Like