EN 301 549 Report
Notes:
(Based on VPAT® Version 2.4)
This report covers the degree of conformance for the following accessibility standard/guidelines:
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.
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.
1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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”; “Files: Manage Publication” screens.
Decorative image has non-empty alt attribute in the: “Collections: Copy Collection” screen.
Images must have alternate text in the: “Files: Edit” screen.
Sort icon is not described in the : “Files: Annotate screen” screen.
'...' button icon contains role="img" while visually appearing to be decorative in the: “Files: Asset information - Basic tab” screen.
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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: “Assets - Files: Share Link” screen.
Certain ARIA roles do not contain particular children in the: “Select Assets Component - List View” screen.
Checkboxes are not associated with their visible labels in the: “Files: Annotate” screens.
Visible label/form fields are not associated in the: “Collections: Copy Collection”; “Files: Asset information - Advanced tab” screens.
role="presentation" is used incorrectly in the: “Files: Share Link” screen.
Form elements must have labels in the: “Files: Annotate” screen
The Email field is not associated with its visible label in the: “Download Modal” screen.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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” 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 misplaced due to user interaction or content update in the: “Left Navigation” screen.
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Make it easier for users to see and hear content including separating foreground from background.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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 (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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)” screens.
Elements must have sufficient color contrast in the: “Files: Manage Publication”; “Assets - Files: Selected Element with Action Bar (Column View)” screens.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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” screens.
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
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 - Search Results”; ”Select Assets Component - List View”;” Assets - Collections: Copy Collection; Action Bar” screens.
1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
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” screens.
An icon (or part of the icon required to understand its content) does not have a 3:1 color contrast ratio with the adjacent background or adjacent colors in the: “Select Assets Component - Grid View” screen.
The selected state of the reorder button does not have a sufficient contrast ratio: “across multiple pages in the application”.
All the empty text input fields lack 3 to 1 contrast ratio in the: “Files: Asset information - IPTC tab”; “Collections: Properties (Advanced Tab)”; “Files: Asset information - IPTC Extension tab”;” Files: Asset information - Advanced tab” screen.
1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
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.
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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 accesskeys 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 - Files: Asset information - Basic tab”; “Assets - Collections: Download Modal”; “Assets - Collections: Properties (Basic Tab)”; “AEM Assets Rail View”; “Select Assets Component - Informational modal”; “Files: Main Navigation (Card View)”; “Files: Annotate” screens.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Do not design content in a way that is known to cause seizures.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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” screens.
Keyboard focus is lost or misplaced due to user interaction in the: “Left Navigation”; “Select Assets Component - Informational modal”;” Assets - Files: Edit” screens.
Keyboard focus is not maintained in the modal in the: “Select Assets Component - Grid View” screen.
Keyboard focus order is not logical in the: “Assets - Files: Annotate” screen.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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” screens.
Controls have same name but different actions: “Select Assets Component - Grid View” screen.
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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.
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
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” screen.
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 (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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” screens.
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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.
3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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 (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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 - Collections: Copy Collection” screens.
Dialog miss appropriate roles and attribute in the: “Select Assets Component - Informational modal” screens.
State: Expand/collapse state of the element is missing or incorrect in the: “Assets - Files: Edit”; “Action Bar”; “Assets - Files: Annotate”; ”Files: Annotate” screens.
State: Selected state of the element is missing or incorrect in the: “Assets - Collections: Copy Collection”; “Calendar”; “Assets - Files: Annotate”; “Assets - Files: Asset information - Basic tab”; “Assets - Collections: Create Workflow Modal”;” Assets - Files: Main Navigation (Card View)”; ”Files: Main Navigation (Card View)” screens.
Frames does not have an accessible name in the: “AEM Assets Rail View”; “Select Assets Component - Grid View” screens.
Required ARIA attributes must be provided in the: “Files: Filter”; “Collections: Copy Collection”; “Files: Share Link”; “Header” screens.
ARIA attributes must conform to valid values in the: “Files: Edit” screen.
Combo boxes do not have its programmatic state on page load in the:” Assets - Collections: Download Modal” screen.
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
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” screens.
Status message of the successful form submission is not automatically announced: “across multiple pages in the application”.
Notes:
Notes:
Notes: Not Applicable
Notes:
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center
Notes:
Notes:
Notes:
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