Adobe Experience Manager (AEM) Cloud Service Assets
Accessibility Conformance Report published by Adobe
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 32 criteria
- Supports
- 15
- Partially supports
- 11
- Does not support
- 1
- Not applicable
- 5
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 13
- Partially supports
- 7
- Does not support
- 2
- Not applicable
- 2
- Not evaluated
- 0
Source: View the original report published by Adobe.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (73)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Web: Most non-text content has text alternatives or a text alternate that serves an equivalent purpose. The following exceptions exist: The decorative images are not hidden from the screen reader in the “Assets - Collections: Copy Collection”; “Assets - Files: Share Link”; “Assets - Files: Asset information - Basic tab; Header”; “Collections: Properties (Basic Tab)” screens. An active image has a text alternative that does not convey the same purpose as the image in the. “Assets - Files: Annotate” screen. [role='img'] elements have an alternative text in the: “Files: Filter”; “Files: Annotate” |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Web: Prerecorded audio-only files are not present. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Web: Prerecorded videos are not present. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Web: Prerecorded videos are not present, so audio description is not required. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: Live multimedia files with audio are not present, so synchronized captions are not required. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Web: Prerecorded multimedia files are not present, so audio descriptions are not required. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Web: Most information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. The following exceptions exist: Some heading levels are out of order in the: “Select Assets Component - Informational modal”; “Select Assets Component - Search Results” screens. Some text that visually functions as a heading is not marked up as a heading in the: “AEM Assets Rail View”; “Assets - Collections: Copy Collection” screens. Data is arranged visually like a data table, but the programmatic table header markup is missing or incomplete in the: “A |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The reading and navigation order of most content is logical and intuitive. The following exceptions exist: Visually hidden content is announced by a screen reader in the: “Select Assets Component - Search Results”; “Files: Annotate”; and “Assets - Collections: Copy Collection”, “Main Content Hub” screens. The reading order of static content changes the meaning of that content in the: “Assets - Files: Annotate” screen. Informative (static) content is not readable by a screen reader in the: “Action Bar; Assets - Files: Assets Main Page (Column View)” screen. Screen reader focus is lost or m |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions to operate and/or understand content do not rely on sensory characteristics of components such as shape, color, size, visual location. |
| 1.3.4 | Orientation | AA | Supports | Web: Orientation of the content is not locked to either landscape or portrait unless a specific orientation is essential for the functionality. |
| 1.3.5 | Identify Input Purpose | AA | Supports | Web: The purpose for each input field that collects an individual's personal data is programmatically defined based on the WCAG list of Input Purposes for User Interface Components. |
| 1.4.1 | Use of Color | A | Partially Supports | Web: For most content, color is not used as the only method to convey information, indicate an action, prompt a response, or distinguish visual elements. The following exceptions exist: Color clone is used to identify the form field error in the: Collections: Download Modal screen. |
| 1.4.2 | Audio Control | A | Supports | Web: A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays for more than 3 seconds. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text and images of regular text have the required color contrast ratio with their backgrounds. The following exceptions exist: The color contrast ratio between text and its background is less than 4.5:1 in the: “Assets - Collections: Copy Collection”; “Action Bar; Assets - Files: Asset information - Basic tab”; “Assets - Collections: Properties (Basic Tab)”; “Assets - Files: Assets Main Page (Column View)”, “Header”, “Main Content Hub” screens. Elements must have sufficient color contrast in the: “Files: Manage Publication”; “Assets - Files: Selected Element with Action Bar (Column V |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Most content is readable and functional when browser zoom is set to 200% of its initial size. The following exceptions exist: Content is lost, clipped, or obscured when the page is zoomed to 200%, in the: “Select Assets Component - List View”; “Select Assets Component - Search Results”; “Assets - Files: Edit”; “Assets - Files: Annotate”, “Asset Preview” screens. Functionality is lost when the page is zoomed to 200% in the: “Add to collection”, “Collections screen inside a collection”, “Main Content Hub” screens. |
| 1.4.5 | Images of Text | AA | Supports | Web: When content can be presented visually using only text, an image of text is not used to present that text. |
| 1.4.10 | Reflow | AA | Partially Supports | Web: The content of most pages is viewable without scrolling horizontally when the viewport is set to 320 CSS pixels wide. The following exceptions exist: Some page content does not reflow to fit horizontally when the page width is changed to 320 CSS pixels in the: “Assets - Collections: Copy Collection”; “Action Bar”; “Files: Asset information - Advanced tab”; “Files: Asset information - IPTC tab”; “Files: Asset information - IPTC Extension tab” screens. Some part of the page content is lost and overlaps when the page width is changed to 320 CSS pixels in the: “Select Assets Component - Searc |
| 1.4.11 | Non-text Contrast | AA | Does Not Support | Web: Most, if not all, boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content do not have a 3:1 color contrast ratio with adjacent color(s) or their background. The following issues exist: The visual boundary of an interactive element does not have a 3:1 color contrast ratio with the adjacent background in the: “AEM Assets Rail View”; “AEM Assets Rail View”; “Calendar”; “Add to collection screen”, “Header” screens. An icon (or part of the icon required to understand its content) does not have a 3:1 color contrast ratio wit |
| 1.4.12 | Text Spacing | AA | Partially Supports | Web: Most functions of the product support the required text style properties without loss of content or functionality. The following exceptions exist When text spacing is adjusted some content cannot be seen because it is cut off in the: "Link Share" screen. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: In most cases when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. The following exceptions exist: Additional content that becomes available on hover, does not allow the user to move the mouse pointer over that same additional content without the additional content disappearing in the: “Header” component. |
| 2.1.1 | Keyboard | A | Partially Supports | Web: On most pages, all functionality is available using only the keyboard (unless that functionality cannot be accomplished in any known way using a keyboard). If shortcut keys and access keys present, some may conflict with existing browser and screen reader shortcuts, and some functionality based on custom gestures may not be available when a screen reader is turned on. The following exceptions exist: Multiple functions cannot be performed using only the keyboard in the: “AEM Assets Rail View”; “Assets - Files: Edit”; “Action Bar; Assets – Files”: “Filter; Assets - Files: Annotate”; “Assets |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: Keyboard focus is never locked or trapped in a particular area, and the user is able to navigate to and from all navigable elements using only a keyboard. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Web: If a single character key shortcut exists, then the single character key shortcut can be turned off or remapped, or it is only active when the relevant user interface component is in focus. |
| 2.2.1 | Timing Adjustable | A | Supports | Web: If a time limit exists, the user is given options to turn off, adjust, or extend that time limit. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Web: Moving, blinking, scrolling, or auto-updating information can be paused, stopped, hidden, or otherwise controlled by the user. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Web: The tested application does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Supports | Web: A method is provided to skip navigation and other page elements that are repeated across web pages. |
| 2.4.2 | Page Titled | A | Partially Supports | Web: Most pages have descriptive and informative titles. The following exceptions exist: Page TITLE element does not identify purpose of page in the: “Collections screen inside a collection” screen. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: The navigation order of most interactive elements (such as links, buttons, or form elements) is logical and preserves meaning and operability. The following exceptions exist: Keyboard focus an element that is hidden or empty in the: “Select Assets Component - List View”;” Files: Filter”, “Main Content Hub” screens. Keyboard focus is lost or misplaced due to user interaction in the: “Left Navigation”; “Select Assets Component - Informational modal”; “Assets - Files: Edit”, “Add to collection” screens. Keyboard focus is not maintained in the modal in the: “Select Assets Component - Grid Vie |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Web: The purpose of the link(s) can be determined from the link text alone or from the link text and its programmatic context. |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Multiple ways are available to find other pages on the site. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most headings and labels for form and interactive controls are informative. The following exceptions exist: Interactive control Programmatic label does not convey purpose of control in the: “AEM Assets Rail View”; “Left Navigation”, “Main Content Hub” screens. Controls have same name but different actions in the: “Select Assets Component - Grid View”; “Add to collection”, “Collections screen inside a collection”, “Link Share”, “Main Content Hub” screens. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: In most cases, it is visually apparent which page element is currently receiving keyboard focus. The following issues exist: Multiple interactive elements do not have a visual focus indicator in the: “Select Assets Component - Grid View”; “Calendar” screen. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | Web: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: All functionality that can be operated with a pointer can be operated with single-point actions. |
| 2.5.2 | Pointer Cancellation | A | Supports | Web: For functionality that can be operated using a single pointer, at least one of the following is true: The action is not triggered on the down event. The action triggers on the up event, and a mechanism is available to abort the function before completion or to undo the function after completion. The up-event reverses any outcome of the preceding down-event. Completing the function on the down-event is essential. |
| 2.5.3 | Label in Name | A | Partially Supports | Web: For most user interface components that include visible text labels, the accessible name matches (or includes) the visible text in the label. The following exceptions exist: The accessible name of an interactive element does not contain the visible label in the: “Select Assets Component - Grid View”, “Main Content Hub” screens. The programmatic labels do not contain the visible label in the: “Files: Asset information - IPTC tab”; “Files: Asset information - IPTC Extension tab”; “Files: Asset information - Advanced tab” screens. |
| 2.5.4 | Motion Actuation | A | Not Applicable | Web: Functionality that can be triggered by device motion or user motion detected by a device can be disabled, and the functionality can be operated without using motion. |
| 2.5.7 | Dragging Movements | AA | Supports | Web: All functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | Web: The size of the target for each clickable control is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. |
| 3.1.1 | Language of Page | A | Supports | Web: The language of each page is correct and can be determined programmatically. |
| 3.1.2 | Language of Parts | AA | Supports | Web: The language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. |
| 3.2.1 | On Focus | A | Supports | Web: When an element receives focus, a change in context (such as a substantial change to the page, the spawning of a pop-up window, or a change in focus) that may disorient the user does not occur. |
| 3.2.2 | On Input | A | Supports | Web: When a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user unless the user is informed about the change ahead of time. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: Navigation patterns that are repeated on web pages are presented in the same relative order each time they appear and do not change order when navigating through the site. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Labels, names, and text alternatives for content that have the same functionality across multiple web pages are consistently identified. |
| 3.2.6 | Consistent Help | A | Supports | Web: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order. |
| 3.3.1 | Error Identification | A | Partially Supports | Web: For most form controls where an input error is automatically detected, a text message or alert is provided that identifies the field/control where the error was detected and describes the error. The following exceptions exist: Input validation failures are not described in text or a text alternative in the: “Files: Manage Publication”; “Files: Share Link”; “Add Assets” screens. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: For most form controls/input fields requiring user input, labels, instructions, and/or error messages are provided to identify the controls/input fields in the form so that users know what input data is expected. The following exceptions exist: The Search edit field is required but relies on color alone to identify in the: “Files: Share Link”;” Collections: Create Workflow Modal” screens. The Email field is required but this is not identified in the: “Download Modal” screen. Label is not persistent in the: “Create Workflow Modal”;” Files: Share Link” screen. The label for a form field is |
| 3.3.3 | Error Suggestion | AA | Supports | Web: If input errors are automatically detected, suggestions are provided in text for correcting the input in a timely and accessible manner before the data is submitted to the server. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Web: If the user can change or delete legal transactions, financial transactions, student exam responses, or data transactions that are unrecoverable or unintentionally modify or delete data, the changes and/or deletions are reversible, verified, or confirmed. |
| 3.3.7 | Redundant Entry | A | Supports | Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the Web site. |
| 4.1.1 | Parsing | A | Partially Supports | Web: In most product functions, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. Exceptions include: Certain ARIA roles do not contain needed child roles in the: “Assets - Files: Asset information - Advanced tab”; “Files: Asset information - Advanced tab”; “Files: Asset information - IPTC tab” screens. Interactive controls are nested in the: “Assets - Files: Filter” screen. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Web: The name, role, state, and/or value of most, if not all, user interface components cannot be programmatically determined. The following issues exist: Multiple buttons do not have a programmatic name and role in the: “Filters; Action Bar”; “Select Assets Component - Grid View”; “Select Assets Component - List View”; “Files: Edit”; “Assets - Files: Selected Element with Action Bar (Column View)”; “Assets - Files: Asset information - Advanced tab” screens. Multiple elements that appear and function like a combo box do not have the required attributes in the: “Assets - Files: Edit”; “Assets - |
| 4.1.3 | Status Messages | AA | Does Not Support | Web: Most, if not all, status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist: Some status messages are not automatically announced by the screen reader in the: “Filters”;” Select Assets Component - Grid View”; “Select Assets Component - Search Results”; “Assets - Collections: Copy Collection”; “Add to collection”, “Header” screens. Status message of the successful form submission is not automatically announced: “across multiple pages in the application”. |
| 4.2.1 | Usage without vision | - | Partially Supports | Web: Most functionality is usable without vision. Exceptions are noted in: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 3.3.1 Error Identification 4.1.1 Parsing 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most functionality is usable with limited vision. Exceptions are noted in: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.4 Resize Text 1.4.10 Reflow 1.4.11 Non-Text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 2.4.7 Focus Visible 3.3.1 Error Identification 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most functionality is usable without perception of color. Exceptions are noted in: 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.11 Non-Text Contrast 3.3.1 Error Identification |
| 4.2.4 | Usage without hearing | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.6 | Usage without vocal capability | - | Not Applicable | Web: The product does not require the use of speech or other vocal output. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Web: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions are noted in: 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.5.3 Label in Name 4.1.1 Parsing 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Web: All functionality is usable by people with limited reach. 1.4.13 Content on Hover or Focus 2.5.3 Label in Name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Web: All functionality may be operated in a mode that minimizes the potential for triggering photosensitive seizures. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions are noted in: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.10 Reflow 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.5.3 Label in Name 3.3.1 Error Identification 3.3.2 Labels or Instructions |
| 4.2.11 | Privacy | - | Not Applicable | Web: The product does not provide any privacy features. |
| 5.1.4 | Functionality closed to text enlargement | - | Not Applicable | The product does not have closed functionality. |
| 5.1.5 | Visual output for auditory information | - | Not Applicable | The product does not have closed functionality. |
| 5.5.1 | Means of operation | - | Not Applicable | The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate. |
| 5.5.2 | Operable parts discernibility | - | Partially Supports | The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions are noted in 1.3.1 Info and Relationships , 2.4.6 Headings and Labels , and 4.1.2 Name, Role, Value. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | Tactile or auditory status is not included in the product. |
| 5.6.2 | Visual status | - | Supports | Visual status of controls is discernable in the product. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated November 2024. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.