Skip to main content

Documentation checklist

Checkpoint 1: Provide documentation in an accessible format

This page provides specific examples to implement the documentation techniques for accessible documents in Microsoft® Word.

On this page:

 


Rationale

Some users may not be able to access documentation if it is not in an accessible format. The following techniques provide information to create accessible Microsoft® Word documents.


Required development techniques

The following techniques are the minimum required to meet Checkpoint 1 from the IBM Documentation Accessibility Checklist for documents created with Microsoft® Word:

1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.

  1. Provide alternative text for all images.

    Example 1
    Word objects that require alternate text include Symbols, Clip Art, Objects, Drawings and Auto Shapes. Word Art is an image, but Word automatically adds the text you type to the alternative text field for the Word Art image. When you create a Diagram, Word automatically adds the type of diagram (e.g. Pyramid Diagram) in the alternative text field, however this is usually not a sufficient description and will need to be modified.

    To add alternative text for an image: Example 2
    When images or charts are copied from other applications such as Freelance or Microsoft Office, ensure the pasted information is accessible. Select the pasted image, go to the Alternative Text field on the Web tab of the Format Object dialog and verify that alternative text has been provided. If not, add a detailed text description. If the image cannot be adequately described using alternate text, provide a more detailed description in the surrounding text.

  2. Provide a text description in addition to alternative text for complex charts and graphs.

    Example 3
    For images or charts provide alternative text for the image. If the image cannot be adequately described using alternate text, provide a more detailed description in the surrounding text. If alternate text had been provided for the image in the original Office document, the alternate text will be copied into Word.

1.2 Information and Relationships: Define information, structure, and relationships.

  1. Define document structure.

    Example 4
    Properly format all text used as section headings by using Word styles such as "Heading 1", "Heading 2", etc. This allows screen readers to create an outline of the document. Using bold text to indicate headings is not sufficient to create an accessible document.

  2. Do not use text formatting as the only way to convey meaning.

    There are no unique examples for this technique in PowerPoint. Please follow the general examples for text formatting to meet this checkpoint.

  3. Identify the purpose of each link in the link text.

    There are no unique examples for this technique in PowerPoint. Please follow the general examples for accessible link texts to meet this checkpoint.

1.3 Color & contrast: Any information that is conveyed by color is also visually evident without color.

  1. Do not use color as the only way to convey meaning.

    There are no unique examples for this technique in PowerPoint. Please follow the general examples for color to meet this checkpoint.

  2. Provide sufficient contrast between text and the page background.

    There are no unique examples for this technique in PowerPoint. Please follow the general examples for text contrast to meet this checkpoint.

1.4 Meaningful sequence: Define document reading order.

  1. Define document reading order.

    Example 5
    Ensure that document elements are presented in a logical reading order. Avoid complex layout, sidebars and other ornamentation as they make it difficult to maintain a logical reading order.

1.5 Forms: Define form element labels.

  1. Provide an accessible label for form fields.

    Example 6
    Forms work best if the input field and associated label is placed on a same line. Select the "form element" (text, check box, drop down) from the Forms Toolbar and place it next to the associated Field Label. To make form label accessible, depending on the form layout, accessibility is addressed in different ways:

1.6 Tables: Identify table cells and relationships between cells.

  1. Identify row and column headers for data tables.

    Example 7
    To create accessible data tables:

1.7 Threshold violations: Do not include text or images that flash more than 2 times in a one second period.

  1. Do not include text or images that flash more than 2 times in a one second period.

    There are no unique examples for this technique in PowerPoint. Please follow the general examples images that flash to meet this checkpoint.

1.8 Navigation: Provide an accessible method to navigate long documents.

  1. Provide an accessible method to navigate long documents.

    Example 8
    Properly format all text used as section headings by using Word styles such as "Heading 1", "Heading 2", etc. This allows screen readers to create an outline of the document and make the outline available to the user for navigation. Using bold text to indicate headings is not sufficient to create an accessible document.

    Example 9
    Provide a Table of Contents for long documentation. Table of Contents enables the screen reader user the ability to easily navigate to specific sections of the document.

1.9 Language of Page: Define the default language.

  1. Define the language of the document.

    Example 10
    Use the Language dialog via Tools-Language-Set Language to define the primary language of the document so screen readers can correctly read the content.


Recommended development techniques

The techniques above are required; the following techniques are recommended to enhance accessibility:


Required test techniques

Test the documentation to ensure that it complies with accessibility requirements. The techniques listed here are specific for Microsoft Word documents.

Required test software


Techniques

The following techniques are required to verify this checkpoint:
  Action Result
1. Document language: Verify the document language is set properly.
  1. Use Tools-Language-Set Language to view the document language.

Pass:

Fail:

2. Verify all meaningful images have meaningful alternative text, and decorative or redundant images have null alt text.
  1. In Word, display the context menu for each image (right click on image) and select Format Picture option. Select the "Web" tab in the format picture dialog to see the alternative text for the image

Pass:

Fail:

3. Complex images:
  1. Verify that a full text alternative is provided for the meaningful information for all complex images.
  2. Verify that the alternative text for the image (found in the Web tab of the Format Picture dialog) provides information on where to find the full text description of the complex image.

Pass:

Fail:

4. Headers: Verify all headers are formatted using the proper header markup. If it looks visually like a heading, it must be styled as a heading.
  1. Use the Word "style" toolbar to see if text is formatted to as a header or as normal text

Pass:

Fail:

5. If data tables are used:
  1. Verify that no large or complex tables are used. A complex table is one where more than one row header applies to any cell, or more than one column header applies to any cell.
  2. Verify the tables are created using the Word "Table – Insert – Table" option, i.e., ensure columns are not simulated using the Tab key to put data into columns.

Pass:

Fail:

6. Verify that link text is meaningful for all links and unique for each different link.

Pass:

Fail:

7. Large document navigation: For documents over 5 pages, a long document navigation method is provided.
  1. Verify that a usable table of contents is provided with the ability to navigate to all major sections of the document.

Pass:

Fail:

8. Verify keyboard navigation for embedded elements that are not controlled by the document application. (For example, if you embed a video object in a document, the editor does not control the video element.)
  1. Verify that you can navigate to the embedded element from the document body, and then back to the document body using the keyboard, with no mouse interaction required.
  2. Verify that all user controls provided for the embedded element can be controlled using the keyboard, with no mouse interaction required.

Pass:

Fail:

9. Verify the following text formatting and color requirements.
  1. Verify that color is never used as the only way to convey meaning
  2. Verify that text formatting is never used as the only method to convey information
  3. Verify that sufficient contrast is provided by default between the text and the page background. The background color should provide sufficient contrast, and no patterned backgrounds should be used.

Pass:

Fail:

10. Verify that no content flashes or blinks at a rate faster than two times per second. Here is how to test this:
  1. Count the number of blinks that occur in one second (or count the number of blinks in 10 seconds and divide by 10).
  2. Verify that no more than two blinks per second occur.
  3. If an element is blinking or flashing, but at a rate too fast to count, it is a violation of this requirement.

Pass:

Fail:

11.
  1. Use the screen reader's basic reading keys to verify the following:
    1. The document has a logical reading order.
    2. When text links are used, the purpose of each link is clear from the link text.
    3. For all meaningful images, the screen reader announces a short text alternative with equivalent meaning.
    4. For decorative images, or images used only for visual formatting, screen reader ignores the image.
    5. The screen reader announces text equivalents for any other important non-text elements.
    6. All document structure elements are recognized and announced by the screen reader (when screen reader support is available). For example: Headers, Lists, Tree structures. Use special screen reader "list" features to list headers, etc., where available.
  2. If forms fields are included, verify the following:
    1. Tab to each form field and verify the screen reader announces labels associated with form fields and control elements.
    2. If sufficient information is not announced when tabbing to a form field, verify the user can "unprotect" the document in order to read the surrounding static text. Verify the form field is usable and understandable in that mode.
  3. If data tables are included, verify the following using the screen reader's table navigation keys:
    1. The row and column headers that apply to a cell are announced when moving to the cell.
    2. If the screen reader cannot announce the headers, the table must be small enough to allow the reader to mentally keep track of the rows and columns. This means the table must be very small (usually 4 simple columns or less).

Pass:

Fail:

©2009 IBM Corporation

Last updated September 1, 2009