Guideline

Applicable

Compliance

Section 1194.21 – Software Applications and Operating Systems

Not Applicable

The AEM software application is operated via a web-based interface.

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

Applicable
(User Interface)

Supports with exceptions
(User Interface)

Applicable
(Authored Content)

Supports
(Authored Content)

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

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
(UI)

Adobe EM provides equivalents for most images. Exceptions include the representations of image assets such as cards and renditions.

Supports
(Authored Content)

Authors can add alternate text descriptions to images when editing their advanced properties.

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

Not applicable
(UI)

The AEM 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
(UI)

The AEM interface does not use color as the only means of conveying information.

Supports
(Authored Content)

Template and 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
(UI)

The AEM interface is not fully readable without associated style sheets.

For example: Every screen in the application has context sensitive content, such as error messages, displayed out of context, when CSS is disabled.

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
(UI)

The AEM interface does not include server-side image maps.

Not applicable
(Authored Content)

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

Not applicable
(UI)

The AEM interface does not include client-side image maps.

Supports
(Authored Content)

AEM supports the use of client-side instead of server-side image maps.

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

Does not support
(UI)

Grids in the AEM interface, such as the Sites and Assets grids, do not include header information.

Supports
(Authored Content)

Content authors can add header information to data tables in the cell properties dialog or by utilizing the source-editing feature of the CQ Rich Text Editor, where source editing has been enabled.

(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
(UI)

Grids in the AEM interface, do not contain two or more logical levels of row or column headers.

Supports
(Authored Content)

Content authors can add header information to data tables in the cell properties dialog or by utilizing the source-editing feature of the Rich Text Editor, where source editing has been enabled.

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

Not applicable
(UI)

Frames are not used in the AEM interface.

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
(UI)

The AEM interface does not cause the screen to flicker.

Supports
(Authored Content)

Authors may add content that causes the screen to flicker. However, AEM supports the creation of content that complies 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
(UI)

It should be possible to use AEM without requiring a text alternative.

Supports
(Authored Content)

It is possible to create web pages that meet the standard but it is also possible to create text-only pages.

(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
(UI)

Some scripted controls, such as the checkboxes in the Assets and Communities screens and sliders in Filter menus do not include 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 §1194.21(a) through (l).

Not applicable
(UI)

AEM does not require plug-ins or applets.

Supports
(Authored Content)

AEM enables authors to add links to PDF files and embed movies created in Adobe Flash® in a page, but does not generate the links automatically.

(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
(UI)

Identity, role and state information is available for many controls in the AEM interface with exceptions including:

• Checkboxes in the Assets and Communities screens that are not conveyed as checkboxes and the checked state is not exposed.

• The value properties of sliders in Filter menus are not exposed.

• Journal entry, Q&A Question, Q&A Answer & forum post buttons, in the Communities screen, do not have labels.

• Buttons and links with sub menus are not indicated as having sub menus.

• The user interface relies upon mouse based drag and drop functionality to perform some tasks.

• Timeline > Show All listbox not exposed as a listbox.

Supports
(Authored Content)

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

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

Supports with exceptions
(UI)

AEM does not include a keyboard method to skip repetitive navigation links. Headings, landmarks and collapsible controls, such as drop down menus and tree controls do help to reduce the number of repetitive links.

Supports
(Authored Content)

Authors can add methods to skip links to pages as well as structural elements such as Title components that are rendered as HTML heading elements.

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

Not applicable
(UI)

AEM does not require time-based responses.

Not applicable
(Authored Content)

AEM does not create content that requires timed responses. Authors may create this functionality and can ensure that it meets this requirement.

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

The AEM user interface contains controls and content that does not expose the information necessary for screen reader users to understand and operate the application.

(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 supports the use of screen magnifiers. However, not all elements provide a clear visual indication of current focus and focus is not programmatically exposed in some cases.

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

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

Most operations and interface objects in AEM do not require fine motor control. However, some advanced controls, such as tree menus, do include small icons and require fine levels of control. In some cases these can be operated using the keyboard but in others, such the checkboxes in the Assets and Communities - list views, and Drag & Drop based interactions, they cannot.

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.