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:

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.

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: The product provides sufficient text alternatives for most instances of non-text content. Exceptions include:
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.

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: The product does not contain pre-recorded audio-only or video-only media.

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: Partially Supports
Web: The product contains audio content and [open | closed] captions are provided for most instances. Exceptions include:
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)
Web: Partially Supports
Web: The product provides [audio description | transcripts] for most videos. Exceptions include:
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.

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 visual structure and relationship information is provided through element semantics | object information or in text. Exceptions include:
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)
Web: Partially Supports
Web: The product presents most content in a meaningful sequence. Exceptions include:
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)

Web: Supports
Web: Instructions do not rely solely on sensory characteristics.

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: Most functions of the product do not convey information through color alone. Exception include:
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)
Web: Supports (Not Applicable)
Web: The product does not contain audio that plays automatically.

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: Most product functionality can be operated through a keyboard interface. Exceptions include:
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)
Web: Supports
Web: The product does not include keyboard traps.

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

Web: Supports (Not Applicable)
Web: The product does not provide character key shortcuts.

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: Partially Supports
Web: In most cases, when a time limit exists, the user is given an option to turn off, adjust, or extend the time limit. Exceptions include:
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)
Web: Partially Supports
Web: On most screens where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. Exceptions include:
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.

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: Supports (Not Applicable)
Web: The product 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: The product provides a way to bypass repeated blocks.

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: Supports
Web: The titles of pages describe their purpose.

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: Most components receive focus in a meaningful order. Exceptions include:
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)
Web: Partially Supports
Web: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. Exception include:
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.

Criteria
Conformance Level
Remarks and Explanations

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

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

Web: Supports
Web: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click.

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

Web: Partially Supports
Web: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:
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

Web: Supports (Not Applicable)
Web: The product does not have functionality operated by device motion or user motion.

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 is programmatically determinable within the product.

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: Components do not initiate a change of context when focused.

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: Partially Supports
Web: In most cases, 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, or the user is informed about the change ahead of time. Exceptions include:
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.
3.2.6 Consistent Help (Level A 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.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: Where input errors are automatically detected items in error are identified and error messages are provided as text.

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: Labels are provided for most input fields. Exceptions include:
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.
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.

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) - 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 (Not Applicable)
Web: This criterion was removed from WCAG 2.2

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: Partially Supports
Web: User interface components in some product functions do not provide programmatic [name, role, state, or value] information. Examples include:
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:

Criteria
Conformance Level
Remarks and Explanations

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: The product does not contain live synchronized media.

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: Partially Supports

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

Web: Supports
Web: Content does not restrict its view and operation to a single display orientation.

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: Partially Supports

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: Partially Supports

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)
Web: Supports
Web: The product allows browser zoom | operating system display scaling | to resize text up to 200 percent without loss of content or functionality.

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: The product uses text instead of images of text, except for branding elements that are considered essential.

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: Partially Supports

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: Partially Supports

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: Partially Supports

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: Partially Supports

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
Web: Supports
Web: Users can locate web pages in the product through multiple ways.

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. 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: Partially Supports

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: Partially Supports

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

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: Partially Supports

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)
Web: Supports
Web: Changes of language for passages or phrases can be programmatically determined.

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: When navigational mechanisms are repeated in the product, they occur in a consistent relative order.

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: Components with the same functionality are identified consistently.

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: Where input errors are automatically detected, suggestions for correction are provided to the user.

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: The product does not process legal commitments or financial transactions.

3.3.8 Accessible Authentication (Minimum) (Level AA 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 website.

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: Partially Supports

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:

Criteria
Conformance Level
Remarks and Explanations
302.1 Without Vision
Web: Partially Supports
Web: Most functions of the product are usable without vision. Exceptions include:
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
302.2 With Limited Vision
Web: Partially Supports
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.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
302.3 Without Perception of Color
Web: Partially Supports
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
302.4 Without Hearing
Web: Partially Supports
Web: Most functions of the product are usable without hearing. Exceptions include:
As noted in 1.2.2 Captions (Pre-recorded)
302.5 With Limited Hearing
Web: Partially Supports
Web: Most functions of the product are usable with limited hearing. Exceptions include:
As noted in 1.2.2 Captions (Prerecorded)
302.6 Without Speech
Web: Supports
Web: All functions of the product are usable without speech.
302.7 With Limited Manipulation
Web: Partially Supports
Web: Most functions of the product are usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
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
302.8 With Limited Reach and Strength
Web: Supports
Web: The product is functional with limited reach and strength.
302.9 With Limited Language, Cognitive, and Learning Abilities
Web: Partially Supports
Web: Most functions of the product are 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 include:
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

Chapter 4: Hardware

Notes: The ICT covered by this report is not hardware. As such, the requirements of this chapter do not apply.

Chapter 5: Software

Notes:

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope – Incorporation of WCAG 2.0 AA
See WCAG 2.2 section
See information in WCAG 2.2 section
502 Interoperability with Assistive Technology
Heading cell – no response required
Heading cell – no response required
502.2.1 User Control of Accessibility Features
Not Applicable
The product is not platform software, so this requirement does not apply.
502.2.2 No Disruption of Accessibility Features
Not Applicable
The product is not platform software, so this requirement does not apply.
502.3 Accessibility Services
Heading cell – no response required
Heading cell – no response required
502.3.1 Object Information
Partially Supports
The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.2 Modification of Object Information
Partially Supports
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.3 Rows, Column, and Headers
Partially Supports
In most instances, when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
502.3.4 Values
Partially Supports
For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.5 Modification of Values
Partially Supports
For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.6 Label Relationships
Partially Supports
For most elements that act as a label for another element and elements that are labelled by another element, the labelling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.7 Hierarchical Relationships
Supports
When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology.
502.3.8 Text
Partially Supports
Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
502.3.9 Modification of Text
Supports
When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology.
502.3.10 List of Actions
Supports
When one or more actions may be performed on an element, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology.
502.3.11 Actions on Objects
Partially Supports
For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:
As noted in 2.1.1 Keyboard
502.3.12 Focus Cursor
Partially Supports
On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 2.4.7 Focus Visible
502.3.13 Modification of Focus Cursor
Supports
When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.
502.3.14 Event Notification
Partially Supports
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:
As noted in 4.1.3 Status Messages
502.4 Platform Accessibility Features
Not Applicable
The product is not platform software, so this requirement does not apply.
503 Applications
Heading cell – no response required
Heading cell – no response required
503.2 User Preferences
Not Applicable
Not applicable to web
503.3 Alternative User Interfaces
Not Applicable
The product does not provide an alternative user interface that functions as assistive technology.
503.4 User Controls for Captions and Audio Description
Heading cell – no response required
Heading cell – no response required
503.4.1 Caption Controls
Not Applicable
The product does not display video with synchronized audio that requires captions.
503.4.2 Audio Description Controls
Not Applicable
The product does not provide prerecorded media that requires audio description.
504 Authoring Tools
Heading cell – no response required
Heading cell – no response required
504.2 Content Creation or Editing
See WCAG 2.2 section
See information in WCAG 2.2 section
504.2.1 Preservation of Information Provided for Accessibility
Not Applicable
The product is not an authoring tool.
504.2.2 PDF Export
Not Applicable
The product is not an authoring tool.
504.3 Prompts
Not Applicable
The product is not an authoring tool.
504.4 Templates
Not Applicable
The product is not an authoring tool.

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

Criteria
Conformance Level
Remarks and Explanations
4.2.1 Usage without vision
Web: Partially Supports
Web: Most functions of the product are usable without vision. Exceptions include:
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
4.2.2 Usage with limited vision
Web: Partially Supports

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

4.2.3 Usage without perception of colour
Web: Partially Supports
Web: Most functions of the product are usable without perception of color. Exceptions include:
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
4.2.4 Usage without hearing
Web: Partially Supports
Web: Most functions of the product are usable without hearing. Exceptions include:
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
4.2.5 Usage with limited hearing
Web: Partially Supports
Web: Most functions of the product are usable with limited hearing. Exceptions include:
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
4.2.6 Usage with no or limited vocal capability
Web: Supports
Web: All functions of the product are usable without speech.
4.2.7 Usage with limited manipulation or strength
Web: Partially Supports
Web: Most functions of the product are usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:
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
4.2.8 Usage with limited reach
Web: Partially Supports
Web: Most functions of the product are usable by people with limited reach. Exceptions include:
As noted in 2.5.3 Label in Name
4.2.9 Minimize photosensitive seizure triggers
Web: Supports (Not Applicable)
Web: The product does not contain flashing content.
4.2.10 Usage with limited cognition, language or learning
Web: Partially Supports
Web: Most functions of the product are 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 include:
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
4.2.11 Privacy
Web: Supports (Not Applicable)
Web: The product does not ask for or display legal, financial, or personal data.

Chapter 5: Generic Requirements

Notes:

Criteria
Conformance Level
Remarks and Explanations
5.1 Closed functionality
Heading cell – no response required
Heading cell – no response required
5.1.2 General
Heading cell – no response required
Heading cell – no response required
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
Heading cell – no response required
Heading cell – no response required
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
Heading cell – no response required
Heading cell – no response required
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.1.7 Access without speech
Not Applicable
The product does not have closed functionality.
5.2 Activation of accessibility features
Not Applicable
The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features.
5.3 Biometrics
Not Applicable
Biometrics is not included in the product.
5.4 Preservation of accessibility information during conversion
Not Applicable
The product is not an authoring tool.
5.5 Operable parts
Heading cell – no response required
Heading cell – no response required
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
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.6 Locking or toggle controls
Heading cell – no response required
Heading cell – no response required
5.6.1 Tactile or auditory status
Not Applicable
Tactile or auditory status is not included in the product.
5.6.2 Visual status
Not Applicable
Visual status of controls isn’t discernible in the product
5.7 Key repeat
Not Applicable
Key repeat functionality is not found in the product.
5.8 Double-strike key acceptance
Not Applicable
Double -strike key acceptance is not found in the product.
5.9 Simultaneous user actions
Not Applicable
The product does not require simultaneous user actions for core functionality. All actions triggered by key combinations are also available via the graphical user interface using mouse or sequential keyboard navigation.

Chapter 6: ICT with Two-Way Voice Communication

Notes: Not Applicable

Chapter 7: ICT with Video Capabilities

Notes:

Criteria
Conformance Level
Remarks and Explanations
7.1 Caption processing technology
Heading cell – no response required
Heading cell – no response required
7.1.1 Captioning playback
Supports
The product displays closed captions.
7.1.2 Captioning synchronization
Supports
When the product displays captions, synchronization is preserved between the captions and the corresponding audio.
7.1.3 Preservation of captioning
Not Applicable
The product does not transmit, convert, or record video with synchronized audio.
7.1.4 Captions characteristics
Supports
When the website or application displays captions for a video that has synchronized audio, the display characteristics (such as color, font, or size) of the caption text can be modified by the user so people with low vision or color blindness can adapt the caption text to meet their needs.
7.1.5 Spoken subtitles
Does Not Support
The product does not provide access to subtitles with an option for the subtitles to be read aloud. Examples include:
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.
7.2.1 Audio description playback
Does Not Support
The product does not provide a mechanism to select and play closed audio descriptions. Exception includes:
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.
7.2.2 Audio description synchronization
Not Applicable
The product does have a mechanism to play closed audio description.
7.2.3 Preservation of audio description
Not Applicable
The product does not transmit, convert, or record video with synchronized audio
7.3 User controls for captions and audio description
Partially Supports
The product provides user controls for captions, but not for audio descriptions. Exception includes:
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