Adobe Experience Platform
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
- 11
- Does not support
- 2
- Not applicable
- 8
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 7
- Partially supports
- 10
- Does not support
- 3
- Not applicable
- 4
- 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 (105)
| 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 application. Exception includes: Some images that act as a link or control do not have a text alternative, so people who are blind and/or use a screen reader will not understand the function performed by each image. This occurs on the following pages: Create dataset from schema - Step 1; Customer - Profiles - Overview. A complex image does not have a long description to convey the information presented by the image, so people who are blind and/or use a screen reader will not be able to understand the information prese |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Web: The product contains audio content in the video and [open | closed] captions are provided. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Web: The product contains prerecorded video content that would not require audio description or a media alternative. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Web: Most structure and relationship information are not provided programmatically or in text. Exceptions include: A group of form controls is not programmatically associated with their group label, so the purpose of individual controls in the group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following pages: Create a computed attribute; Create Audience: Build Rule; Ai Assistant. A heading level is out of order, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exception includes: 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: Home. 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 on the following page: Dataset activity. The screen reader skips and does not announce info |
| 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 includes: Color is used as the only method to convey information, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following pages: Customer - Profiles - Overview; Dataset activity; Data Management - Places. Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be |
| 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. Exception includes: An action cannot be performed when using a screen reader, so people who are blind and others who use a screen reader cannot perform this action. This occurs on the following pages: Use Case Playbook Overview; Schemas - Create Schema. A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following pages: Create a computed attribute; Widget Library; Customer - Profiles - Overview; Data |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | Web: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Web: The product does not include time |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | Web: The product does not include elements which move, blink, scroll, or auto-update. |
| 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 mechanism to bypass repeated blocks |
| 2.4.2 | Page Titled | A | Partially Supports | Web: Most pages have descriptive and informative titles. Exception includes: The page's programmatic title does not identify the purpose of the page, so people who use a screen reader will not know the purpose of the page without reading its content. This occurs on the following pages: Administration - Permissions; Create a computed attribute; License Usage - Details - Data visualization; Edit Widget; Create query. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: Most components receive focus in a meaningful order. Exception includes: Keyboard focus or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following pages: Create a computed attribute; Data Management - Places. Keyboard focus is not confined within a modal, 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 occ |
| 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 includes: The purpose of the link is not made clear by its 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 the link goes. This occurs on the following pages: Home; Use Case Playbooks - Instance. |
| 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. |
| 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 an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Administration - Permissions; Use Case Playbook Overview; Widget Library; Customer - Profiles - Overview; Home; Use Case Playbooks - Instance; Add field groups; Schemas - Overview; Schemas - Create Schema. An interac |
| 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 | 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. Th |
| 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 | Partially Supports | Web: Most input errors are identified and described to the users in text. Exceptions include: A form field with an error is not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field the error occurred. This occurs on the following page: Schemas - Name and Review. An error for a form input (such as a text input f |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: Labels are provided for most input fields. Exception includes: The label for a form field is missing, so the field's purpose is not clear. This occurs on the following page: Add field groups. Select or dropdown control missing a visible label, so the select or dropdown control purpose is not clear This occurs on the following pages: Create a computed attribute; License Usage - Details - Data visualization. |
| 3.3.7 | Redundant Entry | A | Not Applicable | 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 | Supports | For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata . |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Web: User interface components in most product functions do not provide programmatic [name, role, state, or value] information. Exceptions include: An element has 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 the element or how to interact with it. This occurs on the following pages: Administration - Permissions; Data Management – Places; Data governanc |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Web: The product contains prerecorded video content that would not require audio description |
| 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 | Not Applicable | Web: The product does not contain input fields that collect information about the user. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include: The color contrast ratio between placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following pages: Administration - Permissions; Create query. The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Schemas – Deque Test Schema - Structure Ta |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Most content is readable and functional when browser zoom is set to 200% of its initial size. Exceptions include: Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following pages: Create a computed attribute; Data governance; Home; Use Case Playbooks - Instance; Use Case Playbook - Playbook Detail; Add field groups; Experience Events; Profile: Computed attributes; Schemas - Create Schema; Edit governance labels modal. Functionality is lost when th |
| 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 | Does Not Support | Web: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. [Loss of information or functionality occurs] [and] [content which does not require two-dimensional layout for meaning relies on scrolling in two dimensions]. Exceptions include: 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 |
| 1.4.11 | Non-text Contrast | AA | Does Not Support | Web: Most of the boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content does not have a 3:1 color contrast ratio with adjacent color(s) or their background. Exceptions include: The visual boundary of an interactive element (like a radio button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the boundaries of the interactive element. This occurs on the following pages: Schemas - Deque Test Schema - Structure Tab; Com |
| 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 Exceptions include: When text spacing is adjusted to help people with vision, reading and cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: View Profile Detail; Schemas - Create Schema. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: When additional content appears on hover, becomes hidden when the mouse pointer moves over it. Exception includes: 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 on the following pages: Customer - Profiles - Overview; License Usage - Details - Data visualization; Schemas - Video Modal. 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 peopl |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Multiple ways are available to find other pages on the site. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most of the headings and labels are descriptive. Exception includes: A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: Schemas – Deque Test Schema - Structure Tab; Compose Audience; Use Case Playbook Overview; Widget Library; Customer - Profiles - Overview; Dataset activity; Data governance; Data Management - Places; Use Case Playbook - Playbook Detail; Add field groups; View Profile |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exception includes: An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following pages: Create a computed attribute; Schemas - Name and Review; Home; Data Management - Places; Create dataset from schema - Step 1; Schemas - Video Modal. The visual focus indicator for an interactive element (such as a link, button, or form input) is not visible, so s |
| 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. Exception includes: A focused element is 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: Create a computed attribute; Home; View Profile Detail; Schemas - Video Modal; Publish a computed attribute modal; Edit governance labels modal. |
| 2.5.7 | Dragging Movements | AA | Partially Supports | Web: Most 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. Exception includes: Some functionality relies on a dragging movement with no single-pointer, single touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture on the following pages: Create a computed attribute; Customer - Profiles - Overview; View Profile Detail; Edit Widget; Create query. |
| 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 inline 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. Exception includes: A target's hit area does not meet minimum 24x24 pixel size or spacing. making it |
| 3.1.2 | Language of Parts | AA | Partially Supports | Web: On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. Exception includes: A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following pages: Home; Add field groups. |
| 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 are provided in text for correcting the input in a timely and accessible manner before the data is submitted to the server. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | 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 Web site. |
| 4.1.3 | Status Messages | AA | Does Not Support | Web: When status messages do not receive focus, the product does not provide the update to assistive technology. Exception includes: A status message is 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 message or they may not hear it in a timely fashion. This occurs across all web pages. |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 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. Exception includes: 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. Exception includes: 4.1.2 Name, Role, Value |
| 502.3.3 | Row, 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. Exception includes: 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) is available programmatically, so it can be perceived and conveyed by assistive technology. Exception includes: 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 its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exception includes: 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 labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exception includes: 1.3.1 Info and Relationships 4.1.2 Name, Role, Value |
| 502.3.7 | Hierarchical Relationships | - | Partially Supports | For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exception includes: 1.3.1 Info and Relationships 4.1.2 Name, Role, Value |
| 502.3.8 | Text | - | Partially Supports | All the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exception includes: 1.3.2 Meaningful Sequence |
| 502.3.9 | Modification of Text | - | Supports | The product allows assistive technology to modify the text. |
| 502.3.10 | List of Actions | - | Partially Supports | Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology. Exception includes: 4.1.2 Name, Role, Value. |
| 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. Exception includes: 2.1.1 Keyboard Navigation |
| 502.3.12 | Focus Cursor | - | Partially Supports | The product exposes focus location, text insertion point, and object selection state for most user interface components. Exception includes: 2.4.7 Focus Visible. |
| 502.3.13 | Modification of Focus Cursor | - | Supports | When a user can set focus, set the text insertion point, or change selection state of an object in the product, then the focus or selection state can also be changed programmatically. |
| 502.3.14 | Event Notification | - | Partially Supports | In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exception includes: 4.1.3 Status Messages |
| 503.4.1 | Caption Controls | - | Supports | The product provides user controls for closed captions. |
| 503.4.2 | Audio Description Controls | - | Partially Supports | The product does not provide user controls for audio descriptions. Exceptions include: A multimedia (video and audio) file does not have an audio description track. This occurs on the following page: Schemas - Video Modal. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | 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 | - | Does Not Support | Web: Most functions of the product are not usable without vision. Exception includes: 1.1. 1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 3.1.2 Language of Parts 3.2.2 On Input 3.3.1 Error Identification 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Does Not Support | Web: Most functions of the product are not usable with limited vision. Exception includes: 1.1.1Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.4 Resize Text 1.4.10 Reflow 1.4.11 Non-Text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 2.4.7 Focus Visible 3.1.2 Language of Parts 3.2.2 On Input 3.3.1 Error Identification 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most functionality is usable without perception of color. Exceptions are noted in: 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.11 Non-Text Contrast |
| 4.2.4 | Usage without hearing | - | Supports | Web: All functionality is usable without hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Web: All functionality is usable with limited hearing. |
| 4.2.6 | Usage with no or limited vocal capability | - | Not Applicable | Web: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Does Not Support | Web: Most, if not all, functionality is not usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength. Exception includes: 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.5.3 Label in Name 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Web: All functionality is usable by people with limited reach. Exception includes: 1.4.13 Content on Hover or Focus 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 | - | Does Not Support | Web: Most, if not all, functionality is not 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. Exception includes: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.10 Reflow 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.5.3 Label in Name 3.1.2 Langua |
| 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 | - | Partially Supports | The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exception includes: 4.1.2 Name, Role, Value. |
| 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 | The visual status of controls is discernible in the product. |
| 7.1.1 | Captioning playback | - | Supports | The product provides video with closed captions 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 | - | Does Not Support | When the product displays captions for video that has synchronized audio, the display characteristics (such as color, font, or size) of caption text cannot be modified by the user Exception includes: A multimedia player does not provide a way for the user to modify the appearance of captions to their individual needs, so people who are deaf, have limited hearing, and others who rely on captions to understand the content may not have access to the information. This occurs on the following page: Schemas - Video Modal. |
| 7.1.5 | Spoken subtitles | - | Does Not Support | When the product displays captions for video that has synchronized audio, most, if not all, captions cannot be announced as spoken output. Exception includes: 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 page: Schemas - Video Modal |
| 7.2.1 | Audio description playback | - | Does Not Support | The product does not allow the user to play audio description if it is available for video that has synchronized audio. Exceptions include: 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 page: Schemas - Video Modal. |
| 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 |
| 12.1.1 | Accessibility and compatibility features | - | Not Applicable | Documentation is not provided for the product. |
| 12.2.2 | Information on accessibility and compatibility features | - | Not Applicable | Support services are not provided for the product. |
| 12.2.3 | Effective communication | - | Not Applicable | Support services are not provided for the product. |
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 April 2025. 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.