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: 48K), or view the information below.
Download Adobe® Reader®
Date: November 2005
Name of Product:
Adobe® LiveCycle™ Designer 7.1
| Criteria | Supporting Features | Remarks and Explanations |
|---|---|---|
|
Section 1194.21 Software Applications and Operating Systems |
Completed | |
|
Section 1194.22 Web-based internet information and applications |
Not applicable | Adobe® LiveCycle™ Designer is not Web-based Internet Information or a Web-based Application. |
|
Section 1194.23 Telecommunications Products |
Not applicable | Adobe LiveCycle Designer is not a Telecommunications Product. |
|
Section 1194.24 Video and Multi-media Products |
Not applicable | Adobe LiveCycle Designer is not a Video or Multi-media product. |
|
Section 1194.25 Self-Contained, Closed Products |
Not applicable | Adobe LiveCycle Designer is not a Self-contained or Closed Product. |
|
Section 1194.26 Desktop and Portable Computers |
Not applicable | Adobe LiveCycle Designer is not a Desktop or Portable Computer. |
|
Section 1194.31 Functional Performance Criteria |
Completed | |
|
Section 1194.41 Information, Documentation, and Support |
Completed |
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 with some exceptions | There were some cases in which Adobe LiveCycle Designer functions and features were not accessible through 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 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 | No specific disruption of Assistive Technology software occurred. |
|
(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 | The product is partially compatible with Assistive Technology (screen reader and screen magnifier software). In some cases, focus was not tracked by Assistive Technology (e.g., forms layout mode). |
|
(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 | |
|
(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 some exceptions | Screen readers cannot access and read toolbar images within the Adobe LiveCycle Designer interface. |
|
(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 some exceptions | In the Adobe LiveCycle Designer interface, screen readers cannot track and identify caret location when creating forms. |
|
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
Supports | Adobe LiveCycle Designer does not override user-selected contrasts and color selections. |
|
(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 was used in this software application. |
|
(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 | Adobe LiveCycle Designer does not use color coding as the only means of conveying information. |
|
(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. |
Supports | In Adobe LiveCycle Designer, the Script Editor and the XML Source Editor allow the user to adjust the font size and foreground/background colors. |
|
(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 | There is no blinking text or object in this software. |
|
(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 some exceptions | The purpose of Adobe LiveCycle Designer is to create electronic forms. The Adobe LiveCycle Designer software interface, which includes dialog boxes with input, cannot be accessed completely independently and read by screen readers (e.g., the field property dialog box). The PDF e-forms that are created by Adobe LiveCycle Designer are accessible by default. The usability of a PDF form to a disabled user depends on the e-form design. |
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 with some exceptions | The product does not provide full accessibility for visually impaired users using Assistive Technology. Reviewers were not able to read complete information on the menu and toolbars and assign focus on the edit screen. |
|
(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 some exceptions | The product does not provide full accessibility for visually impaired users using Assistive Technology. Screen readers do not read static text, field names, and contents of the combo boxes. |
|
(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 | No audio signal is generated by the software. |
|
(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 | No audio signal is generated by the software. |
|
(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 | No speech input signal is required to operate the software. |
|
(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 | The product is compatible with alternative input devices (e.g., trackball, one-handed keyboard) and built-in accessibility tools (e.g., onscreen keyboard, sticky keys). The user can define custom keyboard shortcuts. |
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 exceptions (No TTY/TDD) | Support for Adobe products is available in a variety of formats and a number of online resources from Adobe Systems. |
