PDF Accessibility

Adobe's Portable Document Format (PDF) is widely used in distributing documents on campus. It is possible to make most PDF files accessible for users with disabilities, but it is generally much easier to make HTML web pages accessible, and HTML is more widely supported by assistive technologies. Also, certain content (such as mathematical and scientific notation) can not currently be made accessible in PDF files. Therefore, the first consideration related to PDF accessibility must always be this:

Is PDF necessary for my document, or could I communicate the same information using an HTML web page?

If your answer to the above question is "Yes, PDF is necessary", it is important to follow certain steps in order to create a PDF that is accessible. It is also possible to correct accessibility problems post-production using Adobe Acrobat Professional. This page contains workflows for both situations.

Making a PDF Accessible from Scratch

  1. Use authoring tools that support accessible tagged PDF (e.g., Microsoft Word in Windows)
  2. Follow best practices for authoring documents that are accessible:
    • Use built-in styles for headings
    • Add alt text to images (in Office 2010 and 2011 use Description field; not Title)
    • For data tables, explicitly identify the header row (in Word, do this in Table Properties)
  3. Export to Tagged PDF (see below)

Exporting from Word to Tagged PDF

Creating an Accessible Tagged PDF from Adobe InDesign

The following steps apply to InDesign CS5.5. Documents created using CS4 and earlier versions of InDesign require accessibility repair using Adobe Acrobat Pro (see the next section).

There are additional details about each of these steps, plus a few others, in Adobe's white paper New Solutions for Creating Accessible PDF Documents with Adobe InDesign CS5.5 (in PDF). There are additional resources available on the Adobe InDesign CS5.5 Accessibility website.

PDF Document Accessibility Repair Workflow (using Adobe Acrobat Pro)

NOTE: Modifying PDFs can have unpredictable results, and there is no "Undo". Save often! (Saving multiple versions is recommended)

  1. Does document have text?
    1. If no, covert to text (View > Tools > Recognize Text)
  2. Is document tagged? (Ctrl+D, "Description" tab)
    1. If no, add tags (View > Tools > Accessibility > Add Tags To Document)
  3. Does document need to be "touched up"? (View > Tools > Accessibility > Touch Up Reading Order)
    1. Click decorative or redundant images, then click "background"
    2. Add alt text to remaining images (right click on image, "Edit alt text")
    3. Rearrange order if needed (click "Show order panel", drag items)
  4. Are headings marked up as headings at appropriate levels?
    1. Determine visually what the heading structure should be
    2. View > Show/Hide > Navigation Panes > Tags
    3. Use PDF text selector to highlight headings
    4. In Tag pane, select "Find Tag from Selection"
    5. To change tag, right click, select Properties, enter Alternate Text
  5. Does other markup need to be fixed?
    1. Delete tag and start over from scratch????
  6. Are URLs encoded as links?
    1. If not, Tools > Document Processing > Create Links from URLs
  7. Is the language of the document defined?
    1. File > Properties > Advanced > Language
  8. Check for any lingering errors
    1. Tools > Accessibility > Full check

PDF Form Accessibility Repair Workflow (using Adobe Acrobat Pro)

  1. 1. Is form interactive?
    1. If no, proceed to Creating Accessible PDF Forms using Acrobat Pro
  2. Is tab order intuitive?
    1. If no, correct it (Tools > Forms > Edit, play with Tab Order; select "Close Form Editing" when finished)
  3. Are all text fields appropriately labeled? How to tell:
    1. Tools > Forms > Edit; look in Properties for ToolTip of each field, or
    2. Tab through form using Read Out Loud (View > Read Out Loud > Activate Read Out Loud)
  4. To fix labels on text fields:
    1. Right click on field; select Properties
    2. Enter a detailed, easy-to-understand prompt as Tooltip
  5. Are radio buttons appropriately grouped and labeled?
    1. All radio buttons in a set should have the same name
    2. Tooltip is the overall prompt for the set (similar to legend in HTML)
    3. Labels for individual radio buttons within the set are defined using the Button Value field in the Options tab
  6. Are checkboxes appropriately labeled?
    1. Checkboxes can’t be grouped like radio buttons. The workaround is to be sure the prompt for the overall set of checkboxes is clear within the tooltip for each option (for example, "Favorite Food: Tofu", "Favorite Food: Steak", "Favorite Food: Pizza", etc.)
  7. Finishing touches
    1. Tools > Document Processing > Create Links from URLs
    2. Tools > Accessibility > Add Tags To Document
    3. Repair tags as needed
    4. Tools > Accessibility > Full Check

Creating Accessible PDF Forms using Adobe Acrobat Pro

Creating Accessible PDF Forms using Adobe LiveCycle Designer

Some people prefer using LiveCycle Designer for creating PDF forms. It is fairly easy and intuitive, and has many more features for creating robust interactive forms. The pros and cons of each are beyond the scope of this document, but there are other sources for this information, including Adobe's Acrobat versus LiveCycle Designer.

If you choose to create forms using LiveCycle Designer, here are some things to keep in mind related to accessibility:

PDF Accessibility Resources