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: May 22, 2014
Name of product: Adobe® Experience Manager (AEM) 6.0 Forms
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 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, 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.

Does not support

Some functionality can be achieved using the keyboard alone in AEM Forms, but some features require a mouse to operate, including:

  • Checkboxes not reachable or operable in the forms list view.

  • Error messages are only revealed on mouse hover.

  • Resources in the forms editing sidebar cannot be reached or operated using the keyboard alone.

  • The drag and drop functionality to move a custom widget to the form requires a mouse, and cannot be performed using the keyboard.

(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 with exceptions

AEM Forms does not disable accessibility features, except for pinch zoom in Safari/iOS that has been disabled.

(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

AEM Forms provides a visual indication for most elements with some exceptions:

  • Focus sometimes goes to non-interface elements, and cannot be seen visually.

  • Focus is sometimes obscured by the header and footer in responsive mode.

  • There is no visual indication of focus in the image and edit toolbars when editing a form.

  • The visual indication of focus is sometimes faint, particularly on image links.

  • The focus order is sometimes unpredictable, and reset to the start after some operations, such as deleting a tag.

(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

AEM Forms provides sufficient information for basic interface elements, but does not provide sufficient information for more complex elements, including:

  • Checkboxes in list view do not expose the correct role, state, or name.

  • Menu buttons with incorrect roles and structure.

  • The tree view in the browse tab of the left sidebar does not expose the correct role or state.

  • Some autocomplete widgets have an incorrect structure, and some do not expose the correct role or name.

  • Some buttons do not have a name.

(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

AEM Forms uses bitmap images consistently throughout the 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 with exceptions

AEM Forms makes most text available to assistive technologies, with the exception of some information that is provided as CSS background images with no text alternative.

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

Supports with exceptions

AEM Forms does not override user selected contrast selections, with the following exception:

  • Some information is provided as CSS background images that are not displayed in Windows’ high contrast mode.

(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

AEM Forms 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 with exceptions

AEM Forms does not rely on color alone, with the following exception:

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

(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

AEM Forms does not provide a facility to adjust contrast, but users can choose their own color schemes for forms they create.

(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

AEM Forms does not use flashing or blinking content.

(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

Some parts of AEM Forms cannot be operated correctly using assistive technologies, including:

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

  • Some form controls have been incorrectly labeled.

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

  • Error messages are not available to assistive technologies.

 

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

Does not support

Some non-text objects have a text equivalent in AEM Forms, but the majority do not, including:

  • Most images lack an alt attribute.

  • Some functionality is provided as CSS background images with no text equivalent.

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

Not applicable

AEM Forms does not have 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 with exceptions

AEM Forms does not rely on color alone, with the following exception:

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

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

Does not support

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

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

Not applicable.

AEM Forms 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

AEM Forms does not use server-side image maps

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

Does not support

The AEM Forms list view is presented as a tree grid without column or row headers associated.

(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

AEM Forms does not have data tables with two or more logical levels or row or column headers.

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

Does not support

None of the IFrames have a title in AEM Forms.

(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

AEM Forms does not cause the screen to flicker.

(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

AEM Forms does not require 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

Some scripted elements do not provide the correct role, state, or name in AEM Forms.

(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

AEM Forms doesn’t require a plug-in. If authors use content that require a plug-in in their forms, they will need to provide a link to the appropriate plug-in.

(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

Some parts of AEM Forms cannot be operated correctly using assistive technologies, including:

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

  • Some form controls have been incorrectly labeled.

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

  • Error messages are not available to assistive technologies.

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

Supports with exceptions

AEM Forms does not have skip links, but provides landmark regions for assistive technologies.

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

Not applicable

AEM Forms does not require timed responses.

 

 

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.