Adobe Accessibility Conformance Report
International Edition
(Based on VPAT® Version 2.4)
(Based on VPAT® Version 2.4)
Standard/Guideline |
Included in Report |
---|---|
Level A (Yes) |
|
Level A (Yes) |
|
(Yes) |
|
(Yes) |
The terms used in the Conformance Level information are defined as follows:
Tables 1 and 2 also document conformance with:
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.
AEM Assets Service Pack 15
May 2024
Adobe Experience Manager Assets is a digital asset management system that allows users to create, manage, and deliver assets with blazing speed – all from a single platform for marketing, creative, and business teams.
Product testing involved use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
This report covers the degree of conformance for the following accessibility standard/guidelines:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Most non-text content has text alternatives or a text alternate that serves an equivalent purpose. The following exceptions exist:
|
Provide alternatives for time-based media.
Web: Supports (Not Applicable)
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Revised Section 508
|
Web: Not Applicable |
Web: Prerecorded audio-only files are not present. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Web: Not Applicable |
Web: Prerecorded videos are not present. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Web: Not Applicable |
Web: Prerecorded videos are not present, so audio description is not required. |
1.2.4 Captions (Live) (Level AA)
Revised Section 508
|
Web: Not Applicable |
Web: Live multimedia files with audio are not present, so synchronized captions are not required. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Web: Not Applicable |
Web: Prerecorded multimedia files are not present, so audio descriptions are not required. |
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.3.1 Info and Relationships (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Most information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. The following exceptions exist:
|
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: The reading and navigation order of most content is logical and intuitive. The following exceptions exist:
|
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Web: 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 (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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 (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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. |
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.1 Use of Color (Level A)
Revised Section 508
|
Web: Does Not Support |
Web: Status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist:
|
1.4.2 Audio Control (Level A)
Revised Section 508
|
Web: 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) (Level AA)
Revised Section 508
|
Web: Does Not support |
Web: Status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist:
|
1.4.4 Resize text (Level AA)
Revised Section 508
|
Web: Supports |
Web: Content is readable and functional when browser zoom is set to 200% of its initial size. |
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Web: 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 (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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:
|
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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:
|
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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 (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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. |
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A)
Revised Section 508
|
Web: 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:
|
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Web: 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 (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: 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. |
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.2.1 Timing Adjustable (Level A)
Revised Section 508
|
Web: 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 (Level A)
Revised Section 508
|
Web: Supports |
Web: Moving, blinking, scrolling, or auto-updating information can be paused, stopped, hidden, or otherwise controlled by the user. |
Do not design content in a way that is known to cause seizures.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.3.1 Three Flashes or Below Threshold (Level A)
Revised Section 508
|
Web: Not Applicable |
Web: The tested application does not contain flashing content. |
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.4.1 Bypass Blocks (Level A)
Revised Section 508
|
Web: Supports |
Web: A method is provided to skip navigation and other page elements that are repeated across web pages. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Web: Supports |
Web: Pages have descriptive and informative titles. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Web: 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:
|
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Web: 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 (Level AA)
Revised Section 508
|
Web: Supports |
Web: Multiple ways are available to find other pages on the site. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most headings and labels for form and interactive controls are informative. The following exceptions exist:
|
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: In most cases, it is visually apparent which page element is currently receiving keyboard focus. The following issues exist:
|
Make it easier for users to operate functionality through various inputs beyond keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.5.1 Pointer Gestures (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: All functionality that can be operated with a pointer can be operated with single-point actions. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: 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. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: 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:
|
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: 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. |
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A)
Revised Section 508
|
Web: Supports |
Web: The language of each page is correct and can be determined programmatically. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Web: 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. |
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.2.1 On Focus (Level A)
Revised Section 508
|
Web: 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 (Level A)
Revised Section 508
|
Web: 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 (Level AA)
Revised Section 508
|
Web: 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 (Level AA)
Revised Section 508
|
Web: Supports |
Web: Labels, names, and text alternatives for content that have the same functionality across multiple web pages are consistently identified. |
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A)
Revised Section 508
|
Web: 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:
|
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Web: 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:
|
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Web: 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) (Level AA)
Revised Section 508
|
Web: 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. |
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.1.1 Parsing (Level A)
Revised Section 508
|
Web: 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:
|
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: The name, role, state, and value of most user interface components can be programmatically determined. The following exceptions exist:
|
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Does Not Support |
Web: Status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. The following issues exist:
|
Notes: Not Applicable
Notes:
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
302.1 Without Vision |
Web: Partially Supports |
Web: Most functionality is usable without vision. Exceptions are noted in: |
302.2 With Limited Vision |
Web: Partially Supports |
Web: Most functionality is usable with limited vision. Exceptions are noted in: |
302.3 Without Perception of Color |
Web: Partially Supports |
Web: Most functionality is usable without perception of color. Exceptions are noted in: 1.4.1 Use of Color |
302.4 Without Hearing |
Web: Supports (Not Applicable) |
Web: The product does not require the use of hearing. |
302.5 With Limited Hearing |
Web: Supports (Not Applicable) |
Web: The product does not require the use of hearing. |
302.6 Without Speech |
Web: Supports (Not Applicable) |
Web: The product does not require the use of speech. |
302.7 With Limited Manipulation |
Web: Partially Supports |
Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions are noted in: |
302.8 With Limited Reach and Strength |
Web: Supports (Not Applicable) |
Web: All functionality is usable with limited reach and strength. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Web: 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: |
Notes: Not Applicable
Notes: Not Applicable
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Web: Partially Supports |
Web: Most functionality is usable without vision. Exceptions are noted in: |
4.2.2 Usage with limited vision |
Web: Partially Supports |
Web: Most functionality is usable with limited vision. Exceptions are noted in: |
4.2.3 Usage without perception of colour |
Web: Partially Supports |
Web: Most functionality is usable without perception of color. Exceptions are noted in: |
4.2.4 Usage without hearing |
Web: Supports (Not Applicable) |
Web: The product does not require the use of hearing. |
4.2.5 Usage with limited hearing |
Web: Supports (Not Applicable) |
Web: The product does not require the use of hearing. |
4.2.6 Usage with no or limited vocal capability |
Web: Supports (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 |
Web: 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: |
4.2.8 Usage with limited reach |
Web: Partially Supports |
Web: All functionality is usable by people with limited reach. |
4.2.9 Minimize photosensitive seizure triggers |
Web: Supports (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 |
Web: 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 |
4.2.11 Privacy |
Web: Supports (Not Applicable) |
Web: The product does not provide any privacy features. |
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed functionality |
|
|
5.1.2 General |
|
|
5.1.2.1 Closed functionality |
See 5.2 through 13 |
See information in 5.2 through 13 |
5.1.2.2 Assistive technology |
See 5.1.3 through 5.1.6 |
See information in 5.1.3 through 5.1.6 |
5.1.3 Non-visual access |
||
5.1.3.1 Audio output of visual information |
Not Applicable |
The product does not have closed functionality. |
5.1.3.2 Auditory output delivery including speech |
Not Applicable |
The product does not have closed functionality. |
5.1.3.3 Auditory output correlation |
Not Applicable |
The product does not have closed functionality. |
5.1.3.4 Speech output user control |
Not Applicable |
The product does not have closed functionality. |
5.1.3.5 Speech output automatic interruption |
Not Applicable |
The product does not have closed functionality. |
5.1.3.6 Speech output for non-text content |
Not Applicable |
The product does not have closed functionality. |
5.1.3.7 Speech output for video information |
Not Applicable |
The product does not have closed functionality. |
5.1.3.8 Masked entry |
Not Applicable |
The product does not have closed functionality. |
5.1.3.9 Private access to personal data |
Not Applicable |
The product does not have closed functionality. |
5.1.3.10 Non-interfering audio output |
Not Applicable |
The product does not have closed functionality. |
5.1.3.11 Private listening volume |
Not Applicable |
The product does not have closed functionality. |
5.1.3.12 Speaker volume |
Not Applicable |
The product does not have closed functionality. |
5.1.3.13 Volume reset |
Not Applicable |
The product does not have closed functionality. |
5.1.3.14 Spoken languages |
Not Applicable |
The product does not have closed functionality. |
5.1.3.15 Non-visual error identification |
Not Applicable |
The product does not have closed functionality. |
5.1.3.16 Receipts, tickets, and transactional outputs |
Not Applicable |
The product does not have closed functionality. |
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.1.6 Operation without keyboard interface |
||
5.1.6.1 Closed functionality |
See 5.1.3.1 through 5.1.3.16 |
See information in 5.1.3.1 through 5.1.3.16 |
5.1.6.2 Input focus |
Not Applicable |
The product does not have closed functionality. |
5.2 Activation of accessibility features |
Supports |
The product does have specific documented accessibility features and allows preferences to be set for accessibility. |
5.3 Biometrics |
Not Applicable |
Biometrics is not included in the product. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
The product does not convert content. |
5.5 Operable parts |
||
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: |
5.6 Locking or toggle controls |
||
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. |
5.7 Key repeat |
Not Applicable |
Key repeat functionality is not found in the product. |
5.8 Double-strike key acceptance |
Not Applicable |
Double-strike key acceptance is not found in the product. |
5.9 Simultaneous user actions |
Not Applicable |
The product does not require simultaneous user actions to achieve any functionality. |
Notes:
Notes:
Notes: Not Applicable
Notes: See WCAG 2.1 section
Notes: Not Applicable
Notes: Not Applicable
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.
Notes: Not Applicable