(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). |
Does not support
(Application) |
Images, such as icons on the main toolbar, or on the floating panel in content editing, do not include alternate text descriptions.
Many image icons in the interface include alternate text descriptions but some do not, including:
The Search icon button in the Marketing Cloud interface does not include a label. Some icons, such as the filter icon, do not have sufficient alternate text descriptions.
The navigation bar icons in the WCM interface, such as Digital Asset Management, do not include labels. |
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
(Application) |
The AEM 5.6 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
(Application) |
The AEM 5.6 interface does not use color as the only means of conveying information.
However, grids may contain status information that is available through color alone. |
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
(Application) |
The AEM 5.6 interface is not fully readable without associated style sheets.
For example, in the Marketing Cloud interface elements, such as user preferences, appear out of context when style sheets are 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
(Application) |
The AEM 5.6 interface does not include server-side image maps. |
Not applicable
(Authored Content) |
AEM 5.6 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
(Application) |
The AEM 5.6 interface does not include client-side image maps. |
Supports
(Authored Content) |
AEM 5.6 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
(Application) |
Grids in the AEM 5.6 interface, such as the Websites grid in the WCM interface, do not include header information. Grids in the Marketing Cloud interface, such as the Sites grid, use heading elements rather than table 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 AEM 5.6 Rich Text Editor. |
(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
(Application) |
Grids in the AEM 5.6 interface, such as the Websites grid in the WCM interface, do not include header information. Grids in the Marketing Cloud interface, such as the Sites grid, do not have more than one logical level of 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 AEM 5.6 Rich Text Editor. |
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Does not support
(Application) |
iframes in the AEM 5.6 interface, do not include titles. |
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
(Application) |
The AEM 5.6 interface does not cause the screen to flicker. |
Supports
(Authored Content) |
Authors may add content that causes the screen to flicker. However, AEM 5.6 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
(Application) |
It should be possible to use AEM 5.6 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
(Application) |
Some scripted controls, such as the pagination controls in the user list in the Users section, do not include functional text equivalents.
Some scripted controls, such as the tree menu in the Websites tab of the WCM interface, provide labels to assistive technology but not role information. |
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
(Application) |
AEM 5.6 does not require plug-ins or applets. |
Supports
(Authored Content) |
AEM 5.6 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 (Application) |
Identity, role and state information is available for many controls in the AEM 5.6 interface with exceptions including:
-
Information about some form controls and icons in toolbars, such as search inputs and buttons, is not available to assistive technologies.
-
Some controls, such as the Templates list in the New Site dialog, are not operable without a mouse.
-
Some form controls in panels, such as the Scene7 Media Browser, do not include programmatic labels.
-
It is not possible to select and activate many objects in grids, such as the checkboxes in the Sites grid, in the Marketing Cloud interface, using a keyboard alone.
-
Text in some content objects in edit mode, such as data tables, does not provide sufficient information.
-
Focus is not programmatically exposed in some content, such as data tables in the data table editor.
|
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.
Providing programmatic labels for groups of controls may require editing of the page source code. |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports with exceptions
(Application) |
AEM 5.6 does not include a method to skip repetitive navigation links. Collapsible controls, such as drop down menus and tree controls do help to reduce repetitive links and contain structural markup. |
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
(Application) |
AEM 5.6 does not require time-based responses. |
Not applicable
(Authored Content) |
AEM 5.6 does not create content that requires timed responses. Authors may create this functionality and can ensure that it meets this requirement. |
