Can RoboHelp 10 produce accessible content?
Yes, this version of RoboHelp helps you to create WebHelp output for users who have visual or hearing impairments, mobility impairments, or other types of disabilities. You can also take steps at a design level to remove obstacles for people with disabilities using your Help system.RoboHelp 10 can also generate tagged PDF files that are partially accessible with the primary language defined. You can use Adobe Acrobat to complete the process by adding alternative text to images in the PDF file.
What does WebHelp produced with RoboHelp 10 do to comply with accessibility standards?
RoboHelp 10 features a Section 508 Compliant option for WebHelp that provides "alt" text (alternative text) for images, dynamic elements, frames, forms, and more. This text allows visually impaired people using a screen review aid (or assistive software) to "hear" where they are in your Help system and to know what buttons they are pushing.In WebHelp Section 508, images that have alt text are TOC books, pages, and the plus/minus icons, TOC/Search/Index/Glossary tabs or panes, navigation buttons (Show, Hide, browse sequences, WebSearch, Sync TOC), and buttons from design-time controls (See Also and Related Topics.)Other elements that have alt text are expanding and drop-down text, triggers and targets, and popups.
WebHelp Section 508 navigation frames have "names" and "titles." The title is readable by assistive software.WebHelp Section 508 HTML tables are generated so that row and column headers can be identified by screen review aids.WebHelp Section 508 forms designed to be completed online will be generated and comply with assistive technologies.WebHelp Section 508 does not require speech, or auditory, visual, or mobility ability alone - it can be used by more than one mode of operation and information retrieval. For example, mobility-impaired people can use the keyboard or the mouse, whichever method of navigation works best for them.
What should RoboHelp authors do?
While WebHelp Section 508 output is compliant for framesets and navigation, you need to make sure you develop Section 508 compliant topics.
For more information, see Accessibility Best Practices for RoboHelp 10.