Download the PDF

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, 2013

Name of product: Adobe® LiveCycle® Flex Workspace ES4

Contact for more information: access@adobe.com

 

Section 1194.21 Software Applications and Operating Systems - Detail
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

Most controls in the LiveCycle Workspace interface are fully operable using a keyboard alone with some exceptions including:

  • The “Help” drop-down menu cannot be activated by the keyboard alone.

  • Some radio buttons and tabs in the Preferences section cannot be activated using the keyboard alone.

  • Tables with sortable columns cannot be sorted using the keyboard alone.

  • Processes cannot be moved to “Favorites” using the keyboard alone.

(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 Workspace 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

Current focus is programmatically exposed for most controls in LiveCycle Workspace with some exceptions, including:

  • Focus is not programmatically exposed for interface elements that are inside containers outside the viewport.

  • The visual indication of focus is faint for tab controls.

(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

LiveCycle Workspace provides identity information to Assistive Technology, with some exceptions, including:

  • The Tree menu does not have the correct roles and states.

  • The names of the combo boxes in the “Manage UI Settings” tab in the “Preference” section have names that do not match the prompts.

  • Some radio buttons do not have the correct name in the “Manage Column Headers” tab in the “Preferences” section.

(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

Meanings associated with images are used consistently in the LiveCycle Workspace application.

(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

LiveCycle Workspace supports this requirement.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

Does not support

LiveCycle Workspace does not inherit user-selected contrast and color selections from the operating system.

(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

The LiveCycle Workspace interface does not use animation.

(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 Workspace does not use color 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.

Not applicable

LiveCycle Workspace 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 Workspace 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.

Supports with exceptions

Most form controls in LiveCycle Workspace are accessible to Assistive Technologies, with some exceptions, including:

  • Information about screens is not available when screens are first loaded.

  • The names of the combo boxes in the “Manage UI Settings” tab in the “Preferences” section have names that do not match the prompts.

  • Some radio buttons do not have the correct name in the “Manage Column Headers” tab in the “Preferences” section.

Section 1194.22 Web-based Internet information and applications - Detail
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 with exceptions

Non-text elements in LiveCycle Workspace have a text equivalent with some exceptions, including:

  • The expand/collapse images used to expand and collapse the Tree menu in the help section do not have a text alternative.

  • Some images in the help files include redundant text descriptions.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Not applicable

LiveCycle Workspace 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

LiveCycle Workspace supports this requirement.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Supports with exceptions

LiveCycle Workspace works without requiring an associated style sheet, except for the Welcome screen.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not applicable

LiveCycle Workspace 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

LiveCycle Workspace does not use client-side image maps.

(g) Row and column headers shall be identified for data tables.

Supports

LiveCycle Workspace provides information about row and column headers for data 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

LiveCycle Workspace does not have tables with two or more logical levels of row or column headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation

Supports with exceptions

LiveCycle Workspace does not use frames.

The LiveCycle Workspace help system includes frames that do not have 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.

Supports

LiveCycle Workspace supports this requirement.

(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

A text-only version is not required for LiveCycle Workspace as the application is accessible or 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

LiveCycle Workspace supports this requirement.

(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

For Flash movies in the LiveCycle Workspace there is a plug-in detection script included. 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.

Supports with exceptions

Most form controls in LiveCycle Workspace are accessible to Assistive Technologies, with some exceptions, including:

  • Information about screens is not available when screens are first loaded.

  • The names of the combo boxes in the “Manage UI Settings” tab in the “Preferences” section have names that do not match the prompts.

  • Some radio buttons do not have the correct name in the “Manage Column Headers” tab in the “Preferences” section.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supports

LiveCycle Workspace only has four links in the navigation.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Not applicable

LiveCycle Workspace 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.

Section 1194.31 Functional Performance Criteria - Detail
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

Most interface elements in LiveCycle Workspace are accessible to screen readers, with some exceptions, including:

  • Information about screens is not available when screens are first loaded.

  • The names of the combo boxes in the “Manage UI Settings” tab in the “Preferences” section have names that do not match the prompts.

  • Some radio buttons do not have the correct name in the “Manage Column Headers” tab in the “Preferences” section.

  • Some radio buttons and tabs in the Preferences section cannot be activated using the keyboard alone.

  • Tables with sortable columns cannot be sorted using the keyboard alone.

  • Processes cannot be moved to “Favorites” using the keyboard alone.

(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.

Does not support

LiveCycle Workspace does not allow text and objects to be resized.

Current focus is programmatically exposed for most controls in LiveCycle Workspace with some exceptions, including:

Focus is not programmatically exposed for interface elements that are inside containers outside the viewport.

The visual indication of focus is faint for tab controls.

(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