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: April 21, 2016

Name of product: Adobe® Experience Manager (AEM) 6.2 Forms - Adaptive Forms

Contact for more information: access@adobe.com

 
 
Section 1194.22 Web-based Intranet and 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
(User Interface)

 

AEM Forms – Adaptive Forms provides equivalents for most images. Exceptions include representations of image assets.

 

 

Supports
(Authored Content)

Authors can add alternative text to images.

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

Not applicable
(User Interface)

 

The AEM Forms - Adaptive Forms interface does not include multimedia.

 

Supports
(Authored Content)

It is possible to add synchronized alternatives to multimedia content added to documents. However, this must be done in multimedia editing software.

(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 with exceptions
(User Interface)

The AEM Forms - Adaptive Forms interface does not rely on color alone, with the following exception:

  • The current step for creating an adaptive form is shown by color alone.

 

Supports
(Authored Content)

Content authors can ensure that color alone is not used to convey information.

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

Does not support
(User Interface)

AEM Forms – Adaptive Forms is a web application that requires style sheets to operate correctly.

 

.

Supports
(Authored Content)

Template and content authors can ensure that documents can be read 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
(User Interface)

AEM Forms – Adaptive Forms does not use server-side image maps.

 

Not applicable
(Authored Content)

AEM Forms – Adaptive Forms does not create 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.

Supports with exceptions
(User Interface)

AEM Forms – Adaptive Forms does not use client-side image maps.

 

Not applicable
(Authored Content)

AEM Forms – Adaptive Forms does not support client-side image maps

 

 

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

Does not support
(User Interface)

 

Grids in the AEM Forms – Adaptive Forms interface do not include header information.

 

 

 

Supports with exceptions
(Authored Content)

The AEM Forms – Adaptive Forms table component identifies column headers by default, but row headers are not supported.

(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
(User Interface)

Some parts of AEM Forms – Adaptive The AEM Forms – Adaptive Forms interface does not contain grids with two or more logical levels of row or column headers.

 

Not applicable
(Authored Content)

AEM Forms – Adaptive Forms does not create data 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

Does not support
(User Interface)

Iframes do not have a title in AEM Forms – Adaptive Forms.

 

Supports
(Authored Content)

Authors can ensure that frames include 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
(User Interface)

The AEM Forms – Adaptive Forms interface does not cause the screen to flicker.

 

Supports
(Authored Content)

AEM Forms – Adaptive Forms supports the creation of content that conforms with this standard.

(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
(User Interface)

AEM Forms – Adaptive Forms does not required a text-only page.

 

Supports
(Authored Content)

Authors can create pages that meet the standard or provide a text-only page.

(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
(User Interface)

Some scripted controls do not provide functional text equivalents.

 

Supports
(Authored Content)

Authors can ensure that scripted content contains text equivalents.

(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 Section 1194.21(a) through (l).

Supports
(User Interface)

AEM Forms – Adaptive Forms does not require plug-ins or applets.

 

Supports
(Authored Content)

AEM Forms – Adaptive Forms enables authors to add links to the appropriate plug-in if any plug-ins are required.

(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
(User Interface)

Some parts of AEM Forms – Adaptive Forms cannot be operated using assistive technologies.

  • Some interface elements do not expose the correct role, state, or name.

  • Some form controls have not been correctly labeled.

  • Some elements are not reachable or operable using the keyboard alone.

 

Supports with exceptions
(Authored Content)

Authored forms support keyboard accessibility and provide role and state information. Programmatic labels (aria-labels) are created when form inputs are added to a document.

There may be some exceptions. Exceptions include:

  • No information is given to the user that an option is selected in a drop-down list.

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

Supports with exceptions
(User Interface)

The AEM Forms – Adaptive Forms interface does not provide a method to skip repetitive navigation links, however headings and collapsible controls help to reduce the number of repetitive links.

 

Supports
(Authored Content)

Authors can add structural elements and methods to skip links to help with 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
(User Interface)

AEM Forms – Adaptive Forms does not require time-based responses.

 

Not applicable
(Authored Content)

AEM Forms – Adaptive Forms does not create content that requires timed responses. If time-based responses are needed, authors can create functionality that meets this requirement.

Note to 1194.22: e 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.).

Does not support

See 1194.22 for details.

(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

AEM Forms – Adaptive Forms does not require visual acuity greater than 20/70. However, not all elements provide a clear visual indication of 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

AEM Forms – Adaptive Forms does not require hearing.

(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

AEM Forms – Adaptive Forms does not require audio.

(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

AEM Forms – Adaptive Forms does not require speech.

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

Does not support

AEM Forms – Adaptive Forms requires the use of a computer mouse for full functionality.
 
Section 1194.41 Information, Documentation, and Support - Detail
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.