Adobe Journey Optimizer
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 — 31 criteria
- Supports
- 12
- Partially supports
- 12
- Does not support
- 2
- Not applicable
- 5
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 8
- Partially supports
- 12
- Does not support
- 2
- Not applicable
- 2
- 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 (93)
| 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: Email Designer - Personalization Editor; Journey Properties flyout; Create offer workflow - Step 1: Details; Campaign report; Channel configurations: Creation flow for email channel; Content fragments: creation; Create audi |
| 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 | Not Applicable | Web: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Web: Most visual structure and relationship information is not provided through semantics. Examples include: Some content that is visually presented as multiple lists is not marked up as a list, so the presence and structure of each list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Create decision policy Workflow - Step 4: Summary; Create decision policy Workflow - Step 2: Add Decision Scopes. Some text that visually functions as a heading is not marked up as a heading, so the structure of the content is not |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions include: The correct reading order of dynamically changing content is not programmatically determinable by screen readers, so people who are blind and/or use a screen reader may not be made aware of new or changed content that is dynamically added to a page. This occurs on the following page: Create audience - build rule. 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 r |
| 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. Exceptions include: Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of some controls, 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: Journey Properties flyout; Create offer workflow - Audiences panel; Create decision policy Workflow - Step 2: Add Decision Scopes. Color is used as the only method to convey information so that information will not be ava |
| 1.4.2 | Audio Control | A | Supports | 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: 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 on the following pages: Campaign report; Create Journey; Email Designer - Personalization Editor; Orchestration; Create audience - compose audience; Create offer workflow - Step 1: Details; Draft journey; Create decision policy Workflow - Step 2: Add Decision Scopes. |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | 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. Exception includes: 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 on the following pages: Channel configurations: Creation flow for email channel; Create Journey. |
| 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: Create Journey; Content fragments: creation; Content creation in email designer; Create Campaign workflow-Properties tab; Email Designer - Personalization Editor; Channel configurations: Creation flow for email channel; Create audience - compose audience. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: Most components receive focus in a meaningful order. Exceptions include: The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs in the following component: Left hand navigation and following pages: Journey Properties flyout; Campaign report; Create decision policy Workflow - Step 2: Add Decision Scopes; Create Journey workflow-Exit Criteria; Email Designer - Personalization Editor; Create aud |
| 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. Most components receive focus in a meaningful order. 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 page: Channel configurations: Creation flow for email channel. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: The product does not rely on multipoint or path-based gestures. |
| 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: Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Campaign report; Email Designer - Personalization Editor. The accessible name of multiple interactive elements (such as links, buttons, or form input |
| 2.5.4 | Motion Actuation | A | Supports | 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. Exception includes: When a user changes the setting of some user interface controls (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 disori |
| 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: Create decision policy Workflow - Step 2: Add Decision Scopes. Errors for so |
| 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 on the following pages: Journey inventory page (Browse tab)-List View; Create audience - build rule-Audiences tab; Campaign report. Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following pages: Create offer workflow - Step 1: Details; Journey Properties flyout. Select or dropdown control missing a visible label so the purpose of the |
| 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.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. Examples include: Multiple form input elements do not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of each element and may not understand its purpose or how to interact with it. This occurs on the following pages: Create Journey workflow-Search and Filter; Campaign report. Multiple buttons do not have a programmatic name, so each button's name (such as "Submit" or "Cancel |
| 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 does not contain prerecorded video content that would 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 | Supports | 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 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: Campaign report; Create audience - build rule; Home page; Create decision policy Workflow - Step 2: Add Decision Scopes; Create audience - build rule-Attributes tab; Create offer workflow - Step 2: Add Constraints; Content creation in email designer; Create Journey. The color contrast ratios on hover or focus between the text l |
| 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 Journey; Create audience - build rule-Attributes tab; Create decision policy Workflow - Step 3: Add Fallback Offer; Create audience - compose audience; Content creation in email designer; Campaign report; Email Designer - Personalization Editor; Channel configurat |
| 1.4.5 | Images of Text | AA | Partially Supports | Web: On most pages, when content can be presented visually using only text, an image of text is not used to present that text. Exception includes: Text on the page is text embedded in an image instead of actual text. An image of text is difficult to zoom or otherwise modify, so people who have low vision and need to enlarge text to read it may not be able to read the text. People with other disabilities that need to otherwise modify text to read it also may not be able to read this text. This occurs on the following page: Draft journey. |
| 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. Examples 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 the cont |
| 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 on the following pages: Journey Properties flyout; Email Designer - Personalization Editor; Campaign report; Content creation in email designer; Create decision policy Workflow - Step 1: Details; Create decision policy Wo |
| 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, some content cannot be seen because it is cut off. This occurs on the following pages: Campaign report; Create decision policy Workflow - Step 2: Add Decision Scopes. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: In most cases, when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. 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 on the following pages: Draft journey; Campaign report. Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is m |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through multiple ways in the site. |
| 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: Email Designer - Personalization Editor; Campaign report; Create decision policy Workflow - Step 4: Summary; Create Campaign workflow-Actions tab; Create offer workflow - Step 1: Details; Journey Properties flyout; Create |
| 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 on the following pages: Create Journey; Journey Properties flyout; Content creation in email designer; Orchestration; Campaign report; Draft journey; Create audience - build rule; Email Designer - Personalization Editor. The visual focus indicator for multiple interactive elem |
| 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 page: Create audience - build rule. |
| 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. This occurs on the following pages: Content creation in email designer; Campaign report; Create Journey; Create audience - build ru |
| 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 | 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 page: Email Designer - Personalization Editor. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product, such as the primary navigation menu and the sub menu in settings, 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. When editing files changes to user-controllable data are reversible or can be confirmed before finalizing. |
| 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 | Does Not Support | Web: When status messages do not receive focus, the product does not provide the update to assistive technology. Example 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 component: Creation flow header and following pages: Create decision policy Workflow - Step 2: Add Decision Scopes; Create offer workflow - Step 1: Details; Create offer workflow - Step 3: Add Rep |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | Web: The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Not Applicable | Web: The product is not platform software. |
| 502.3.1 | Object Information | - | Partially Supports | Web: 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: As noted in 4.1.2 Name, Role, Value |
| 502.3.2 | Modification of Object Information | - | Partially Supports | Web: 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: As noted in 4.1.2 Name, Role, Value |
| 502.3.3 | Row, Column, and Headers | - | Partially Supports | Web: 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: As noted in 1.3.1 Info and Relationships |
| 502.3.4 | Values | - | Partially Supports | Web: 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. Exception includes: As noted in 4.1.2 Name, Role, Value |
| 502.3.5 | Modification of Values | - | Partially Supports | Web: 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. Exception includes: As noted in 4.1.2 Name, Role, Value |
| 502.3.6 | Label Relationships | - | Partially Supports | Web: 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. Exceptions include: As noted in 1.3.1 Info and Relationships As noted in 4.1.2 Name, Role, Value |
| 502.3.7 | Hierarchical Relationships | - | Supports | Web: 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 | - | Supports | Web: All text, text attributes (such as whether text is static or editable), and text boundaries (such as text that receives visual focus) are programmatically determinable, so they can be perceived and conveyed by assistive technology. |
| 502.3.9 | Modification of Text | - | Supports | Web: 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 | Web: 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 | Web: 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: As noted in 2.1.1 Keyboard |
| 502.3.12 | Focus Cursor | - | Partially Supports | Web: 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. Exception includes: As noted in 2.4.7 Focus Visible |
| 502.3.13 | Modification of Focus Cursor | - | Supports | Web: 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 | - | Supports | Web: In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exception includes: As noted in 4.1.3 Status Messages |
| 503.4.1 | Caption Controls | - | Not Applicable | Web: The product does not contain video with synchronized audio that requires captions, and it provides user controls for captions. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Not Applicable | Web: This product is not an authoring tool. |
| 504.2.2 | PDF Export | - | Not Applicable | Web: This product is not an authoring tool. |
| 4.2.1 | Usage without vision | - | Partially Supports | Web: Most functionality is usable without vision. Exceptions include: As noted in 1.1.1 Non-text Content 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.2 Page Titled 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.1.2 Language of Parts As noted in 3.2.2 On Input As noted in 3.3.1 Error Identification As noted in 4.1.2 Name, Role, Value As noted in 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most functionality is usable with limited vision. Exceptions include: As noted in 1.1.1 Non-text Content As noted in 1.4.1 Use of Color As noted in 1.4.3 Contrast (Minimum) As noted in 1.4.4 Resize text As noted in 1.4.5 Images of Text 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.4.2 Page Titled 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.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most functionality is 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 As noted in 3.3.1 Error Identification |
| 4.2.4 | Usage without hearing | - | Partially Supports | Web: Most functionality is usable without hearing. Exceptions include: As noted in 1.1.1 Non-text Content As noted in 2.2.1 Timing Adjustable |
| 4.2.5 | Usage with limited hearing | - | Partially Supports | Web: Most functionality is usable with limited hearing. Exceptions include: As noted in 2.2.1 Timing Adjustable |
| 4.2.6 | Usage with no or limited vocal capability | - | Supports | Web: All functionality is usable without speech or other vocal output. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Web: Most functionality is 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.4.2 Page Titled 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 functionality is usable by people with limited reach. Exceptions include: As noted in 2.5.3 Label in Name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | Web: All functionality may be operated in a mode that minimizes the potential for triggering photosensitive seizures. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions include: 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.4.2 Page Titled 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.1 Error Iden |
| 4.2.11 | Privacy | - | Supports | Web: Where the product provides features for accessibility, it maintains the privacy of people who use these features at the same level as other users. |
| 5.1.4 | Functionality closed to text enlargement | - | Not Applicable | Web: The product does not have closed functionality. |
| 5.1.5 | Visual output for auditory information | - | Not Applicable | Web: The product does not have closed functionality. |
| 5.1.7 | Access without speech | - | Not Applicable | Web: The product does not have closed functionality. |
| 5.5.1 | Means of operation | - | Not Applicable | Web: 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 | Web: 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 | Web: Tactile or auditory status is not included in the product. |
| 5.6.2 | Visual status | - | Not Applicable | Web: Visual status of controls is discernible in 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 December 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.