Documentation checklist

Checkpoint 1: Accessible format

This page provides specific examples to implement the documentation techniques for accessible documents in Lotus Symphony Presentations.

Rationale

To ensure that all users can access documentation, you must provide documents in an accessible format. If documentation is provided in multiple formats, at least one of the formats must be accessible and the accessible version must be clearly identified.


Required development techniques

The following techniques are the minimum required to meet Checkpoint 1 from the IBM Documentation Accessibility Checklist for documents created with Lotus Symphony Presentations:

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.1.1 Alternative text: Provide alternative text for all images.

Example 1

Symphony Presentations objects that require alternate text include Gallery images, Objects, Drawings and Auto Shapes. To add alternative text for an image:

Example 2

Group all graphic objects into a single object. Some images are composites of many elements that make the page difficult to read with a screen reader. For example, a background image of the world may represent each country as a separate graphic. As those objects have not been grouped into a single image, this will cause a problem for anyone using a screen reader. To be accessible, the objects should be grouped as a single object. To group objects:

Required test for development technique 1.1.1

Manually review the alternative text for each image to verify it adequately describes the image.


1.1.2 Text description: 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.

Provide a summary in the alternative text field on the Alternative Text tab of the Graphic Properties dialog. If the summary does not include enough information to understand the chart, use one of the following techniques to provide additional information about the chart:

Required test for development technique 1.1.2

If alternative text is used, manually review the text for each image to verify it adequately describes the image. If alternative text cannot be used, manually review the surrounding text or speaker notes to verify the image is adequately described.


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

1.2.1 Structure: Define document structure.

Example 4

Use the Symphony Presentations page layout templates and placeholders to add content to the page. Text added to the page using predefined templates and placeholders will automatically be added to the Outline view of the presentation. Text that is inserted using Insert – Text Box will not be part of the Outline view and may not be read by a screen reader.

Required test for development technique 1.2.1

Manually review the markup using the editor.


1.2.2 Text formatting: Do not use text formatting as the only way to convey meaning.

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

Required test for development technique 1.2.2

Manually review the markup using the editor.


1.2.3 Link purpose: Identify the purpose of each link in the link text.

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

Required test for development technique 1.2.3

Manually review each link using the editor. You can also use Symphony's built-in Navigator (Ctrl+Shift+F5) to verify the links in the document.


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

1.3.1 Color alternatives: Do not use color as the only way to convey meaning.

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

Required test for development technique 1.3.1

Manually review the document to verify proper use of color.


1.3.2 Sufficient contrast: Provide sufficient contrast between text and the page background.

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

Required test for development technique 1.3.2

Manually review the document to verify sufficient contrast between text and page background.


1.4 Meaningful sequence: Define document reading order.

1.4.1 Reading order: Define document reading order.

Example 5

By default, screen readers will read objects on a slide in the order in which they were added to the page. Pages with more than 2 items on a page may not read in the correct order, even if they only contain text objects. In Symphony Presentations, , To view the reading order use the Navigator dialog box (Ctrl + Shift + F5). The screen reader reads Symphony objects in the order shown in the Navigator. Assure the order will make sense when using a screen reader. If not, adjust the reading order using the Arrange context menu item. You can explicitly set the reading order on a page using the following steps:

Required test for development technique 1.4.1

Manually review each slide using Symphony's built-in Navigator (Ctrl+Shift+F5) to verify the order of all the objects. The Navigator view shows an organizational summary of the presentation objects. Each object on the slide is shown in the tree structure of the Navigator. The currently selected object on the slide is highlighted with green handles and simultaneously is shown in the Navigator with an "*" asterisk next to the name.


1.5 Forms: Define form element labels.

1.5.1 Form labels: Provide an accessible label for form fields.

This technique does not apply to Symphony Presentations.

Required test for development technique 1.5.1

Manually review to verify accessible labels are provided for all form fields.


1.6 Tables: Identify table cells and relationships between cells.

1.6.1 Table headers: Identify row and column headers for data tables.

Example 7

To create accessible data tables:

Required test for development technique 1.6.1

Manually review the table to make sure it is not created with tabs or spacing. If your presentation contains complex table, use a screen reader to verify the table reads properly.


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

1.7.1 Flashing content: 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 Symphony Presentations. Please follow the general examples images that flash to meet this checkpoint.

Required test for development technique 1.7.1

Manually review to verify images do not flash more than 2 times in one second period.


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

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

Example 8

Use the Symphony Presentations page layout templates and placeholders to add content to the page. Text added to the page using predefined templates and placeholders will automatically be added to the Outline view of the presentation. Text that is inserted using Create – Text Box will not be part of the Outline view and may not be read by a screen reader. The Outline view will enable users to quickly navigate a long Symphony presentation.

Required test for development technique 1.8.1

Manually review the Outline view to verify each slide has a unique title. You can also use Symphony's built-in Navigator (Ctrl+Shift+F5) to verify each slide has a unique title.


1.9 Language of Page: Define the default language.

1.9.1 Language definition: Define the language of the document.

Specifying the language improves readability and accessibility of document. If no language is identified, select Choose File > Preferences > IBM Lotus Symphony > Language Settings to identify the document language.

Required test for development technique 1.9.1

Manually review the language is set.


Recommended development techniques

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


 

©2012 IBM Corporation

Last updated November 1, 2010