Hasan does not own a computer and is using his phone to read important information on a government service. The information is only available in PDF. He cannot read it on his phone because it isn’t mobile friendly, and so the text does not resize.
Uta is an auditory learner. The government has released a new report on climate change that she's listening to using a screen reader. The report has not been designed for accessibility, so the content is being read to her in the wrong order.
Vanda is blind and needs to fill in an application form using a screen reader. The form is only available online as a scanned PDF. As there is no alternative version, Vanda has to ask a friend for help.
To make a PDF accessible:
Before you create or export a PDF, consider whether it’s the right format for your audience and purpose. PDFs can be difficult to access because they use a fixed layout that doesn’t reflow or resize well on mobile devices. Many PDFs also start as scanned images, which are harder to read for sighted users and screen readers. They also tend to have large file sizes, which can be difficult to download in rural or low-bandwidth areas. These challenges are why PDFs should only be used when there is a clear need for a fixed layout.
When possible, write page content instead of including a PDF, this improves accessibility and Search Engine Optimization. Use a PDF on the website only when there is a real need to preserve a fixed layout, for example:
Avoid posting PDFs that are scanned or image-only.
If you publish a PDF on a government website, you must also provide the same information in HTML.
PDF may be appropriate for internal use when the document is meant to be read, not modified (for example, a reference guide or a formatted presentation handout).
If ongoing updates are needed, a Word document or shared online file is usually a better choice. This helps avoid version-control issues and makes collaboration easier.
For professional design advice, public servants can contact their GCPE Communications Shop for support.
If you’re converting a document (such as a Word file) to PDF, start by making the original document accessible. A well-structured source file makes it much easier to create an accessible PDF.
Starting with an accessible Word document does not necessarily mean your PDF will be accessible, but following accessibility best practices in your source file will put you further ahead in the process.
Sometimes you may be working with an existing PDF that lacks headings, lists or other structure. In that case follow the instructions in how to tag your PDF to add formatting like headings and lists.
Resource: Microsoft’s video on improving heading accessibility (external link)
Before you export to PDF check that your source document:
Resources: Creating accessible Microsoft Word documents
If you're working with a PDF that was created by scanning a printed document, the text on the page isn’t actual text, it’s an image of text. That makes it unreadable for screen readers and unsearchable for sighted users.
Use Optical Character Recognition (OCR) to convert the scanned text into selectable, searchable text. To do this in Adobe Acrobat:
Resource: Recognize text in scanned documents (Adobe Help Centre)
Run the Accessibility Checker near the beginning of your PDF work to see what Acrobat detects, and then run it again at the end to confirm everything has been fixed. To do this:
The checker will almost always flag 'Colour Contrast' and 'Logical Reading Order'. These items need a human to review them, so they will appear even when your document is built correctly.
Resource: Using the Accessibility Checker (YouTube tutorial)
Setting the document language helps screen readers understand and pronounce the text correctly. To set the language:
If your document includes more than one language, first set the main document language. For sections written in another language, you’ll need to identify those passages manually when tagging the PDF so screen readers switch pronunciation correctly. To do this:
Tags give your PDF a logical structure that screen readers rely on. They identify headings, paragraphs, lists, images, tables and decorative elements. A correctly tagged PDF is essential for accessibility.
First, check whether your PDF already has tags.
Avoid using Auto-tag unless necessary. It can create incorrect or confusing tag structures that require extra cleanup.
To add tags to your PDF open the 'Order' tab in the Accessibility Checker:
Resource: Tagging your PDF (YouTube tutorial)
Before converting a document to PDF, make sure your source file is accessible. Elements like headings, lists, links, titles and alt text should be added in the original program before you create the PDF. This makes it much easier to generate a properly tagged PDF. After conversion, check that your formatting carried over correctly.
If you're working with a PDF that was created without proper heading structure you can add or fix heading tags in Acrobat. Headings should always be added in the source document when possible, so they're both visual and structural. But if you’re working with an existing PDF and don’t have access to the source file, you can tag text as a heading to repair the structure for screen readers. To do this:
Lists should always be created properly in the source document so they have the correct structure in the PDF. Proper list tags ensure screen readers recognize lists and read items in the right order. They also allow people to navigate item by item. After converting to PDF, check that each list item is tagged properly.
If you’re working with a PDF that uses visual but not structural lists, for example dashes or symbols instead of list formatting, you can fix them in Acrobat. To do this:
Bookmarks are links that take readers directly to a specific page or section in your PDF. They make documents easier to navigate for all users, not just those using assistive technology. Bookmarks are required for accessibility if your PDF is longer than 21 pages, but they are often useful even in shorter documents.
When creating bookmarks, use clear and descriptive labels that match the section headings. Avoid generic labels which don't provide any context, for example: ‘Page 3'.
Resource: Creating Bookmarks (YouTube tutorial)
The Accessibility Checker will flag ‘Logical Reading Order’ when you run it. That's because it needs a human to review the order to make sure it's logical. The tagged order should follow the same flow that a sighted person would use. In most cases this means, left to right and top to bottom.
To check the logical reading order:
Resource: Using Logical Reading Order (YouTube tutorial)
You can’t change link text after a document is converted to a PDF, so make sure your links are clear in the source document.
Only use tables for actual data, not for laying out content.
Just because a table has been tagged does not mean it’s fully accessible. Most of the work, like keeping tables simple, avoiding merged or split cells, and marking header cells, should be done in your source document before converting to a PDF. Once the table is in the PDF, you can check and adjust the tags to make sure header and data cells are correctly identified.
Tags need to indicate which cells are headers and which cells are data. To do this you need to check how individual cells are tagged:
To add or correct header cells:
Resource: PDF Accessibility: Tables (YouTube)
Colour contrast plays an important role in making your PDF easy for everyone to read. Make sure your text stands out clearly from the background and avoid relying on colour alone to communicate meaning. Whenever possible, set colours and contrast in your source document so the PDF exports with good readability. Learn more about using colour and contrast.
Figures are anything visual in your document for example, photos, graphics, shapes or charts.
Alternative text (alt text) helps people who cannot see the visual content understand the context of it. Learn more about using visuals and writing alt text.
To add alt text in a PDF:
Run the Accessibility Checker to find any instances of missing alt text. But remember, just because alt text is present doesn’t mean it’s useful, someone needs to manually review each description to confirm it makes sense in context.
After tagging and formatting, test your PDF using a screen reader (or ask someone who uses one) to make sure content reads in the correct order, alternative text works and the navigation is clear.
If you don’t have access to formal user testing, you can do a basic check of your PDF using free screen-reader tools. Always confirm with privacy or security team before installing or enabling any new software.
Built-in options (no installation needed):
These tools are not a replacement for testing with actual screen reader users, but they can help you catch issues like incorrect reading order, missing alt text or inaccessible navigation.