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 these exceptions: 1. In the Map field component, the “Back” arrows in the dropdowns.
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 Send an Email dialog, the error messages for the Subject, Headline and Body text fields are not programmatically associated with the fields.
1.3.2 Meaningful Sequence A Partially Supports When the sequence in which content is presented affects its meaning, the content is
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 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 these exceptions: 1. On the canvas page, mouse dragging is required to change the position of the workflow tree and cannot be moved with the keyboard. 2. On the Add Workflow start dialog, the “Select a Method” combobox cannot be operated with a keyboard.
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 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 can extend the session by selecting the Continue button on the session timeout dialog.
2.2.2 Pause, Stop, Hide A Partially Supports The edges of the blue dot that appears when a workflow is completed pulses. Users cannot pause, stop or hide the dot until they close the dialog.
2.3.1 Three Flashes or Below Threshold A Supports The edges of the blue dot that appears when a workflow is completed d oes not pulse more than three times in any one second period.
2.4.1 Bypass Blocks A Supports Maestro provides a method to bypass the header navigation content.
2.4.2 Page Titled A Does Not Support Maestro 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 Workflows page, after clearing the “Search” field or removing a “Filter”
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 these exceptions: 1. On the canvas notification banner, the “View Guide” control has an accessible
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 Maestro.
3.3.1 Error Identification A Partially Supports Field input errors are clearly described in text, with this one exception:
3.3.2 Labels or Instructions A Partially Supports Visible labels or instructions are provided for input fields with these exceptions: 1. On the Workflows page, the results per page control lacks a visible label. 2. In the Add a Step listbox, the “Add the next step after this” field lacks a persistent visible label. 3. On the Set Up Invite dialog, the “Input custom message” field lacks a persistent visible label.
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 Map Fields component:
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 Supports In most cases, the contrast ratio between text and its background color meets the minimum contrast requirement, with one exception: 1. In the Date Picker calendar component, the dates do not meet the minimum contrast requirement.
1.4.4 Resize Text AA Does Not Support When content is scaled up to 200%, the following areas have a loss of content or functionality: 1. When using browser zoom, the canvas page displays a message that 200% browser zoom is not supported. However, in-page zoom controls are available up to 200%. 2. The Workflow Instance page header that is launched from the Workflows page. 3. The Templates Details page that is launched from the Workflows page. 4. The “Your Workflow is ready” dialog.
1.4.5 Images of Text AA Supports The Docusign logo is the only image that contains text in Maestro. 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 Maestro.
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. In the Date Picker calendar component, the “Previous” and “Next” icons do not
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. In the Add a Step listbox, the placeholder text is obscured in the “Add the next step after this” field when text spacing requirements are applied. 2. On the Workflow Templates page, the description of the templates are truncated when text spacing requirements are applied.
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 Maestro 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 canvas, the labels of the dialogs are not sufficiently descriptive. 2. On the Workflows page, the pagination region label is not sufficiently 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 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 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 Maestro.
3.2.4 Consistent Identification AA Supports Meaningful icons, functional images, links, or buttons that are repeated across pages in Maestro 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 Send an Email dialog, if the Subject, Headline and Body fields are empty when submitting the form, a “Configuration Error” text appears but
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 one exception: 1. In the Add Conditional Rule dialog, a toast message indicates an error that is not announced to screen reader users.

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.