Adobe RoboHelp 8 - Section 508 Voluntary Product Accessibility Template

Section 1194.21 Software Applications and Operating Systems

Applicable

Supports with exceptions

Section 1194.22 Web-Based Intranet and Internet Information and Applications

Applicable

Supports with exceptions

Section 1194.23 Telecommunications Products

Not applicable

—

Section 1194.24 Video and Multimedia Products

Not applicable

—

Section 1194.25 Self-Contained, Closed Products

Not applicable

—

Section 1194.26 Desktop and Portable Computers

Not applicable

—

Section 1194.31 Functional Performance Criteria

Applicable

Supports with exceptions

Section 1194.41 Information, Documentation, and Support

Applicable

Supports

(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

Supports with exceptions

Some functions in RoboSource are not accessible via the keyboard.

For example, in the History Viewer, toolbar and context menus cannot be accessed using the keyboard.

There is limited keyboard access to the Structure View.

(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.

Supports

RoboHelp 8 does not disrupt or disable activated accessibility features of other products.

(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes.

Supports with exceptions

RoboHelp 8 provides an on-screen indication of the current focus that moves among interactive interface elements as the input focus changes, with some exceptions.

For example, visual focus is lost on some buttons and programmatic focus is not available in some lists in the Style and DHTML Effect dialogs.

In RoboSource 3.1, drop down menus do not programmatically expose focus to Assistive Technology.

(d) Sufficient information about a user interface element including the identity, operation, and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text.

Supports with exceptions

Some controls in RoboHelp 8 and RoboSource 3.1 do not provide sufficient information about identity, operation, or state to Assistive Technology.

For example, some buttons in the Table Insert dialog in RoboHelp, and menus and lists in RoboSource are not correctly labeled or recognized by Assistive Technology.

(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.

Supports

RoboHelp 8’s indicators of status or control are consistent throughout the application.

(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.

Supports

Text content, input caret location and attributes are all available for editable text in RoboHelp 8.

(g) Applications shall not override user-selected contrast and color selections and other individual display attributes.

Supports with exceptions

RoboSource 3.1 is only partially capable of using the Windows system settings for color, fonts, contrast, and size of UI elements.

For example, large text settings do not affect text in list boxes.

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

Not Applicable

RoboHelp 8 does not use animation.

(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Supports

Color coding is not the only way of conveying information in RoboHelp 8.

(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.

Not Applicable

RoboHelp 8 does not permit the user to adjust color and contrast settings.

(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.

Not Applicable

RoboHelp 8 does not use flashing or blinking text, objects, or other elements.

(l) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Supports with exceptions

Some dialog boxes and controls are not fully accessible to assistive technology.

For example, some lists in the Style and DHTML Effectdialogs are not fully accessible to Assistive Technology.

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt," "longdesc," or in element content).

Supports

In RoboHelp alternate text can be added to HTML pages using HTML Syntax view.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Supports

RoboHelp allows authors to embed externally created multimedia content.

Authors need to ensure that included multimedia provides equivalent alternatives.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Supports

The use of color for conveying information in RoboHelp output is controlled by the author.

Table templates use color coding instead of markup to indicate headings. See (g)

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Supports with exceptions

RoboHelp 8 Web and Flash Help uses both inline and external styles. The use of styles can be controlled by the author.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not applicable

RoboHelp 8 does not create server-side image maps.

(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Supports

RoboHelp 8 generates client-side image maps except where the regions cannot be defined with an available geometric shape.

(g) Row and column headers shall be identified for data tables.

Supports with exceptions

Authors need to identify table headers by editing the code in HTML view. The Design view does not provide a way to identify headers..

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

Supports with exceptions

See (g).

(i) Frames shall be titled with text that facilitates frame identification and navigation.

Supports with exceptions

WebHelp frames are titled, but some of the titles are confusing.

FlashHelp frames are not titled.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Supports

RoboHelp allows authors to embed multimedia and dynamic content. Authors need to ensure that the content does not cause screen flicker.

(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

Supports

RoboHelp supports the creation of text-only content.

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.

Supports

RoboHelp will generate scripted behaviors, and authors may include scripting in the HTML. Authors must ensure that functional text is provided.

(m) When a web page requires that an applet, plug-in, or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).

Supports

RoboHelp can utilize Flash and other plug-ins within HTML and Flash Help. The author must ensure that a link is provided to a plug-in or applet that complies with this criterion.

(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Supports

For HTML and Flash Help, an author may include forms as part of the content using markup. Authors must ensure that any forms added can be completed using Assistive Technology.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supports

RoboHelp 8 supports via the ability of Assistive Technologies to navigate frames in HTML and Flash Help.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supports

For HTML and Flash Help, an author may include markup to create timed responses.

Authors need to ensure that the user is alerted and sufficient time is given to the user to indicate that more time is required.

(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.

Supports with exceptions

Some functions in RoboSouare not accessible via the keyboard.

Some controls in RoboHelp 8 and RoboSource 3.1 do not provide sufficient information about identity, operation, or state to Assistive Technology.

(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.

Supports with exceptions

There is not always a clear on-screen indication of focus in RoboHelp 8.

(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided.

Supports

(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

Supports

(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.

Supports

(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Supports with exceptions

Some drawing tools, such as the Cable Drum and client-side image map regions, require the use of the mouse.

There is no alternative for these modes of operation.

(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge.

Supports

Adobe provides electronic versions of all product support documentation.

(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.

Supports

Adobe provides information on accessibility features in the documentation. Electronic versions of all product support documentation are provided.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

Supports

Product support for Adobe products is available in a variety of formats and from a number of online sources available from Adobe Systems.