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: July 17, 2008
Name of product: Adobe® LiveCycle® Process Management ES 8.2
Contact for more information: access@adobe.com
| Guideline | Applicable | Compliance |
|---|---|---|
| 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 |
| 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. | Supports with exceptions |
All design and administration components support keystrokes. Adobe is currently unable to add a form to Favorites via the keyboard. Preferences, Messages, and Help may not fully support keyboard interaction. |
| (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 |
Adobe LiveCycle Workspace ES does not disable or disrupt any other product's accessibility feature. |
| (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 |
LiveCycle Process Management ES has an onscreen focus to the end user. During navigation though various pages, the focus is displayed to users, all the time, while they tab. With the exception of the areas not tested (see paragraph a), the focus is always read to the user, via the screen reader, except where limitations of the screen reader exist. |
| (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 |
The screen reader does not indicate where the user is when the user lands on a new page. |
| (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 with exceptions |
Some controls in Adobe LiveCycle Workbench ES do not have text equivalents. |
| (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 |
|
| (g) Applications shall not override user-selected contrast and color selections and other individual display attributes. | Does not support |
LiveCycle Process Management ES does not support user-selected contrast or color. |
| (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 |
No animation is used in the product. |
| (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 |
Color coding is not used as the sole means of conveying information in LiveCycle Process Management ES. |
| (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 |
LiveCycle Process Management ES does not support changes in color or contrast. |
| (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 |
LiveCycle Process Management ES does not use flashing or blinking text. |
| (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 |
Forms are provided by other tools such as Adobe LiveCycle Forms ES for HTML-based forms or Adobe Reader® or Acrobat® for PDF-based forms. LiveCycle Process Management ES does not itself provide electronic forms. Form Guides in LiveCycle Workspace ES do not expose sufficient information to assistive technology. |
| Criteria | Supporting features | Remarks and explanations |
|---|---|---|
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt," "longdesc," or in element content). |
Supports |
Text equivalents are provided. Applies to LiveCycle Process Management ES user interface. Authors need to verify that their content conforms to this paragraph. |
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not applicable |
LiveCycle Process Management ES does not use multimedia presentation. |
(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 |
No information is presented to the end user solely using color. Applies to LiveCycle Process Management ES user interface. Authors need to verify that their content conforms to this paragraph. |
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports |
Without the presence of a style sheet, the navigation is visually hindered. |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not applicable |
LiveCycle Process Management ES does not use 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. |
Not applicable |
LiveCycle Process Management ES does not use image maps. |
(g) Row and column headers shall be identified for data tables. |
Supports |
Applies to LiveCycle Process Management user interface but not to Form Administrator interface. |
(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 exception |
No tables have more than one logical level of rows or column headers. Applies to LiveCycle Process Management ES user interface. LiveCycle Process Management ES uses table headers, but the cells are not associated with the headers. |
(i) Frames shall be titled with text that facilitates frame identification and navigation. |
Supports |
Frames have names but do not have descriptive titles. Authors need to verify that their content conforms to this paragraph. |
(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 |
No flashing or blinking text, objects, or other elements are used in the product. Applies to LiveCycle Process Management ES user interface. Authors need to verify that their content conforms to this paragraph. |
(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 |
|
(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 with exceptions |
Some form controls may not be accessible to 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 |
Authors need to verify that their content conforms to this paragraph. |
(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 |
LiveCycle Process Management ES presents the form. Electronic forms that will be completed online can fully support conventional assistive technology through the use of an appropriately designed form template. Authors need to verify that their content conforms to this paragraph. |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports with exceptions |
Authors need to verify that their content conforms to this paragraph. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supports with exception |
The product does not use timed responses. However, users are not notified if they are editing a workflow task that may expire during the session. |
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.
| 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 areas of the product may not be keyboard navigable. |
| (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 |
|
| (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. | Not applicable |
LiveCycle Forms ES does not utilize 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 |
|
| (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 |
Users may be required to use a mouse in certain areas of the product. Some controls may not be keyboard accessible. |
| Criteria | Supporting features | Remarks and explanations |
|---|---|---|
(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. |
