Adobe Accessibility Conformance Report
International Edition

(Based on VPAT® Version 2.4)

Name of Product/Version:

 
  • Adobe Acrobat Pro Continuous (purchased as a subscription license)
  • Adobe Acrobat Pro Classic (purchased as a one-time perpetual license)
  • Adobe Acrobat Standard Continuous (purchased as a subscription license)
  • Adobe Acrobat Standard Classic (purchased as a one-time perpetual license)
  • Acrobat Reader

 

Report Date: June 2022

 

Product Description: Acrobat Pro is designed for creating, editing, collaborating, signing and distributing PDF documents and forms.

 

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.1.1 (2019-11) / 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 Chapter 
  • 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. 

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: All parts of the Sign Experience support this criterion.
  • Send Experience: All parts of the Send Experience support this criterion.
  • Admin Experience: The Admin Experience provides sufficient text alternatives for most instances of images and non-text content. Exceptions include:
  • Some image buttons do not have text alternatives.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): Authored content 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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any content that requires captions.

Authored Content (PDF): Authored content does not create any content that requires captions.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): The product does not create 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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain live synchronized media.

Authored Content (PDF): Authored content 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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): The product does not create video content that would require audio description.

1.2.6 Sign Language (Prerecorded) (Level AAA)
Also applies to:
EN 301 549 Criteria – Does Not Apply

Revised Section 508 – Does not apply

Not evaluated

1.2.7 Extended Audio Description (Level AAA)
Also applies to:
EN 301 549 Criteria – Does Not Apply

Revised Section 508 – Does Not Apply

Not evaluated

1.2.8 Media Alternative (Prerecorded) (Level AAA)
Also applies to:
EN 301 549 Criteria – Does Not Apply

Revised Section 508 – Does Not Apply

Not evaluated

1.2.9 Audio-only (Live) (Level AAA)
Also applies to:
EN 301 549 Criteria – Does Not Apply

Revised Section 508 – Does Not Apply

Not evaluated

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:

  • Sign Experience: Partially Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Partially Supports

Web:

  • Sign Experience: Throughout the Sign Experience, visual structure and relationship information is provided through object information or in text. 
  • In the Sign Experience the form fields are layered on top of an image of the document. The reader can access the full document with assistive technology such as a screen reader using the “Read Agreement” or “Download PDF” selections in the Options menu. 
  • Once the document has been signed and submitted, any values entered into form fields will no longer be accessible to the assistive technology user (such as a screen reader). The original accessible PDF is still readable but any added values are not.
  • Send Experience: The Send Experience does not provide appropriate programmatic or textual equivalents for most visual structure and relationship. Examples include:
  • Text which is styled to look like and function as headings are not marked as such.
  • Tables used for layout.
  • Landmarks of the same type are not distinguished by name.
  • Admin Experience: The Admin Experience does not provide appropriate programmatic or textual equivalents for most visual structure and relationship. Examples include:
  • Tables used for layout.
  • Form controls not associated with visible labels.
  • Groups of controls are not associated with their respective group headings.

Authored Content (PDF): Although authored PDF content does provide programmatic or textual equivalents for most visual structure and relationships, correctly authored and tagged PDF content is not maintained in the Output PDF file.

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:

  • Sign Experience: Partially Supports
  • Send Experience: Partially Supports
  • Admin Experience: Supports

Authored Content (PDF): Partially Supports

Web:

  • Sign Experience: In the Sign Experience the sequence is, by default left-to-right and top-down. The document can be opened in a PDF reader to get the correct sequence.
  • Send Experience: The focus order of the Send Experience does not match the visual order in several locations. Exceptions include:
  • Content order does not match the visual order on the Publish a Web Form page.
  • When dynamic content appears while previewing a document to Add a Signature field, the dynamic content is not in the correct interaction order.
  • Admin Experience: All parts of the Admin Experience support this criterion.

Authored Content (PDF): The product preserves the reading order of structured and unstructured content, such as headings and text. However, the reading sequence of form fields may not correspond to their visual order or tab order.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: All parts of the Sign Experience support this criterion.
  • Send Experience: All parts of the Send Experience support this criterion.
  • Admin Experience: Most of the Admin Experience provides instructions for understanding and operating content that does not rely solely on sensory characteristics.  Exceptions include:
    • Controls in "Reports - My Activity" do not appear to be actionable. Users can only discover that these are controls by attempting to interact with them.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): Authored Content does not restrict its view and operation to a single display orientation and responds appropriately to screen orientation changes.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The purpose of each input field collecting information about the user can be programmatically determined.

Authored Content (PDF): Authors can ensure that content meets this criterion.

1.3.6 Identify Purpose (Level AAA 2.1 only)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: The Sign Experience does not rely on the use of color alone to visually convey information.
  • Send Experience: The Send Experience does not rely on the use of color alone to visually convey information.
  • Admin Experience: Throughout the Admin Experience, color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element, except:
    • In the Dashboard Header where focus states rely solely on color.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): Authored content 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:

  • Sign Experience: Partially Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web: Some components on the product do not meet the minimum contrast requirements such as:

  • Control text, label text, error text and hint text have insufficient contrast.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Does Not Support
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web: Throughout the product, when resizing text by up to 200%, text is no longer contained within its containers and overlaps with elements, causing it to be difficult to read.

Authored Content (PDF): As a function of a PDF viewer application, the authored content can be zoomed up to 200 percent without loss of content or functionality.

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:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: The Sign Experience uses text instead of images of text.
  • Send Experience: Most images of text are not used in places where text can be used instead. Exceptions include:
  • On the login page there are some controls represented by images of text.
  • Admin Experience: The Admin Experience uses text instead of images of text.

Authored Content (PDF): Authors can ensure that content meets this criterion.

1.4.6 Contrast Enhanced (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

1.4.7 Low or No Background Audio (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

1.4.8 Visual Presentation (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

1.4.9 Images of Text (No Exception) Control (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Content responds and reflows as necessary when zoomed and does not require scrolling in two dimensions.

Authored Content (PDF): As a function of a PDF viewer application, the authored content responds and reflows as necessary when zoomed and does not require scrolling in two dimensions.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: User interface components and meaningful graphics have sufficient contrast with the surrounding background.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: There is no loss of content or functionality when users override author specified text styles.

Authored Content (PDF): As a function of a PDF viewer application, There is no loss of content or functionality when users override author specified text styles.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Throughout the product, content is not made visible via hover or focus or, when it is, it is dismissable, hoverable, and persistent.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: All Sign Experience functionality can be operated through a keyboard interface.
  • Send Experience: Some interactive elements are available using the keyboard. However, most interactive elements are not focusable using the keyboard, such as:
  • Custom elements, such as custom buttons, which cannot be reached or activated via keyboard.
  • Actionable controls and widgets which do not appear in the tab order.
  • Scrolling regions that cannot be scrolled by keyboard.
  • Admin Experience: Some interactive elements are available using the keyboard. However, most interactive elements are not focusable using the keyboard, such as:
  • Custom elements, such as custom buttons, which cannot be reached or activated via keyboard.
  • Actionable controls and widgets which do not appear in the tab order.
  • A help control in the Dashboard that cannot be reached by keyboard alone.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not feature any content or controls that cause a keyboard trap.

Authored Content (PDF): Authors can ensure that content meets this criterion.

2.1.3 Keyboard (No Exception) (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: No Shortcuts are used in the product.

Authored Content (PDF): The product does not create 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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not include time limits.

Authored Content (PDF): The product does not create time limits.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): Authors can ensure that content meets this criterion.

2.2.3 No Timing (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

2.2.4 Interruptions (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

2.2.5 Re-authenticating (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

2.2.6 Timeouts (Level AAA 2.1 only)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain flashing content.

Authored Content (PDF): Authors can ensure that content meets this criterion.

2.3.2 Three Flashes (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

2.3.3 Animation from Interactions (Level AAA 2.1 only)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Does Not Support
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web: The product does not provide a mechanism to bypass repeated navigation.

Authored Content (PDF): This criterion does not apply to non-web documents.

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:

  • Sign Experience: Does Not Support
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web: Throughout the product, the page titles are generally not descriptive or unique.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: Components receive focus in a meaningful order consistent with the expected interaction and/ or reading order
  • Send Experience: Most components receive focus in a meaningful order. Exceptions include:
    • Focus not managed when content changes on login.
    • Focus order does not follow the visual order on the Add Signature Field.
  • Admin Experience: Most components receive focus in a meaningful order. Exceptions include:
  • Focus order does not follow the visual order on and the Dashboard header and footer.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Links within the product make sense within their context of use.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Multiple ways of locating web pages are provided, such as via Search, except when the location is the result of, or a step in, a process.

Authored Content (PDF): This criterion does not apply to non-web documents.

 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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Headings and labels are descriptive.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: The keyboard focus indicator is visible on all interactive components.
  • Send Experience: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
    • On the Reports - My Activity page, the keyboard focus is not clearly visible on all sides of some elements.
  • Admin Experience: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
    • When users first log in and are taken to the Dashboard, a popup appears with the text "Welcome to your new home". This item has no visible focus indicator.

Authored Content (PDF): Authors can ensure that content meets this criterion.

2.4.8 Location (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

2.4.9 Link Purpose (Link Only) (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

2.4.10 Section Headings (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not require multi-point or path-based pointer gestures.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product contains only functionality that can be activated on the up event of a single pointer.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: For components that have visible text labels, that text exists in the component's accessible name.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any functionality that can be operated by device motion or user motion.

Authored Content (PDF): Authors can ensure that content meets this criterion.

2.5.5 Target Size (Level AAA 2.1 only)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 only)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The language is programmatically determinable within the product.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Content is only presented in one language at a time.

Authored Content (PDF): Authors can ensure that content meets this criterion.

3.1.3 Unusual Words (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

3.1.4 Abbreviations (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

3.1.5 Reading Level (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

3.1.6 Pronunciation (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: Changes of context do not occur automatically on user input.
  • Send Experience: Most of the product does not cause an unexpected change of context on user input.  Exceptions include:
    • Focus is moved unexpectedly when the value of a combobox is changed on the Add Signature Field
  • Admin Experience: Changes of context do not occur automatically on user input.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

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

Authored Content (PDF): This criterion does not apply to non-web documents.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Components with the same functionality, such as form controls with the same purpose are identified consistently.

Authored Content (PDF): This criterion does not apply to non-web documents.

3.2.5 Change on Request (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: Where input errors are automatically detected, items in error are identified and error messages are conveyed to assistive technologies.
  • Send Experience: Where input errors are automatically detected, items in error are identified and error messages are conveyed to assistive technologies. However, some exceptions include:
    • In the Add Files dialog, form features an “Attach” button that remain disabled until the attachment is selected.  However, the reason for the disabled button is not disclosed to assistive technologies.
  • Admin Experience: Where input errors are automatically detected, items in error are identified and error messages are conveyed to assistive technologies.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: Labels and instructions (where necessary) are provided when content requires user input.
  • Send Experience: Most interactive elements in the product convey an accessible name to assistive technology. Exceptions include:
    •  Instructions for operating alternatives to drag & drop interfaces are not described sufficiently.
  • Admin Experience: Labels and instructions (where necessary) are provided when content requires user input.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product provides suggestions to the user when input errors are automatically detected.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Changes to user-controllable data are reversible or can be confirmed before finalizing.

Authored Content (PDF): Authors can ensure that content meets this criterion.

3.3.5 Help (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

3.3.6 Error Prevention (All) (Level AAA)
Also applies to:
EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Not evaluated

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any parsing errors that cause access problems.

Authored Content (PDF): The authored content is not implemented using markup languages.

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:

  • Sign Experience: Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: User interface components provide programmatic name, role, state, and value information.
  • Send Experience: Most user interface components do not convey their name, role or value to assistive technology, such as:
    • Controls meant to act like buttons are not given appropriate semantics to match that role and often also lack accessible names.
    • Form fields often rely on placeholder text for labeling or have no labels at all.
    • Interactive elements often do not have roles which match their behavior.
  • Admin Experience: Most user interface components do not convey their name, role or value to assistive technology, such as:
  • Disclosure controls do not convey their states.
  • Interactive elements often do not have roles which match their behavior.
  • Controls often do not have accessible names.

Authored Content (PDF): Authors can ensure that content meets this criterion.

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:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: Status messages, when provided, are presented in a way that can be programmatically determined and do not require that they receive focus.

Authored Content (PDF): This criterion does not apply to non-web documents.

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:

  • Sign Experience: Partially Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Partially Supports

Web:

  • Sign Experience: As noted in 1.3.2 Meaningful Sequence, In the Sign Experience the sequence is, by default left-to-right and top-down. The document can be opened in a PDF reader to get the correct sequence.
  • Also, as noted in 1.3.1 Info and Relationships, once the document has been signed and submitted, any values entered into form fields will no longer be accessible to the assistive technology user (such as a screen reader). The original accessible PDF is still readable, but any added values are not.
  • Send Experience: Several pieces of functionality within the product are inaccessible to users without vision, as shown in 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value.
  • Admin Experience: Several pieces of functionality within the product are inaccessible to users without vision, as shown in 1.1.1 Non-text content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value.

Authored Content (PDF): Several pieces of functionality within the product are inaccessible to users without vision, as shown in 1.3.1 Info and Relationships.

302.2 With Limited Vision

Web:

  • Sign Experience: Partially Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: Some pieces of functionality within the product are inaccessible to users with low vision, as shown in 1.4.3 Contrast (Minimum) and 1.4.4 Resize Text.
  • Send Experience: Several pieces of functionality within the product are inaccessible to users with low vision, as shown in 1.4.3 Contrast (Minimum), 1.4.4 Resize Text.   and 2.4.3 (Focus Order).
  • Admin Experience: Several pieces of functionality within the product are inaccessible to users with low vision, as shown in 1.4.3 Contrast (Minimum), 1.4.4 Resize Text.   and 2.4.3 (Focus Order).

Authored Content (PDF): Authors can create content which is functional with limited vision.

302.3 Without Perception of Color

Web:

  • Sign Experience: Partially Supports
  • Send Experience: Partially Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.3 Contrast (Minimum).  
  • Send Experience: Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.3 Contrast (Minimum).
  • Admin Experience: Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.3 Contrast (Minimum).

Authored Content (PDF): Authors can create content which is functional without perception of color.

302.4 Without Hearing

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any audio content that requires hearing.

Authored Content (PDF): Authors can create content which is functional without hearing.

302.5 With Limited Hearing

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any audio content that requires hearing.

Authored Content (PDF): Authors can create content which is functional with limited hearing.

302.6 Without Speech

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not require user speech.

Authored Content (PDF): Authors can create content which is functional without speech.

302.7 With Limited Manipulation

Web:

  • Sign Experience: Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: All of the Sign Experience can be used by users with limited manipulation.
  • Send Experience: Most functionality within the Send Experience is inaccessible to users with limited manipulation as shown in 2.1.1 Keyboard, 2.4.3 Focus Order and 2.4.7 Focus Visible.
  • Admin Experience: Most functionality within the Admin Experience is inaccessible to users with limited manipulation as shown in 2.1.1 Keyboard, 2.4.3 Focus Order and 2.4.7 Focus Visible.

Authored Content (PDF): Authors can create content which is functional with limited manipulation.

302.8 With Limited Reach and Strength

Web:

  • Sign Experience: Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: All of the Sign Experience can be used by users with limited reach and strength.
  • Send Experience: Most functionality within the Send Experience is inaccessible to users with limited reach and strength, as shown in 2.1.1 Keyboard.
  • Admin Experience: Most functionality within the Admin Experience is inaccessible to users with limited reach and strength, as shown in 2.1.1 Keyboard.

Authored Content (PDF): Authors can create content which is functional with limited reach and strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: All of the Sign Experience can be used by users with limited language, cognitive, and learning abilities.
  • Send Experience: The Send Experience provides consistent navigation, understandable naming conventions, and icons that visually explain their purpose in supporting users with limited language, cognitive and learning abilities, notwithstanding the exceptions include issues noted in 2.4.3 Focus Order and 3.2.2 On Input.  
  • Admin Experience: The Admin Experience provides consistent navigation, understandable naming conventions, and icons that visually explain their purpose in supporting users with limited language, cognitive and learning abilities, notwithstanding the exceptions include issues noted in 2.4.3 Focus Order.

Authored Content (PDF): Authors can create content which is functional with limited cognition.

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:

  • Sign Experience: Partially Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Partially Supports

Web:

  • Sign Experience: As noted in 1.3.2 Meaningful Sequence, In the Sign Experience the sequence is, by default left-to-right and top-down. The document can be opened in a PDF reader to get the correct sequence.
  • Also, as noted in 1.3.1 Info and Relationships, once the document has been signed and submitted, any values entered into form fields will no longer be accessible to the assistive technology user (such as a screen reader). The original accessible PDF is still readable, but any added values are not.
  • Send Experience: Multiple pieces of functionality within the Send Experience are inaccessible to users without vision, as shown in 1.1.1 Non-text content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, 2.4.3 Focus Order, 3.2.2 On Input, 3.3.2 Labels or Instructions and 4.1.2 Name, Role, Value.
  • Admin Experience: Multiple pieces of functionality within the Admin Experience are inaccessible to users without vision, as shown in 1.1.1 Non-text content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, 2.4.3 Focus Order and 4.1.2 Name, Role, Value.

Authored Content (PDF): Several pieces of functionality within the product are inaccessible to users without vision, as shown in 1.3.1 Info and Relationships.

4.2.2 Usage with limited vision

Web:

  • Sign Experience: Partially Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: Some pieces of functionality within the product are inaccessible to users with low vision, as shown in 1.4.3 Contrast (Minimum) and 1.4.4 Resize Text.
  • Send Experience: Several pieces of functionality within the product are inaccessible to users with low vision, as shown in 1.4.3 Contrast (Minimum), 1.4.4 Resize Text.   and 2.4.3 (Focus Order).
  • Admin Experience: Several pieces of functionality within the product are inaccessible to users with low vision, as shown in 1.4.3 Contrast (Minimum), 1.4.4 Resize Text.   and 2.4.3 (Focus Order).

Authored Content (PDF): Authors can create content which is functional with limited vision.

4.2.3 Usage without perception of colour

Web:

  • Sign Experience: Partially Supports
  • Send Experience: Partially Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.3 Contrast (Minimum).  
  • Send Experience: Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.3 Contrast (Minimum).
  • Admin Experience: Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.3 Contrast (Minimum).

Authored Content (PDF): Authors can create content which is functional without perception of color.

4.2.4 Usage without hearing

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any audio content that requires hearing.

Authored Content (PDF): Authors can create content which is functional without hearing.

4.2.5 Usage with limited hearing

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any audio content that requires hearing.

Authored Content (PDF): Authors can create content which is functional with limited hearing.

4.2.6 Usage without vocal capability

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not require user speech.

Authored Content (PDF): Authors can create content which is functional without speech.

4.2.7 Usage with limited manipulation or strength

Web:

  • Sign Experience: Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: All of the Sign Experience can be used by users with limited manipulation or strength.
  • Send Experience: Most functionality within the Send Experience is inaccessible to users with limited manipulation or strength, as shown in 2.1.1 Keyboard, 2.4.3 Focus Order and 2.4.7 Focus Visible.
  • Admin Experience: Most functionality within the Admin Experience is inaccessible to users with limited manipulation or strength, as shown in 2.1.1 Keyboard, 2.4.3 Focus Order and 2.4.7 Focus Visible.

Authored Content (PDF): Authors can create content which is functional with limited manipulation or strength.

4.2.8 Usage with limited reach

Web:

  • Sign Experience: Supports
  • Send Experience: Does Not Support
  • Admin Experience: Does Not Support

Authored Content (PDF): Supports

Web:

  • Sign Experience: All of the Sign Experience can be used by users with limited reach.
  • Send Experience: Most functionality within the Send Experience is inaccessible to users with limited reach, as shown in 2.1.1 Keyboard.
  • Admin Experience: Most functionality within the Admin Experience is inaccessible to users with limited reach, as shown in 2.1.1 Keyboard.

Authored Content (PDF): Authors can create content which is functional with limited reach.

4.2.9 Minimize photosensitive seizure triggers

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain any flashing content.

Authored Content (PDF): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures.

4.2.10 Usage with limited cognition

Web:

  • Sign Experience: Supports
  • Send Experience: Partially Supports
  • Admin Experience: Partially Supports

Authored Content (PDF): Supports

Web:

  • Sign Experience: All parts of the Sign Experience support this criterion.
  • Send Experience: Some features of the Send Experience will present challenges for users with cognitive impairments, as noted in 2.4.3 Focus Order and 3.2.2 On Input.
  • Admin Experience: Some features of the Admin Experience will present challenges for users with cognitive impairments, as noted in 2.4.3 Focus Order.

Authored Content (PDF): Authors can create content which is functional with limited cognition.

4.2.11 Privacy

Web:

  • Sign Experience: Supports
  • Send Experience: Supports
  • Admin Experience: Supports

Authored Content (PDF): Supports

Web: The product does not contain accessibility components that compromise the privacy of the user.

Authored Content (PDF): Authored content does not contain accessibility components that compromise the privacy of the user.

Chapter 5: Generic Requirements

Notes:
 

Criteria

Conformance Level

Remarks and Explanations

5.1 Closed Functionality

5.2 Activation of accessibility features

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 General

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

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 functionality that is closed to keyboards.

5.2 Activation of accessibility features

Not Applicable

The product does not have accessibility features requiring activation.

5.3 Biometrics

Not Applicable

The product does not rely on biological characteristics.

5.4 Preservation of accessibility information during conversion

Authored Content (PDF): Does Not Support

Authored Content (PDF): When converting a source document to PDF, the product does not preserve most accessibility information, as shown in 1.3.1 Info and Relationships.

5.5 Operable parts

5.5.1 Means of operation

Not Applicable

This product does not have operable parts.

5.5.2 Operable parts discernibility

Not Applicable

This product does not have operable parts.

5.6 Locking or toggle controls

5.6.1 Tactile or auditory status

Not Applicable

This product does not have locking or toggle controls.

5.6.2 Visual status

Not Applicable

This product does not have locking or toggle controls.

5.7 Key repeat

Not Applicable

This product relies on platform software to supply key repeat functionality.

5.8 Double-strike key acceptance

Not Applicable

This product does not, by itself, supply a keyboard or keypad.

5.9 Simultaneous user actions

Not Applicable

Simultaneous user actions are not required to operate the product.

Chapter 6: ICT with Two-Way Voice Communication

Notes: Not Applicable
 

Chapter 7: ICT with Video Capabilities

Notes: Not Applicable
 

Chapter 8: Hardware

Notes: Not Applicable
 

Chapter 9: Web (see WCAG 2.1 section)

Notes:Not Applicable
 

Chapter 10: Non-Web Documents

Notes: Not Applicable
 

Chapter 11: Software

Notes: 

 

Criteria

Conformance Level

Remarks and Explanations

11.0 General (informative)

Heading cell – no response required

Heading cell – no response required

11.1.1.1 through 11.4.1.3

See WCAG 2.x section

See information in WCAG 2.x section

11.5 Interoperability with assistive technology

Heading cell – no response required

Heading cell – no response required

11.5.1 Closed functionality

Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.5.2 to clause 11.5.2.17.

Heading cell – no response required

Heading cell – no response required

11.5.2 Accessibility services

Heading cell – no response required

Heading cell – no response required

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.2 Platform accessibility service support for assistive technologies

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.3 Use of accessibility services


Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.

Note: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

It is best practice to develop software using toolkits that automatically implement the underlying platform accessibility services.

Supports

The product supports the use of platform accessibility features.

11.5.2.4 Assistive technology

Where the ICT is assistive technology it shall use the documented platform accessibility services.

Note 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

Note 2: Assistive technology can also use other documented accessibility services.

Not Applicable

This product is not assistive technology.

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

Does Not Support

As noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value, most objects in the product do not expose name, role, or state information to assistive technology.

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

Does Not Support

As noted in 1.3.1 Info and Relationships, the product does not expose the row, column, and headers of table cells to assistive technology.

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

Supports

The product exposes the values of input controls to assistive technology.

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

Partially Supports

The product UI exposes most label relationships to assistive technologies. Exceptions are noted in 1.3.1 Info and Relationships.

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

Does Not Support

The product does not expose hierarchical parent-child relationships to assistive technology, as noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

Partially Supports

Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions are noted in 1.3.2 Meaningful Sequence.

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

Does Not Support

Most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology as noted in 4.1.2 Name, Role, Value.

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Partially Supports

As noted in 2.1.1 Keyboard, the product does not allow assistive technology to perform some actions on objects.

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

Supports

The product exposes focus, text insertion point, and text selection to assistive technology.

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Supports

The product exposes focus, text insertion point, and text selection to assistive technology.

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

Partially Supports

The product notifies assistive technology of most user interaction events. However, the “Success” status is not exposed to assistive technology. Exceptions are noted in 4.1.3 Status Messages.

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Partially Supports

The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions are noted in 4.1.2 Name, Role, Value.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Supports

The product allows assistive technology to modify the text and values of input controls.

11.6 Documented accessibility usage

Heading cell – no response required

Heading cell – no response required

11.6.1 User control of accessibility features

Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

Supports

Accessibility features are included in the product and can be amended to suit the user needs.

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

Supports

The product does not disrupt platform accessibility features.

11.7 User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for color, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.

Supports

User preferences are included in the product and can be amended to suit the user needs.

11.8 Authoring tools

Heading cell – no response required

Heading cell – no response required

11.8.1 Content technology

Heading cell – no response required

Heading cell – no response required

11.8.2 Accessible content creation

(if not authoring tool, enter “not applicable”)

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

Note: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

See WCAG 2.x section

See information in WCAG 2.x section

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

Note 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

Note 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

Partially Supports

Authors can ensure the information required for accessibility is preserved to the extent the information is supported by the destination format while converting content from one format to another. Exceptions are noted in 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence, 1.4.3 Contrast (Minimum), 1.4.4 Resize text, and 4.1.2 Name, Role, Value.

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

Supports

The product provides functionality for authors to run reports on sites to identify accessibility issues.

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such.

Supports

The product provides templates to assist authors in the creation of content.  Authors can ensure the WCAG 2.1 level A and AA requirements are satisfied.

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