Adobe 65030089 - Robohelp - PC Using Manual page 299

USING ROBOHELP HTML 10
Generating output
Add or remove search highlights in WebHelp
In a WebHelp system, search results are highlighted by default in the displayed topics. You can set the highlight color
according to your preferences.
Note: WebHelp, WebHelp Pro, FlashHelp, and FlashHelp Pro projects use the same procedure to enable Search highlight.
Double-click the WebHelp layout.
1
Click Navigation.
2
3 Select or deselect Enable Highlight Search Result.
4 When search result highlighting is enabled, click the color picker box and select a highlight color of your choice
from the pop-up menu.
Creating Section 508-compliant WebHelp
Section 508-compliant output facilitates Help access for users with visual, hearing, or mobility impairments.
Text-to-speech utilities read the contents of the active window, available options, or text you type. These utilities and
screen review aids translate onscreen text to speech or to a dynamic, refreshable, Braille display. This technology can
provide keyboard assistance or shortcuts, captions for speech and sound, and visual warnings such as flashing toolbars.
Consider the following when you create Section 508-compliant WebHelp:
• WebHelp systems generated with the Section 508 option open in all supported browsers. However, view output
with Internet Explorer to ensure compliance.
• For master projects generated using pure HTML or Section 508-compliant WebHelp, the subprojects are available
only from the TOC if you merge WebHelp systems. They are not available from the index or full-text search.
Subprojects appear as a book in the TOC. When users click the subproject TOC book, the subproject opens in a
new browser window.
WebHelp features that support Section 508 compliance
• A Section 508 Compliant option that provides alternative text for images, dynamic elements, frames, forms, and so
on. Visually impaired users using assistive software can hear where they are in the output and what they are
selecting.
• Alternative text is provided for images of TOC books, pages, and the plus/minus icons, TOC/Search/Index tabs or
panes, navigation buttons, and buttons from design-time controls.
• Other elements with alternative text include expanding and drop-down text, triggers and targets, and pop-up
menus.
• Navigation frames that assistive software can read.
• Generation of HTML tables so that assistive software can identify row and column headers.
• Online forms that assistive software can read.
• Output that more than one mode of operation and information retrieval can use. For example, mobility-impaired
users can use the keyboard or mouse. No features require auditory, visual, or mobility ability alone.
Guidelines to ensure Section 508 compliance in Help systems
• WebHelp is compliant for framesets and navigation. Make sure that other elements in topics are compliant.
• If the Help system contains form buttons or multimedia elements, such as images and audio, provide visual
equivalents, such as screen tips so that assistive software can read from the screen.
Last updated 7/13/2012
293