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 - Workbench

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.

Supports with exceptions

AEM Forms Workbench utilizes the Eclipse integrated development environment. Eclipse provides keyboard access to many Workbench functions internal to the IDE with some exceptions including:

  • Some Workbench processes do not support keyboard access. Including the Event creation function in which some of the dialog elements cannot be reached using the keyboard.

  • Keyboard focus cannot be set on some controls, including help links in the New Form Assistant.

  • Keyboard interactivity is not consistent between integrated tools outside of the Eclipse IDE, such as AEM Forms Designer.

(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

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

Most user interface elements in the Workbench interface have a clear visual indication of focus with some exceptions, including:

  • Some controls in dialog boxes, such as radio buttons in the Event creation process, do not provide a visual indication of focus.

  • Focus cannot be set on some controls, including help links in the New Form Assistant.

(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

Workbench provides sufficient information about many user interface elements though some task flows are not accessible to Assistive Technology, including:

  • In AEM Forms Designer and AEM Forms Process Designer, graphical objects in the design workspace do not provide sufficient information to Assistive Technology.

  • Some buttons do not provide text equivalents for Assistive Technology.

  • Some tabs in Workbench do not provide sufficient information.

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

Does not support

Toolbar and other icons and images are not visually consistent within the Workbench tools.

(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

Most textual information in Workbench is available to Assistive Technology with some exceptions including:

  • Some text in AEM Forms Designer and AEM Forms Process Designer is not accessible to Assistive Technology.

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

Supports with exceptions

AEM Forms Workbench does support user selected color and contrast settings in most parts of the application with some exceptions including:

  • Some dialogs, such as New Form, do not correctly inherit user selected color and contrast settings, resulting in illegible text. Other dialogs in the New Application process utilize text labels that do not inherit 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

AEM Forms Workbench 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 Workbench user interface 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 

Workbench 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

Workbench does not use flashing or blinking text, objects, or other elements in the 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 the Workbench interface can be operated using the keyboard alone, with some exceptions, including:

  • Some Workbench processes do not support keyboard access. Including the Event creation function in which some of the dialog elements cannot be reached using the keyboard.

  • Identity, role and state information is provided to Assistive Technology for controls in the Workbench interface with some exceptions including:

  • Some buttons do not provide text equivalents for Assistive Technology.

  • Some tabs in Workbench do not provide sufficient information.

 
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

Applications created in Workbench can include text alternatives for non-text elements with some exceptions, including:

  • Alternate text descriptions for images in HTML documents are not included in converted PDF documents.

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

Not Applicable

Workbench does not utilize multimedia presentations.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Not applicable

Authors need to ensure that PDF documents, forms, and applications they create meet this requirement.

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

Supports

PDF forms and documents created in Workbench do not use style sheets.

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

Not Applicable

Workbench does not generate 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

Workbench does not generate client side image maps.

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

Supports

Forms, applications and PDF documents created in Workbench can include programmatically identifiable 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.

Does not support

Nested table headers are not supported in Workbench PDF output. 

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

Not applicable

Workbench does not create 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

Workbench does not use flashing or blinking text, objects, or other elements in the user interface.

(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 

 

(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 

 

(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

It is possible for authors to provide links to plug-ins with forms and applications developed using Workbench.

(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

Forms and documents created using Workbench support full keyboard accessibility and authors can ensure all form controls provide sufficient information to Assistive Technology.

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

Supports

Authors can use structural tags, such as headings, lists and tables that can be utilized by Assistive Technology to skip over repetitive blocks of content.

Authors can also adjust the tab order of fields and elements within forms to provide more efficient keyboard 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

By default, no timed response is required in applications designed with Workbench.

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.

Does not support

Some controls and inputs in the Workbench user interface are not accessible to screen readers.

For example:

  • Some Workbench processes do not support keyboard access. Including the Event creation function in which some of the dialog elements cannot be reached using the keyboard.

  • Some buttons do not provide text equivalents for Assistive Technology.

  • Some tabs in Workbench do not provide sufficient information.

(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

Some controls in Workbench do support user selected color contrast settings and some button labels are not readable when large fonts are selected.

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

Not applicable

 

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

Not applicable

 

(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