Accessible PDF documents
Introduction
PDF (Portable Document Format) is a common format for distributing printable documents. This format was created by Adobe and can be opened with Adobe Acrobat as well as many web browsers.
What makes a PDF accessible?
An accessible PDF is usable by persons with and without disabilities, who may use adaptive technologies or techniques to access information. For instance, a blind user may use a screen reader or a braille display. A person with a motor impairment may use a keyboard rather than a mouse to navigate between form fields. Other users may need to adjust the font size or spacing to compensate for vision loss or learning / cognitive disabilities.
General document accessibility guidelines also apply to PDFs. That means that the document should be properly structured with headings, there is sufficient contrast, and images have alternate text. Refer to the general document accessibility guide for additional information.
Since PDF documents often contain interactive components like forms, their accessibility should be evaluated based on the Web Content Accessibility Guidelines. Following this guide does not ensure compliance with these guidelines, but it is a good start.
Recommended authoring tools
Microsoft Word
Note: These instructions apply to Word 2013 and 2016.
The easiest way to create an accessible PDF is to begin with an accessible Word document. Once you have created an accessible document in Word, export it through File > Export (do not print to PDF!).
If you don’t have Adobe Acrobat installed, use the Create PDF/XPS Document option. In the dialog box, select Options and check these boxes:
- Create bookmarks using: Headings
(or bookmarks, if you have created them) - Document properties
- Document structure tags
The remaining boxes should be unchecked.
Adobe products
Adobe InDesign, FrameMaker, and LiveCycle Designer will export to tagged PDF, and offer more control over visual styles than Word. (LiveCycle Designer is specifically tailored to creating forms.)
Validating and remediating accessibility with Acrobat Pro
Adobe Acrobat Pro is the essential tool for validating and remediating PDF accessibility. The current version as of August 2018 is Acrobat Pro DC. The following information is specific to this version.
Automated validation
- Open your PDF document and select Tools
- Under Accessibility, select Full Check. This will generate a list of issues that need to be either resolved or checked manually.
- If Accessibility isn’t already displayed in tools you can reveal it by selecting View > Tools > Accessibility
- Uncheck “Create accessibility report” and select Start checking. A list of issues will appear in a sidebar titled “Accessibility Checker”.
- Inspect each failure
Remediating issues
Some issues can be fixed simply by opening the context menu for the issue and selecting Fix. (Open the context menu by right-clicking or pressing the application key.)
Common issues and solutions
Pay special attention to the following areas of PDF accessibility.
Scanned documents: images of text
PDFs created from scanning in a paper document need, at minimum, to have the text recognized in order to be made accessible. This can be done automatically using Optical Character Recognition (OCR). The OCR process is not 100% accurate, so perform a manual review of the text. See Performing OCR on a Scanned Document.
Document structure (tags)
An important part of PDF accessibility is “tagging”. Tags describe the structural meaning of an element within the document. For example, a link must be tagged as a link to be interactive and a heading must be tagged as a heading to appear in the navigation pane. If you are experienced with HTML, you should find the concept of tags familiar.
Using a recommended authoring tool, tags will be automatically created based on the existing document structure. For instance, a heading created in Microsoft Word will be tagged as a heading in the PDF when you export.
To check if a document is tagged, press Control + D to bring up the document properties, or run the Accessibility Checker. If not tagged, return to your authoring tool (ie.g. Word) if possible, ensure you have structured the document correctly, and export again using the settings given above.
To manually set tags, use the Touch Up Reading Order tool (Tools > Accessibility > Reading Order)
Alternative text (“alt text”) for Images
To set alt text in Acrobat, navigate to Tools > Accessibility > Set Alternate Text. If your image does not show up in the list of figures, or the message “There is no figure information to display” appears, the images have not been correctly tagged as figures, and you will first have to tag them.
Decorative images (which should be ignored by screen readers) should be tagged as “Background”.
Language and title
A meaningful title and the document’s language need to be specified. In Acrobat, press Control + D to bring up the document’s properties. The language field can be found under the Advanced tab.
Bilingual PDF documents present special issues and should be avoided, especially for forms. It is preferable to offer multiple versions of the same PDF, one for each language.
A passage in a different language than the main language of the document must be tagged separately. For example, an English paragraph may appear in a French document stating that the document is also available in English. See Specifying the language for a passage or phrase.
Bookmarks
Any PDF longer than 1 page should include bookmarks. These may be automatically generated (such as when exporting from Word, provided the correct settings are used – see above) or you may have to create bookmarks manually within Acrobat.
Forms
Creating an accessible PDF form is tricky, as form fields created in other programs such as Word are not directly exported into the PDF. See Adobe’s guide to creating accessible forms. Some general tips:
- Instructions: Put instructions at the beginning of the form, rather than in between form fields.
- Labels: In Acrobat, there is no way to specify what label applies to what form field, so each form field must also have its label entered into the “Tooltip” field. Radio buttons and check boxes require additional steps; see University of Ottawa’s PDF accessibility guide, specifically the section “Common PDF accessibility errors with solutions” > “Form fields properties”.
- Input format: Ensure that the correct format is suggested, if one is required.
Ex. Date of birth (YYYY-MM-DD). As with all labels, this should be repeated in the tooltip. - Required fields: Indicate which fields are required. Do not rely solely on colour. If an asterisk (*) is used to indicate required fields, include the following text at the start of the form (eg. * indicates a required field).
- Tab order: Test the form using only the keyboard (using the Tab key to move between fields).
- Ensure that it is obvious (visually) which field is active at all times
- Ensure that the tab order follows the expected (visual) order
Reading order
Documents created in graphics software, rather than Word, may present information in the wrong order to screen readers and other assistive technologies. For instance, the elements might be read in the order they were created, rather than the intended visual order. Multiple columns of text can also cause reading order issues. This can be checked by pressing Control + 4 to reflow the document (See “Other PDF accessibility testing tools” below). See check and correct reading order.
Missing spaces and line breaks
Improper characters used by the author for spaces or line breaks causes words to jam together with reflow. This authoring problem occurs frequently with PDF. To test for this, export to plain text in Acrobat, or select all and copy / paste into a plain text editor like Notepad. In the plain text version, are there missing spaces and line breaks? If so, check your export settings in the authoring program. Next, try using a wider spaced font. If you have reduced the letter or word spacing, put this back to the default. If the issue persists, consider using a different authoring tool.
Tables
Table cells must be associated with table headers. Begin with a simple table (one with no merged cells) in Microsoft Word. Ensure that it is correctly structured with table headers by checking with the aforementioned Reading Order tool. An example of a correctly structured table is shown here. See Repair mis-tagged tables (WCAG) and Examine and Repair Tables (Adobe).
Other PDF accessibility testing tools
Enabling Acrobat’s built-in accessibility features allows you to manually test the reading order and other structural issues. Adobe recommends that you check Reflow view, Read Out Loud, and plain text export.
Testing a form with NVDA (a free screen reader) will quickly identify label and tab order issues. Try to fill out the form using nothing but your ears and your keyboard. This will give you an idea of what screen reader users will experience.
An alternative to Acrobat’s inbuilt accessibility checker is Free PDF Accessibility Checker (PAC 3). While this program alone won’t allow you to remediate issues, you may be able to make your fixes upstream in the authoring tool (Word, InDesign, etc.). It may also identify issues that Acrobat does not.
Additional resources
- W3C PDF Techniques for WCAG 2.0
23 techniques for solving specific WCAG violations, mostly forms and tables (100 pages, 2016) - Adobe: Creating accessible PDFs
Brief overview of creating an accessible PDF with Acrobat DC (8 pages, 2018) - Fixing inaccessible PDFs Using Acrobat Pro
Very brief repair workflow for resolving some of the above accessibility issues (6 pages, 2014) - Acrobat Pro DC PDF Accessibility Repair Workflow
Step-by-step guide to resolving most of the issues above, specific to the current version (60 pages, 2015) - 10 common accessibility errors with solutions
The product of reviewing over 1500 PDF documents, this guide from the University of Ottawaa provides more details including screenshots about solving common issues (24 pages, 2014) - AcceDe: Making PDF documents accessible with Adobe Acrobat Pro
Extremely detailed guide, complete with exercises. Consult this if your questions aren’t answered by the other resources. Slightly dated (95 pages, 2011) - Creation of accessible PDF
Checklist of actions performed to make a PDF accessible. No details. (1 page, 2009)