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 - Screens Player

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

Not Applicable

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

There are three different AEM Screens players for iOS, OS X and Android. The AEM Screens Player software can be run on a system that has or does not have a 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

The AEM Screens Player does not disrupt or disable accessibility features of the operating system or other products.

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

Does not support

Current focus may be provided by the AEM Screens Player, and the focus may be programmatically exposed. However, if the AEM Screens Player is launched in full screen mode, there may not be a clear indication of focus.

(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

Labels are not tied directly to the form fields in the AEM Screens – Preferences window.

(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

Images are used consistently in AEM Screens Player.

(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

Textual information in AEM Screens is available to assistive technology. However, full screen mode in AEM Screens may not allow for text input.

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

Supports with exceptions

The AEM Screens Player does not override user selected contrast and color selections, however it may have limited support for contrast modes.

(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

The AEM Screens Player 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 AEM Screens Player does not use color as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

(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 

The AEM Screens Player does not allow a 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

AEM Screens Player does not cause the screen to flicker.

(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

Labels are not tied directly to the form fields in the AEM Screens – Preferences window.

 
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

Controls and functions in the AEM Screens user interface may be accessible to screen readers with some exceptions. However, if the AEM Screens Player is launched in full screen mode and the device deployment does not allow the user the ability to use the assistive technology on the device; for example, putting the device in a locked box for kiosk purposes; then the deployment would not support the criteria.

(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 Screens Player supports the use of screen magnifiers. However, if the AEM Screens Player is launched in full screen mode, there may not be a clear 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

 

(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