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
- 19
- Partially supports
- 9
- Does not support
- 0
- Not applicable
- 4
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 14
- Partially supports
- 5
- Does not support
- 2
- Not applicable
- 3
- 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 | Most non-text content, including complex and functional images, have meaningful text equivalents. Most decorative images are ignored by screen readers. Exceptions: ● The progress step controls within the "Welcome to Docusign CLM" dialog are functional images without a text alternative. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | The web application does not contain prerecorded audio-only nor video-only content. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | The web application does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | The web application does not contain prerecorded synchronized media. |
| 1.3.1 | Info and Relationships | A | Partially Supports | In most instances, information and structural relationships can be determined programmatically from the content. Exceptions: ● Documents are displayed as images of text; their information and structural relationships cannot be programmatically determined. ● Visually highlighted text within a document is not perceivable by assistive technology. This includes highlighted text associated with user comments and in-document text search. ● Visual headings are not always defined as headings. ● Related items are not always defined as lists. ● Visual groupings within menus are not always defined. ● In the search results table, checkboxes to select files or folders are not programmatically associated with the file or folder name. ● On the search results page, the “# Selected” checkbox has a tooltip that is not programmatically associated with the checkbox. |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | The reading sequence is meaningful throughout the web application, except when some dialogs are open. Content in the background is not hidden from assistive technology for the following dialogs: ● The “Welcome to Docusign CLM” modal ● Search filters |
| 1.3.3 | Sensory Characteristics | A | Supports | The web application does not rely on sensory characteristics for instructions. |
| 1.4.1 | Use of Color | A | Supports | Color is not used as the sole means to convey information, indicate an action, prompt a response, or distinguish a visual element. |
| 1.4.2 | Audio Control | A | Supports | The web application does not contain any audio which plays automatically for more than 3 seconds. |
| 2.1.1 | Keyboard | A | Partially Supports | In most instances, interactive elements receive keyboard focus and are keyboard-operable. Exceptions: ● Keyboard users cannot select text in documents or trigger the context menu that contains the “copy” and “comment” actions. ● The buttons to remove search history items are neither focusable or keyboard-operable. ● The progress step controls within the "Welcome to Docusign CLM" dialog are neither focusable or keyboard-operable. ● The tooltip for the “# Selected” checkbox that appears when multiple files or folders are selected on the search results page cannot be triggered with keyboard focus. |
| 2.1.2 | No Keyboard Trap | A | Supports | There are no keyboard traps in the web application. Focus can be moved away from each control using only a keyboard interface. |
| 2.1.4 | Character Key Shortcuts | A | Supports | The web application does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Supports | The web application does not feature time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | The web application does not display content that moves, blinks, scrolls, or auto-updates. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | The web application does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Supports | The web application contains a “skip link” to bypass the header navigation content. |
| 2.4.2 | Page Titled | A | Supports | All web pages have titles that describe their topic or purpose. |
| 2.4.3 | Focus Order | A | Partially Supports | In most cases, elements that receive focus are presented in a logical order that honors the presentation and preserves meaning. In most cases, focus is properly managed. Exceptions: ● Some menus found in the header incorrectly force focus inside the popup when content is revealed. ● Focus is not always moved to the newly added content. This applies to: ○ The sidebar panels in the document preview, such as “Details”, “Add Reminder”, and “Tasks” ○ The “Welcome to Docusign CLM” modal content ● Focus is not properly moved into some dialogs and keyboard focus is not properly contained within some dialogs |
| 2.4.4 | Link Purpose (In Context) | A | Supports | The purpose of each link can be determined from the link text alone or from the link text |
| 2.5.1 | Pointer Gestures | A | Supports | All functionality can be operated using a single pointer. There are no path-based or multi-point gestures within the web application. |
| 2.5.2 | Pointer Cancellation | A | Supports | All single-pointer 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 | Partially Supports | In most cases, the accessible name of components contain the text that is presented visually. Exceptions: ● The search filter dialogs that appear on the search results page, such as “Expiration Date” and “Party”, all have the accessible name of “Filter Menu” instead of the visible label and dialog heading. ● The visually labelled “Change” button that triggers a dialog on the search results page has the accessible name “Open Results Settings Dialog”. |
| 2.5.4 | Motion Actuation | A | Not Applicable | The web application does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | The human language of each page can be programmatically determined. |
| 3.2.1 | On Focus | A | Supports | User interface components do not initiate a change of context when they receive focus. |
| 3.2.2 | On Input | A | Partially Supports | In most cases, the web application does not cause an unexpected change of context when interacting with elements. Exception: ● On the search results page, when a user selects a document or folder in the table, the search bar and filters above the table are replaced by new controls to perform actions on the current selection. |
| 3.2.6 | Consistent Help | A | Supports | Help mechanisms, where provided on multiple pages, appear in the same order relative to other content on the page. |
| 3.3.1 | Error Identification | A | Supports | Input errors are identified when the user submits each form, and the errors are described to the user in text. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | In most cases, labels or instructions are provided and visible for all form fields. Exceptions: ● The search field contains placeholder text in place of visible instruction text. |
| 3.3.7 | Redundant Entry | A | Supports | The web application does not require information previously entered to be entered again. |
| 4.1.1 | Parsing | A | Supports | For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. For WCAG 2.2, this success criterion is obsolete and removed. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | The web application provides the correct name, role, state, and other important accessibility information for most of its controls. These properties are properly associated and available on controls for users who rely on assistive technology. Exceptions: ● The “Help” and user avatar popups are incorrectly implemented as ARIA menus instead of ARIA disclosures. ● The “Actions” menu does not programmatically indicate its ARIA collapsed state. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | The web application does not contain synchronized media with live audio content. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | The web application does not contain any prerecorded synchronized media. |
| 1.3.4 | Orientation | AA | Supports | Content does not restrict its view and orientation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Supports | All form fields in the web application that collect user input identify their purpose. |
| 1.4.3 | Contrast (Minimum) | AA | Supports | Text has sufficient contrast against its background. |
| 1.4.4 | Resize Text | AA | Partially Supports | When content is scaled up to 200%, there is a loss of the following content and functionality: |
| 1.4.5 | Images of Text | AA | Supports | Documents are presented as images of text. This presentation is considered essential to support the document viewer functionality. |
| 1.4.10 | Reflow | AA | Does Not Support | When content is set to a width of 320 CSS pixels, one or more of these three issues frequently occur: ● There is a loss of information ● There is a loss of functionality ● The layout requires horizontal scrolling |
| 1.4.11 | Non-text Contrast | AA | Supports | All interface components and graphical objects have a contrast ratio of at least 3:1. |
| 1.4.12 | Text Spacing | AA | Supports | The web application allows for relevant text style properties to be changed without a loss of content or functionality. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Content that appears on hover or focus is dismissible, hoverable, and persistent. |
| 2.4.5 | Multiple Ways | AA | Supports | The web application in scope operates primarily as a document explorer and viewer with associated tasks. The application |
| 2.4.6 | Headings and Labels | AA | Partially Supports | In most cases, headings and labels are descriptive throughout the web application. Exceptions: ● In the “All Filters” dialog, the labels of the controls to star and unstar filters do not include the name of the filter they apply to. ● In the “Choose Users” dialog, the button to sort users by name does not describe whether the sorting order is ascending or descending. This modal is displayed when assigning or reassigning tasks. |
| 2.4.7 | Focus Visible | AA | Partially Supports | There is one instance where a keyboard operable user interface component did not provide a visible keyboard focus indicator: ● The button to change the user account on the “Log In” page |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Partially Supports | In most cases, when interactive elements receive keyboard focus, the focused element is not obscured or entirely hidden. Exceptions: ● When navigating to a document from the “Tasks” page, the collapsable “Tasks” panel will be open automatically. Depending on the width of the viewport, this panel obscures or entirely hides the following elements when focused: ○ The document page navigation and zoom controls ○ Focusable text in the document associated with user comments |
| 2.5.7 | Dragging Movements | AA | Does Not Support | The web application contains one instance where functionality is operated with dragging movements. Dragging is used to reorder columns in the “Columns” dialog found on the search results page. This functionality is not operable with a single pointer. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | The target size of pointer inputs is at least 24 by 24 CSS pixels. |
| 3.1.2 | Language of Parts | AA | Supports | The human language of each passage or phrase in the content can be programmatically determined. |
| 3.2.3 | Consistent Navigation | AA | Supports | Navigational mechanisms that are repeated on multiple pages within a set of pages occur in the same relative order each time they are repeated. |
| 3.2.4 | Consistent Identification | AA | Supports | Components that have the same functionality within a set of pages are identified consistently. |
| 3.3.3 | Error Suggestion | AA | Supports | For all automatically detected input errors where suggestions for correction are known, the suggestions are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | The web application does not contain pages that cause legal commitments or financial transactions, modify, or delete user-controllable data in a data storage system, or submit user test responses. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | The web application does not require a cognitive function test for any steps. |
| 4.1.3 | Status Messages | AA | Partially Supports | In most instances, status messages can be programmatically determined and do not require focus. Exceptions: ● In the “Tasks” panel of a document, when a user attempts to complete a task without the required fields, errors are not communicated to screen reader users without the fields 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.