Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
- Name of Product/Version: Adobe Exchange Marketplace
- Product Description: A marketplace where plugins, integrations and apps are listed to enhance Adobe creative cloud and experience cloud products
- Date: July 10, 2026
- Contact information: access@adobe.com
- Notes: The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html
- Evaluation Methods Used: Testing Adobe Exchange Marketplace involved extensive use of leading assistive technology such as screen readers, screen magnifiers, and speech recognition software, as well exclusive 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 standards/guidelines:
Level AA (Yes)
Level AAA (No)
Level AA (Yes)
Level AAA (No)
Level AA (Yes)
Level AAA (No)
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 2.2 Level AAA.
WCAG 2.2 Report
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Chapter 10 - Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 - Non-Web Software (closed functionality).
- 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.
Table 1: Success Criteria, Level A
Notes:
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.
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)
Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: Purchase Modal; Report Abuse Modal; Manage Creative Cloud Plugins; Configuration; Application Details.
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
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)
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)
Captions are not provided for media that includes audio and video, so the information provided by the audio track is not available to people who are deaf or hard of hearing. This occurs in the following component: Video Player.
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)
Pre-recorded multimedia content with synchronized video and audio content has no text transcript or audio description track, so the visual content presented is not available to people who are blind or have low vision. This occurs on the following components: YouTube Player; Video Player.
Guideline 1.3 Adaptable:
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
- 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)
Some text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs in the following component: Header and following pages: Purchase Modal; Order Details and Post Acquisition; Creative Cloud Browse; Application Details; Home Page; Creative Cloud Product Details.
One or more data cells is incorrectly marked up as a header cell in a table, so the table structure and the header/data relationship between the cell(s) and other cells in the table will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following page: Configuration.
Some blocks of text are marked up as headings but are not headings, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Deployment Log; Configuration; Creative Cloud Browse.
Content that does not visually function as a list is marked up as a list, so the structure of the page is misrepresented to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Creative Cloud Product Details.
Data is arranged visually like a complex data table with multiple rows of column headers and/or columns of row headers, but there is no programmatic markup to associate the headers with any data. People who are blind and/or use a screen reader will not be aware of the association between the table headers and their related data. This occurs on the following page: Deployment Log.
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)
The screen reader skips and does not announce informative static content (text or images), so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following page: Purchase Modal.
Screen reader focus is lost or misplaced due to user interaction or content update, making navigation difficult or impossible for people who are blind and/or use a screen reader or other assistive technology. This occurs in the following component: Header.
Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs in the following component: YouTube Player and following page: Purchase Modal.
Screen readers can read content outside the modal dialog, so people who are blind and/or use a screen reader may become disoriented or confused. This occurs on the following page: Purchase Modal.
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)
Guideline 1.4 Distinguishable:
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
- 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)
Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of a control, so that information will not be available to people who are color blind and people who are blind and/or use a screen reader. This occurs on the following page: Order Details and Post Acquisition.
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)
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
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)
Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs in the following component: YouTube Player and following pages: Order Details and Post Acquisition; Purchase Modal.
People who use the keyboard to navigate and operate content cannot dismiss or close a modal without submitting data. This occurs in the following component: YouTube Player.
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)
2.1.4 Character Key Shortcuts (WCAG 2.1)
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
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
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)
Some content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs in the following component: Video Player.
Timed Toast content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs in the following component: YouTube Player and following pages: Creative Cloud Product Details; Deployment Log.
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)
The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following page: Purchase Modal.
Guideline 2.3 Seizures:
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
- 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)
Guideline 2.4 Navigable:
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
- 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
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)
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)
Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs in the following component: Header.
Keyboard focus or touch screen swiping goes to multiple elements that are hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs in the following component: YouTube Player.
When a modal closes, keyboard focus is not returned to the control that opened the modal or to another logical location, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following page: Purchase Modal.
Keyboard focus is not confined within multiple modals, so people who use the keyboard to navigate content (including screen reader users) will be able to navigate outside of the modal, which may cause them to become disoriented. This occurs in the following component: YouTube Player and following pages: Purchase Modal; Order Details and Post Acquisition.
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)
The purpose of multiple links is not made clear by each link's text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where each link goes. This occurs in the following component: YouTube Player and following page: Creative Cloud Browse.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
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
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
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
2.5.3 Label in Name (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.3 (Web)
- 10.2.5.3 (Non-web document)
- 11.2.5.3 (Open Functionality Software)
- 11.2.5.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs in the following component: Header and following pages: Creative Cloud Product Details; Home Page.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
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
Guideline 3.1 Readable:
Make text content readable and understandable.
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)
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
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)
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)
When a user changes the setting of a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriented. This occurs in the following component: Video Player.
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
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)
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)
The labels for some form fields are missing, so each field's purpose is not clear. This occurs in the following component: Video Player and following page: Configuration.
EN 301 549 Criteria - Does not apply
Revised Section 508 – Does not apply
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
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) - 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)
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)
Some elements that appear and function like a modal dialog do not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it. This occurs on the following pages: Order Details and Post Acquisition; Creative Cloud Product Details; Purchase Modal.
Multiple elements have an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it. This occurs in the following component: YouTube Player and following page: Manage App Builder.
Multiple elements do not have an attribute in their HTML code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs in the following component: YouTube Player.
A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs in the following component: Header.
The HTML code for a link or button is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of the element. This occurs on the following page: Creative Cloud Product Details.
Multiple buttons do not have a programmatic role, so each button's role (usually button, but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs in the following component: Header and following page: Order Details and Post Acquisition.
An element's programmatic role requires that the element have a parent element, but the parent element is missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element without the context provided by the parent. This occurs in the following component: YouTube Player and following page: Deployment Log.
An element's HTML code has syntax errors, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Purchase Modal.
Multiple buttons do not have a programmatic name, so each button's name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Order Details and Post Acquisition; Creative Cloud Browse.
An element does not have an attribute in its HTML code that will provide its programmatic state (such as "checked"/"not checked") to assistive technology or the state assigned is not correct, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the current state of the element or how to interact with it. This occurs on the following page: Creative Cloud Product Details.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked. This occurs in the following components: YouTube Player; Header and following page: Manage App Builder.
Table 2: Success Criteria, Level AA
Notes:
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)
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: The product provides audio description for most videos. Exceptions include:
Some multimedia (video and audio) files do not have an audio description track, so the visual content presented by each video is not available to people who are blind or have low vision. This occurs in the following components: YouTube Player; Video Player.
1.3.4 Orientation (Level AA 2.1 and 2.2)
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
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
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: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Exceptions include:
No programmatic purpose is provided for an input element (like a text input field), so browsers or assistive technology are not able to automatically suggest information to fill in the input. This occurs on the following page: Purchase Modal.
The programmatic purpose provided for an input element (like a text input field) is not accurate, so information automatically suggested by the browser or assistive technology to fill in the input will be incorrect. This occurs on the following page: Purchase Modal.
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: Most text meets minimum contrast requirements. Exceptions include:
The color contrast ratio between text and its background is less than 4.5:1, so people who are colour-blind or have low vision may have difficulty reading the text. This occurs in the following components: YouTube Player; Video Player and following pages: Purchase Modal; Order Details and Post Acquisition.
The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1, so people who are colour-blind or have low vision may have difficulty reading the text label of each control. This occurs in the following components: Video Player; YouTube Player and following page: Order Details and Post Acquisition.
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)
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)
1.4.10 Reflow (Level AA 2.1 and 2.2)
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: At the required width of 320 CSS pixels, most content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Exception includes:
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following page: Deployment Log.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following page: Purchase Modal.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs in the following component: Video Player.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
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: Most meaningful non-text content elements have sufficient contrast. Exceptions include:
The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs in the following components: YouTube Player; Video Player.
The focus indicators of some interactive elements (like buttons or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when each interactive element is receiving focus. This occurs in the following component: YouTube Player and following pages: Creative Cloud Browse; Creative Cloud Product Details.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements. This occurs in the following component: YouTube Player and following pages: Manage App Builder; Purchase Modal; Environment Details.
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon. This occurs in the following components: YouTube Player; Video Player and following pages: Creative Cloud Product Details; Environment Details.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
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: Most functions of the product support the required text style properties without loss of content or functionality. Exception includes:
When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, the spacing for some or all text on the page does not adjust. This occurs on the following page: Purchase Modal.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
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: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include:
Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs in the following components: Video Player; YouTube Player.
Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs in the following components: YouTube Player; Video Player.
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
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: Most headings and labels for form and interactive controls are informative. Exceptions include:
Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following pages: Configuration; Application Details; Creative Cloud Product Details; Creative Cloud Browse; Manage Creative Cloud Plugins.
Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs on the following pages: Home Page; Application Details; Purchase Modal.
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: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs in the following component: YouTube Player and following page: Purchase Modal.
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: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include:
Multiple focused elements are completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following pages: Order Details and Post Acquisition; Purchase Modal.
2.5.7 Dragging Movements (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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: The size of the target for most clickable controls 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. Exceptions include:
Multiple target hit areas do not meet a minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs in the following component: YouTube Player.
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)
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
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
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)
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)
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
4.1.3 Status Messages (Level AA 2.1 and 2.2)
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) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exception includes:
Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages, or they may not hear them in a timely fashion. This occurs in the following components: Video Player; YouTube Player and following pages: Configuration; Deployment Log; Purchase Modal; Report Abuse Modal; Manage App Builder.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
As noted in 1.1.1 Non-text Content
As noted in 1.2.3 Audio Description or Media Alternative (Pre-recorded)
As noted in 1.2.5 Audio Description (Pre-recorded)
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 3.2.2 On Input
As noted in 4.1.2 Name, Role, Value
As noted in 1.1.1 Non-text Content
As noted in 1.2.3 Audio Description or Media Alternative (Pre-recorded)
As noted in 1.2.5 Audio Description (Pre-recorded)
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.2.2 Captions (Pre-recorded)
As noted in 1.2.2 Captions (Prerecorded)
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
As noted in 1.1.1 Non-text Content
As noted in 1.2.2 Captions (Pre-recorded)
As noted in 1.2.3 Audio Description or Media Alternative (Pre-recorded)
As noted in 1.2.5 Audio Description (Pre-recorded)
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.2 Name, Role, Value
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.2 Name, Role, Value
As noted in 1.3.1 Info and Relationships
As noted in 2.1.1 Keyboard
As noted in 2.4.7 Focus Visible
As noted in 4.1.3 Status Messages
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 on the Adobe Accessibility Compliance website.
EN 301 549 Report
Chapter 4: Functional Performance Statements (FPS)
Notes:
As noted in 1.1.1 Non-text Content
As noted in 1.2.3 Audio Description or Media Alternative (Pre-recorded)
As noted in 1.2.5 Audio Description (Pre-recorded)
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 3.2.2 On Input
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.5 Identify Input Purpose
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.10 Reflow
As noted in 1.4.11 Non-text Contrast
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.11 Non-Text Contrast
As noted in 1.2.2 Captions (Prerecorded)
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 1.2.2 Captions (Prerecorded)
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.2.2 On Input
As noted in 4.1.2 Name, Role, Value
As noted in 2.5.3 Label in Name
As noted in 1.3.5 Identify Input Purpose
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.3 Status Messages
Chapter 5: Generic Requirements
Notes:
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
A multimedia player that provides access to subtitles does not provide an option for the subtitles to be read aloud, so people who are blind or low vision may not be able to hear the dialog in a language they can understand. This occurs on the following components: Video Player; YouTube Player.
A multimedia player cannot play an audio description track, so people who are blind or have low vision are not able to access the information in the video portion of the multimedia described in the audio track. This occurs on the following components: Video Player; YouTube Player.
A multimedia player provides a closed caption control but does not also provide a control to activate the audio description track, so people who are blind, have low vision, and others who need audio description will not be able to access information provided by the video alone. This occurs on the following components: Video Player; YouTube Player.
Clause 8: Hardware
Notes: The ICT covered by this report is not hardware. As such, the requirements of this clause do not apply.
Clause 9: Web (see WCAG 2.2 section)
Notes: SeeWCAG 2.2 section
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes: Not Applicable
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable