Adobe Experience Manager Edge Delivery Services
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
- 12
- Partially supports
- 11
- Does not support
- 0
- Not applicable
- 9
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 13
- Partially supports
- 8
- Does not support
- 0
- Not applicable
- 3
- 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 (110)
| 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 images and 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: List View; Edge Delivery Services; Edit demo - DA. Authored Content: Authors can provide text alternatives for images and non-text content. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Web: The product provides audio description for video-only media. Authored Content: Authors can provide audio description for what would otherwise be video-only media |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded synchronized media. Authored Content: Authored content 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. Authored Content: Authored content does not contain video content that would require audio description or a media alternative. |
| 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: An HTML list element contains content that is visually presented as a part of the list, but the content's HTML coding does not include it programmatically in that list, so the structure of the list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Preview. Some content that is visually presented as multiple lists is not marked up as a list, so the presence an |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions include: 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: Native authoring (Project da.live). Authored Content: The product allows authors to present content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. Authored Content: Authors can ensure that content meets this criterion. |
| 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 a control, 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 page: Block-collection config - DA. Color is used as the only method to identify errors on some form fields, so the errors for those fields will not be available to people who are colorblind and people who are blind and/or use a scr |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. Authored Content: Authored content 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 on the following pages: Block-collection config - DA; Edit demo - DA; Right Bar Buttons; New menu. Authored Content: Authors can ensure that content meets this criterion. |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. Authored Content: Authored content does include keyboard traps. Examples include: There is a keyboard trap, so people who use a keyboard to navigate content will get stuck in one place on the page. This occurs on the following page: Sample Blocks - Video. |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | Web: The product does not provide character key shortcuts. Authored Content: Authored content does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Web: The product does not include time limits. Authored Content: Authored content does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | Web: The product does not include elements which move, blink, scroll, or auto-update. Authored Content: Playback control is a function of the user’s media player, not the authored content. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Web: The product does not contain flashing content. Authored Content: Authors can ensure that content does not flash. |
| 2.4.1 | Bypass Blocks | A | Supports | Web: The product provides mechanism to bypass repeated blocks. Authored Content: Authored content does not contain repeated blocks that would require a skip mechanism. |
| 2.4.2 | Page Titled | A | Supports | Web: The titles of pages describe their purpose. Authored Content: The product allows authors to customize the page title. |
| 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 on the following page: History. 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 on the following page: Native authoring (Project |
| 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. Exceptions include: Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following pages: Native authoring (Project da.live); List View. Authored Content: Authors can ensure that most content meets this criterion. E |
| 2.5.1 | Pointer Gestures | A | Not Applicable | Web: The product does not rely on multipoint or path-based gestures. Authored Content: Authored content 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. Authored Content: Authors can ensure that content meets this criterion. |
| 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 page: List View. The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people |
| 2.5.4 | Motion Actuation | A | Not Applicable | Web: The product does not have functionality operated by device motion or user motion. Authored Content: Authored content 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. Authored Content: Authors can set the language of the page. |
| 3.2.1 | On Focus | A | Supports | Web: Components do not initiate a change of context when focused. Authored Content: Authors can ensure that content meets this criterion. |
| 3.2.2 | On Input | A | Supports | Web: Changes of context do not occur automatically on user input. Authored Content: Authors can ensure that content meets this criterion. |
| 3.2.6 | Consistent Help | A | Supports | Web: The product 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. Authored Content: Authors can ensure that content meets this criterion. |
| 3.3.1 | Error Identification | A | Partially Supports | Web: Most input errors are identified and described to the users in text. Exceptions include: Errors for some form inputs (such as text input fields, radio buttons, select dropdowns, or checkboxes) are not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following page: New menu. Authored Content: Authored content does not detect input errors that are displayed to users. |
| 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: Block-collection config - DA; Edit demo - DA. 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: New menu; History; List View. Authored Content: Authors can ensure that most content meets this criterion. Exceptions include: The labels for some form fields are missing, so each field's purpose is not |
| 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. Authored Content: Authors can ensure that content meets this criterion. |
| 4.1.1 | Parsing | A | Supports | Web: Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. Authored Content: Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. |
| 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: 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: List View; Block-collection config - DA; Edit demo - DA. 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. Authored Content: Authored content 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. Authored Content: Authored content does not contain 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. Authored Content: Authors can ensure that 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. Authored Content: Authors can ensure that content meets this criterion. |
| 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: New menu; Edit demo - DA; Native authoring (Project da.live); Block-collection config - DA; Browse. 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 colorblind or have low vision may have difficulty reading the text label of each con |
| 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: Right Bar Buttons; Edit demo - DA. Functionality is lost 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 this functionality. This occurs on the following pages: Edit demo - DA; Edge Delivery Servic |
| 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. Exceptions include: 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: Edge Delivery Services. Authored Content: Authors can ensure that conten |
| 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. Exceptions include: When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following pages: Edit demo - DA; Right Bar Buttons. When the page is adjusted to an |
| 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: List View; History. The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorb |
| 1.4.12 | Text Spacing | AA | Supports | Web: The product supports the required text style properties without loss of content or functionality. Authored Content: Authors can ensure that content meets this criterion. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Web: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion. Authored Content: Authors can ensure that most content meets this criterion. 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 page: Sample Blocks - Video. Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product. Authored Content: Authors can provide more than one way to locate a page in a set of pages. |
| 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: Edge Delivery Services; History; Block-collection config - DA; List View; Edit demo - DA. Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are |
| 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: Edge Delivery Services; New menu; Browse. The visual focus indicator for an interactive element (such as a link, button, or form input) is not visible, so sighted people who use a keyboard to navigate content will not know when that element is receiving |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | Web: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. Authored Content: Authors can ensure that content meets this criterion. |
| 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. Authored Content: Authors can ensure that content meets this criterion. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | Web: The size of the target for each clickable control 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. Authored Content: Authors can ensure that most content meets this criterion. Exceptions include: Mul |
| 3.1.2 | Language of Parts | AA | Supports | Web: Changes of language for passages or phrases can be programmatically determined. Authored Content: Authors can set the language for individual phrases within content. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order. Authored Content: Navigational mechanisms are repeated in the same relative order in a set of pages. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Components with the same functionality are identified consistently. Authored Content: Authors can ensure that components with the same functionality are identified consistently in a set of pages. |
| 3.3.3 | Error Suggestion | AA | Supports | Web: Where input errors are automatically detected suggestions for correction are provided to the user. Authored Content: Authors can provide suggestions for correction of automatically detected input errors. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | 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. Authored Content: Authored content does not contain legal or financial data and does not modify user-controllable data. |
| 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. Authored Content: Authors can ensure that content meets this criterion. |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: Most status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include: 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 on the following pages: Native authoring (Project da.live); List View. Authored Content: Authors can ensure that most content meets this criterion. Exceptions include: Some status messages are not a |
| 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 |
| 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. Exceptions include: As noted in 1.3.1 Info and Relationships |
| 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.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 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 | - | 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.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.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.3.1 Error Identification As noted in 4.1.2 Name, Role, Value As noted in 4.1.3 Status Messages Authored Content: Authors can create content in which most functions can be used without vision. Exceptions include: As noted |
| 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.1 Info and Relationships As noted in 1.3.2 Meaningful Sequence As noted in 1.4.1 Use of Color As noted in 1.4.3 Contrast (Minimum) As noted in 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 2.1.1 Keyboard As noted in 2.4.3 Focus Order As noted in 2.4.6 Headings and Labels As noted in 2.4.7 Focus Visible As noted in 3.3.1 Error Identification As note |
| 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 As noted in 3.3.1 Error Identification Authored Content: Authors can create content which is functional for users without perception of color. Exceptions include: As noted in 1.4.3 Contrast (Minimum) As noted in 1.4.11 Non-Text Contrast |
| 4.2.4 | Usage without hearing | - | Supports | Web: The product is functional for users without hearing. Authored Content: Authors can create content which is functional for users without hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Web: The product is functional for users with limited hearing. Authored Content: Authors can create content which is functional for users 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. Authored Content: Authors can create content which is functional for users 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.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 4.1.2 Name, Role, Value Authored Content: Authors can create content which is functional with limited manipulation and strength. Exceptions include: As noted in 1.4.13 Content on Hover or Focus As noted in 2.1 |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Web: Most functions of the product are usable by people with limited reach. Exceptions are noted in: As noted in 2.5.3 Label in Name Authored Content: Authors can create content which is functional with limited reach. Exceptions include: As noted in 1.4.13 Content on Hover or Focus 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. Authored Content: 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 are noted in: 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 1.4.5 Images of Text As noted in 1.4.10 Reflow As noted in 2.1.1 Keyboard As noted in 2.4.3 Focus Order As noted in 2.4.4 Link Purpose (in context) As noted in 2.4.6 He |
| 4.2.11 | Privacy | - | Not Applicable | Web: The product does not ask for or display legal, financial, or personal data. Authored Content: Authored content 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 not require speech input for any functionality. All operations can be performed using mouse and keyboard input. The application does not rely on voice commands or speech recognition features. |
| 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 | - | Does Not Support | The product does not provide closed caption playback. Examples include: Sample Blocks - Video |
| 7.1.2 | Captioning synchronization | - | Not Applicable | The product does not display closed captions. |
| 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 | - | Not Applicable | The product does not display closed captions. |
| 7.1.5 | Spoken subtitles | - | Not Applicable | The product does not contain video that has synchronized audio. |
| 7.2.1 | Audio description playback | - | Does Not Support | The product does not provide a mechanism to select and play closed audio description. Examples include: Sample Blocks - Video |
| 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. |
| 11.6.1 | User control of accessibility features | - | Not Applicable | The product is not platform software. |
| 11.6.2 | No disruption of accessibility features | - | Not Applicable | The product does not disrupt platform accessibility features. |
| 11.8.3 | Preservation of accessibility information in transformations | - | Not Applicable | The product does not provide restructuring transformations or re-coding transformations. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product does not have accessibility checking functionality. |
| 11.8.5 | Templates | - | Not Applicable | The product does not provide templates for authored content. |
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.