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

Name of product: Adobe® LiveCycle® Designer ES4

Contact for more information: access@adobe.com

  

Summary
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 Systems

Applicable

Supports

Section 1194.23 – Telecommunications Products

Not Applicable

Section 1194.24 – Video and Multimedia Products

Applicable

Supports

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

  

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

All user interface controls and functions in LiveCycle Designer can be executed via the keyboard with some exceptions including:

Signature Settings button and dialog. 

Inline hyperlinked text in palettes cannot be focused.

'Corners' controls in Border panel.

(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 Designer does not disrupt or disable Windows operating system accessibility features such as filter keys, toggle keys, sticky keys, and the on-screen keyboard.

(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

There is a well-defined and programmatically-exposed indication of focus for most of the LiveCycle Designer interface with some minor exceptions, including:

Focus is not correctly exposed to Assistive Technology for objects in Design View. 

(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 Designer provides identity, operation and state information to Assistive Technology in many parts of the interface, however some objects and controls do not provide this information, including:

Objects in the Welcome screen such as the New Form button.

Color pickers in application dialog boxes.

Palette names are not available. Keyboard focus moves to the first control in a palette without announcing the palette name.

Identity and role information are not available for objects in the Design View, although identities are available through the Hierarchy palette. For example, when a table is selected in Design View its label is available in the Hierarchy panel, although its role is not available directly.

(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

Bitmap images have unique names where used.

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

In most cases LiveCycle Designer provides text content, caret location and attributes.

However, in Design View, text information is not available for elements such as captions or headings for tables, although caption text for objects is available via the Object palette.

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

Supports

LiveCycle Designer supports user selected contrast and color settings.

(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

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

The LiveCycle Designer interface does not rely on 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

LiveCycle Designer allows authors to adjust color and font settings for code and scripting window.

(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

Flashing and blinking text and objects are not used in the LiveCycle Designer 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 Designer are accessible to assistive technologies, with some exceptions, including:

Some controls do not provide identity, role and state information, such as bitmap-based radio group controls in panels and color pickers in dialog boxes.

  

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

Authors can add alternative text descriptions for non-text objects in LiveCycle Designer through Custom Screen Reader Text, or a Tooltip.

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

Supports

Authors need to ensure that multimedia incorporated into a form includes synchronized equivalents.

(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 Designer supports the use of alternative methods of conveying information. For example, through text as well as color.

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

Supports

PDF documents created in LiveCycle Designer do not utilize style sheets.

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

Not Applicable

PDF documents created in LiveCycle Designer do not include 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

PDF documents created in LiveCycle Designer do not include image maps. 

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

Supports

Cells in tables can have a role of ‘header’ applied and this role is available to assistive technology.

(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

LiveCycle Designer supports the association of data cells with two or more logical levels of row and column headers through the embedding of sub forms, including header roles. 

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

Not Applicable

PDF documents created in LiveCycle Designer do not include 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

LiveCycle Designer does not create flickering content.  It is up to document authors to ensure compliance with 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

LiveCycle Designer supports the creation of a fully accessible primary document.

(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 Designer supports the inclusion of functional text for the information provided by a script. 

(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

A page for downloading the Acrobat plug-in is permanently available on the Adobe web site. Authors are encouraged to provide a link to this page. 

(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

LiveCycle Designer provides role and state information for form fields and allows authors to add ‘name’ values to form controls as well as Tooltips and Custom Screen Reader Text.There is full keyboard access to all standard form controls and authors can edit the Tab order of elements in a form.

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

Supports

Links can be added to documents in LiveCycle Designer and heading elements can be included to help users 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.

Supports

LiveCycle Designer supports the inclusion of alerts and the amount of time required to complete an action can be controlled by the document author.  

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.24 Video and Multi-media Products - Detail
Criteria Supporting features Remarks and explanations

a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. As soon as practicable, but not later than July 1, 2002, widescreen digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional displays measuring at least 13 inches vertically, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes DTV receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals.

Not Applicable

Adobe LiveCycle Designer does not include any display hardware.

(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry.

Not Applicable

Adobe LiveCycle Designer does not include any television tuner hardware.

(c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned.

Supports

 

(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described.

Supports

 

(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent.

Supports

 

  

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

LiveCycle Designer provides support for screen readers. However, some interface elements do not provide full support, including:

Some controls in panels and dialog boxes.

Some functions in the Design View such as the state of objects, the selection of multiple objects and editing text.

(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