Docusign Web Forms Recipient Experience
Accessibility Conformance Report published by DocuSign
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% coverage). The remainder are missing from our extraction, not necessarily from DocuSign's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
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 — 30 criteria
- Supports
- 25
- Partially supports
- 0
- Does not support
- 0
- Not applicable
- 5
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 15
- Partially supports
- 1
- Does not support
- 0
- Not applicable
- 4
- 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 (50)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | All non-text content, including complex and functional images, have meaningful text equivalents. Decorative images are ignored by assistive technology. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | The web application contains no prerecorded audio-only or video-only content. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | The web application does not contain synchronized media with prerecorded audio content. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | The web application does not contain any prerecorded synchronized media which would require an alternative for time-based media or audio description. |
| 1.3.1 | Info and Relationships | A | Supports | Information and structural relationships can be determined programmatically from the content. |
| 1.3.2 | Meaningful Sequence | A | Supports | The correct reading sequence is meaningful throughout the web application. |
| 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 | Not Applicable | The web application does not contain any audio which plays automatically for more than 3 seconds. |
| 2.1.1 | Keyboard | A | Supports | All functionality of the content is operable through a keyboard interface. Users have the ability to navigate, activate and perform all actions with a keyboard. |
| 2.1.2 | No Keyboard Trap | A | Supports | For every component that receives keyboard focus, focus can be moved away from that component using only a keyboard interface. |
| 2.1.4 | Character Key Shortcuts | A | Supports | The web application does not provide keyboard 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 | Not Applicable | The web application does not include large blocks of repeated content on different pages that would require bypass functionality. |
| 2.4.2 | Page Titled | A | Supports | All web pages have titles that describe their topic or purpose. |
| 2.4.3 | Focus Order | A | Supports | Elements that receive focus are presented in a logical order that honors the presentation and preserves meaning. Navigation with a keyboard follows the visual presentation of focusable elements. |
| 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 together with its programmatically determined link context. |
| 2.5.1 | Pointer Gestures | A | Supports | All functionality can be operated using a single pointer without using a path-based gesture or a multi-point gesture. |
| 2.5.2 | Pointer Cancellation | A | Supports | Single-pointer functions can be aborted by moving the pointer to a neutral location. |
| 2.5.3 | Label in Name | A | Supports | For all user interface components with text labels or images of text, the accessible name of the component contains the text that is presented visually. |
| 2.5.4 | Motion Actuation | A | Supports | 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 all pages on the web application is correctly identified. |
| 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 | Supports | The web application does not cause an unexpected change of context when interacting with elements. |
| 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. Error text appears next to the field in error and required fields that are not completed. |
| 3.3.2 | Labels or Instructions | A | Supports | Labels or instructions are provided for all form fields. These labels and instructions are programmatically associated with the form fields for those who rely on assistive technology. |
| 4.1.1 | Parsing | A | Supports | The web application does not contain parsing errors. |
| 4.1.2 | Name, Role, Value | A | Supports | The web application provides the correct name, role, state, and other important accessibility information for its controls. These properties are properly associated and available on all controls for users who rely on assistive technology. |
| 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 which would require an audio description. |
| 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 | Partially Supports | All form fields created by the web application relating to user information programmatically identify their purpose, such as the signer’s “Name” and “Email.” Exceptions: ● The web application does not allow form fields created by the sender to programmatically identify their purpose. |
| 1.4.3 | Contrast (Minimum) | AA | Supports | All text and images of text have sufficient contrast against their background. |
| 1.4.4 | Resize text | AA | Supports | Text can be resized up to 200 percent with the browser without loss of content or functionality. There are no CSS properties that prevent users from resizing text. |
| 1.4.5 | Images of Text | AA | Not Applicable | The web application does not contain images of text. |
| 1.4.10 | Reflow | AA | Supports | The web application can be resized to a width of 320 CSS pixels / a height of 256 CSS pixels without loss of content or functionality, and without requiring scrolling in two dimensions, |
| 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 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 is a simple step-by-step process that allows users to enter and edit form information. Since the web application falls under the exception as a set of pages that are steps within a process, navigation is only allowed sequentially from step to step. |
| 2.4.6 | Headings and Labels | AA | Supports | Headings and labels are descriptive throughout the web application. |
| 2.4.7 | Focus Visible | AA | Supports | All keyboard operable user interface components provide a visible keyboard focus indicator with sufficient contrast. |
| 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 web pages occur in |
| 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. These suggestions are provided visually and programmatically using HTML and ARIA. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | The website 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. |
| 4.1.3 | Status Messages | AA | Supports | Status messages can be programmatically determined and do not require 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.