Adobe Acrobat Sign
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
- 14
- Partially supports
- 14
- Does not support
- 1
- Not applicable
- 2
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 8
- Partially supports
- 15
- Does not support
- 0
- Not applicable
- 1
- Not evaluated
- 0
Source: View the original report published by Adobe.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (101)
| 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: Share / Unshare Agreement modal; Send page - Document uploaded; Delegate agreement modal; Add A Reminder Modal; Send in Bulk-Upload(Add recipients section); Track this agreement page. A decorative image is not hidden from a |
| 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 | Partially Supports | Web: The product contains audio content in media and closed captions are provided for most instances. Exception includes: Captions are not provided for media that includes audio and video, so the information provided by the audio track is not available to people who are deaf or hard of hearing. This occurs on the following page: Workflows page. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Web: The product provides audio description for prerecorded video. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Web: Most visual structure and relationship information is provided through semantics. 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: Track this agreement page. Some content that is visually presented as a list is not properly marked up as a list, so the structures of those lists are n |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions include: The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: New Authoring Page; E-Sign Documents Page; Track this agreement page. 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 hea |
| 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 in the following component: Right pane (New authoring page) and following pages: Manage; E-Sign Documents Page; Admin - Global Settings. Color is used as the only method to convey information so that information will not be available to people w |
| 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 in the following component: Left pane (New authoring page) and following pages: Document properties modal; Admin - Global Settings; New Authoring Page; Track this agreement page; Manage; Add A Reminder Modal; E-Sign Documents Page; Reports. |
| 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 | Supports | Web: The product supports the adjustment or cancellation of time-based limits. |
| 2.2.2 | Pause, Stop, Hide | A | Partially Supports | Web: On most pages, where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. Exceptions include: The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs in the following component: Left pane (New authoring page). The user cannot pause, stop, or hide moving or blinking |
| 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: Send page - Document uploaded; New Authoring Page; Workflows page; Send in Bulk-Upload(Add recipients section); Review and Sign email; Send page - default view; Send successful. |
| 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: Manage. Keyboard focus or touch screen swiping goes to multiple elements that are hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs in the following component: Header (Post Login) an |
| 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. Exceptions include: The purpose of multiple links is not made clear by each link's text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where each link goes. This occurs in the following component: Header (Post Login) and following pages: Home; E-Sign Documents Page; Send in Bulk-Upload(Add recipients section). |
| 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: Add A Reminder Modal; Admin - Global Settings; Confirmation to Sign. The accessible name of multiple interactive elements (such as links, buttons, or |
| 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 a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriente |
| 3.2.6 | Consistent Help | A | Supports | Web: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order. |
| 3.3.1 | Error Identification | A | Partially Supports | Web: Most input errors are identified and described to the users in text. Exception includes: 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 in the following component: Left pane (New authoring page) and following pages: Send page - Document uploaded; Add A Reminder Modal; Share / Unshare Agreement modal. |
| 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: Send in Bulk-Upload(Add recipients section); E-Sign Documents Page; Share / Unshare Agreement modal; Manage; Request e-Signatures modal; e-Signature. 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: Login; Cancel Modal; Share / Unshare Agreement modal; Delegate agreement modal. Select or dropdown |
| 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: Add A Reminder Modal; Share / Unshare Agreement modal. An element functions as if it has two programmatic roles, so one or both roles may be incorrectly conveye |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Web: The product provides audio description for prerecorded video. |
| 1.3.4 | Orientation | AA | Supports | Web: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Partially Supports | Web: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Exception includes: No programmatic purpose is provided for an input element (like a text input field), so browsers or assistive technology are not able to automatically suggest information to fill in the input. This occurs on the following page: Login. |
| 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 (or less than 3:1 for large text), so people who are colorblind or have low vision may have difficulty reading the text. This occurs in the following component: Header (Post Login) and following pages: Individual Documents modal; Admin - Global Settings. 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 in the following compo |
| 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: Review and Sign email; Send page - Document uploaded; Add A Reminder Modal; Track this agreement page; E-Sign Documents Page. 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 t |
| 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 pages: Login; E-Sign Documents Page; Track this agreement page; New Authoring |
| 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 does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following pages: |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: Most meaningful non-text content elements have sufficient contrast. Exceptions include: The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs in the following component: Right pane (New authoring page) and following pages: Login; E-Sign Documents Page; Cancel Modal; e-Signature; New Authoring Page; Workflows page; Share / Unshare Agreement modal; Admin - Global |
| 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 page: Home. |
| 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 in the following component: Header (Post Login) and following pages: E-Sign Documents Page; Workflows page. Content that appears on mouse hover (such as tooltips, drop-down menu |
| 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 in the following component: Left pane (New authoring page) and following pages: Send page - Document uploaded; Recipient Group modal; Reports; Send in Bulk-Upload(Add recipients section); Manage. Multiple programmatic labels for controls or form |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs in the following components: Right pane (New authoring page); Left pane (New authoring page) and following pages: e-Signature; Recipients modal; E-Sign Documents Page. The visual focus indicator for multiple interactive elements (such as links, buttons, or form inputs) is not |
| 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. |
| 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 in the following component: Left pane (New authoring page) and following pages: Send page - default view; Send page - D |
| 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. Exception includes: 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: Portions of content on multiple pages that are in a different language from the rest of the content on the page are not programmatically assigned the language for the portion of content, so screen readers may mispronounce those parts of the content. This occurs in the following components: Header (Post Login); Header (Pre Login) and following page: E-Sign Documents Page. |
| 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 | Partially Supports | Web: Where input errors are automatically detected, suggestions for correction are provided to the user in most cases. Exception includes: A form field's error message does not suggest how to correct the error, so users may have difficulty determining how to complete the form successfully. This occurs on the following page: Send page - Document uploaded. |
| 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 | Partially Supports | Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptionsincludes: 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: Left pane (New authoring page) and following pages: Send page - Document uploaded; Manage; Cancel Modal; Recipient Group modal; Send in Bulk-Upload(Add recipien |
| 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 | - | Does Not Support | Web: The multimedia player does not provide closed caption controls. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | Web: The product does not contain media with a video component that offers audio descriptions controls. |
| 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.2 Pause, Stop, Hide 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 3.3.3 Error Suggestion As noted in 4.1.2 Name, Role, Value As note |
| 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.3.5 Identify Input Purpose As noted in 1.4.1 Use of Color As noted in 1.4.3 Contrast (Minimum) As noted in 1.4.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.2 Pause, Stop, Hide 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 |
| 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 1.2.2 Captions (Prerecorded) As noted in 2.2.2 Pause, Stop, Hide |
| 4.2.5 | Usage with limited hearing | - | Partially Supports | Web: Most functionality is usable with limited hearing. Exceptions include: As noted in 1.2.2 Captions (Prerecorded) As noted in 2.2.2 Pause, Stop, Hide |
| 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.2 Pause, Stop, Hide 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.2 Pause, Stop, Hide 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. |
| 7.1.1 | Captioning playback | - | Does Not Support | Web: The product does not display closed captions. Example includes: Workflows page (Video) |
| 7.1.2 | Captioning synchronization | - | Not Applicable | Web: The product does not support closed captions. |
| 7.1.3 | Preservation of captioning | - | Not Applicable | Web: The product does not transmit, convert, or record video with synchronized audio. |
| 7.1.4 | Captions characteristics | - | Not Applicable | Web: The product does not support closed captions. |
| 7.1.5 | Spoken subtitles | - | Not Applicable | Web: The product does not support closed captions. |
| 7.2.1 | Audio description playback | - | Does Not Support | Web: The product does not provide a mechanism to select and play audio description. Example includes: Workflows page (Video) |
| 7.2.2 | Audio description synchronization | - | Not Applicable | Web: The product does not have a mechanism to play audio description. |
| 7.2.3 | Preservation of audio description | - | Not Applicable | Web: The product does not transmit, convert, or record video with synchronized audio. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated January 2026. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.