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.
Adobe(R) Accessibility Quick Reference Card http://blogs.adobe.com/accessibility/2008/03/reference_card_for_accessible.html
WordToPDFReferenceCard_v1.pdf (presented by the blog page listed above) http://blogs.adobe.com/accessibility/assets/WordToPDFReferenceCard_v1.pdf
caBIG_PPT_508_Quick_Guide_FINAL_July_2009.ppt https://wiki.nci.nih.gov/download/attachments/7474647/caBIG_PPT_508_Quick_Guide_FINAL_July_2009.ppt
The quick guide is used with the PowerPoint templates posted on this page: https://wiki.nci.nih.gov/pages/viewpageattachments.action?pageId=10852174
caBIG_508_QuickGuide_Word_April_2009_Final.ppt https://wiki.nci.nih.gov/download/attachments/7474647/caBIG_508_QuickGuide_Word_April_2009_Final.ppt
Creating Accessible Documents at CBIIT (attached to this page) https://wiki.nci.nih.gov/download/attachments/21693549/DevelopingAccessibleDocs.pdf
Developing Accessible Technical Documents at NCI CBIIT
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 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="d26aed67-5dc3-4b8b-a8c3-6bf1a521424c"><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. |
|
Creating Accessible Word Documents
Table 1.2 explains how you can prepare your Word documents for accessibility. Note that Word documents lose some of the accessibility options you introduce once they reach Acrobat. It is likely that you will need to post-process the file in Acrobat.
Note: Refer to wordCheckList-HHS.pdf and adobeCheatSheatWordToPDFa.pdf for helpful tips.
Step |
Steps for creating accessible documents in Word |
For more information, see |
---|---|---|
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. |
|
2 |
Add alternate text to images.
|
|
3 |
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. |
|
4 |
Use meaningful link anchors rather than URLs when possible. |
|
5 |
Configure PDFMaker to tag the document properly.
|
|
Creating Accessible PDFs
Although the HHS says that PDFs do not need to be 508 compliant if a compliant HTML version of the document exists, it is a good idea to get in the practice of taking as many steps as you can to improve your PDF document's accessibility.
Table 1.3 explains how to create an accessible PDF once your document is in Acrobat.Table 1.3 explains how to create an accessible PDF once your source file is in Acrobat.
Note: Refer to the HHS checklist for accessible PDFs for helpful tips.
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 suggests ways you can test your ePublisher, Flare, and PDF output for accessibility.
Ways to Test Your Output |
For more information, see |
---|---|
Refer to the HHS accessibility checklists. |
|
In ePublisher, run the accessibility report. Ignore errors about missing long descriptions and table summaries. If you use alternate text for graphics and include either a text introduction or caption for tables, you're covered on those. |
|
Download the WAVE Firefox toolbar and view the help in Text-only view. |
|
Download an evaluation copy of JAWS and read the document out loud. |
|
Use the Adobe Read Out Loud feature to simulate what it would be like for other assistive technology (such as JAWS) to read your PDFs out loud. |
|
Turn off your monitor when you use either JAWS or Adobe Read Out Loud (this takes some practice with each tool) to simulate what it is like not to see what you are doing. |
|
Tab through the output to make sure that the reading order is logical. |
|