PDF standards and how they differ in terms of accessibility

Tagged with:

PDF (Portable Document Format) files have been widely used for many years, and are even seen as a universal, simple solution which is compatible with almost everything. This has led to PDF files going from originally being a format for print to being widely used across many industries. Despite it initially seeming like a format that would be very accessible, by default it tends to not be, and there are many vastly different standards of PDF which can have many different implications for accessibility, and even the best formats require some work to be able to create properly.

There are many different types and standards of PDF files, and all are made differently. In this guide, I will list a few of those standards which might be used as examples (even though there are many more):

  1. PDF Full Text and Graphics / PDF (FTG) / PDF Normal: This type of PDF includes both text, graphics and Images and was originally standardised to make PDFs that can be rendered at the best possible resolution. For a PDF to comply with this standard, you must have text as text, graphics as graphics, lines as lines, and only use an image when it is necessary (such as when you are adding an actual photograph)
  2. PDF Image Only / PDF (I): This type of PDF is made up of images only, it's commonly used for sharing photographs or scanned documents. These files can be easily shared and read on a variety of devices, but they are not as accessible as other types of PDFs, due to not actually containing any text but simply an image, and therefore not being visible to any screen readers.
  3. Searchable / OCR PDFs / PDF (I + HT): These documents usually originate from a PDF Image Only file that has been converted to this format using OCR (optical character recognition) software. Searchable / OCR PDF documents are essentially composed of two different layers. A JPEG or bitmap on top (to ensure that the document will look the same to the user) and a layer containing text beneath which has been created using OCR (optical character recognition) software to be able to determine the contents of the document. This allows people to highlight and search for text in the document, and use it more normally compared to an Image Only PDF, however, despite being an improvement, it is not even near to being fully accessible due to it lacking landmarks to add semantic meaning to the page.
  4. PDF Universal Accessibility / PDF (UA): This standard is intended for creating PDFs that are accessible and requires things such as PDFs being tagged, in order to correctly represent to document's structures (tables, headings, lists, etc.), have a logical reading order, alternate text, embedded fonts and much more. These documents tend to be the most accessible but aren't as complicated to make as it sounds.

Note: This is just a very small sample of the many standards that exist, however from this you can see that not all documents are created equal and the accessibility of a PDF file can differ.

Tips for making your PDF documents more accessible:

Whilst there are many different standards, and some have accessibility requirements, it is worth following these more general tips whenever you are making a PDF to ensure that it is more accessible:

Always attempt to create PDFs from source files/media

To put it simply, the most accessible documents will have always have been converted directly from the original source (where it was created) For example, a word document can be converted directly, which is significantly better than converting things multiple times. One thing that you should attempt to avoid doing at all costs is scanning something using a scanner to "make it a PDF", as this produces documents that are inaccessible to people with disabilities, due to it simply being a bitmap/image.

Ensure that PDF files have proper semantic headings and that all images and complex diagrams have alternate text

Note: If the original document that you want to turn into a PDF was made in Microsoft Word, Ben Watson had made a brilliant guide on the basics of making accessible word documents which outlines how to ensure that your document is ready to export.

One way to check if a PDF document is accessible within Adobe Acrobat Pro is by going to Tools > Accessibility > Full Check / Accessibility check this will allow you to check these basics if you have an Acrobat Pro licence. If you don't have a copy of Adobe Acrobat Pro, you can check on a browser if you can highlight text on a PDF, and that the original file had proper headings and alternate text, however unfortunately the only way to test this without an Acrobat Pro licence fully is to use an actual screen reader.

It is always good to use existing accessibility checkers, such as the one built into Microsoft Word and Adobe Acrobat to check the original or PDF documents.

If you cannot find or do not have the original source for a document, use scanning / OCR tools to be able to add text to the scanned version

In the event that you need to use an image-only document, and there is no way to recover/find the original source document, you can use optical character recognition/scanning tools, such as what is built into Adobe Acrobat Pro to be able to create a text layer. You can either scan the original bitmap and use both or convert it entirely to just be the scanned document, deleting the original bitmap. In most cases, we would recommend using Adobe Acrobat Pro to convert scanned documents, as most other software is paid and usually even more limited.

After having scanned your image-only PDF, you can use software such as Adobe Acrobat Pro to create heading landmarks to make it more accessible.

Be careful when using complex layouts to ensure that there is a logical reading order

Quite a lot of modern PDF templates and designs tend to have issues where they don't have a logical reading order. For example, a lot of templates that have layouts with multiple columns may not necessarily have used the order panel in Adobe Acrobat Pro to be able to show this, which can end up meaning that instead of reading down the individual column, like what would make sense to the user, some screen readers can end up reading across the whole document instead, which ends up meaning that the document does not make any sense to the user (due to the nature of the second column not being intended to be read with the first column, but separately) These kinds of layouts, when not properly specified, can pose large accessibility issues for some users.

On some versions of Adobe Acrobat Pro, you can ensure that your PDF document has a logical reading order by going to Tools > Accessibility > TouchUp Reading Order > Show Order Panel, to be able to change the reading order of your document so can be properly read by screen readers.

Overall, on this point, it is easiest to avoid complex layouts, however, when needed you can either ensure that your document can be read in a logical order by screen readers by using Adobe Acrobat Pro.

Is it actually worth using PDF?

To put it shortly: not unless a document is explicitly made for print usage, and print usage only, at which point it should be published with another version of the document in an accessible format, such as HTML.

The Government Digital Service (GDS), has even published an article specifically discouraging the use of PDF files in most scenarios in its blog post, titled "Why GOV.UK content should be published in HTML and not PDF" To quote the blog post from the organisation:

"Compared with HTML content, information published in a PDF is harder to find, use and maintain. More importantly, unless created with sufficient care PDFs can often be bad for accessibility and rarely comply with open standards."

They cover a range of issues, such as the fact that they are not able to change to fit the size of different screens, which especially becomes an issue when they are used on smaller screens such as smartphones, they are very hard to make somewhat accessible, they are not easily maintainable (to update things such as the layout and the standards of, say, 50,000 files, you would need to modify each one manually instead of being able to make changes in bulk, such as what can be done with most web content) and, unlike with most web content or word documents, users cannot adjust things such as colours and contrast, to be able to make a document easier for people to read.

Quite a lot of the time, it is just worth publishing something either as web content that has been made accessible or in formats such as odt (Open Document Text) files or OpenDocument format files, which can be made from within word, LibreOffice, OpenOffice or any modern document editor (and these pieces of software are free to use, unlike Adobe Acrobat Pro) This advice is echoed by the GDS.

Public sector organisations are required to, when publishing PDF documents on their website, provide the files in an alternative format, such as a webpage (HTML) or an OpenDocument format file. Whilst there are exemptions to this, such as for schools and colleges in cases where a document is not needed to be able to access basic services, quite a lot of time, exclusively publishing documents on your website in PDF format, as a public sector organisation, may potentially be in breach of The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 if published after 2018.

Overall, despite PDF files initially seeming like an accessible format, there can be many issues with the ways that most modern PDF files are created in terms of accessibility. By following these steps and understanding how types of PDF differ, you can ensure that everyone, including those with disabilities, can access the information in your documents in an equal way.

Share on:


Site preferences

Please feel free to display our site, your way by finding the preferences that work best for you. We do not track any data or preferences at all, should you select any options in the groups below, we store a small non-identifiable token to your browser's Local Storage, this is required for your preferencesto persist across pages accordion be present on repeat visits. You can remove those tokens if you wish, by simply selecting Unset, from each preference group.


Code block theme

Code theme help

Code block themes can be changed independent of the site theme.

  • Default: (Unset) Code blocks will have the same theme as the site theme.
  • Light 1: will be default for users viewing the light theme, this maintains the minimum 7:1 (WCAG Level AAA) contrast ratio we have used throughout the site, it can be quite difficult to identify the differences in colour between various syntax types, due to the similarities in colour at that contrast ratio
  • Light 2: drops the contrast for syntax highlighting down to WCAG Level AA standards (greater than 4.5:1)
  • Dark: Syntax highlighting has a minimum contrast of 7:1 and due to the dark background differences in colour may appear much more perceivable


Motion & animation

Motion & animation help

  • Default (Unset): Obeys device settings, if present. If no preference is set, there are subtle animations on this site which will be shown. If you have opted for reduce motion, smooth scrolling as well as expanding and collapsing animations will no longer be present, fading transtitions and micro animations will still be still present.
  • None: All animations and transitions are completely removed, including fade transitions.


Underline all links

Underline all links help

  • Default (Unset): Most links are underlined, with a few exceptions such as: the top level links in the main navigation (on large screens), cards, tags and icon links.
  • Yes: Will add underlines to the exceptions outlined above, resulting in every link being underlined

Text and paragraphs

Font size (main content)

Font size help

This setting does not apply to the site's header or footer regions

  • Default (Unset): Font sizes are set to site defaults
  • Selecting Large or Largest will increase the font size of the main content, the size of the increase depends on various factors such as your display size and/or zoom level. The easiest way to determine which option suits you best would be to view this text after clicking either size's button
Letter spacing

Letter spacing help

  • Default (Unset): Default letter spacing applies
  • Increased: Multiplies the font size by 0.12 and adds the sum as spacing between each character
Line height

Line height help

  • Default (Unset): all text has a minimum line height of 1.5 times the size of the text
  • Increased: all text has a line height of twice the size of the text
Paragraph spacing

Paragraph spacing help

Paragraph spacing help
  • Default (Unset): The space between paragraphs is equivalent to 1.5 times the height of the paragraph's text
  • Increased: The space between paragraphs is equivalent to 2.25 times the height of the paragraph's text
Word spacing preference

Word spacing help

  • Default (Unset): No modifications to word spacing are present
  • Increased: Spaces between words are equivalent to 0.16 times the font size