Adobe Exchange 2026
Accessibility Conformance Report published by Adobe
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 32 criteria
- Supports
- 11
- Partially supports
- 15
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 11
- Partially supports
- 12
- Does not support
- 0
- Not applicable
- 1
- Not evaluated
- 0
Source: View the original report published by Adobe.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (102)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | 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. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Web: The product does not contain pre-recorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | 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) | A | 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. |
| 1.3.1 | Info and Relationships | A | 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 incorr |
| 1.3.2 | Meaningful Sequence | A | 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. |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | 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 | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | 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 | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts (WCAG 2.1) | A | Not Applicable | Web: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | 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, ha |
| 2.2.2 | Pause, Stop, Hide | A | 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. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Web: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Supports | Web: The product provides a way to bypass repeated blocks. |
| 2.4.2 | Page Titled | A | Supports | Web: The titles of pages describe their purpose. |
| 2.4.3 | Focus Order | A | 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. W |
| 2.4.4 | Link Purpose (In Context) | A | 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. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: All functionality that can be operated with a pointer can be operated with single-point actions. |
| 2.5.2 | Pointer Cancellation | A | 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 | A | 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 | A | Not Applicable | Web: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Web: The language is programmatically determinable within the product. |
| 3.2.1 | On Focus | A | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | 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 disoriente |
| 3.2.6 | Consistent Help | A | 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. |
| 3.3.1 | Error Identification | A | 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 | A | 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 | A | 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. |
| 4.1.1 | Parsing | A | Not Applicable | Web: This criterion was removed from WCAG 2.2 |
| 4.1.2 | Name, Role, Value | A | 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 Pos |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | 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 | AA | Supports | Web: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | 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 |
| 1.4.3 | Contrast (Minimum) | AA | 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 |
| 1.4.4 | Resize text | AA | 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 | AA | Supports | Web: The product uses text instead of images of text, except for branding elements that are considered essential. |
| 1.4.10 | Reflow | AA | 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: |
| 1.4.11 | Non-text Contrast | AA | 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 col |
| 1.4.12 | Text Spacing | AA | 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 | AA | 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 |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through multiple ways. |
| 2.4.6 | Headings and Labels | AA | 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 con |
| 2.4.7 | Focus Visible | AA | 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) | AA | 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 | AA | 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) | AA | 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. ma |
| 3.1.2 | Language of Parts | AA | Supports | Web: Changes of language for passages or phrases can be programmatically determined. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Components with the same functionality are identified consistently. |
| 3.3.3 | Error Suggestion | AA | Supports | Web: Where input errors are automatically detected, suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Web: The product does not process legal commitments or financial transactions. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | 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 | AA | 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. |
| 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.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 |
| 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.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. |
| 4.2.1 | Usage without vision | - | 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.2.2 | Usage with limited vision | - | 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 |
| 4.2.3 | Usage without perception of colour | - | 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 | - | 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 | - | 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 | - | Supports | Web: All functions of the product are usable without speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | 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 | - | 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 | - | Not Applicable | Web: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | 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 Visi |
| 4.2.11 | Privacy | - | Not Applicable | Web: The product does not ask for or display legal, financial, or personal data. |
| 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.7 | Access without speech | - | Not Applicable | The product does not have closed functionality. |
| 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.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 |
| 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 |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated July 10, 2026. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.