Adobe RoboHelp 11 Voluntary Product Accessibility Template

Transcription

1 Adobe RoboHelp 11 Voluntary Product Accessibility Template The purpose of the Voluntar y 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 suppor t accessibility. It is assumed that offerers will provide additional contact information to facilitate more detailed inquiries. The first table of the Template provides a summar y 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 subpar ts B and C of the Standards. The second column describes the suppor ting 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 suppor ting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product. Date: 1/14/2014 Name of Product: Adobe RoboHelp 11 Contact for more Information: access@adobe.com Guideline Applicable Compliance Software Applications and Operating Systems Applicable Suppor ts with Web-based Intranet and Internet Information and Systems Applicable Suppor ts Telecommunications Products Not Applicable Video and Multimedia Products Not Applicable Self-Contained, Closed Products Not Applicable Desktop and Por table Computers Not Applicable Functional Performance Criteria Applicable Suppor ts with Information, Documentation, Suppor t Applicable Suppor ts Page 1 of 12

2 Section 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 industr y 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. with interface does not disrupt or disable most accessibility features of the operating system or accessibility applications with some, 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. Adobe RoboHelp 11 Voluntary Product Accessibility Template Page 2 of 12

3 (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. with 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. with 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 identif y controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. interface suppor ts the consistent use of image icons throughout the application. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 3 of 12

4 (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. Text information in Adobe RoboHelp 11 is available to assistive technologies with some, 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. with interface suppor ts 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 interface does not use animated content. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 4 of 12

5 (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. with 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 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. interface does not use flashing or blinking text, objects, or other similar elements. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 5 of 12

6 (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. 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 inser ting 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. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 6 of 12

7 Section Web-based Internet information and applications - Detail Criteria Supporting Features Remarks and explanations (a) A text equivalent for ever y non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). Alternative text for non-text elements can be provided both when an image is inser ted onto the page via the Inser t > Image menu option, or by manually editing the HTML in the HTML View authoring environment. However, techniques for providing useful text alternatives are not provided, so it is the author s responsibility to ensure the alternative text is helpful. (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. interface allows authors to embed multimedia content. However, there is no option in the Multimedia dialog box to provide equivalent alternatives such as captions or transcripts. It is the author s responsibility to ensure that captions are already included within the multimedia content or, if required, transcripts can be added separately as a separate document. (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. interface gives authors full control over color choice. However, it is the author s responsibility to ensure that color alone is not used to convey information. (d) Documents shall be organized so they are readable without requiring an associated style sheet. interface uses both inline and external style sheets. However, it is the author s responsibility to ensure that documents are readable without requiring an associated style sheet. Adobe RoboHelp 11 Voluntary Product Accessibility Template Page 7 of 12

8 (e) Redundant text links shall be provided for each active region of a server-side image map. Not applicable interface does not provide functionality for adding 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. interface suppor ts client-side image maps only. (g ) Row and column headers shall be identified for data tables. interface suppor ts the use of table header cells for data tables. However, the author must indicate table headers separately in the HTML View there is no option in the Table menu to identif y table 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. interface allows authors to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. However, the author must provide this markup separately in the HTML View there is no option in the Table menu to provide this association. (i) Frames shall be titled with text that facilitates frame identification and navigation interface allows users to inser t iframes. However, there is no option in the menu to provide a title. The author must provide the title manually in HTML View. (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. interface does not create flickering content. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 8 of 12

9 (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this par t, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. It should be possible to ensure content generated by the Adobe RoboHelp 11 user interface fully accessible without resor ting to alternative text-only pages. (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. interface allows authors to inser t their own scripts into Web pages. However, it is up to the author to ensure that their scripts include functional text that can be read by assistive technologies. (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 (a) through (l). interface allows authors to create links to applets and plug-ins necessar y 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. interface allows authors to inser t form controls. However, it is the author s responsibility to add form labels and to ensure these are programmatically associated with the relevant form controls via the HTML View. There is no option to add labels when dropping form controls into the Design View. (o) A method shall be provided that permits users to skip repetitive navigation links. interface provides table of contents and index options that allow users to bypass navigation links. Authors can also choose to manually create a means of skipping repetitive navigation links in the HTML View. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 9 of 12

10 (p) When a timed response is required, the user shall be aler ted and given sufficient time to indicate more time is required. interface does not automatically allow for the generation of timed responses. However, authors may add timed responses to scripted HTML content manually, ensuring that appropriate aler ts and controls are provided. Note to : 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 ) published by the Web Accessibility Initiative of the World Wide Web Consor tium: 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) , (j) - 7.1, (k) Section 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 suppor t for Assistive Technology used by people who are blind or visually impaired shall be provided. with 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 suppor t for Assistive Technology used by people who are visually impaired shall be provided. with interface suppor ts 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. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 10 of 12

11 (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or suppor t for Assistive Technology used by people who are deaf or hard of hearing shall be provided interface does not require user hearing. (d) Where audio information is impor tant for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditor y fashion, or suppor t for assistive hearing devices shall be provided. 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 suppor t for Assistive Technology used by people with disabilities shall be provided. 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. with Some par ts 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. Adobe RoboHelp 11 Voluntary Product Accessibilit y Template Page 11 of 12

12 Section Information, Documentation, and Support - Detail Criteria Supporting Features Remarks and explanations (a) Product suppor t documentation provided to endusers shall be made available in alternate formats upon request, at no additional charge. Adobe provides electronic versions of all product suppor t 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. Adobe provides information on accessibility features, par ticularly with regards to creating accessible content using the application, in the documentation and on the application s website. Electronic versions of all product suppor t documentation are provided. (c) Suppor t services for products shall accommodate the communication needs of end-users with disabilities. Product suppor t for Adobe products is available in a variety of formats from a number of online sources available from Adobe. Adobe RoboHelp 11 Voluntary Product Accessibility Template Page 12 of 12