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: March 22, 2012
Name of product: Adobe® LiveCycle® Forms Manager ES4
Contact for more information: access@adobe.com
Guideline | Applicable | Compliance |
---|---|---|
Section 1194.21 – Software Applications and Operating Systems |
Not Applicable |
— |
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 with Exceptions |
Section 1194.41 – Information, Documentation, Support |
Applicable |
Supports |
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). |
Does Not Support |
Most images and controls within the LiveCycle Forms Manager interface do not have text alternatives, for example:
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not Applicable |
The LiveCycle Forms Manager interface does not include multimedia. |
(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 with Exceptions |
The LiveCycle Forms Manager user interface does not use color as the only means of conveying information with some exceptions, including:
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports with Exceptions |
The LiveCycle Forms Manager interface supports this requirement, but the usability of the interface is degraded. Many icon buttons, such as the Activate and Download buttons, are rendered using CSS sprites, which are not visible without the associated style sheet. |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not Applicable |
The LiveCycle Forms Manager interface 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. |
Not Applicable |
The LiveCycle Forms Manager interface does not use client-side image maps. |
(g) Row and column headers shall be identified for data tables. |
Does Not Support |
While information about column headers exists for the data tables in LiveCycle Forms Manager, such as the main documents table, this information is not programmatically associated with cells within the data grid. |
(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. |
Not Applicable |
LiveCycle Forms Manager does not contain complex data tables with two or more logical levels of row and column headers. |
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Not Applicable |
The LiveCycle Forms Manager user interface does not use 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 |
|
(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. |
Not Applicable |
It is not necessary to provide a text-only version of the LiveCycle Forms Managers interface as it can be made accessible. |
(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 |
The scripting utilized in LiveCycle Forms Manager creates information that can be read by Assistive Technology, however some controls, such as the Date Picker calendar control, or the Tags dialog box, do not provide sufficient information 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 |
|
(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. |
Does Not Support |
Many controls required to manage forms in the LiveCycle Forms Manager interface do not provide sufficient information to Assistive Technology. For example:
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports with Exceptions |
There is no explicit way to skip repetitive navigation items in the LiveCycle Forms Manager interface, but structural elements like lists, and tab panels may be used to skip over repetitive content. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Does Not Support |
The LiveCycle Forms Manager session timeout is not announced and it may not be extended. |
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. |
Does Not Support |
Many controls required to manage forms in the LiveCycle Forms Manager interface do not provide sufficient information to Assistive Technology. For example:
|
(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. |
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 |
While there are few operations within the LiveCycle Forms Manager that require fine motor control, and none that require simultaneous actions, some controls do not provide a well-defined on-screen indication of the current focus and are not operable using a keyboard. |