Page History
...
The following tables list steps technical writers at CBIIT must take to create Section 508-compliant documents. These steps may overlap with but do not replace the HHS checklists for achieving Section 508 compliance.
Table 1.1 The following table explains how to prepare a FrameMaker document for accessibility.
Step | Steps for creating accessible documents in FrameMaker | For more information, see | ||
---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="cdb10b0b7fa6f93d-6b6f217c-4e8c46d3-b43f87fa-5f9dcdd6d9a75c66e4172155"><ac:plain-text-body><![CDATA[ | 1 | Design with accessibility in mind. Only use our template styles, including character styles for common formatting such as bold and italic. Resist overriding template styles. | [[http://www.webaim.org/]|http://www.webaim.org/|WebAIM website] | ]]></ac:plain-text-body></ac:structured-macro> |
2 | Use our latest FrameMaker template that consolidates all paragraph styles into each file in the book. | L:\Technical Writing\Templates\FrameMaker Templates\Current FM Templates | ||
3 | Add alternate text to images.
|
| ||
4 | Use row and column headings and captions for all tables. Do not merge table rows or columns. Do not allow rows to break across pages. |
| ||
5 | Use meaningful link anchors rather than URLs when possible. Use the Go to URL hypertext marker for all URLs in FrameMaker. |
| ||
6 | In the PDF Setup dialog box, select Generate PDF Bookmarks, Generate Tagged PDF (click Default to tag all styles), and Create Named Destinations for All Paragraphs. |
|
...
Step | Steps for creating accessible PDFs For more information, see | |
---|---|---|
1 | In the document properties, enter NCI CBIIT as the Author. In the Keywords field, enter 508 Compliant as one of your keywords. | |
2 | Specify document language.
| |
3 | Use the document structure to prevent errors in the accessibility report.
| |
4 | Run an accessibility full check using the Adobe PDF option.
|
|
5 | Fix any problems reported by the accessibility checker. Documents from Word tend to have more problems than documents from FrameMaker. Documents from Word may need post-processing in Acrobat. Use the accessibility checker report as a troubleshooting guide to narrow down problem areas.
|
|
6 | Once the steps above result in a PDF with no accessibility errors according to Adobe, set the scope of your tables. Adobe does not require you to set the scope but it is one more thing that you can do quickly to prepare your PDFs better for assistive technology.
|
Accessibility Testing
Table 1.4 The followine table suggests ways you can test your ePublisher, Flare, and PDF output for accessibility.
...
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.
This section includes the following topics:
Wiki Markup \[#PreparingPreparing FrameMaker Files for Accessibility#Preparing FrameMaker Files For Accessibility\]
- Preparing Word Files For Accessibility
- Characteristics of Accessible PDFs
- Checking Documents for Accessibility
- Using the WebWorks ePublisher Accessibility Report
...