Adobe Accessibility Conformance Report

(Based on VPAT® Version 2.4)

Product Information

Name of Product/Version: Adobe Assets Cloud
Product Description: 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.
Date: November 2024
Contact information: access@adobe.com
Evaluation Methods Used: 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.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline

Included in Report

Web Content Accessibility Guidelines 2.0

Level A (Yes)
Level AA (Yes)
Level AAA (No)

Web Content Accessibility Guidelines 2.1

Level A (Yes)
Level AA (Yes)
Level AAA (No)

Web Content Accessibility Guidelines 2.2

Level A (Yes)
Level AA (Yes)
Level AAA (No)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018

(Yes)

EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, - V3.1.1 (2019-11)

(Yes)

Terms

The terms used in the Conformance Level information are defined as follows:

Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criterion.
Does Not Support: The majority of product functionality does not meet the criterion.
Not Applicable: The criterion is not relevant to the product.
Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG Level AAA criteria.

WCAG 2.2 Report

The Guideline tables below document conformance with:

EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.

Note: When reporting on conformance with the WCAG 2.2 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.

Guideline 1.1 Text Alternatives:

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)
Also applies to:
EN 301 549 Criteria

9.1.1.1 (Web)
10.1.1.1 (Non-web document)
11.1.1.1.1 (Open Functionality Software)
11.1.1.1.2 (Closed Functionality Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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”; “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”, “Add Assets” screens.

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.

Guideline 1.2 Time-based Media:

Provide alternatives for time-based media.

Criteria

Conformance Level

Remarks and Explanations

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

9.1.2.1 (Web)
10.1.2.1 (Non-web document)
11.1.2.1.1 (Open Functionality Software)
11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: Prerecorded audio-only files are not present.

1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

9.1.2.2 (Web)
10.1.2.2 (Non-web document)
11.1.2.2 (Open Functionality Software)
11.1.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: Prerecorded videos are not present.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

9.1.2.3 (Web)
10.1.2.3 (Non-web document)
11.1.2.3.1 (Open Functionality Software)
11.1.2.3.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: Prerecorded videos are not present, so audio description is not required.

1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria

9.1.2.4 (Web)
10.1.2.4 (Non-web document)
11.1.2.4 (Open Functionality Software)
11.1.2.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Supports (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)
Also applies to:
EN 301 549 Criteria

9.1.2.5 (Web)
10.1.2.5 (Non-web document)
11.1.2.5 (Open Functionality Software)
11.1.2.5 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: Prerecorded multimedia files are not present, so audio descriptions are not required.

Guideline 1.3 Adaptable:

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)
Also applies to:
EN 301 549 Criteria

9.1.3.1 (Web)
10.1.3.1 (Non-web document)
11.1.3.1.1 (Open Functionality Software)
11.1.3.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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:

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.

One or more data cells is incorrectly marked up as a header cell in the: “Add to collection” screen.

A block of text is marked up as a heading but is not a heading in the: “Add Assets”, “Asset Preview” screens.

A block of content has incorrect semantic markup, so its meaning, structure, or relationships is not conveyed to people who are blind and/or use a screen reader. This occurs on the following screen: “Header”

1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria

9.1.3.2 (Web)
10.1.3.2 (Non-web document)
11.1.3.2.1 (Open Functionality Software)
11.1.3.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 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

9.1.3.3 (Web)
10.1.3.3 (Non-web document)
11.1.3.3 (Open Functionality Software)
11.1.3.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.1.3.4 (Web)
10.1.3.4 (Non-web document)
11.1.3.4 (Open Functionality Software)
11.1.3.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.1.3.5 (Web)
10.1.3.5 (Non-web document)
11.1.3.5.1 (Open Functionality Software)
11.1.3.5.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

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.

Guideline 1.4 Distinguishable:

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)
Also applies to:
EN 301 549 Criteria

9.1.4.1 (Web)
10.1.4.1 (Non-web document)
11.1.4.1 (Open Functionality Software)
11.1.4.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 (Level A)
Also applies to:
EN 301 549 Criteria

9.1.4.2 (Web)
10.1.4.2 (Non-web document)
11.1.4.2 (Open Functionality Software)
11.1.4.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.1.4.3 (Web)
10.1.4.3 (Non-web document)
11.1.4.3 (Open Functionality Software)
11.1.4.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 View)” screens.

The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1 in the: “Main Content Hub” screen.

1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria

9.1.4.4 (Web)
10.1.4.4 (Non-web document)
11.1.4.4.1 (Open Functionality Software)
11.1.4.4.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 (Level AA)
Also applies to:
EN 301 549 Criteria

9.1.4.5 (Web)
10.1.4.5 (Non-web document)
11.1.4.5.1 (Open Functionality Software)
11.1.4.5.2 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.1.4.10 (Web)
10.1.4.10 (Non-web document)
11.1.4.10 (Open Functionality Software)
11.1.4.10 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

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:

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”; “Add Assets”, “Add to collection”, “Asset Preview”, “Collections screen inside a collection”, “Header”, “Link Share”, “Main Content Hub” screens.

1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

9.1.4.11 (Web)
10.1.4.11 (Non-web document)
11.1.4.11 (Open Functionality Software)
11.1.4.11 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: 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 with the adjacent background or adjacent colors in the: “Select Assets Component - Grid View”, “Add to collection”, “Main Content Hub” screens.

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.

The focus indicator of an interactive element (like a button or input field) does not have a 3:1 color contrast ratio with the background in the: “Add to collection”, “Asset Preview”, “Collections screen inside a collection”, “Main Content Hub” screens.

The indicator for the state of an interactive element (like a checkbox or radio button) does not have a 3:1 color contrast ratio with the background in the: “Asset Preview”, “Link Share” screens.

1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

9.1.4.12 (Web)
10.1.4.12 (Non-web document)
11.1.4.12 (Open Functionality Software)
11.1.4.12 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: 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 (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

9.1.4.13 (Web)
10.1.4.13 (Non-web document)
11.1.4.13 (Open Functionality Software)
11.1.4.13 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: 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.

Guideline 2.1 Keyboard Accessible:

Make all functionality available from a keyboard.

Criteria

Conformance Level

Remarks and Explanations

2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria

9.2.1.1 (Web)
10.2.1.1 (Non-web document)
11.2.1.1.1 (Open Functionality Software)
11.2.1.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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:

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”, “Asset Preview” screens.

2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria

9.2.1.2 (Web)
10.2.1.2 (Non-web document)
11.2.1.2 (Open Functionality Software)
11.2.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.2.1.4 (Web)
10.2.1.4 (Non-web document)
11.2.1.4.1 (Open Functionality Software)
11.2.1.4.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

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.

Guideline 2.2 Enough Time:

Provide users enough time to read and use content.

Criteria

Conformance Level

Remarks and Explanations

2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria

9.2.2.1 (Web)
10.2.2.1 (Non-web document)
11.2.2.1 (Open Functionality Software)
11.2.2.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.2.2.2 (Web)
10.2.2.2 (Non-web document)
11.2.2.2 (Open Functionality Software)
11.2.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Supports

Web: Moving, blinking, scrolling, or auto-updating information can be paused, stopped, hidden, or otherwise controlled by the user.

Guideline 2.3 Seizures:

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)
Also applies to:
EN 301 549 Criteria

9.2.3.1 (Web)
10.2.3.1 (Non-web document)
11.2.3.1 (Open Functionality Software)
11.2.3.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Not Applicable

Web: The tested application does not contain flashing content.

Guideline 2.4 Navigable:

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)
Also applies to:
EN 301 549 Criteria

9.2.4.1 (Web)
10.2.4.1 (Non-web document) – Does not apply
11.2.4.1 (Open Functionality Software) – Does not apply
11.2.4.1 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

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)
Also applies to:
EN 301 549 Criteria

9.2.4.2 (Web)
10.2.4.2 (Non-web document)
11.2.4.2 (Open Functionality Software) - Does not apply
11.2.4.2 (Closed Software) - Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 (Level A)
Also applies to:
EN 301 549 Criteria

9.2.4.3 (Web)
10.2.4.3 (Non-web document)
11.2.4.3 (Open Functionality Software)
11.2.4.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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:

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 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

9.2.4.4 (Web)
10.2.4.4 (Non-web document)
11.2.4.4 (Open Functionality Software)
11.2.4.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.2.4.5 (Web)
10.2.4.5 (Non-web document) – Does not apply
11.2.4.5 (Open Functionality Software) – Does not apply
11.2.4.5 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Web: Multiple ways are available to find other pages on the site.

2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria

9.2.4.6 (Web)
10.2.4.6 (Non-web document)
11.2.4.6 (Open Functionality Software)
11.2.4.6 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 (Level AA)
Also applies to:
EN 301 549 Criteria

9.2.4.7 (Web)
10.2.4.7 (Non-web document)
11.2.4.7 (Open Functionality Software)
11.2.4.7 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply

Web: Supports

Web: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

Guideline 2.5 Input Modalities:

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)
Also applies to:
EN 301 549 Criteria

9.2.5.1 (Web)
10.2.5.1 (Non-web document)
11.2.5.1 (Open Functionality Software)
11.2.5.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.2.5.2 (Web)
10.2.5.2 (Non-web document)
11.2.5.2 (Open Functionality Software)
11.2.5.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

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.

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 (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

9.2.5.3 (Web)
10.2.5.3 (Non-web document)
11.2.5.3.1 (Open Functionality Software)
11.2.5.3.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

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:

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 (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

9.2.5.4 (Web)
10.2.5.4 (Non-web document)
11.2.5.4 (Open Functionality Software)
11.2.5.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports (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 (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply

Web: 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) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply

Web: 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.

Guideline 3.1 Readable:

Make text content readable and understandable.

Criteria

Conformance Level

Remarks and Explanations

3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria

9.3.1.1 (Web)
10.3.1.1 (Non-web document)
11.3.1.1.1 (Open Functionality Software)
11.3.1.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: Supports

Web: The language of each page is correct and can be determined programmatically.

3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria

9.3.1.2 (Web)
10.3.1.2 (Non-web document)
11.3.1.2 (Open Functionality Software) – Does not apply
11.3.1.2 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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.

Guideline 3.2 Predictable:

Make Web pages appear and operate in predictable ways.

Criteria

Conformance Level

Remarks and Explanations

3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria

9.3.2.1 (Web)
10.3.2.1 (Non-web document)
11.3.2.1 (Open Functionality Software)
11.3.2.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.3.2.2 (Web)
10.3.2.2 (Non-web document)
11.3.2.2 (Open Functionality Software)
11.3.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.3.2.3 (Web)
10.3.2.3 (Non-web document) – Does not apply
11.3.2.3 (Open Functionality Software) – Does not apply
11.3.2.3 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

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)
Also applies to:
EN 301 549 Criteria

9.3.2.4 (Web)
10.3.2.4 (Non-web document) – Does not apply
11.3.2.4 (Open Functionality Software) – Does not apply
11.3.2.4 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs

Web: 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 (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply

Web: 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.

Guideline 3.3 Input Assistance:

Help users avoid and correct mistakes.

Criteria

Conformance Level

Remarks and Explanations

3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria

9.3.3.1 (Web)
10.3.3.1 (Non-web document)
11.3.3.1.1 (Open Functionality Software)
11.3.3.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 (Level A)
Also applies to:
EN 301 549 Criteria

9.3.3.2 (Web)
10.3.3.2 (Non-web document)
11.3.3.2 (Open Functionality Software)
11.3.3.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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:

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 missing, so the field's purpose is not clear in the: “Add to collection” screen.

3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria

9.3.3.3 (Web)
10.3.3.3 (Non-web document)
11.3.3.3 (Open Functionality Software)
11.3.3.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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)
Also applies to:
EN 301 549 Criteria

9.3.3.4 (Web)
10.3.3.4 (Non-web document)
11.3.3.4 (Open Functionality Software)
11.3.3.4 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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.

3.3.7 Redundant Entry (Level A 2.2 only)

EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply

Web: 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) (Level A 2.2 only)

EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply

Web: 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.

Guideline 4.1 Compatible:

Maximize compatibility with current and future user agents, including assistive technologies.

Criteria

Conformance Level

Remarks and Explanations

4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria

9.4.1.1 (Web)
10.4.1.1 (Non-web document)
11.4.1.1.1 (Open Functionality Software)
11.4.1.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

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:

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

9.4.1.2 (Web)
10.4.1.2 (Non-web document)
11.4.1.2.1 (Open Functionality Software)
11.4.1.2.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)

Web: 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 - Collections: Copy Collection”; “Main Content Hub” screens.

Dialog miss appropriate roles and attribute in the: “Select Assets Component - Informational modal”; “Add Assets”, “Add to collection”, “Asset Preview”, “Link Share” 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)”; “Asset Preview”; “Main Content Hub” screens.

Frames does not have an accessible name in the: “AEM Assets Rail View”; “Select Assets Component - Grid View”; “Add Assets” 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.

An element that appears and functions like a grid (similar to a data table) does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology in the: “Main Content Hub” screen.

An element is missing or has an incorrect programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of the element and may not understand its purpose or content or how to interact with it: “Header” screen.

The content of a tooltip cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content in the: “Asset Preview” screen.

A button does not have a programmatic name, so its name is not conveyed to screen readers in the: “Header” screen.

A button does not have a programmatic role, so its role (usually button, but sometimes link or something else) is not conveyed to screen readers in the: “Asset Preview” screen.

4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

9.4.1.3 (Web)
10.4.1.3 (Non-web document)
11.4.1.3 (Open Functionality Software)
11.4.1.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: 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”.

Revised Section 508 Report

Notes:

Chapter 3: Functional Performance Criteria (FPC)

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:

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

302.2 With Limited Vision

Web: 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

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

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

1.4.3 Contrast (minimum)

3.3.1 Error Identification

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:

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

4.1.1 Parsing

4.1.2 Name, Role, Value

302.8 With Limited Reach and Strength

Web: Supports

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:

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

2.4.7 Focus Visible

3.3.1 Error Identification

3.3.2 Labels or Instructions

4.1.1 Parsing

4.1.2 Name, Role, Value

Chapter 4: Hardware

Notes: Not Applicable

Chapter 5: Software

Notes: Not Applicable

Chapter 6: Support Documentation and Services

Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.

EN 301 549 Report

Notes:

Chapter 4: Functional Performance Statements (FPS)

Notes:

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:

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

Web: 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

Web: 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

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 without 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:

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

Web: 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

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

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.1.1 Parsing

4.1.2 Name, Role, Value

4.1.3 Status Messages

4.2.11 Privacy

Web: Supports (Not Applicable)

Web: The product does not provide any privacy features.

Chapter 5: Generic Requirements

Notes:

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

Not Applicable

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 1.3.1 Info and Relationships, 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value.

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 discernable 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