Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

Overview

When possible, PDFs should be eliminated in favor of web pages because they do not work well on mobile devices and are challenging to navigate for people using assistive technology.

However, if you must publish your information in PDF format the content needs to be fully accessible to everyone.

Whenever we publish online content, we need to make sure everyone can read it, including keyboard only users and people using assistive technology such as a screen reader.

This is also true for PDF documents. Similar to directly coding content into a website, there are special steps we must take to make sure that a PDF document can be read by assistive technology. 

Any other attachments such as Word and Excel documents must also be fully accessible to everyone, including users who use assistive technology like screen readers.

Issues with PDF Documents

  • Mobile Issues: Unlike web pages, PDF documents are not responsive and do not adjust to your screen size, such as on a mobile device. This forces the user to have to zoom in and the swipe left to right /right to left in order to read the content.

  • Difficulty Navigating Content: They are difficult for web users, including screen reader users, to navigate when seeking specific information. Because the website navigation menu doesn’t appear when viewing the file, users can become disoriented.

  • Language Barriers: Content within PDFs are not easily made available in different languages. Per the city’s Digital Accessibility and Inclusion Standards, you need to provide vital information in required languages.

  • Not Designed for Reading on Screen: PDFs are not really designed for reading on screens. They should mainly be used as a way to print information.

  • Maintenance and Outdated Information: PDF documents are more time consuming to update and maintain and as a result often times are overlooked and as a result information in PDF documents is more likely to be outdated.

Step-by-Step Guides - Creating Accessible PDF and Word Documents

General Checklist and Guidelines

  1. Make sure the PDF is in a text based format.

  2. Create a logical reading order by providing a main heading and subheadings.

  3. Tag and build your document structure in Microsoft Word
    Apply properly nested headings <h1>, <h2>, <h3>, <h4>, <h5>, etc.
    The <h1> heading should be reserved for the document title
    Add paragraphs <p>

  4. Add ALT text (alternative text) for images.

  5. Complex charts and diagrams that are embedded in the PDF can’t be accessed by screen reader users. In these cases a text based equivalent needs to be provided. This could be a summary of what the chart/graphic is conveying to sighted users.  

  6. Provide sufficient color contrast between text, links and background color.

  7. Provide sufficient color contrast for non text content such a form elements.

  8. Ensure that content displayed in a data table is fully accessible to screen reader users.  

  9. Provide a table of contents so it’s easy for users to find and navigate to information. 

  10. Save your Word or PDF document as a tagged PDF. 

  11. Provide meaningful document titles for screen reader users, using Adobe Acrobat Pro.

  12. Avoid writing important information in the document header or footer. Screen readers will not announce content displayed in the header and footer.

  13. Provide descriptive link text.

  14. Provide labels for interactive form controls in PDF documents

  15. Indicate required form controls in PDF forms

  16. Ensure that any interactive elements such as forms are fully accessible to keyboard users and screen reader users.

  17. Providing name, role, value information for form fields in PDF documents

  18. Test your document in Microsoft Word or Adobe Acrobat for accessibility compliance.

  19. Indicate when user input falls outside the required format in PDF forms

  20. In a PDF created to conform to PDF/Universal Accessibility (ISO 14289), the content can be reflowed and zoomed in to make reading possible for someone with low-vision.

Creating Accessible PDF Documents Using Microsoft Word

Step-by-step guide on how to create an accessible PDF document using Microsoft Word

Use Appropriate Font Type and Font Size

  • Choose an easy to read font like Arial or Verdana

  • The font size should be 12 pt or larger

Use Color Appropriately

  • Make sure there is enough contrast between the words and the background. For example, do not put light gray text on a medium gray background.

  • Never use color alone to convey important information. Some people have color vision problems which prevents them from distinguishing between certain colors.

Add Alternative Text and Captions to Images

Specify Column Headers and Row Headers in Data Tables

Use Meaningful Hyperlink Text

  • Make sure your link text is more descriptive than “Click here” or “View”.

Use Built-in Formatting Styles

  • When adding headers to the document, utilize the various items in the Styles pane instead of manually enlarging and/or bolding text.

  • Make sure that the headings are in chronological reading order. For example, any headers directly below the Heading 1 section must be Heading 2. It must not skip directly from Heading 1 to Heading 3.

  • Include a table of contents for long documents

  • Use the bulleted or number list buttons to format lists

Test Your Document for Accessibility Compliance

Save the Word Document as a PDF

Create Accesible Forms in PDF Documents

General Guidelines

Compared to forms built in HTML, PDF forms have some inherent accessibility limitations. For example, in HTML a visible text label can be directly associated with its form field. In a PDF, the visible label must be duplicated in the "Tooltip". This Tooltip is read to a screen reader user while navigating the form.

Because the visible label and Tooltip are not directly associated, their values can be different. For example, in this screenshot the visible label is "First name", but the Tooltip which is presented to screen reader users is "Last name."

mismatch-label-tooltip.png

These four steps are required to ensure the accessibility of a PDF form:

  • Add the correct form fields to the PDF.

  • Include text in the Tooltip field that describes the purpose of the form control to a screen reader user.

  • Add tags to the form fields.

  • Check (and if necessary, repair) the tab order.

Provide Labels for Interactive Form Controls in PDF Documents

Ensure that users of assistive technology are able to perceive form control labels and understand how form controls are used.

Form controls allow users to interact with a PDF document by filling in information or indicating choices which can then be submitted for processing.

Assistive technology users must be able to recognize and understand the form fields, make selections, and provide input to complete the forms, and submit the form, just as sighted users can. Understandable labels that convey the purpose of each form control are essential to form accessibility.

Form inputs generally have labels and instructions to help users understand what information is required and how to fill in the form. Unless these labels are programmatically associated with the relevant fields, assistive technology might not be able to associate them correctly, and thus users might not understand how to complete the form.

Please see step by step instructions on how to create accessible forms in PDF documents.

Additional Resources

WCAG Related References

1.3.1 Info and Relationships (Level A)

4.1.2 Name, Role, Value (Level A)

  • No labels