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
- 15
- Partially supports
- 6
- Does not support
- 1
- Not applicable
- 10
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 14
- Partially supports
- 2
- Does not support
- 1
- Not applicable
- 7
- 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 Participant Experience does not contain audio-only or video-only content. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | The Participant Experience does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | The Participant Experience does 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. |
| 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 Participant Experience. |
| 1.4.1 | Use of Color | A | Supports | Where color is used to convey meaning, that same meaning is conveyed with another visual cue. For example, completed tasks are |
| 1.4.2 | Audio Control | A | Not Applicable | The Participant Experience does 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 these exceptions: 1. On the Task page, the message buttons are not keyboard accessible. 2. On the Upload Request dialog, the Escape key does not close the “Upload Documents” and “Document actions” menus. 3. On the Upload Request dialog, the options in the “Document actions” menu are not keyboard accessible. 4. On the View dialog, the pages in the document cannot be scrolled with the keyboard alone. |
| 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 interactive elements without the focus being trapped. |
| 2.1.4 | Character Key Shortcuts | A | Supports | The Participant Experience does not have character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | The Participant Experience does not contain time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | The Participant Experience does not contain moving, blinking, scrolling, or auto-updating content. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | The Participant Experience does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Not Applicable | The Participant Experience does not contain blocks of content that repeat across multiple pages. |
| 2.4.2 | Page Titled | A | Does Not Support | The Participant Experience page title is not sufficiently descriptive. |
| 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 most cases, focus is properly managed with these exceptions: 1. On the Task page, in the Messages region, when a user activates a message button and the message content loads, focus is not moved to the added content, and nothing is announced to screen reader users. 2. When the user activates the “Save” button on the “Upload Request” dialog |
| 2.4.4 | Link Purpose (In Context) | A | Partially Supports | In the View dialog, when the PDF document being viewed contains links, the purpose of the links is not defined. |
| 2.5.1 | Pointer Gestures | A | Supports | The Participant Experience does 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 Participant Experience does 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 | Supports | When users enter input or change the settings of interactive elements, a change of context does not occur. |
| 3.2.6 | Consistent Help | A | Not Applicable | The Participant Experience does 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 | Supports | Visible labels or instructions are provided for input fields. |
| 3.3.7 | Redundant Entry | A | Supports | The Participant Experience does 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 user is notified of state and property changes, with these exceptions. 1. On the Task page, in the Messages region, when creating a new message, the Messages textarea does not have an accessible name. 2. On the Upload Request dialog, the Help control in the banner is implemented as a button when it should |
| 1.2.4 | Captions (Live) | AA | Not Applicable | The Participant Experience does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | The Participant Experience does 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 Participant Experience does not contain input fields that collect information about the user. |
| 1.4.3 | Contrast (Minimum) | AA | Supports | The contrast ratio between text and its background color meets the minimum contrast requirement. |
| 1.4.4 | Resize Text | AA | Supports | When content is scaled up to 200%, a loss of content or functionality does not occur. |
| 1.4.5 | Images of Text | AA | Does Not Support | In the View dialog, the document pages are rendered as images, so the content in the |
| 1.4.10 | Reflow | AA | Partially Supports | When content is set to a width of 320 CSS pixels, most content is presented without a loss of information or functionality, and without requiring horizontal scrolling, with these exceptions: 1. When the Upload Request dialog is magnified to 400%, the name of the Upload Request and the names of the files that have been uploaded are truncated with an ellipsis. 2. When the View dialog is magnified to 400%, the PDF content displayed decreases in size. |
| 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 | The Participant Experience is a single web page, so it does not require more than one method of navigating to other web pages. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Most headings and labels are clear and descriptive, with these exceptions: 1. In the footer of the task page, the language selector does not have a visible label or an accessible name. 2. On the Upload Request dialog, there are multiple “Sign”, “View”, and “Document actions” buttons, but the accessible names of these buttons are not unique. 3. On the Task page, in the Messages region, when the user activates the “Messages Members” button, a heading of “Participants” appears at the top of the region, creating a disjointed experience. |
| 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 | Not Applicable | The Participant Experience does not contain drag-and-drop controls. |
| 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 | The Participant Experience 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 | Supports | Error suggestions are provided for all fields that require them and clearly describe how to correct the error. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | The Participant Experience does 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 | The Participant Experience does not contain an authentication process. |
| 4.1.3 | Status Messages | AA | Supports | Status messages are provided and are programmatically determined through role or properties and announced by assistive technologies without receiving focus. |
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.