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: December 21, 2009
Name of product: Adobe® LiveCycle® Collaboration Service
Contact for more information: access@adobe.com
Summary Table
| 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 (ConnectNow output only) |
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 |
Many components in LiveCycle Collaboration Service are fully operable using the keyboard alone with some exceptions including: Some controls in the Developer Portal, such as the Report and Download SDK buttons and the navigation links such as ‘My Account’. Some text inputs such as the Account Url input are not operable with a keyboard alone. Some controls in the SDK Navigator, for example: Selecting items in lists, such as the Applications list in the Rooms Console, requires a mouse. Selecting Video Tutorials in the list requires a mouse. |
(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 |
LiveCycle Collaboration Service does not interfere with or deactivate accessibility features of any operating system. |
(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 Collaboration Service supports an on-screen indication of current focus for most controls with some exceptions including: Navigation links and some controls and buttons in the Developer Portal. There is no clear visual indication of focus for the list of Video Tutorials in the SDK Navigator. Buttons in the SDK Navigator installer do not provide a clear indication of focus. Focus is not programmatically exposed to Assistive Technology. |
(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. |
Does Not Support |
Identity role and state information is not available to Assistive Technology for controls in the Developer Portal. With the exception of some inputs in the Room Console, sufficient information is not provided to Assistive Technology in the SDK Navigator. |
(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. |
Does Not Support |
Textual information in LiveCycle Collaboration Service is not available to Assistive Technology. |
(g) Applications shall not override user-selected contrast and color selections and other individual display attributes. |
Does Not Support |
LiveCycle Collaboration Service does not inherit user selected contrast 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. |
Supports |
LiveCycle Collaboration Service does not use animation in the user interface. |
(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 |
LiveCycle Collaboration Service does not use color coding as the only way 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. |
Not Applicable |
LiveCycle Collaboration Service 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. |
Supports |
LiveCycle Collaboration Service does not use flashing or blinking text, objects, or other elements in the software's user interface. |
(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. |
Does Not Support |
With some exceptions, form controls in LiveCycle Collaboration Service do not provide sufficient information to Assistive Technology. Most form controls are operable using the keyboard alone, with some exceptions including: Some controls in the Developer Portal, such as the Report and Download SDK buttons and the navigation links, such as ‘My Account’, require a mouse. Selecting items in lists, such as the Applications list in the Rooms Console, requires a mouse. Selecting Video Tutorials in the list in the SDK Navigator requires a mouse. |
| 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 |
There are non-text objects, such as buttons on the toolbar that do not expose a text equivalent. |
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Supports with Exceptions |
ConnectNow includes a Notes pod where it is possible to add captions and synchronize these with a 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 |
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports |
ConnectNow is readable without requiring an associated style sheet. |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not Applicable |
ConnectNow 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 |
ConnectNow does not use server-side image maps. |
(g) Row and column headers shall be identified for data tables. |
Not Applicable |
ConnectNow does not use tables. |
(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 |
ConnectNow does not use tables. |
(i) Frames shall be titled with text that facilitates frame identification and navigation. |
Not Applicable |
ConnectNow does not create 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 |
By default ConnectNow does not have content that causes the screen to flicker at a frequency greater than 2Hz or lower than 55Hz. |
(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 |
There is no need for a text-only page, as the application 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. |
Not Applicable |
ConnectNow does not use client-side scripting. |
(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 |
ConnectNow includes a plug-in detection script. If the Flash plug-in is not detected in the user’s browser a link to download the plug-in is available. |
(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 |
Most form controls do not provide sufficient information to Assistive Technology. For example, identity information is only available for the links in the Get Started dialog. No information is available to Assistive Technology for controls in the Prefer |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Does Not Support |
There is no way to skip over the ConnectNow application menu or toolbar with a keyboard alone. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Supports |
ConnectNow does not require timed responses. |
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 |
Identity role and state information is not available to Assistive Technology through LiveCycle Collaboration Service. |
(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 Exceptions |
LiveCycle Collaboration Service supports an on-screen indication of current focus for most controls with some exceptions including: Navigation links and some controls and buttons in the Developer Portal. There is no clear visual indication of focus for |
(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 |
Operation of the LiveCycle Collaboration Service interface does not require simultaneous actions and many functions are fully operable using a keyboard. |
| 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. |
