Voluntary Product Accessibility Template
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.
View or download the PDF file (PDF: 59K), or view the information below.
Download Adobe® Reader®
Date: August 30 2005
Name of Product:
Adobe® LiveCycle™ Form Manager 7.0
| Criteria | Supporting Features | Remarks and Explanations |
|---|---|---|
|
Section 1194.21 Software Applications and Operating Systems |
Completed | See Section Detail for 1194.21. |
|
Section 1194.22 Web-based internet information and applications |
Completed | See Section Detail for 1194.22. |
|
Section 1194.23 Telecommunications Products |
Not applicable | Adobe® LiveCycle™ Form Manager is not a Telecommunications Product. |
|
Section 1194.24 Video and Multi-media Products |
Not applicable | Adobe LiveCycle Form Manager is not a Video or Multi-media Product. |
|
Section 1194.25 Self-Contained, Closed Products |
Not applicable | Adobe LiveCycle Form Manager is not a Self-Contained, Closed Product. |
|
Section 1194.26 Desktop and Portable Computers |
Not applicable | Adobe LiveCycle Form Manager is not a Desktop or Portable Computer. |
|
Section 1194.31 Functional Performance Criteria |
Completed | See Section Detail for 1194.31. |
|
Section 1194.41 Information, Documentation, and Support |
Completed | See Section Detail for 1194.41. |
Section 1194.21 Software Applications and Operating Systems - Detail
Voluntary Product Accessibility Template
| 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 | All design and administration components support keystrokes. |
|
(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 | |
|
(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 some exceptions | Adobe LiveCycle Form Manager provides an onscreen focus to the end user. While navigating though various pages, the focus is displayed to the user, all the time, while they tab. |
|
(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 some exceptions | Some collapsible, contracting links are ambiguous. |
|
(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 | |
|
(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 when combined with compatible Assistive Technology | |
|
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
Supports | |
|
(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 some exceptions | Color coding is not used as the sole means of conveying information in Adobe LiveCycle Form Manager. |
|
(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 | |
|
(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 | Adobe LiveCycle Form Manager 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 | Forms are provided by other tools such as Adobe LiveCycle Forms for HTML-based forms or Adobe Reader®/Adobe Acrobat® for PDF-based forms. Access to the information, field elements, and functionality required for the completion and submission of forms accessed through Adobe LiveCycle Form Manager is dependent upon the proper preparation of the form’s native format (i.e., PDF/HTML). |
Section 1194.22 Web-based Internet information and applications - Detail
Voluntary Product Accessibility Template
| 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 for the elements of the Adobe LiveCycle Form Manager user interface. Access to the information, field elements, and functionality required for the completion and submission of forms accessed through Adobe LiveCycle Form Manager is dependent upon the proper preparation of the form’s native format (i.e., PDF/HTML). |
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not applicable | Adobe LiveCycle Form Manager does not make use of 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 with some exceptions | No information is presented to the end user solely using color. Applies to Adobe LiveCycle Form Manager user interface. |
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports with some exceptions | 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 | Adobe LiveCycle Form Manager does not make use of 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 | Adobe LiveCycle Form Manager does not make use of image maps. |
|
(g) Row and column headers shall be identified for data tables. |
Supports | Applies to Adobe LiveCycle Form Manager 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 some exceptions | No tables have more than one logical level of rows or column headers. Applies to Adobe LiveCycle Form Manager user interface. Adobe LiveCycle Form Manager 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 through equivalent facilitation | Frames have names but do not have descriptive titles. |
|
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
Not applicable | No flashing or blinking text, objects, or other elements are used in the product. Applies to Adobe LiveCycle Form Manager user interface. |
|
(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 | |
|
(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 some exceptions | Some interface elements that are generated from scripts, such as the calendar date selector, cannot be read by Assistive Technology. Other script-driven content and interface elements 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 | Web administrators can provide links to an appropriate user agent such as Adobe Reader when required to view the form. |
|
(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 | Access to the information, field elements, and functionality required for the completion and submission of forms accessed through Adobe LiveCycle Form Manager is dependent upon the proper preparation of the form’s native format (i.e., PDF/HTML). |
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Does not support | |
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supports with some exceptions | Product does not use timed responses. The exception is that the workflow item could expire without the user knowing it. |
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
Voluntary Product Accessibility Template
| 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 | |
|
(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 |
Not applicable | Adobe LiveCycle Form Manager does not generate an audio signal or warnings. User hearing is not required to interact with Adobe LiveCycle Form Manager. |
|
(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 | Adobe LiveCycle Form Manager does not generate an audio signal or warnings. User hearing is not required to interact with Adobe LiveCycle Form Manager. |
|
(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. |
Not applicable | User speech is not required to interact with Adobe LiveCycle Form Manager. |
|
(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 |
Section 1194.41 Information, Documentation, and Support - Detail
Voluntary Product Accessibility Template
| 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, with mechanisms available for the conversion of these documents to alternate formats. |
|
(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 electronic versions of all product support documentation, with mechanisms available for the conversion of these documents to alternate formats. |
|
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supports with some exceptions (no TTY/TDD) | Support for Adobe products is available in a variety of formats and a number of online resources from Adobe Systems. |
