Section 1194.21 – Software Applications and Operating Systems

Applicable

Supports with exceptions

Section 1194.22 – Web-based Intranet and Internet Information and Systems

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

Section 1194.41 – Information, Documentation, 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.

Does not support

Some elements of the Adobe RoboHelp 10 interface cannot be activated with keyboard-only controls.

For example, it is not possible to navigate between tabs within a panel using keyboard-only controls.

It is not possible to activate toolbar controls such as Menu, Auto-hide, and Close using the keyboard alone.

Some interactive interface elements, such as the Formatting toolbar, do not receive focus with the keyboard.

It is not possible to select or move items in views, such as the Link view, using the keyboard alone.

(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

RoboHelp 10 does not disrupt or disable most accessibility features of the operating system or accessibility applications.

(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

There is a visual indication of focus for all controls in RoboHelp 10.

Focus is not programmatically exposed for items in the Snippets panel.

(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 10 interface provide identity, operation and state information to assistive technology.

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

For example, the Resource Manager tab, the Snippets panel and the Links view do not provide identity, operation, and state information to 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

Adobe RoboHelp 10 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 with exceptions

Text information in Adobe RoboHelp 10 is available to assistive technology with some exceptions, including:

The textual Values for User Defined Variables and Snippet code are not available to assistive technology.

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

Supports with exceptions

The Adobe RoboHelp 10 interface supports Windows High Contrast Mode.

However, not all controls and interface elements fully inherit user selected settings, including:

For example, toolbar icons do not inherit user display settings.

Text in the Main design panel is not readable in Windows High Contrast Mode.

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

Supports

The Adobe RoboHelp 10 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

The Adobe RoboHelp 10 interface uses color coding to identify links in the Link view. This information is not provided through another means, such as text.

The interface uses color coding to ‘tag’ text with conditional build tags. Text alternatives are provided via tooltips, but these not available to keyboard users, or rendered by screen readers.

(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 10 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 10 interface does not use flashing or blinking text, objects, or other elements in the software's user interface.

(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

The Adobe RoboHelp 10 interface provides keyboard access to some form fields. However, it is not always possible for assistive technology users to consistently identify field elements.

For example, some fields in the Options and New Snippet dialogs are not identified to assistive technologies.

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

Supports with exceptions

Alternate text for non-text elements can be added in the design and HTML View in Adobe RoboHelp 10.

Alternative text for image icon buttons in SWF output is not available to assistive technologies.

Alternative text for images in HTML, XML, and PDF documents can be added in the authoring environment.

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

Supports

Adobe RoboHelp 10 allows authors to embed multimedia content featuring equivalent alternatives, which may be added by the content author.

(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

Adobe RoboHelp 10 gives authors full control over color choice.

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

Supports

Adobe RoboHelp 10 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

Adobe RoboHelp 10 does not use 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

Adobe RoboHelp 10 generates client-side image maps.

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

Supports with exceptions

Adobe RoboHelp 10 allows authors to add table headers using the HTML View.

(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

Adobe RoboHelp 10 allows authors to add table headers using the HTML View.

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

Supports with exceptions

Adobe RoboHelp 10 do not generate frames

(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

Adobe RoboHelp 10 does not create flickering content.

(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

It should be possible to make content generated by Adobe RoboHelp 10 fully accessible without using text alternatives.

However, Robohelp 10 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

Interface elements, created using scripting, do include functional text that can be read by assistive technology.

(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

Adobe RoboHelp 10 allows authors to create links to applets and plug-ins necessary to view content.

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

Adobe RoboHelp 10 allows authors to add accessible forms using the HTML View.

Authors need to ensure that forms exported in PDF and Flash technologies are authored to be accessible to assistive technologies.

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

Supports

Adobe Robohelp 10 provides tables of contents, index and search options that allow users to bypass navigation links.

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

Supports

Adobe RoboHelp 10 does not automatically generate timed responses.

Authors may add timed responses to scripted content and should ensure that appropriate alerts and controls are provided.

(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 10 interface cannot be operated using a keyboard alone.

For example, navigation via panel controls is not possible using the keyboard alone.

Some controls do not provide sufficient information 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

RoboHelp 10 supports the use of Screen Magnifiers. However, some controls do not provide a clear indication that they have received focus, such as the items in the Project Management Panel and Glossary.

(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

Many parts of the interface require mouse control in order to perform some basic functions.

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

There is no alternative for these modes of operation.