Most preparations for accessibility should be done in the source files. The following pages explain how to prepare documents for accessibility.

• Section 508 Compliance for Confluence Wiki Pages
• Section 508 Compliance Checklists for Various File Types

A few key actions can make content significantly more accessible.

Refer also to Accessibility and 508 Compliance (overview).

This page gathers documents that the Documentation Team has found or developed regarding Section 508 compliance. These documents will be posted in the appropriate place after consultation with other members of the Training and Development Team. The contents are:

Creating Accessible Technical Documents at CBIIT

To make our documents compliant with Section 508 of the Rehabilitation Act, we must prepare our source files and then test our output files. The tools we currently use to create our source files, Adobe FrameMaker and Microsoft Word, both allow us to prepare for accessibility.

Our output files are currently in PDF and ePublisher WebHelp 5.0 formats. The tools we currently use to create those files, Adobe Acrobat 9 and WebWorks ePublisher Pro 9.2, contain tools of their own that check for how well files conform to the Section 508 accessibility standards. We can run those checks to see if we need to make any additional tweaks to our source files. We should avoid as much post-processing to output files as we can.

Most of our preparations for accessibility should be done in the source files. This document explains how to prepare a FrameMaker document for accessibility and links to procedures where you can accomplish the same goals in Word.

Refer to:

...