ACR Index Get a draft ACR

Accessibility Conformance

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 these exceptions:
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 one exception: 1. On the Assign to Someone Else dialog, the remaining characters counter is not programmatically associated with the "Provide a reason" textarea. Field Groupings Indication: Most field groupings are programmatically indicated with one exception: 1. On the Drawing dialog, the color and pen width controls in the toolbar are not programmatically indicated. Semantic Markup Used for Headings: Most headings are implemented with semantic markup with these exceptions: 1. On the freeform signing page, text appears as a visual heading but is not marked up as such. 2. On the Agreement dialog, text appears as visual headings but are not marked up as such. 3. On the Thumbnails dialog, text appears as a visual heading but is not marked up as such.
1.3.2 Meaningful Sequence A Partially Supports Most content is presented in the correct reading order with these exceptions: 1. When the Comments dialog is open, content behind the dialog is reachable by screen readers causing content to be read out of sequence. 2. When the Supplemental File dialog is open, content behind the dialog is reachable by screen readers causing content to be read out of sequence. 3. On the Drawing dialog, the color palette buttons are announced twice in browse mode.
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 one exception: 1. On the Drawing dialog, color is the only visual cue used to indicate the color of the color palette buttons.
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:
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 user journeys tested did not have character key shortcuts.
2.2.1 Timing Adjustable A Supports When the session timeout occurs, users are allowed to extend the session by selecting the “Continue” button on the session timeout dialog.
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 titles for both regular signing and freeform signing are insufficiently descriptive.
2.4.3 Focus Order A Partially Supports 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. When signing a document that has grouped checkboxes, in some cases, keyboard focus may not be intuitive. 2. On the Adopt Stamp dialog, the input field used for uploading files receives keyboard focus but it is visually hidden and not interactive. 3. Focus is not maintained within the Supplemental File modal dialog. 4. On the Drawing dialog, the <canvas> element receives keyboard focus but it is not interactive.
2.4.4 Link Purpose (In Context) A Supports The purpose of all links can be determined from its link text alone or when combined with its 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 Comments dialog, the accessible name for the "All Recipients" button is "who can see this".
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 language selected.
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 on both the regular signing and freeform signing 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 Visible labels or instructions are provided for input fields with these exceptions: 1. In the Comments dialog, the "Write a comment" and “Write a reply” textareas do not have a visible label. 2. On the freeform signing page, the date signed, name and checkbox fields do not have a visible label. 3. On the freeform signing page, instructions indicating the fields placed on the document can be repositioned with the arrow keys are not provided.
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.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 live 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 Supports The contrast ratio between text and its background color meets the minimum contrast requirement.
1.4.4 Resize Text AA Partially Supports Most of the text can be scaled up to 200% without a loss of content and functionality with one exception: 1. Some footer content is removed from the view.
1.4.5 Images of Text AA Supports The Docusign logo is the only image that contains text in Signing. 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 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 one exception: 1. Some footer content is removed from the view.
1.4.11 Non-text Contrast AA Partially Supports Controls, control states, and graphical objects meet the 3:1 contrast requirement with one exception: 1. On the freeform signing page, the resizing controls on the corners of the signature and text fields 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 one exception: 1. When signing a document, applying the text spacing requirements results in text being truncated in the Note field.
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 Signing 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 one exception: 1. On the Drawing dialog, the "CLEAR ALL" button label is insufficiently descriptive.
2.4.7 Focus Visible AA Partially Supports Most interactive elements have a visible focus indicator when they receive keyboard focus with these exceptions: 1. On the Agreement dialog, the “X” close button does not have a visible focus indicator when it receives keyboard focus. 2. On the Adopt Stamp dialog, when the user uploads an image, the zoom control does not have a visible 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 Supports The target size for pointer inputs is at least 24 by 24 CSS pixels.
3.1.2 Language of Parts AA Does Not Support Changes in language occur in the language selector menu. When the language of the menu item differs from the default language of the page, that language is not set via the lang attribute on the container of the menu item.
3.2.3 Consistent Navigation AA Supports Repeated navigation components occur in the same relative order visually and programmatically on both the regular signing and freeform signing pages.
3.2.4 Consistent Identification AA Supports Meaningful icons, functional images, links, or buttons that are repeated across both the regular signing and freeform signing pages 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 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 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 one exception: 1. When signing a document, if the user selects the "Finish" button before the required fields have been completed, a status message indicating the number of required fields remaining appears at the top of the page. This visible status message is apparent to sighted users, but not announced to people using a screen reader.

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 Not stated. 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.