Docusign
Accessibility Conformance Report published by DocuSign
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
- 14
- Partially supports
- 7
- Does not support
- 1
- Not applicable
- 10
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 12
- Partially supports
- 2
- Does not support
- 4
- Not applicable
- 6
- Not evaluated
- 0
Source: View the original report published by DocuSign.
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 (56)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Meaningful Images: Most meaningful images have appropriate text alternatives, with one exception: |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | The user journeys tested did not contain audio-only or video-only content. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | The user journeys tested did not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | The user journeys tested did not contain prerecorded synchronized media. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Field Error/Description Association: Field error messages and field descriptions are programmatically associated with input fields, with one exception: 1. In the Rename document modal dialog, the file type extension is not |
| 1.3.2 | Meaningful Sequence | A | Supports | When the sequence in which content is presented affects its meaning, the content is presented in the correct reading order. |
| 1.3.3 | Sensory Characteristics | A | Supports | References to shape, size, visual location, orientation, or sound were not found in the user journeys tested. |
| 1.4.1 | Use of Color | A | Supports | Where color is used to convey meaning, that same meaning is conveyed with another visual cue. |
| 1.4.2 | Audio Control | A | Not Applicable | The user journeys tested did not contain audio content that automatically starts. |
| 2.1.1 | Keyboard | A | Partially Supports | Most interactive elements receive keyboard focus and are keyboard-operable, with some exceptions: 1. In the Request Types table, the links to open each request type are not keyboard focusable nor operable. 2. When the “Start” menu is expanded, keyboard navigation through the menu items and submenus behaves unexpectedly. |
| 2.1.2 | No Keyboard Trap | A | Supports | When using a keyboard alone and when using a keyboard with a screen reader, the user can move keyboard focus to and from all |
| 2.1.4 | Character Key Shortcuts | A | Supports | The user journeys tested did not have character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | The user journeys tested did not contain time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | The user journeys tested did not contain moving, blinking, scrolling, or auto-updating content. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | The user journeys tested did not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Not Applicable | The user journeys tested did not contain blocks of content that repeat across multiple pages. |
| 2.4.2 | Page Titled | A | Does Not Support | The page title is not sufficiently descriptive. It is “Requests | Docusign” at all times. |
| 2.4.3 | Focus Order | A | Partially Supports | Focus Order: The focus order of interactive elements is logical and intuitive, and in a sequence that preserves meaning and operability. Focus Management: In several instances, focus is not managed properly: 1. When activating any sortable column header, the table reloads and keyboard |
| 2.4.4 | Link Purpose (In Context) | A | Supports | The purpose of all links can be determined from their link text alone or when combined with their context. |
| 2.5.1 | Pointer Gestures | A | Supports | The user journeys tested did not contain multipoint or path-based gestures. All functionality can be activated with a single pointer. |
| 2.5.2 | Pointer Cancellation | A | Supports | All functionality is executed on the up event, and a mechanism to cancel or undo the action is provided. |
| 2.5.3 | Label in Name | A | Supports | Accessible names for interactive elements include the visible label. |
| 2.5.4 | Motion Actuation | A | Not Applicable | The user journeys tested did not contain functionality that responds to device or user motion. |
| 3.1.1 | Language of Page | A | Supports | The default language of the page is set via the lang attribute of the <html> element. In addition, when the language of the page is changed via the language selector, the value of the lang attribute is updated to reflect the selected language. |
| 3.2.1 | On Focus | A | Supports | When interactive elements receive keyboard focus, a change of context does not occur. |
| 3.2.2 | On Input | A | Partially Supports | When users enter input or change the settings of interactive elements, a change of context does not occur, with some exceptions: 1. When the value of the “Results per page” select control in the table pagination is changed, the table reloads and keyboard focus unexpectedly moves away from the control. 2. In the Notifications tab in the Settings modal dialog, when toggling the switch |
| 3.2.6 | Consistent Help | A | Not Applicable | The user journeys tested did not contain a help mechanism that occurs on multiple pages. |
| 3.3.1 | Error Identification | A | Supports | Field input errors are clearly described in text. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Correct visible labels or instructions are provided for input fields, with some exceptions: 1. In the Email tab in the Settings modal dialog, a loading icon is incorrectly shown on a button when the form has shown an error. 2. In the Filter dialogs, the operator comboboxes do not have visible labels. 3. In the Share and New Approval modal dialogs, the search fields use placeholder text to provide instructions. |
| 3.3.7 | Redundant Entry | A | Supports | The user journeys tested did not require information previously entered to be entered again. |
| 4.1.1 | Parsing | A | Not Applicable | This criterion has been removed from WCAG 2.2. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | For most user interface components, the name and correct role can be programmatically determined, values, states, and properties can be set by the user, and the |
| 1.2.4 | Captions (Live) | AA | Not Applicable | The user journeys tested did not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | The user journeys tested did not contain prerecorded synchronized media. |
| 1.3.4 | Orientation | AA | Supports | Content is not restricted to a single-screen orientation. |
| 1.3.5 | Identify Input Purpose | AA | Not Applicable | The user journeys tested did not contain input fields that collect information about the user. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | The contrast ratio between text and its background color meets the minimum contrast requirement, with one exception: 1. In the Request Types table, the links in the Name column do not have sufficient contrast in the hover state. |
| 1.4.4 | Resize Text | AA | Does Not Support | When content is scaled up to 200%, a loss of content or functionality occurs across most of the web application's views. |
| 1.4.5 | Images of Text | AA | Supports | The Docusign logo is the only image that contains text in the user journeys tested. Since the text in the logo is part of a brand name, its presentation is essential and considered an exception. |
| 1.4.10 | Reflow | AA | Does Not Support | When content is set to a width of 320 CSS pixels, there is a loss of information or functionality, or horizontal scrolling is required on all pages in Agreement Desk. |
| 1.4.11 | Non-text Contrast | AA | Supports | Controls, control states, and graphical objects meet the 3:1 contrast requirement. |
| 1.4.12 | Text Spacing | AA | Supports | The text spacing requirements can be applied without resulting in a loss of content or functionality. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Content that is triggered on hover or keyboard focus meets the dismissible, hoverable, and persistent requirements. |
| 2.4.5 | Multiple Ways | AA | Supports | Agreement Desk is a single web page, so it does not require more than one method of navigating to other web pages. Modal dialogs opened from the main Requests page are used to navigate to content. |
| 2.4.6 | Headings and Labels | AA | Supports | Headings and labels are clear and descriptive. |
| 2.4.7 | Focus Visible | AA | Supports | Interactive elements have a visible focus indicator when they receive keyboard focus. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | When interactive elements receive keyboard focus, the focused element is not obscured or entirely hidden. |
| 2.5.7 | Dragging Movements | AA | Does Not Support | There is one instance of dragging movements. To reorder statuses in the Statuses tab in the Settings modal dialog, the drag and drop controls cannot be operated with a single pointer without dragging movements.. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | The target size for pointer inputs is at least 24 by 24 CSS pixels. |
| 3.1.2 | Language of Parts | AA | Supports | Changes in language are programmatically defined using the lang attribute on the containing element or its parent. |
| 3.2.3 | Consistent Navigation | AA | Not Applicable | Agreement Desk is a single web page and does not have repeated navigation components. |
| 3.2.4 | Consistent Identification | AA | Supports | Meaningful icons, functional images, links, or buttons that are repeated are consistently identified. |
| 3.3.3 | Error Suggestion | AA | Partially Supports | Error suggestions are provided for all fields that require them and clearly describe how to correct the error, with one exception: 1. In the Email tab in the Settings modal dialog, when attempting to save an invalid email address, the toast message does not clearly describe the error and expected format. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | The user journeys tested did not contain forms that lead to legal commitments, financial transactions, modification or deletion of user-controlled data, or submission of test responses. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Not Applicable | Agreement Desk does not contain an authentication process. |
| 4.1.3 | Status Messages | AA | Does Not Support | Most status messages are not programmatically determined through role or properties and are not announced by assistive technologies without receiving focus. 1. In the Request Types table, a status message is not announced when setting a default. 2. In the Statuses tab in the Settings modal dialog, a status message is not |
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.