ACR Index Accessibility Conformance Reports for software

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.

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)

Conformance as stated by DocuSign in its published report.
CriterionNameLevel ConformanceRemarks 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: Most field error messages and field descriptions are programmatically associated with input fields, with these exceptions: 1. On the "Upload Profile Photo" dialog launched from the Home page, instructions that appear above the "Upload" button are not programmatically associated with the button. 2. On the Prepare page, if “Other” is selected in the “Envelope Type” select list, a "Envelope Types" input field is added to the page. The instruction text that appears below the “Envelope Types” input field is not programmatically associated with the field. Field Groupings Indication: Most field groupings are programmatically indicated, with these exceptions: 1. On the Create Your Signature dialog launched from the Home page, the signature style radio button grouping is not programmatically indicated. 2. On the Bulk Send dialog launched from the Prepare page, the radio button grouping for the upload method is not programmatically indicated.
1.3.2 Meaningful Sequence A Supports When the sequence in which content is presented affects its meaning, content is presented in the correct reading order.
1.3.3 Sensory Characteristics A Supports In the user journeys tested, references to shape, size, visual location, orientation, or sound were not found.
1.4.1 Use of Color A Partially Supports Where color is used to convey meaning, that same meaning is conveyed with another visual cue, with these exceptions: 1. On the Agreement Template Builder page, color is the only visual cue used to indicate the color of the color palette buttons in the font color menu. 2. On the Agreement Details page, color alone is used to distinguish links and buttons from other non-interactive text.
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 these exceptions: 1. On the Add Fields page, the draggable controls for the collapsible Smart Sections are not keyboard operable. 2. On the Add Fields page, the “+” control used for adding additional checkboxes or radio buttons to a group is not keyboard operable. 3. On the Agreement Template Builder page, the Rule Builder functionality is not keyboard operable. 4. On the Agreement Template Builder page, the toolbar controls are not keyboard operable.
2.1.2 No Keyboard Trap A Partially Supports When using a keyboard alone and when using a keyboard with a screen reader, the user can move keyboard focus to and from most interactive elements without the focus being trapped, with one exception: 1. On the Add Fields page, when there are no fields placed on the document and the keyboard user tries to navigate to the Documents panel using the tab key, keyboard focus becomes trapped in the document.
2.1.4 Character Key Shortcuts A Supports The user journeys tested did not have character key shortcuts.
2.2.1 Timing Adjustable A Supports When the session timeout occurs, users can extend the session by selecting the “Continue” button on the session timeout dialog.
2.2.2 Pause, Stop, Hide A Does Not Support On the Add Fields page, if a user attempts to send an envelope without placing fields on the document, a dialog appears showing a continuously looping animation with no mechanism to pause, stop, or hide it.
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 Supports The Sender Experience provides a method to bypass the header navigation content.
2.4.2 Page Titled A Does Not Support The Sender Experience page titles are insufficiently descriptive.
2.4.3 Focus Order A Partially Supports Focus Order: In most cases, the focus order of interactive elements is logical and intuitive, and in a sequence that preserves meaning and operability, with these exceptions: 1. On the Bulk Send folder view of the Agreements page, the Batch Name buttons receive keyboard focus twice. 2. On the Prepare page, if the “Other” option is selected in the “Envelope Type” select list, a "Envelope Types" input field is added to the page, and the logical focus order is disrupted.
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 Partially Supports Most accessible names for interactive elements include the visible label, with one exception: 1. On the Sharing dialog launched from the Templates page, the accessible name for the "Search Type" does not 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 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 Supports A self-help option is provided and occurs in the same order in the Sender Experience.
3.3.1 Error Identification A Supports Field input errors are clearly described in text.
3.3.2 Labels or Instructions A Partially Supports Visible labels or instructions are provided for input fields with these exceptions:
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 user is notified of state and property changes, with these exceptions. 1. In the header, the navigation controls have an incorrect ARIA role. Additionally, the profile button has an incorrect ARIA role and an insufficient accessible name. 2. On the Agreement Template Builder page: a. The toolbar container has an incorrect ARIA role. b. The selected state for the line spacing control in the toolbar is not announced. c. The color buttons in the toolbar lack an accessible name. d. The font size control in the toolbar has an incorrect ARIA role. e. On the Dropdown field dialog, the "Select Signer" menu button has an insufficient accessible name. f. Within the Rule Builder, the “remove condition” and the accordion buttons have
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 In most cases, the contrast ratio between text and its background color meets the minimum contrast requirement, with one exception: 1. On the Prepare page, the error text for several input fields does not meet the minimum contrast requirement.
1.4.4 Resize Text AA Partially Supports When content is scaled up to 200%, the following areas have a loss of content or functionality: 1. The "Get Started or Use Templates" section on the Home page. 2. The navigation panel on the Agreements page. 3. The Advanced Options dialog launched from the Prepare page. 4. The envelope header and document region on the Add Fields page.
1.4.5 Images of Text AA Supports The Docusign logo is the only image that contains text in the Sender Experience. 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 content or functionality, or horizontal scrolling is required on all pages in Sender Experience.
1.4.11 Non-text Contrast AA Partially Supports Controls, control states, and graphical objects meet the 3:1 contrast requirement with these exceptions: 1. On the Add Fields page, when configuring conditional fields, the gear icon button on the conditional field banner does not meet the 3:1 contrast requirement. 2. On the Agreement Template Builder page, some color palette buttons in the font color menu do not meet the 3:1 contrast requirement.
1.4.12 Text Spacing AA Partially Supports The text spacing requirements can be applied without resulting in a loss of content or functionality, with these exceptions: 1. On the Agreements page, the placeholder text is obscured in the
1.4.13 Content on Hover or Focus AA Partially Supports Most content that is triggered on hover or keyboard focus meets the dismissible, hoverable, and persistent requirements, with one exception: 1. On the right panel of the Add Fields page, when the "+" button is hovered, the "Add custom field" tooltip that appears is not dismissible or hoverable.
2.4.5 Multiple Ways AA Supports The Sender Experience provides more than one way to navigate to other pages within the site: 1. The navigation links at the top of the pages. 2. The Home page links to all pages
2.4.6 Headings and Labels AA Partially Supports Most headings and labels are clear and descriptive, with these exceptions: 1. On the Agreements page, when a filter is applied to the agreements table, the button label changes to the filter applied, which does not convey the purpose of the filter. 2. On the Add Fields page:
2.4.7 Focus Visible AA Partially Supports Most interactive elements have a visible focus indicator when they receive keyboard focus, with one exception: 1. On the Agreements page, the “Sign” button does not have a visible focus indicator when it receives keyboard focus.
2.4.11 Focus Not Obscured (Minimum) AA Supports When interactive elements receive keyboard focus, the focus indicator is not obscured or entirely hidden.
2.5.7 Dragging Movements AA Does Not Support Drag and drop controls cannot be operated with a single pointer without dragging movements.
2.5.8 Target Size (Minimum) AA Partially Supports In most cases, the target size for pointer inputs is at least 24 by 24 CSS pixels, with one exception: 1. On the Add Fields page, if additional radio buttons and checkboxes are added to the document, they do not meet the minimum requirements for target size or spacing.
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 Supports Repeated navigation components occur in the same relative order visually and programmatically throughout the Sender Experience.
3.2.4 Consistent Identification AA Supports Meaningful icons, functional images, links, or buttons that are repeated across pages in the Sender Experience 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 user journeys tested did not contain forms that led to legal commitments, financial transactions, modification or deletion of user-controlled data, or submission of test responses.
3.3.8 Accessible Authentication (Minimum) AA Supports The user journeys tested did not require a cognitive function test for any step in the authentication process.
4.1.3 Status Messages AA Partially Supports Status messages are provided and are programmatically determined through role or properties and announced by assistive technologies without receiving focus, with these exceptions: 1. On the Add Fields page, when a user selects the rotate button to rotate a page in the document, a status

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.