Editing MS Word Accessibility Best Practices

[[Category:Accessibility]]

== Overview ==

This document assumes that the end goal is to create an ADA-compliant PDF using Microsoft Word as the editor of the “native file”.

'''Always keep in mind [http://www.adobe.com/content/dam/Adobe/en/accessibility/products/acrobat/pdfs/acrobat-xi-pdf-accessibility-repair-workflow.pdf Adobe&rsquo;s advice]:''' 

<blockquote>Whenever possible, accessibility should be incorporated directly into the document using the application that created it. When accessibility is incorporated directly into the source document, less repair work will be required in Adobe Acrobat. This is very important when the PDF must be regenerated based on changes in the source file. If changes are only made in the PDF and not in the source file, accessibility work will need to be done each time the document is updated.</blockquote>

== MS Word 2013’s Accessibility Checker ==

This is a feature that is only available in MS Word 2013. Documents have to be saved in the most current format also. 

'''File''' > '''Info''' > '''Inspect Document''' > '''Check Accessibility'''

The Accessibility Checker panel should be displayed to the right of the document. Most of the issues listed below will show up in the Inspection Results if they are found in the document. 

== Table of contents ==

TK documentation of how tables of contents should be constructed in Word to generate the appropriate structure in PDFs.

* All items should be linked to the appropriate location in the document.
* All items should ultimately be broken out into TOC_Title, TOC_Leader, and TOC_Page.

== Headings ==

* Assign heading styles (Heading 1, Heading 2, etc) to headings (and not a variation on the Normal paragraph style with bold text, for example). This will add the appropriate heading tags in the PDF document.
* Be careful to nest headings correctly, e.g. “Heading 2” follows “Heading 1”, “Heading 3” follows “Heading 2”, etc. 

== Tables ==

* All tables need headers. 
** In the sample documents the cells that should be header cells are not marked as such, they are marked as ordinary table cells. 
** ''Select the table'' > ''select cells from the row(s) that contain the headers''
** '''(Table Tools)''' > '''Layout''' > '''Repeat Header Rows'''
* Tables with inconsistent cell counts. 
** All rows in a given table should have the same number of cells. If for some reason one row has fewer cells, at least some of those cells should be assigned a "colspan" that indicates that the cell spans multiple columns in other rows.
** This looks like it's an issue with the Export to PDF function within Word not generating a table that accurately reflects the table as it is set up in Word.
** For an example, `13b-8630 AP_and_college_admissions_for CB Research Note_2013REVKB_EJS.doc`, page 31.
** There are cells in the left column that span multiple rows. There are also cells in the first row that span multiple columns.
** If the table is selected in Word and View Gridlines is checked, the grid in Word accurately takes all this into account.
** However, after exporting the document as a PDF, extra cells are added, and there are some gaps where cells are missing. 
** It looks like this will need to be cleaned up in Acrobat using the Touch-Up Reading Order function.

== Avoid empty paragraph tags ==

* It&rsquo;s common for the PDF document to contain empty Paragraph tags.
* This isn't strictly an issue for compliance, but it does make it more difficult to access the document for compliance because it's necessary to sift through all of the empty tags to find the tags that actually contain content.
This is a result of hitting the Enter key to create space between paragraphs. 
* A cleaner approach would be select a paragraph and edit its layout properties and give it the necessary extra margin above or below to create the gap between it and adjacent content. This will result in only a single Paragraph tag being exported.

== Comments and Annotations ==

Avoid exporting comments.

'''File''' > '''Export''' > '''Create PDF/XPS Document''' > '''Options''' > '''Publish What: Document (and not &ldquo;Document showing markup&rdquo;'''

== Charts ==

'''Any chart is really just one object for the purposes of compliance.''' (Unlike tables, for example, which are objects containing rows, which are each objects that in turn contains cells, which again are more objects which then fork into two flavors: header and data.) 

'''Compliance for charts is simply a matter of providing alternate text.''' A complicated chart may require equally wordy alternate text, which may be a chore on the content side, but once the content is finalized, assigning the text to the chart is always just a matter of dropping that content in -- whatever it might be -- as the alternate text.

To enter alternate text for a chart:

''Right click on the chart'' > '''Format Chart Area''' > '''Chart Options''' > '''Alternate Text tab'''

Alternate text for an image:

''Select the figure'' > '''right click''' > '''Format Picture''' > '''Alt Text tab''' > ''enter the Alternative Text content''

All graphics and text within the chart should be consolidated into one object for the purposes of assigning alternate text. 

* '''TK''' specific examples within Word.
* '''TK''' Take into account imported graphics and other ways of creating a chart or chart-like object that don’t employ Word's built-in chart objects.

== Properties that cannot be exported ==

While the meta title of the document can be set in Word ('''File''' > '''Info''' > '''Properties''' > '''Show Document Panel''' > '''Title'''), it doesn't get set as the title for accessibility purposes in the PDF. This must be done in Acrobat. 

* Open the PDF in Acrobat
* '''Tools panel''' > '''Action Wizard''' > '''Make Accessible '''
* Either run the whole script, or just click on '''Add Document Description'''.
* The title text will be in the text box, simply confirm to set it as the title for accessibility.