Ohio University

Accessible Documents

Microsoft Office Accessibility

Office 365 and some prior versions have a built-in Accessibility Checker. This can be found in some versions under File > Info > Check for Issues. This will identify a limited number of issues. See Microsoft's Accessibility Checker help page for more information.

Accessible Microsoft Templates offer a great way to get started with accessibility and speed up your workflow. They can also be modified to meet OHIO's design guidelines.


Accessible Word documents start with using appropriate styles. You should also include appropriate alternative text for images. In the current version of Word for Windows, right-click on the image and go to "Format Picture". Under "layout and properties", the third icon, expand the Alt Text. Enter in the description field for the alternative text. A title is not required but is helpful. (The description field is read by the greatest number of screen readers and is what is exported as the alt text when creating a PDF.)

WebAim has full details on how to create an accessible Microsoft Word document.

Word for Mac

You will need the most recent version of Word for the Mac to generate a tagged PDF from a word document. Prior versions will not create the tags needed for a PDF document to be accessible, requiring much additional work in the PDF to generate valid tags.


The built in accessibility check will highlight several of the items below and allow you to directly fix those items.

Use the built-in layouts, as these are connected to the outline. If you delete the text fields on the layout and add your own, the text you enter will not be accessible to screen reader users.

General accessibility of powerpoint documents follows the accessibility general principles. Images and other such content like charts and tables should have alternative text. Prior to distribution, you should remove animations and transitions. Embedded audio and video should have multimedia text equivalents. You should also ensure there is a logical reading order. The color contrast for text should be sufficient; you can use the feature to render in greyscale as a quick test.

Webaim's PowerPoint Accessibility provides additional step-by-step instructions on making MS Powerpoint presentations accessible.

PDF Accessibility

To create an accessible PDF, you will need the full version of Adobe Acrobat. Acrobat has a built in "accessibility checker" that will guide you through some of the things that you will need to add to your document to produce an accessible PDF.

Creating Tags

Accessible PDFs have tags added to the document. These tags provide the structure of the document. While users do not interact with the tags directly, assistive technology uses the tags for navigation. The PDF tags are similar, though not identical to, HTML tags.

When creating a document, the default view of a PDF within Acrobat does not show the tags. To show the tags tool, go to the view menu, then select show/hide, navigation panes, then select tags.

The most efficient and effective method of generating these tags actually starts with your source document. When creating a PDF out of a Microsoft Word (MS Word) document that is appropriately using styles such as headings and paragraphs, these styles will convert to the tags we need in the PDF document. If your document contains forms or tables, you will need to do additional work within Acrobat to make these accessible in the PDF.

The Action Wizard in the most recent version of Acrobat XI can guide you through some of the steps to make your PDF accessible.

Why use tags?

  1. Tags provide alternative text for images.
  2. Tags provide table markup such as headings.
  3. Tags provide heading and other structure of the document to aid in locating and navigating to content easily.
  4. Tags provide notice of language changes of text in document. Assistive technology will then speak the marked up text as appropriate for that language.
  5. Tags provide the order of the form fields when tabbing through a document (works with the Reading Order tool).

Outline of steps

  1. Optimize the source document for accessibility; for example, by providing sufficient color contrast between text and background and using semantic features like headings to identify sections instead of big, bold text.
  2. Save the file as a tagged PDF.
  3. Provide metadata for the PDF, such as the document language.
  4. Create and edit tags (similar to HTML tags) to give structural meaning to the document and allow navigation with assistive technology.
  5. Ensure that the reading order - how the content is presented to screen reader users - is logical.
  6. Ensure that the tab order (when the PDF has form fields or links) is sequentially correct.
  7. Check the PDF with automated and manual testing to ensure accessibility.

Accessibility in PDF documents ideally starts with the source document, preferably an MS Word document. For many tags, it is easier to put accessibility into the source document instead of trying to manually add them to the exported PDF. In particular, use the styles to designate headings and changes in text instead of manually changing font size and formatting. Avoid putting in empty line breaks as this will create unnecessary content in the PDF; if needed change the style to add spacing after paragraphs. When possible, use simple tables of one row and/or one column heading, as more complex tables will require more work with the tags in the exported PDF.

If you have a PDF generated from a scan of a hard copy, a lot of work will be required to convert this to text that is compatible with assistive technology. It is a better use of time to locate a digital copy of the original source and convert that than to attempt an Optical Character Recognition on a scan of a hard copy document. If you need to work with a scanned PDF, you will need to run the Optical Character Recognition tool and ensure the converted text is accurate.

Note on Google Docs: "printing" to a PDF from a google doc does not produce a tagged PDF document. To create a tagged document from a Google Doc, export to a MS Word document format first, and then fix styles and alt text as appropriate. Then follow the steps to export to a tagged PDF.

How you convert the document matters. There are several different ways to generate pdfs from word documents. The one that best preserves the accessibility features is to use the Acrobat add-in installed into MS Word when you install Adobe Acrobat. When you export, you may need to select an option to produce an accessible tagged PDF. Other processes such as choosing "print to PDF" from the print menu option may not preserve the tags necessary for your PDF to be accessible, causing additional work to remediate the document.

Using the accessibility checker

The accessibility checker in the full version of Adobe Acrobat will check for the required elements of an accessible PDF. It will generate a report of which elements pass and fail. It checks things like a document title, a document language, as well as the existence of tags for the content in the document and the reading order of the document. Once you have a tagged PDF, run the accessibility check as a reminder of the other features you need in your PDF. Change the initial view to show the document title instead of the file name; assistive technology will read the window title when the document opens.


For documents that include tables, you should make sure the original tables are simple tables- one column heading and/or one row heading. After you convert, you will manually need to change the tags to identify cells as header cells.

Resources for making accessible PDF documents