The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding the availability of commercial Electronic and Information Technology products and services with features that support accessibility. It is assumed that offerers will provide additional contact information to facilitate more detailed inquiries.

The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table. Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.

Date: January 14, 2014

Name of product: Adobe® RoboHelp® 11

Contact for more information: access@adobe.com

 

Section 1194.21 Software Applications and Operating Systems - Detail
Criteria Supporting features Remarks and explanations

(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.

Does not support

Some elements in the Adobe RoboHelp 11 user interface cannot be accessed using the keyboard.

For example, it is not possible to navigate between tab panels using keyboard-only controls.

Additionally, it is not possible to access the “Menu”, “Auto Hide” and “Close” icons within each tab panel using the keyboard alone.

Navigation buttons in the carousel on the application home page cannot be accessed using the keyboard.

Components in the Link View cannot be accessed or controlled via the keyboard.

(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 with exceptions

The Adobe RoboHelp 11 user interface does not disrupt or disable most accessibility features of the operating system or accessibility applications with some exceptions, including:

Toolbar icons and content within project files (both in Design view and HTML view) do not inherit user display settings in Windows High Contrast Mode.

(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

The Adobe RoboHelp 11 user interface mostly uses the operating system’s default indication of focus for applications, which is sufficient in this context. However, some controls do not have a clear visual focus indicator.

For example, items in the project index (displayed when the application is first opened) use the web browser’s default indicator of focus (a dotted line), which does not provide sufficient indication of focus.

(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 inputs and controls in the Adobe RoboHelp 11 user interface provide identity, operation and state information to assistive technologies.

However, this information is not available for all user interface elements.

For example, data cells in the Topic List panel are combined together into a single element with a role of text (rather than coded as data cells).

The “Check for new screen layouts” control in the “New Screen Layout” dialog box also has a role of text rather than the appropriate role of link or button.

(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

The Adobe RoboHelp 11 user interface supports the consistent use of image icons 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 information in Adobe RoboHelp 11 is available to assistive technologies with some exceptions, including:

The textual values for User Defined Variables are not available to assistive technologies.

Content in the “Paragraph Preview” section of the Styles dialog box (displayed when the default.css file in the Project Manager is activated) is not available to assistive technologies.

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

Supports with exceptions

The Adobe RoboHelp 11 user interface supports Windows High Contrast Mode.

However, some controls and icons exhibit low contrast even when in this mode.

For example, toolbar icons and text in the Design and HTML tabs do not inherit user display settings.

(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

The Adobe RoboHelp 11 user interface does not use animated content.

(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 with exceptions

For most content and functionality, the Adobe RoboHelp 11 user interface does not use color coding to convey information.

Exceptions include the “tagging” of text with conditional build tags, in which (in design mode) affected text is highlighted using a series of diagonal lines represented by the color of the conditional tag. Switching to HTML mode reveals the names of relevant tags (hence color perception is not required), but these can be difficult to find in larger HTML files with multiple tags.

In the Design view, the user can hover over the relevant text using a mouse to reveal a tooltip containing the information, but this functionality is not available to keyboard-only users.

(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

The Adobe RoboHelp 11 user interface 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.

Supports

The Adobe RoboHelp 11 user interface does not use flashing or blinking text, objects, or other similar 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

The Adobe RoboHelp 11 user interface provides keyboard access to most form fields. Labels and instructions are also provided for most form controls.

However, it is not always possible for assistive technology users to consistently identify field elements.

For example, several “Search” textboxes throughout the application do not have visible labels – placeholder text is used instead, but this text disappears when the user begins to type, and is not conveyed to assistive technologies when the textbox receives focus.

Additionally, several buttons throughout the application (such as buttons which trigger the Open Dialog Box to choose a file to upload to a project) are not provided with accessible names.

Some sets of related form controls (such as radio buttons) are not grouped together programmatically. Examples include the “Text Wrapping” group label for the “Left”, “Right” and “None” radio buttons when inserting an image, and the “Show Files from” group label for the “Project Manager” and “Table of Contents” radio buttons when creating a PDF for review.

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following Priority 1 checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) – 1.1, (b) – 1.4, (c) – 2.1, (d) – 6.1, (e) – 1.2, (f) – 9.1, (g) – 5.1, (h) – 5.2, (i) – 12.1, (j) – 7.1, (k) – 11.4.

Section 1194.31 Functional Performance Criteria - Detail
Criteria Supporting features Remarks and explanations

(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 elements of the Adobe RoboHelp 11 user interface cannot be operated using a keyboard alone.

For example, it is not possible to move between panels using the keyboard alone.

Some controls do not provide sufficient information to assistive technologies, such as buttons to trigger the Open File Dialog when uploading a file to the project.

(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

The Adobe RoboHelp 11 user interface supports the use of screen magnifiers.

However, some controls do not provide a clear visual indication showing they have received focus, such as the Project Selection screen displayed when the application is initially opened.

(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

The Adobe RoboHelp 11 user interface does not require user hearing.

(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

The Adobe RoboHelp 11 user interface does not require the use of audio.

(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

The Adobe RoboHelp 11 user interface does not require speech input.

(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 parts of the Adobe RoboHelp 11 user interface require mouse control In order to perform some basic functions.

For example, some drawing tools, such as indicating client-side image map regions, require the use of the mouse with fine motor control.

There is no equivalent alternative for this mode of operation.