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® Mobile Forms ES4
Contact for more information: access@adobe.com

 

 

Summary
Guideline Applicable Compliance

Section 1194.21 – Software Applications and Operating Systems

Not Applicable

LiveCycle Mobile Forms are web-based.

Section 1194.22 – Web-based Intranet and Internet Information and Systems

Applicable

Supports with exceptions

Section 1194.23 – Telecommunications Products

Not Applicable

Section 1194.24 – Video and Multimedia Products

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

Applicable

Supports

 

 

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

Authors can add textual alternatives to their images, but some automatically generated content, such as the Document Type icon, do not include text alternatives.

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

Not Applicable

LiveCycle Mobile Forms does not generate 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 

Authors will need to verify that their content conforms to this requirement.

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

Does Not support

Without associated stylesheets, the read order of forms generated by LiveCycle Mobile Forms does not follow a logical order.

Most HTML controls, such as the Calendar widget, require style sheets for their layout.

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

Not Applicable 

LiveCycle Mobile Forms does not use 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 Mobile Forms does not use image maps. 

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

Does Not Support

While authors can add information about column headers to the data tables generated by LiveCycle Mobile Forms, this information is not programmatically associated with cells within the data grid.

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

Does Not Support

Multi-level headers are not supported by LiveCycle Mobile Forms.

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

Not Applicable

LiveCycle Mobile Forms do not generate 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

Authors will need to verify that their content conforms to 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

It is not possible to provide a text-only version where data entry into forms is required.

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

The scripting utilized in LiveCycle Mobile Forms creates information that can be read by Assistive Technology. However some controls, such as the Date Picker calendar control, do not provide sufficient information to 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

Authors will need to verify that their content conforms to this requirement. 

(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

Some generated elements in LiveCycle Mobile Forms do not provide sufficient information to Assistive Technology. For example:

  • The data grid, for tabular data, does not expose sufficient information to Assistive Technology to correctly identify cell headers.

  • The Date Chooser calendar control does not provide sufficient information to be operable using Assistive Technology.

  • In some browsers/field combinations the keyboard focus can become trapped on a field.

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

Supports with Exceptions

Authors will need to verify that their content conforms to this paragraph. Skip links are not generated in HTML mobile forms but other structural elements may be used for navigation, such as list elements.

Headings generated by LiveCycle Mobile Forms do not have heading roles.

(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 Mobile Forms does not support time limits.  

 

 

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

Some generated elements in LiveCycle Mobile Forms do not provide sufficient information to Assistive Technology. For example:

  • The data grid, for tabular data, does not expose sufficient information to Assistive Technology to correctly identify cell headers.

  • The Date Chooser calendar control does not provide sufficient information to be operable using Assistive Technology.

  • In some browsers/field combinations keyboard focus can become trapped on a field.

  • Some HTML elements, such as headings, do not provide a correct identity or role.

(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

Fields generated by LiveCycle Mobile Forms do not provide a well-defined on-screen indication of the current focus.

(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