AEM Assets Service Pack 15
Accessibility Conformance Report published by Adobe
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% coverage). The remainder are missing from our extraction, not necessarily from Adobe's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
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 — 30 criteria
- Supports
- 15
- Partially supports
- 9
- Does not support
- 2
- Not applicable
- 4
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 12
- Partially supports
- 4
- 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 (67)
| 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: A decorative image is not hidden from screen readers in the: “Assets - Files: Annotate” screen. An active image has a text alternative that does not convey the same purpose as the image in the: “Header” component. Images must have alternate text in the: “Files: Edit; Collections: Copy Collection”; “Files: Annotate” screens. |
| 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 content that is visually presented as multiple lists is not marked up as a list in the: “Header” component. Visible label is not associated to the form field in the: “Files: Asset information - Advanced tab”;” “Files: Asset information - Advanced tab”; “Collections: Download Modal” screens. Form elements must have labels in the: “Files: Annotate; Files: Filter”; “Collections: Copy Collection”;” Files: Asset informati |
| 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: The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content in the: “Assets - Files: Annotate” screen. |
| 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 | Does Not Support | Web: Status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist: Color is used as the only method to convey information “across multiple screens in the application”. The Email field is required but relies on color alone to identify in the: “Collections: Download Modal” screens. Edit field error only identified by color in the: “Files: Share Link” 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 | Does Not Support | Web: Status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist: The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1 in the: “Assets - Files: Annotate”; “Assets - Files: Filter”; “across multiple screens in the application” screens and “Action Bar” component. Text content lacks 4.5:1 contrast ratio in the: “Files: Filter”, “Files: Share Link”; “Collections: Download Modal”; “Collections: Create Workflow Modal”; “Files: Manage Publicati |
| 1.4.4 | Resize text | AA | Supports | Web: Content is readable and functional when browser zoom is set to 200% of its initial size. |
| 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: Horizontal scrolling at 320px width in the: “Files: Asset information - Advanced tab” screen. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: Most of the boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content have a 3:1 color contrast ratio with adjacent color(s) or their background. The following exceptions exist: The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background in the: Action Bar” screen and “Calendar” component. All the empty text input fields lack 3 to 1 contrast ratio in the: “Files: Asset information - IPTC Extension tab”;” Files: Asset information - |
| 1.4.12 | Text Spacing | AA | Supports | Web: The spacing between letters, words, lines of text and paragraphs can be adjusted with no loss of content or functionality. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Web: 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. |
| 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: A function cannot be performed using only the keyboard in the: “Assets - Files: Annotate” screen. Screen reader is unable to expand submenus when checkbox is present in the: “Files: Filter” sc |
| 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 | Supports | Web: Pages have descriptive and informative titles. |
| 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 is lost or misplaced as a result of user interaction or content update or refresh in the: “Assets - Files: Share Link”; “Assets - Collections: Download Modal” screens. Keyboard focus order is not logical in the: “Assets - Files: Annotate”; “Assets - Files: Selected Element with Action Bar (Column View)”; screens and “Header” component. Keyboard focus is not maintained in the modal in the: “Files: Produ |
| 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: Multiple buttons have identical programmatic labels but different functionality in the: “Assets - Collections: Copy Collection” screen. |
| 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 (such as links, buttons, or form inputs) do not have a visual focus indicator in the: “Assets – Collections: Create Workflow Modal”; “Assets - Files: Asset information - Basic tab” screens. The visual focus indicator for an interactive element (such as a link, button, or form input) is not visible in the: “Assets - Collections: Copy Collection” screen. |
| 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 programmatic labels do not contain the visible label in the: “Files: Asset information - Advanced tab”; “Files: Asset information - Advanced tab”; “Files: Asset information - IPTC tab”; “Files: Asset information - IPTC Extension tab” screens. |
| 2.5.4 | Motion Actuation | A | Supports | 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. |
| 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.3.1 | Error Identification | A | Does Not Support | Web: For most form controls where an input error is automatically detected, a text message or alert is not provided that identifies the field/control where the error was detected and describes the error. The following issues exist: The Email field generates an error that is not available in text in the: “Collections: Download Modal”; “Files: Share Link” and “across multiple screens in the application”. |
| 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: Visible label missing in the: “Files: Annotate”; “Files: Filter”;” Files: Share Link” screens. Required field is not identified as required in the: “Collections: Create Workflow Modal”;” Collections: Download Modal” screens. Label, instructions or an error message is not described in the:” Files: Share Link” screen. Label is not persistent in the: |
| 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. |
| 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 particular children in the “Assets - Collections: Properties (Basic Tab)”; "Collections: Properties (Basic Tab)";"Files: Edit" screens. IDs of active elements are duplicate in the “Assets - Files: Asset information - Advanced tab”; “Files: Asset information - Advanced tab” screens. Duplicate ID values are used in the “Assets - Files: Asset info |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Web: The name, role, state, and value of most user interface components can be programmatically determined. The following exceptions exist: Expand/collapse state of the element is missing or incorrect in the: “Assets - Files: Annotate”;” Files: Asset information - Basic tab”;” Files: Annotate”;” Files: Main Navigation (Card View)” screens. Combo box does not have its programmatic state in the: “Files: Asset information - Basic tab” screen. Required ARIA attributes must be provided in the: “Files: Share Link”; “Files: Filter”; “Collections: Properties (Basic Tab)”; “Assets - Files: Filter” scre |
| 4.1.3 | Status Messages | AA | Does Not Support | Web: Status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist: Status message of the successful form submission is not automatically announced: “across multiple screens 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.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.10 Non-Text Contrast 1.4.11 Non-Text Contrast 2.1.1 Keyboard 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 with no or limited 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: 2.1.1 Keyboard 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. 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 Non-Text Contrast 2.1.1 Keyboard 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.1.1 Parsing 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 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 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 discernible 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 May 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.