Adobe Accessibility Conformance Report International Edition

(Based on VPAT® Version 2.4)

Name of Product/Version: Acrobat Sign

 

Report Date: May 2022

 

Product Description: Acrobat Sign provides the means to digitally route and track documents for signing providing a convenient, modern way to sign documents electronically.

 

Contact Information: access@adobe.com

 

Evaluation Methods Used: Product testing involved use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.

 

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

 

Standard/Guideline

Included in Report

Web Content Accessibility Guidelines 2.0

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Web Content Accessibility Guidelines 2.1

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018

(Yes)

EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, - V3.2.1 (2021-03)

(Yes)

Terms

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.
  • Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.

 

WCAG 2.1 Report

Tables 1 and 2 also document conformance with:
 

  • EN 301 549:  Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
  • Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
     

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements. 

Table 1: Success Criteria, Level A and AA

Notes: 

 

Guideline 1.1 Text Alternatives:

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Criteria

Conformance Level

Remarks and Explanations

1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.1.1 (Web)
  • 10.1.1.1 (Non-web document)
  • 11.1.1.1.1 (Open Functionality Software)
  • 11.1.1.1.2 (Closed Functionality Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: The product provides sufficient text alternatives for most instances of informative, CSS and media file images.

 

Exceptions include: 

  • Text alternative is missing for the image in the “My Profile - Email Settings” screen.
  • Informative CSS image is missing text alternative in the “My Profile - Access Tokens” and “My Profile - API Request Log” screens.
  • Decorative images are not hidden programmatically in the “Send - Confirmation Screen” and “Signer Experience – Email” screens.
  • Text alternative for the image does not include the essential text in the image in the “Signer Experience – Email” screen.

Guideline 1.2 Time-based Media:

Provide alternatives for time-based media.

Criteria

Conformance Level

Remarks and Explanations

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.1 (Web)
  • 10.1.2.1 (Non-web document)
  • 11.1.2.1.1 (Open Functionality Software)
  • 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not contain prerecorded audio-only or video-only media.

1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.2 (Web)
  • 10.1.2.2 (Non-web document)
  • 11.1.2.2 (Open Functionality Software)
  • 11.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not contain prerecorded synchronized media.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.3 (Web)
  • 10.1.2.3 (Non-web document)
  • 11.1.2.3.1 (Open Functionality Software)
  • 11.1.2.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not contain prerecorded video content that would require audio description or a media alternative.

1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.4 (Web)
  • 10.1.2.4 (Non-web document)
  • 11.1.2.4 (Open Functionality Software)
  • 11.1.2.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not contain live synchronized media.

1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.5 (Web)
  • 10.1.2.5 (Non-web document)
  • 11.1.2.5 (Open Functionality Software)
  • 11.1.2.5 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not contain prerecorded video content that would require audio description.

Guideline 1.3 Adaptable:

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Criteria

Conformance Level

Remarks and Explanations

1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.1 (Web)
  • 10.1.3.1 (Non-web document)
  • 11.1.3.1.1 (Open Functionality Software)
  • 11.1.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most visual structure and relationship information is provided through object information or are available in text.  

 

Exceptions include:

  • Non-decorative content is inserted using CSS pseudo-elements in “Fill and Sign Step 1”, “Publish a Web Form - Create a Web Form Step 2”, “Send Flow - Step 1”, “Send Flow - Step 2”, and “Send in Bulk - Step 2” screens. 
  • Data table has incomplete or missing heading markup in the “Manage - Waiting for you”, “My Profile - My Notifications”, and “Send - Confirmation Screen” screens.
  • More than one table element is used to create a single table in the “My Profile - Access Tokens”, “My Profile - API Request Log”, and “My Profile - View other Accounts” screens. 
  • Layout table uses a data table structure in the “My Profile - API applications Create Modal” and “My Profile - My Notifications” screens. 
  • Input element does not have a label/accessible name in the “My Profile - Email Settings”, “My Profile - Language Preferences”, “My Profile - My Notifications”, “Send - Confirmation Screen”, and “Send in Bulk - Step 1” screens. 
  • Visible label/form field is not associated in the “Publish a Web Form - Create a Web Form Flow Step 1” screen.
  • Group of form controls are not programmatically associated with their group labels or missing a group label in the “My Profile - API applications Create Modal” and “Send in Bulk - Manage and Track” screens
  • Visual heading text is not marked as a heading in the “Send in Bulk - Manage and Track” and “Signer Experience – Email” screens. 
  • Text should not be marked as a heading in the “Fill and Sign Step 1”, “Manage - Waiting for you”, “My Profile”, “Publish a Web Form - Create a Web Form Flow Step 1”, and “Send in Bulk - Step 1” screens.
  • List is not marked up properly for the content in the “Manage - Waiting for you” and “Signer Experience – Email” screens.
  • Non-list content is marked up as a list in the “Publish a Web Form - Create a Web Form Flow Step 1” and “Send Flow - Step 1” screens. 

1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.2 (Web)
  • 10.1.3.2 (Non-web document)
  • 11.1.3.2.1 (Open Functionality Software)
  • 11.1.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: The product presents most content in a meaningful sequence. 


Exception includes:

  • Informative content is not readable by a screen reader in the “Manage - Waiting for you” screen
  • Hidden content is readable with a screen reader in the “My Profile”, “My Profile - Email Settings”, and “Publish a Web Form - Create a Web Form Flow Step 1” screens.
  • Correct reading order of dynamic content not determinable in the “My Profile - Access Tokens” and “My Profile - API Request Log” screens.
  • Reading order of static content changes meaning in the “My Profile - Access Tokens”, “My Profile - API Request Log”, “My Profile - View other Accounts”, and “Publish a Web Form - Create a Web Form Flow Step 1” screens.

1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.3 (Web)
  • 10.1.3.3 (Non-web document)
  • 11.1.3.3 (Open Functionality Software)
  • 11.1.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Web: Instructions that do not rely solely on sensory characteristics in this product.

1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.4 (Web)
  • 10.1.3.4 (Non-web document)
  • 11.1.3.4 (Open Functionality Software)
  • 11.1.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Web: Content does not restrict its view and operation to a single display orientation.

1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.5 (Web)
  • 10.1.3.5 (Non-web document)
  • 11.1.3.5 (Open Functionality Software)
  • 11.1.3.5 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports (Not Applicable)

Web: The product does not contain input fields that collect information about the user.

Guideline 1.4 Distinguishable:

Make it easier for users to see and hear content including separating foreground from background.

Criteria

Conformance Level

Remarks and Explanations

1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.1 (Web)
  • 10.1.4.1 (Non-web document)
  • 11.1.4.1 (Open Functionality Software)
  • 11.1.4.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most functions of the product do not convey information through color alone. 

Exceptions include: 

  • Color alone is used to identify errors in the “My Profile - Auto Delegation” and “My Profile - Request to view modal” screens.
  • Link contrast is not at least 3:1 with surrounding text in the “My Profile - API information” and “Send in Bulk - Step 1” screens.

1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.2 (Web)
  • 10.1.4.2 (Non-web document)
  • 11.1.4.2 (Open Functionality Software)
  • 11.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not contain audio that plays automatically.

1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.3 (Web)
  • 10.1.4.3 (Non-web document)
  • 11.1.4.3 (Open Functionality Software)
  • 11.1.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) 
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most text meets minimum contrast requirements. 

 

Exceptions include:

  • Some placeholder text content has insufficient contrast ratio with the background in the “Send in Bulk - Manage and Track” screen.
  • Some text content has insufficient contrast ratio with the background in the “Fill and Sign - Add Signature Modal”, “Left navigation - My Profile”, “My Profile - Access Tokens”, “My Profile - API applications Create Modal”, “My Profile - API Request Log”, “My Profile - Request to view modal”, “My Profile - View other Accounts”, “Publish a Web Form - Create a Web Form Flow Step 1”, “Publish a Web Form - Create a Web form flow Step 3”, “Send Flow - Step 1”, “Send in Bulk - Step 1”, and “Signer Experience - Access Document (eSign View)” screens. 
  • Some link or button text lacks 4.5:1 contrast ratio on hover or focus with the background in the “Fill and Sign - Add Signature Modal”, “Fill and Sign Step 2”, “Header”, “Left navigation - My Profile”, “My Profile - API applications Create Modal”, “My Profile - Request to view modal”, “Publish a Web Form - Create a Web Form Flow Step 1”, “Publish a Web Form - Create a Web Form Step 2”, “Send Flow - Step 2”, “Send in Bulk - Step 1”, and “Send in Bulk - Step 2” screens.
  • Text over an image lacks 4.5:1 contrast ratio in the “Fill and Sign - Add Signature Modal” screen. 

 

1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.4 (Web)
  • 10.1.4.4 (Non-web document)
  • 11.1.4.4.1 (Open Functionality Software)
  • 11.1.4.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most text can be resized using browser zoom, but content and functionality is lost in some product functions. 

 

Exception includes:

  • Some part of the page content is lost when the page is zoomed to 200% in the “Manage - Waiting for you”, “My Profile - Access Tokens “, “My Profile - API Request Log”, “My Profile - My Notifications”, “Publish a Web Form - Create a Web Form Step 2 “, “Publish a Web Form - Create a Web form flow Step 3 “, “Send Flow - Step 2”, “Send in Bulk - Step 2 “, “Signer Experience - Access Document (eSign View)”, and “Signer Experience - Email “ screens.

1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.5 (Web)
  • 10.1.4.5 (Non-web document)
  • 11.1.4.5.1 (Open Functionality Software)
  • 11.1.4.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Web: The product uses text instead of images of text, except for branding elements that are considered essential.

1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.10 (Web)
  • 10.1.4.10 (Non-web document)
  • 11.1.4.10.1 (Open Functionality Software)
  • 11.1.4.10.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Web: At the required width of 320 CSS pixels, most content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. 
 

Exceptions include:

  • Some page content does not reflow to fit horizontally when the page width is changed to 320 CSS pixels in the “Fill and Sign Step 1”, “Header”, “Publish a Web Form - Create a Web form flow Step 3 “, “Send - Confirmation Screen”, “Send in Bulk - Step 1”, “Signer Experience - Access Document (eSign View)”, and “Signer Experience – Email” screens.
  • Some page content is lost when the page width is changed to 320 CSS pixels in the “Fill & Sign - Add File Modal”, “Fill and Sign - Add Signature Modal”, “Fill and Sign Step 1”, “Fill and Sign Step 2”, “Footer”, “Manage - Waiting for you”, “My Profile”, “My Profile - Access Tokens “, “My Profile - API information”, “My Profile - API Request Log”, “My Profile - Email Settings”, “My Profile - My Notifications”, “My Profile - View other Accounts”, “Publish a Web Form - Create a Web Form Flow Step 1”, “Publish a Web Form - Create a Web Form Step 2”, “Send Flow - Step 1”, “Send Flow - Step 2”, “Send in Bulk - Manage and Track”, and “Send in Bulk - Step 2 “ screens.

1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.11 (Web)
  • 10.1.4.11 (Non-web document)
  • 11.1.4.11 (Open Functionality Software)
  • 11.1.4.11 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Web: Most meaningful non-text content elements have sufficient contrast requirements. 

 

Exceptions include:

  • Active user interface component lacks 3 to 1 contrast ratio in the “My Profile - API applications Create Modal”, “My Profile - Auto Delegation”, “My Profile - Email Settings”, “My Profile - Request to view modal”, and “Send in Bulk - Step 1” screens.
  • The selected state and focus indicator have insufficient contrast ratio against the adjacent background color in the “Fill & Sign - Add File Modal”, “Fill and Sign - Add Signature Modal”, “Fill and Sign Step 2”, “Header”, “Manage - Waiting for you”, “My Profile - Access Tokens”, “My Profile - API Request Log”, “My Profile - Request to view modal”, “My Profile - View other Accounts”, “Publish a Web Form - Create a Web Form Step 2, “Publish a Web Form - Create a Web form flow Step 3 “, “Send Flow - Step 2”, “Send in Bulk - Step 1”, “Send in Bulk - Step 2 “, “Signer Experience - Access Document (eSign View)”, and “Signer Experience - Send Document back”  screens.
  • Graphical object has insufficient contrast ratio against the adjacent background color in the “Fill and Sign Step 1”, “Fill and Sign Step 2”, “Manage - Waiting for you”, “Publish a Web Form - Create a Web Form Flow Step 1”, “Publish a Web Form - Create a Web Form Step 2”, “Publish a Web Form - Create a Web form flow Step 3 “, “Send Flow - Step 1”, “Send Flow - Step 2”, “Send in Bulk - Step 1”, “Send in Bulk - Step 2 “, “Signer Experience - Access Document (eSign View)”, and “Signer Experience - delegate modal” screens.

1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.12 (Web)
  • 10.1.4.12 (Non-web document)
  • 11.1.4.12 (Open Functionality Software)
  • 11.1.4.12 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Web: Most functions of the product support the required text style properties without loss of content or functionality. 
 

Exceptions include: 

  • Some content is unclear because it is cutoff or it overlaps with other content when the text spacing is adjusted in the “Manage - Waiting for you”, “Publish a Web Form - Create a Web Form Step 2”, “Send - Confirmation Screen”, “Send Flow - Step 1”, “Send Flow - Step 2”, and “Send in Bulk - Step 2” screens.

1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.13 (Web)
  • 10.1.4.13 (Non-web document)
  • 11.1.4.13 (Open Functionality Software)
  • 11.1.4.13 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Web: In most product functions, content becomes visible and then hidden in response to pointer hover or keyboard focus.
 

Exception includes: 

  • The content that appears on the hover cannot be hovered using the same pointer without the content disappearing in the “Fill and Sign - Add Signature Modal” screen.

Guideline 2.1 Keyboard Accessible:

Make all functionality available from a keyboard.

Criteria

Conformance Level

Remarks and Explanations

2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.1.1 (Web)
  • 10.2.1.1 (Non-web document)
  • 11.2.1.1.1 (Open Functionality Software)
  • 11.2.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most product functionality can be operated through a keyboard interface. 

 

Exceptions include:

  • Elements that have scrollable content must be accessible by keyboard in the “Fill and Sign Step 2”, “Left navigation - My Profile”, and “Send in Bulk - Step 2” screens.
  • There is no way to perform the function using only the keyboard in the “Left navigation - My Profile”, “Manage - Waiting for you”, “My Profile”, “My Profile - Access Tokens”, “My Profile - API Request Log”, “My Profile - My Notifications”, “My Profile - View other Accounts”, “Publish a Web Form - Create a Web Form Step 2”, “Send in Bulk - Step 1”, and “Send in Bulk - Step 2” screens.
  • Drag and drop is not keyboard accessible in the “Send Flow - Step 2” screen.
  • The action cannot be performed when the screen reader is turned on in the “Publish a Web Form - Create a Web Form Flow Step 1” screen.
  • Device-dependent event handlers are used in the “Publish a Web Form - Create a Web Form Step 2”, “Send in Bulk - Step 1”, and “Send in Bulk - Step 2” screens.

2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.1.2 (Web)
  • 10.2.1.2 (Non-web document)
  • 11.2.1.2 (Open Functionality Software)
  • 11.2.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Web: The product does not include keyboard traps.

2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.1.4 (Web)
  • 10.2.1.4 (Non-web document)
  • 11.2.1.4.1 (Open Functionality Software)
  • 11.2.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports (Not Applicable)

Web: The product does not provide character key shortcuts.

Guideline 2.2 Enough Time:

Provide users enough time to read and use content.

Criteria

Conformance Level

Remarks and Explanations

2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.2.1 (Web)
  • 10.2.2.1 (Non-web document)
  • 11.2.2.1 (Open Functionality Software)
  • 11.2.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most part of the product does not have any adjustment or cancellation of time-based limits. 



Exception includes: 

  • Content visually appears and disappears with no ability to adjust timing in the “My Profile - Auto Delegation” screen

2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.2.2 (Web)
  • 10.2.2.2 (Non-web document)
  • 11.2.2.2 (Open Functionality Software)
  • 11.2.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not applicable)

Web: The product does not include elements which move, blink, scroll, or auto-update.

Guideline 2.3 Seizures:

Do not design content in a way that is known to cause seizures. 

Criteria

Conformance Level

Remarks and Explanations

2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.3.1 (Web)
  • 10.2.3.1 (Non-web document)
  • 11.2.3.1 (Open Functionality Software)
  • 11.2.3.1(Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not contain flashing content.

Guideline 2.4 Navigable:

Provide ways to help users navigate, find content, and determine where they are. 

Criteria

Conformance Level

Remarks and Explanations

2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.1 (Web)
  • 10.2.4.1 (Non-web document) – Does not apply
  • 11.2.4.1 (Open Functionality Software) – Does not apply
  • 11.2.4.1 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Partially Supports

Web: The product provides a heading markup, which allows assistive technology users to bypass repeated blocks. However, for users without assistive technology, a bypass mechanism is not provided.

2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.2 (Web)
  • 10.2.4.2 (Non-web document)
  • 11.2.4.2 (Open Functionality Software) - Does not apply
  • 11.2.4.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most of the titles of pages describe their purpose.
 

Exceptions include:

  • Page title does not identify purpose of page in the “Manage - Waiting for you”, “My Profile”, and “Publish a Web Form - Create a Web form flow Step 3” screens.

2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.3 (Web)
  • 10.2.4.3 (Non-web document)
  • 11.2.4.3 (Open Functionality Software)
  • 11.2.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most components receive focus in a meaningful order. 

 

Exceptions include:

  • Focus is not returned to the triggering element when the modal is closed in the “Fill and Sign - Add Signature Modal”, “My Profile - API applications Create Modal”, and “My Profile - Request to view modal” screens.
  • The keyboard focus order is not logical and it affects the meaning or operability of the content in the “Manage - Waiting for you” and “Send in Bulk - Step 1” screens.
  • The keyboard focus is not maintained in modal in the “Main-Search”, and “Messages-Preview-Preview Tab” screens.
  • Hidden or empty element receives keyboard focus in the “My Profile - Email Settings” screen.

 

2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.4 (Web)
  • 10.2.4.4 (Non-web document)
  • 11.2.4.4 (Open Functionality Software)
  • 11.2.4.4 (Closed Software
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most of the purpose of links in the product can be determined from the link text alone or from the programmatic context of the link.


Exception includes: 

  • The purpose of link is not clear in context in the “Send in Bulk - Step 1” screen.

2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.5 (Web)
  • 10.2.4.5 (Non-web document) – Does not apply
  • 11.2.4.5 (Open Functionality Software) – Does not apply
  • 11.2.4.5 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  •  501 (Web)(Software) – Does not apply to non-web software
  •  504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Web: Users can locate web pages in the product through the menu and options in the main section.

 2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.6 (Web)
  • 10.2.4.6 (Non-web document)
  • 11.2.4.6 (Open Functionality Software)
  • 11.2.4.6 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  •  501 (Web)(Software)
  •  504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most headings and labels are descriptive.  

 

Exceptions include:

  • Buttons have same name but different actions in the “My Profile - Email Settings”, “My Profile - My Signature”, and “Send Flow - Step 1” screens.
  • Programmatic label does not convey purpose of control in the “Manage - Waiting for you” and “Send - Confirmation Screen” screens.
  • Label does not convey purpose of control in the “My Profile - Auto Delegation” screen. 

2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.7 (Web)
  • 10.2.4.7 (Non-web document)
  • 11.2.4.7 (Open Functionality Software)
  • 11.2.4.7 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most focusable elements have a visible keyboard focus indicator.


Exceptions include: 

  • Visible keyboard focus indicator is missing or not visible in the “Manage - Waiting for you”, “My Profile”, “My Profile - Access Tokens”, “My Profile - API Request Log”, “Publish a Web Form - Create a Web Form Step 2”, “Send in Bulk - Manage and Track”, “Send in Bulk - Step 1”, and “Send in Bulk - Step 2” screens.

Guideline 2.5 Input Modalities:

Make it easier for users to operate functionality through various inputs beyond keyboard. 

Criteria

Conformance Level

Remarks and Explanations

2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.1 (Web)
  • 10.2.5.1 (Non-web document)
  • 11.2.5.1 (Open Functionality Software)
  • 11.2.5.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports (Not Applicable)

Web: The product does not rely on multipoint or path-based gestures.

2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.2 (Web)
  • 10.2.5.2 (Non-web document)
  • 11.2.5.2 (Open Functionality Software)
  • 11.2.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Web: Product functions that use a single pointer are completed when the user releases the pointer.

2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.3 (Web)
  • 10.2.5.3 (Non-web document)
  • 11.2.5.3 (Open Functionality Software)
  • 11.2.5.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Web: The accessible names for the controls contain the text of their visible labels.

2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.4 (Web)
  • 10.2.5.4 (Non-web document)
  • 11.2.5.4 (Open Functionality Software)
  • 11.2.5.4 (Closed Software
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports (Not Applicable)

Web: The product does not have functionality operated by device motion or user motion.

Guideline 3.1 Readable:

Make text content readable and understandable. 

Criteria

Conformance Level

Remarks and Explanations

3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.1.1 (Web)
  • 10.3.1.1 (Non-web document)
  • 11.3.1.1.1 (Open Functionality Software)
  • 11.3.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most of the language is programmatically determinable within the product.


Exception includes: 

  • Primary language of the page is not identified in the “Signer Experience – Email” screen.

3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.1.2 (Web)
  • 10.3.1.2 (Non-web document)
  • 11.3.1.2 (Open Functionality Software) – Does not apply
  • 11.3.1.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most of the changes of language for passages or phrases can be programmatically determined.


Exception includes: 

  • Change in language is not marked in the “My Profile - Language Preferences” screen. 

Guideline 3.2 Predictable:

Make Web pages appear and operate in predictable ways. 

Criteria

Conformance Level

Remarks and Explanations

3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.1 (Web)
  • 10.3.2.1 (Non-web document)
  • 11.3.2.1 (Open Functionality Software)
  • 11.3.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Web: Components do not initiate a change of context when focused.

3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.2 (Web)
  • 10.3.2.2 (Non-web document)
  • 11.3.2.2 (Open Functionality Software)
  • 11.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Changes of context do not occur automatically on user input.


Exception includes: 

  • Arrow keys activate dropdown menu options. In the “Footer” screen.

3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.3 (Web)
  • 10.3.2.3 (Non-web document) – Does not apply
  • 11.3.2.3 (Open Functionality Software) – Does not apply
  • 11.3.2.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Web: When navigational mechanisms are repeated in the product they occur in a consistent relative order.

3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.4 (Web)
  • 10.3.2.4 (Non-web document) – Does not apply
  • 11.3.2.4 (Open Functionality Software) – Does not apply
  • 11.3.2.4 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Web: Components with the same functionality are identified consistently.

Guideline 3.3 Input Assistance:

Help users avoid and correct mistakes. 

Criteria

Conformance Level

Remarks and Explanations

3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.1 (Web)
  • 10.3.3.1 (Non-web document)
  • 11.3.3.1.1 (Open Functionality Software)
  • 11.3.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Where input errors are automatically detected, items in error are identified and error messages are provided as text.


Exceptions include:

  • Input error is not described in text in the “My Profile - Auto Delegation” and “My Profile - Request to view modal” screens.

3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.2 (Web)
  • 10.3.3.2 (Non-web document)
  • 11.3.3.2 (Open Functionality Software)
  • 11.3.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: Most labels are provided for input fields.

 

Exceptions include:

  • Visible label missing in the “Fill and Sign - Add Signature Modal”, “Fill and Sign Step 2”, “My Profile - My Notifications”, “Publish a Web Form - Create a Web Form Step 2”, “Publish a Web Form - Create a Web form flow Step 3”, “Send - Confirmation Screen”, “Send Flow - Step 2”, “Send in Bulk - Step 2”, and “Signer Experience - Access Document (eSign View)” screens. 
  • Visible label is not persistent in the “Fill and Sign - Add Signature Modal”, “Fill and Sign Step 1”, “Left navigation - My Profile”, “My Profile - Access Tokens”, “My Profile - API Request Log”, “Publish a Web Form - Create a Web Form Flow Step 1”, “Send Flow - Step 1”, “Send in Bulk - Manage and Track”, “Send in Bulk - Step 1”, and “Signer Experience - delegate modal” screens. 

3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.3 (Web)
  • 10.3.3.3 (Non-web document)
  • 11.3.3.3 (Open Functionality Software)
  • 11.3.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Web: Where input errors are automatically detected, suggestions for correction are provided to the user.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.4 (Web)
  • 10.3.3.4 (Non-web document)
  • 11.3.3.4 (Open Functionality Software)
  • 11.3.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports (Not Applicable)

Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data.

Guideline 4.1 Compatible:

Maximize compatibility with current and future user agents, including assistive technologies. 

Criteria

Conformance Level

Remarks and Explanations

4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.4.1.1 (Web)
  • 10.4.1.1 (Non-web document)
  • 11.4.1.1.1 (Open Functionality Software)
  • 11.4.1.1.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: In most product functions, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. 

 

Exceptions include:

  • Certain ARIA roles must be contained by particular parents and children in the “Fill & Sign - Add File Modal” and “Send Flow - Step 1” screens.
  • Interactive controls are not nested in the “Home” screen. 
  • Page contains duplicate Ids in the “Home”, “My Profile - Email Settings”, “Send - Confirmation Screen”, “Send in Bulk - Manage and Track”, and “Send in Bulk - Step 1” screens.

 

4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.4.1.2 (Web)
  • 10.4.1.2 (Non-web document)
  • 11.4.1.2.1 (Open Functionality Software)
  • 11.4.1.2.2 (Closed Software) – Not required
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Web: User interface components in most product functions provide programmatic name, role, and/or state information. However, some controls do not provide name, role, and/or state information to assistive technology. 

 

Exceptions include:

  • The elements are missing the expand/collapse state in the “Fill and Sign Step 2”, “My Profile”, “My Profile - Access Tokens”, “My Profile - API Request Log”, “My Profile - My Notifications”, “Send in Bulk - Manage and Track”, “Send in Bulk - Step 1”, and “Signer Experience - Access Document (eSign View)” screens.
  • Link does not have a role in the “Left navigation - My Profile” screen.
  • Link does not have discernible text in the “Left navigation - My Profile”, “My Profile”, “My Profile - Access Tokens”, “My Profile - API Request Log”, and “Send in Bulk - Step 1” screens.
  • Buttons do not have an accessible name and/or role in the “My Profile”, “My Profile - Access Tokens, “My Profile - API applications Create Modal”, “My Profile - API information”, “My Profile - API Request Log”, “My Profile - Auto Delegation”, “My Profile - Email Settings”, “My Profile - Language Preferences”, “My Profile - My Notifications”, “My Profile - My Signature”, “My Profile - View other Accounts”, “Send Flow - Step 1”, “Publish a Web Form - Create a Web Form Step 2”, “Send in Bulk - Step 1”, and “Send in Bulk - Step 2” screens.
  • Table sort is missing or incorrect in the “My Profile - Access Tokens”, “My Profile - API Request Log”, and “My Profile - View other Accounts” screens.
  • Checkboxes are missing appropriate role and/or attributes in the “My Profile - Access Tokens”, “My Profile - API Request Log”, and “My Profile - View other Accounts” screens.
  • Disabled and pressed state of the buttons are not conveyed in the “My Profile - API applications Create Modal”, “My Profile - Email Settings”, “My Profile - My Notifications”, “My Profile - Request to view modal”, “Publish a Web Form - Create a Web Form Step 2”, “Send in Bulk - Step 1”, and “Send in Bulk - Step 2” screens.
  • Invalid ARIA attribute or its value in the “Fill & Sign - Add File Modal”, “Header”, “Fill and Sign - Add Signature Modal”, “Fill and Sign Step 1”, “Manage - Waiting for you”, “Publish a Web Form - Create a Web Form Flow Step 1”, and “Send Flow - Step 1” screens.
  • Accordion (toggle) is missing appropriate role and/or attributes in the “Left navigation - My Profile” screen.
  • The element role is missing, incorrect, or invalid in the “Manage - Waiting for you”, “My Profile - Access Tokens”, “My Profile - API Request Log”, “My Profile - View other Accounts, “Send in Bulk - Manage and Track”, and “Signer Experience - Access Document (eSign View)” screens.
  • ARIA input field must have an accessible name in the “Send Flow - Step 1” screen.

4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.4.1.3 (Web)
  • 10.4.1.3 (Non-web document) – Does not apply
  • 11.4.1.3 (Open Functionality Software) – Does not apply
  • 11.4.1.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Web: When status messages do not receive focus, the product does not provide the dynamic and automatic update to the assistive technology. 

 

Exception includes:

  • Status messages are not automatically announced in the “Fill and Sign Step 1”, “Left navigation - My Profile”, “Manage - Waiting for you”, “My Profile - Access Tokens”, “My Profile - API applications Create Modal”, “My Profile - API Request Log”, “My Profile - Auto Delegation”, “My Profile - Email Settings”, “My Profile - Request to view modal”, “Send Flow - Step 1”, “Send in Bulk - Manage and Track”, and “Send in Bulk - Step 1” screens.

Table 2: Success Criteria, Level AAA

Notes: Not Applicable

 

Revised Section 508 Report

Notes:

 

Chapter 3: Functional Performance Criteria (FPC)

Notes:

Criteria

Conformance Level

Remarks and Explanations

302.1 Without Vision

Web: Partially Supports

Web: Most functions of the product are usable without vision. 

 

Exceptions include:

  • As noted in 1.1.1 Non-text Content, images are missing text alternative and media file is missing text alternative.
  • As noted in 1.3.1 Info and Relationships, semantically provided content are not appropriately conveyed programmatically including tables, headings, and lists.
  • As noted in 1.3.2 Meaningful Sequence, the informative content is not readable by a screen reader, the hidden content is readable with a screen reader, an incorrect reading order exists.
  • As noted in 2.1.1 Keyboard, some interactive elements are not operable by the keyboard, elements that have scrollable content must be accessible by keyboard.
  • As noted in 2.2.1 Timing Adjustable, content visually appears and disappears without ability to adjust timing. 
  • As noted in 2.4.3 Focus Order, focus order is not logical when the modal is closed and keyboard focus is lost and misplaced due to user interaction, Hidden or empty element receives focus, keyboard focus is not maintained in modal.
  • As noted in 2.4.4 Link Purpose (In Context), the purpose of the link is not clear in the context.
  • As noted in 3.2.2 Context Changes (on Input), arrow keys activate dropdown menu options.
  • As noted in 3.3.1 Error Identification error message is not displayed in text.
  • As noted in 4.1.1 Parsing, id attribute value must be unique, required parent/child role missing, required ARIA attributes missing
  • As noted in 4.1.2 Name, Role, Value, some interactive elements missing accessible name, role, value, and attributes.

302.2 With Limited Vision

Web: Partially Supports

Web: Most functions of the product are usable with limited vision. 

 

Exceptions include:

  • As noted in 1.4.1 Use of Color, color alone is used to identify the error and the links.
  • As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements.
  • As noted in 1.4.4 resize text, some part of the page content is lost and obscured when the page is zoomed to 200%.
  • As noted in 2.4.7 Focus Visible, visible focus indicator is missing or not visible on some active elements.

302.3 Without Perception of Color

Web: Partially Supports

Web: Most functions of the product are usable without perception of color. 

 

Exceptions include:

  • As noted in 1.4.1 Use of Color, color alone is used to identify the error and the links.
  • As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements.

302.4 Without Hearing

Web: Supports (Not Applicable)

Web: The product does not require the use of hearing.

302.5 With Limited Hearing

Web: Supports (Not Applicable)

Web: The product does not require the use of hearing.

302.6 Without Speech

Web: Supports (Not Applicable)

Web: The product does not require the use of speech.

302.7 With Limited Manipulation

Web: Partially Supports

Web: Users with limited manipulation who use speech recognition or switch control software will have difficulty navigating to controls. 

 

Exceptions include:

  • As noted in 2.1.1 Keyboard, some interactive elements are not operable by the keyboard.
  • As noted in 2.4.3 Focus Order, focus order is not logical when the modal is closed and keyboard focus is lost and misplaced due to user interaction, Hidden or empty element receives focus, keyboard focus is not maintained in modal.

302.8 With Limited Reach and Strength

Web: Partially Supports

Web: Users with limited reach and strength will have difficulty navigating to controls. 

 

Exceptions include:

  • As noted in 2.1.1 Keyboard, some interactive elements are not operable by the keyboard.
  • As noted in 2.4.3 Focus Order, focus order is not logical when the modal is closed and keyboard focus is lost and misplaced due to user interaction, Hidden or empty element receives focus, keyboard focus is not maintained in modal.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Partially Supports

Web: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. The product provides labeling for most controls. 

 

Exceptions include:

  • As noted in 2.2.1 Timing Adjustable, content visually appears and disappears without ability to adjust timing. 
  • As noted in 2.4.6 Headings and Labels, some buttons have the same labels/names but perform different actions, and labels do not convey the purpose of the controls.
  • As noted in 3.3.2 Labels or Instructions, visible labels are not persistent for some controls.

Chapter 4: Hardware

Notes: Not Applicable

 

Chapter 5: Software

Notes:
 

Chapter 6: Support Documentation and Services

Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.

 

EN 301 549 Report

Notes: 

 

Chapter 4: Functional Performance Statements (FPS)

Notes:

Criteria

Conformance Level

Remarks and Explanations

4.2.1 Usage without vision

Web: Partially Supports

Web: Most functions of the product are usable without vision. 

 

Exceptions include:

  •  
  • As noted in 1.1.1 Non-text Content, images are missing text alternative and media file is missing text alternative.
  • As noted in 1.3.1 Info and Relationships, semantically provided content are not appropriately conveyed programmatically including tables, headings, and lists.
  • As noted in 1.3.2 Meaningful Sequence, the informative content is not readable by a screen reader, the hidden content is readable with a screen reader, an incorrect reading order exists.
  • As noted in 2.1.1 Keyboard, some interactive elements are not operable by the keyboard, elements that have scrollable content must be accessible by keyboard.
  • As noted in 2.2.1 Timing Adjustable, content visually appears and disappears without ability to adjust timing. 
  • As noted in 2.4.3 Focus Order, focus order is not logical when the modal is closed and keyboard focus is lost and misplaced due to user interaction, Hidden or empty element receives focus, keyboard focus is not maintained in modal.
  • As noted in 2.4.4 Link Purpose (In Context), the purpose of the link is not clear in the context.
  • As noted in 2.5.3 Label in Name, the accessible name does not contain visible label text.
  • As noted in 3.2.2 Context Changes (on Input), arrow keys activate dropdown menu options.
  • As noted in 3.3.1 Error Identification error message is not displayed in text.
  • As noted in 4.1.1 Parsing, id attribute value must be unique, required parent/child role missing, required ARIA attributes missing
  • As noted in 4.1.2 Name, Role, Value, some interactive elements missing accessible name, role, value, and attributes.
  • As noted in 4.1.3 Status Messages, the status messages are not automatically announced by the screen reader.

4.2.2 Usage with limited vision

Web: Partially Supports

Web: Most functions of the product are usable with limited vision. 

 

Exceptions include:

  • As noted in 1.4.1 Use of Color, color alone is used to identify the error and the links.
  • As noted in 1.4.3 Contrast (Minimum), some text does not meet the minimum contrast requirements.
  • As noted in 1.4.4 Resize text, some part of the page content is lost and obscured when the page is zoomed to 200%.
  • As noted in 1.4.10 Reflow, some part of the page content does not reflow to fit horizontally at the required width of 320 CSS pixels.
  • As noted in 1.4.11 Non-text Contrast, graphical object, focus indicator, selected state and visual boundary does not meet the minimum contrast requirements.
  • As noted in 1.4.12 Text Spacing, some content cannot be seen or unclear because it overlaps with other content when the text spacing is adjusted.
  • As noted in 2.4.7 Focus Visible, visible focus indicator is missing or not visible on some active elements.

4.2.3 Usage without perception of colour

Web: Partially Supports

Web: Most functions of the product are usable without perception of color. 

 

Exceptions include:

  • As noted in 1.4.1 Use of Color, color alone is used to identify the error and the links.
  • As noted in 1.4.3 Contrast (Minimum), some text does not meet the minimum contrast requirements.
  • As noted in 1.4.11 Non-text Contrast, graphical object, focus indicator, selected state and visual boundary does not meet the minimum contrast requirements.

4.2.4 Usage without hearing

Web: Supports (Not Applicable)

Web: The product does not require the use of hearing.

4.2.5 Usage with limited hearing

Web: Supports (Not Applicable)

Web: The product does not require the use of hearing.

4.2.6 Usage without vocal capability

Web: Supports (Not Applicable)

Web: The product does not require the use of speech

4.2.7 Usage with limited manipulation or strength

Web: Partially Supports

Web: Users with limited manipulation or strength who use speech recognition or switch control software will have difficulty navigating to controls. 

 

Exceptions include:

  • As noted in 2.1.1 Keyboard, some interactive elements are not operable by the keyboard.
  • As noted in 2.4.3 Focus Order, focus order is not logical when the modal is closed and keyboard focus is lost and misplaced due to user interaction, Hidden or empty element receives focus, keyboard focus is not maintained in modal.
  • As noted in 2.5.3 Label in Name, the accessible name does not contain visible label text.

4.2.8 Usage with limited reach

Web: Partially Supports

Web: Users with limited reach will have difficulty navigating to controls. 

 

Exceptions include:

  • As noted in 2.1.1 Keyboard, some interactive elements are not operable by the keyboard.
  • As noted in 2.4.3 Focus Order, focus order is not logical when the modal is closed and keyboard focus is lost and misplaced due to user interaction, Hidden or empty element receives focus, keyboard focus is not maintained in modal.
  • As noted in 2.5.3 Label in Name, the accessible name does not contain visible label text.

4.2.9 Minimize photosensitive seizure triggers

Web: Supports (Not Applicable)

Web: The product does not contain flashing content or media.

4.2.10 Usage with limited cognition, language or learning

Web: Partially Supports

Web: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. The product provides labeling for most controls. 

 

Exceptions include:

  • As noted in 1.4.13 Content on Hover or Focus, content that appears on hover cannot be hovered using the same pointer. 
  • As noted in 2.2.1 Timing Adjustable, content visually appears and disappears without ability to adjust timing. 
  • As noted in 2.4.6 Headings and Labels, some buttons have the same labels/names but perform different actions, and labels do not convey the purpose of the controls.
  • As noted in 3.3.2 Labels or Instructions, visible labels are not persistent for some controls.

4.2.11 Privacy

Web: Supports (Not Applicable)

Web: The product does not provide any privacy features.

Chapter 5: Generic Requirements

Notes:

Criteria

Conformance Level

Remarks and Explanations

5.1 Closed Functionality

5.1.2 General

5.1.2.1 Closed functionality

See 5.2 through 13

See information in 5.2 through 13

5.1.2.2 Assistive technology

See 5.1.3 through 5.1.6

See information in 5.1.3 through 5.1.6

5.1.3 Non-visual access

5.1.3.1 Audio output of visual information

Not Applicable

The product does not have closed functionality.

5.1.3.2 Auditory output delivery including speech

Not Applicable

The product does not have closed functionality.

5.1.3.3 Auditory output correlation

Not Applicable

The product does not have closed functionality.

5.1.3.4 Speech output user control

Not Applicable

The product does not have closed functionality.

5.1.3.5 Speech output automatic interruption

Not Applicable

The product does not have closed functionality.

5.1.3.6 Speech output for non-text content

Not Applicable

The product does not have closed functionality.

5.1.3.7 Speech output for video information

Not Applicable

The product does not have closed functionality.

5.1.3.8 Masked entry

Not Applicable

The product does not have closed functionality.

5.1.3.9 Private access to personal data

Not Applicable

The product does not have closed functionality.

5.1.3.10 Non-interfering audio output

Not Applicable

The product does not have closed functionality.

5.1.3.11 Private listening volume

Not Applicable

The product does not have closed functionality.

5.1.3.12 Speaker volume

Not Applicable

The product does not have closed functionality.

5.1.3.13 Volume reset

Not Applicable

The product does not have closed functionality.

5.1.3.14 Spoken languages

Not Applicable

The product does not have closed functionality.

5.1.3.15 Non-visual error identification

Not Applicable

The product does not have closed functionality.

5.1.3.16 Receipts, tickets, and transactional outputs

Not Applicable

The product does not have closed functionality.

5.1.4 Functionality closed to text enlargement

Not Applicable

The product does not have closed functionality.

5.1.5 Visual output for auditory information

Not Applicable

The product does not have closed functionality.

5.1.6 Operation without keyboard interface

5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

See information in 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus

Not Applicable

The product does not have closed functionality.

5.2 Activation of accessibility features

Supports

The product does have specific documented accessibility features and allows preferences to be set for accessibility. 

5.3 Biometrics

Not Applicable

Biometrics is not included in the product.

5.4 Preservation of accessibility information during conversion

Not Applicable

The product does not convert content.

5.5 Operable parts

5.5.1 Means of operation

Not Applicable

The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate.

5.5.2 Operable parts discernibility

Partially Supports

The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions are noted in 1.3.1 Info and Relationships, 2.4.6 Headings and Labels and 4.1.2 Name, Role, Value.

5.6 Locking or toggle controls

5.6.1 Tactile or auditory status

Not Applicable

Tactile or auditory status is not included in the product.

5.6.2 Visual status

Supports

Visual status of controls is discernable in the product.

5.7 Key repeat

Not Applicable

Key repeat functionality is not found in the product.

5.8 Double-strike key acceptance

Not Applicable

Double -strike key acceptance is not found in the product.

5.9 Simultaneous user actions

Not Applicable

The product does not require simultaneous user actions to achieve any functionality.

Chapter 6: ICT with Two-Way Voice Communication

Notes: Not Applicable
 

Chapter 7: ICT with Video Capabilities

Notes: 
 

Chapter 8: Hardware

Notes: Not Applicable
 

Chapter 9: Web (see WCAG 2.1 section)

Notes:
 

Chapter 10: Non-Web Documents

Notes: Not Applicable
 

Chapter 11: Software

Notes: Not Applicable
 

Chapter 12: Documentation and Support Services

Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.

 

Chapter 13: ICT Providing Relay or Emergency Service Access

Notes: Not Applicable