Adobe Accessibility Conformance Report

VPAT® Version 2.0 – November 2017

Product Information

Name of Product/Version: Adobe Sign

Product Description: Adobe Sign is an e-signature solution to authenticate and formally sign agreements sent through the Sign Service.

Date: October 2018

Contact information: access@adobe.com

Notes: “Authored Content (HTML)” refers to documents converted by the product and embedded in web pages. “Authored Content (PDF)” refers to documents converted by the product and exported. The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.

Evaluation Methods Used: Testing Adobe Sign involved extensive use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well exclusive 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 standards/guidelines:

Standard/Guideline Included In Report

Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/

Level A - Yes
Level AA - Yes
Level AAA - No

Section 508 as published in 2017, at http://www.Section508.gov

Yes

EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, at http://mandate376.standards.eu/standard

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.
  • Supports with Exceptions: 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.0 Report

Sections 1 and 2 also document conformance with:

  • EN 301 549:  Chapter 9 - Web, Chapter 10 - Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 - Non-Web Software (closed functionality).
  • 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Section 1: Success Criteria, Level A

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.2.1 (Web)
  • 10.2.1 (non-web document)
  • 11.2.1.1 (Software)
  • 11.2.2.1 (Closed Functionality Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports

Web: Most product functions have components and sections implemented as image content lacking appropriately descriptive textual equivalent. Examples include:

  • The product uses CSS applied iconography for visual identification of numerous controls, states, and conditions, in some cases lacking textual equivalents for the imagery.
  • Uploaded documents are represented using high resolution thumbnail images, uniformly identified by the page number within the file (e.g., “Page 1 of 3”), rather than providing a textual equivalent of the image embedded content, when appropriate. However, the image includes guidance for the user to open the document in the Adobe Web Reader or download and open in Acrobat Reader to allow full reading of appropriately tagged PDF documents.

Authored Content (HTML): Authored HTML content utilizes image thumbnails of uploaded/rendered documents for presentation to the user, tagged with non-descriptive textual equivalents. Authors do not have methods provided to control the representation or the textual equivalent. Direct download links to the original document are, in most cases, provided.

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.2.2 (Web)
  • 10.2.2 (non-web document)
  • 11.2.1.2 (Software)
  • 11.2.2.2.1 and 11.2.2.2.2 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

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

Authored Content (HTML): Authored content 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.2.3 (Web)
  • 10.2.3 (non-web document)
  • 11.2.1.3 (Software)
  • 11.2.2.3 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not contain prerecorded synchronized media.

Authored Content (HTML): Authored content does not contain prerecorded synchronized media.

Authored Content (PDF): Authored content 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.2.4 (Web)
  • 10.2.4 (non-web document)
  • 11.2.1.4 (Software)
  • 11.2.2.4 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

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

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.2.7 (Web)
  • 10.2.7 (non-web document)
  • 11.2.1.7 (Software)
  • 11.2.2.7 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Does Not Support

Authored Content (PDF): Supports with Exceptions

Web: All parts of the Sign Experience support this criterion. And, some other parts of the product provide programmatic representation of information and visual structure. However, most functions of the product have visually meaningful groupings, blocks, or sections of content that are not programmatically determinable. Examples include:

  • Logically related and visually labeled blocks of controls in some forms are not provided programmatically identifiable groupings.
  • Multipart composite widgets and structures are not programmatically identifiable as unified structures.
  • Data tables are used for some field groupings, with row header cells used as legends.
  • Most fields in error are not identified programmatically or associated to error text in a manner available to assistive technology and non-visual users.

Authored Content: (HTML): Authored content presents Signature and fill fields required for user interaction rendered as HTML content floating over a thumbnail image, deriving critical meaning from their visual presentation and spatial location over the image.

Authored Content: (PDF): The product preserves most structure information from source documents, such as headings and tables. Exceptions include:

  • Table headers are not preserved.

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

  • 9.2.8 (Web)
  • 10.2.8 (non-web document)
  • 11.2.1.8 (Software)
  • 11.2.2.8 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports with Exceptions

Web: The product presents content in a meaningful sequence for most pages. For some pages, programmatic reading order of content and focus order of controls diverge from the visually presented natural reading order.

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.

Authored Content (HTML): Authors can ensure that content meets this criterion for documents where a left-to-right and top-to-bottom sequence of overlays is logical. However, a meaningful reading sequence cannot be achieved for some documents, such as documents with overlays arranged in columns.

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 does not correspond to their visual order or tab order.

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

  • 9.2.9 (Web)
  • 10.2.9 (non-web document)
  • 11.2.1.9 (Software)
  • 11.2.2.9 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product’s instructions do not rely solely on sensory characteristics.

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

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

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.2.10 (Web)
  • 10.2.10 (non-web document)
  • 11.2.1.10 (Software)
  • 11.2.2.10 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. And, a majority of the product does not utilize coloration as the sole means of communicating visual information or detail. Exceptions include:

  • The product has custom widgets that utilize coloration for visual indication selection in drop-down menus, including instances of excessively subtle (low contrast) coloration shifts.
  • The product has instances of textual links, embedded within or proximal to static textual content, which are visually differentiated from static text only through coloration.
  • The product uses color coding flags to identify signatories assigned to each field within main view the authoring tools. A textual equivalent is available but requires drilling down into properties dialogs for each field.

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

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.2.11 (Web)
  • 10.2.11 (non-web document)
  • 11.2.1.11 (Software)
  • 11.2.2.11 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

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

Authored Content (HTML): Authored content does not contain audio that plays automatically.

Authored Content (PDF): Authored content does not contain audio that plays automatically.

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.15 (Web)
  • 10.2.15 (non-web document)
  • 11.2.1.15 (Software)
  • 11.2.2.15 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. And, some of the other product functionality can be operated through a keyboard interface. However, many functions of the product have actionable controls that are not operable using only keyboard input. Examples include:

  • The product has custom controls which do not appear in the tab order and cannot be operated through keyboard input, including, in some instances, controls which are required for successful completion of process flows and/or for error correction.
  • The product has custom instructional tooltips and pop-out Help sections on multiple pages which are driven exclusively by mouse interactions, with no keyboard equivalent provided.

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

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.16 (Web)
  • 10.2.16 (non-web document)
  • 11.2.1.16 (Software)
  • 11.2.2.16 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not include keyboard traps.

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

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

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.17 (Web)
  • 10.2.17 (non-web document)
  • 11.2.1.17 (Software)
  • 11.2.2.17 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not contain controls or forms which require precise or minimum timing for operation. The product provides the user with the option to extend session on imminent timeout.

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

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

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

  • 9.2.18 (Web)
  • 10.2.18 (non-web document)
  • 11.2.1.18 (Software)
  • 11.2.2.18 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

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

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

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

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.19 (Web)
  • 10.2.19 (non-web document)
  • 11.2.1.19 (Software)
  • 11.2.2.19 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not contain flashing or blinking animated content.

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

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

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.20 (Web)
  • 10.2.20 (non-web document) – Does not apply
  • 11.2.1.20 (Software) – Does not apply
  • 11.2.2.20 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 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 with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The products uses headings to provide structure and allow users to bypass the repeated site navigation bar on most pages.

Authored Content (HTML): Authored content is presented as single page deliveries and does not contain repeated blocks that would require a skip mechanism.

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.21 (Web)
  • 10.2.21 (non-web document)
  • 11.2.1.21 (Software) - Does not apply
  • 11.2.2.21 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the product has pages with non-unique and generically descriptive page titles; a majority of pages default to the product name “Adobe Sign, an Adobe Document Cloud Solution”.

Authored Content (HTML): Authored HTML pages present generic title values. Authoring tools do not provide a method to alter or update the value.

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.22 (Web)
  • 10.2.22 (non-web document)
  • 11.2.1.22 (Software)
  • 11.2.2.22 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports with Exceptions

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: Most components receive focus in a meaningful order. The product contains a small number of pages where focus order follows a path which diverges from the visually implied logical order of the interaction, as well as instances of active focus management for modal dialogs causing unexpected limitations on Shift+Tab key navigation.

In the Sign Experience the focus order for form fields is in a left-to-right and top-to-bottom order. However, the document can be viewed in a PDF reader for the authored focus order.

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

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.23 (Web)
  • 10.2.23 (non-web document)
  • 11.2.1.23 (Software)
  • 11.2.2.23 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the product has a small number of instances in which product logo images are utilized for links labeled with alternative text generically identifying the product rather than the destination of the link.

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

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

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.2.27 (Web)
  • 10.2.27 (non-web document)
  • 11.2.1.27 (Software)
  • 11.2.2.27 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Does Not Support

Authored Content (PDF): Supports

Web: The language is programmatically determinable within the product.

Authored Content (HTML): The product does not provide authors with a method to define natural language for generated content in Signature views.

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

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.2.29 (Web)
  • 10.2.29 (non-web document)
  • 11.2.1.29 (Software)
  • 11.2.2.29 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

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

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

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.2.30 (Web)
  • 10.2.30 (non-web document)
  • 11.2.1.30 (Software)
  • 11.2.2.30 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the language selection control in the shared page footer section triggers a page reload immediately on changing the value of the selection field.

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

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

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.2.33 (Web)
  • 10.2.33 (non-web document)
  • 11.2.1.33 (Software)
  • 11.2.2.33 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product provides visual indications of errors where input errors are automatically detected.

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

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.2.34 (Web)
  • 10.2.34 (non-web document)
  • 11.2.1.34 (Software)
  • 11.2.2.34 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the product relies upon proximal text, CSS applied iconography, and visual styling to provide meaningful identification of actionable controls and structures within some forms and pages, without providing programmatically determinable structuring or labelling for the actionable controls.

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

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

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.2.37 (Web)
  • 10.2.37 (non-web document)
  • 11.2.1.37 (Software)
  • 11.2.2.37 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. And, the product contains properly parsed and nested tagging structure; however, the web application contains instances of non-unique ID values assigned to elements in the document on a small number of pages. Replicated ID values are, in most cases, not perceptible in a user context, assigned to hidden content and/or are not used for accessibility related property mapping. Exceptions include:

  • The User Profile page contains non-unique IDs used to map field labels for user input, technically invalidating the label assignments.

Authored Content (HTML): Authored HTML content constructed using the product tools is properly formed and validly parsed. Authors can ensure that uploaded externally produced documents meet this requirement.

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.2.38 (Web)
  • 10.2.38 (non-web document)
  • 11.2.1.38 (Software)
  • 11.2.2.38 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the other components of the product contain multiple instances of actionable controls which provide no programmatic reflection of their visually implied name, role, and value/state, including controls that are critical to main path functionality of their page/flow.

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

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

Section 2: Success Criteria, Level AA

Notes:

Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria Conformance Level Remarks and Explanations

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

  • 9.2.5 (Web)
  • 10.2.5 (non-web document)
  • 11.2.1.5 (Software)
  • 11.2.2.5 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not contain live synchronized media.

Authored Content (HTML): Authored content 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.2.6 (Web)
  • 10.2.6 (non-web document)
  • 11.2.1.6 (Software)
  • 11.2.2.6 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

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

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

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

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.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.12 (Web)
  • 10.2.12 (non-web document)
  • 11.2.1.12 (Software)
  • 11.2.2.12 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the product does contain some instances of text, including labels for actionable controls, which do not meet minimum contrast requirements. Exceptions include:

  • Coloration of error message banner sections, including on the Login form.
  • Textual labels for “Search” buttons present on the Dashboard and Management pages.
  • Textual labels for “Edit” controls used within the Account Configuration screens.

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

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.2.13 (Web)
  • 10.2.13 (non-web document)
  • 11.2.1.13 (Software)
  • 11.2.2.13 (Closed Software)
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. And, most pages support browser zoom. Some pages of the product have tags which suppress zoom functionality in some mobile browsers.

Authored Content (HTML): Authors can ensure that uploaded document content meets this criterion, and document files will retain their accommodations when downloaded. Documents rendered in the “Review and Sign” view have tags which suppress zoom functionality in some mobile browsers.

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.2.14 (Web)
  • 10.2.14 (non-web document)
  • 11.2.1.14 (Software)
  • 11.2.2.14 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Does Not Support

  • Sign Experience: Supports

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, other functions of the product, such as Fill & Sign, rely on page thumbnail content from uploaded documents to identify and interact with files.

Authored Content (HTML): Content generated by authoring tools renders uploaded documents as image thumbnail content. Direct links to original content documents are provided and sufficient to meet user needs in most pages. Exceptions include:

  • For documents presented requesting a Signature (delivered via email link), textual content of the page thumbnails is essential for operation of the page functionality. Downloadable file content cannot be used to complete operations and a user is required to interact with the page bearing the thumbnail content.

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

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.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.24 (Web)
  • 10.2.24 (non-web document) – Does not apply
  • 11.2.1.24 (Software) – Does not apply
  • 11.2.2.24 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 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

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: Multiple paths to the product’s pages are provided where appropriate and required.

Authored Content (HTML): Authored HTML content is presented as a single page (linked from an invitational email).

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.25 (Web)
  • 10.2.25 (non-web document)
  • 11.2.1.25 (Software)
  • 11.2.2.25 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: Headings and labels within the product, when present, appropriately describe contents in context.

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

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.26 (Web)
  • 10.2.26 (non-web document)
  • 11.2.1.26 (Software)
  • 11.2.2.26 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the product contains a small number of button controls which lack explicit visual indication of focus, primarily comprised of buttons labeled using CSS applied iconography.

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

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

Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria Conformance Level Remarks and Explanations

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

  • 9.2.28 (Web)
  • 10.2.28 (non-web document)
  • 11.2.1.28 (Software) – Does not apply
  • 11.2.2.28 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Does Not Support

Authored Content (PDF): Supports

Web: All instances of inline change of natural language within the product are programmatically identified.

Authored Content (HTML): When a source document contains inline natural language changes, the product does not preserve them in conversion.

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

Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria Conformance Level Remarks and Explanations

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

  • 9.2.31 (Web)
  • 10.2.31 (non-web document) – Does not apply
  • 11.2.1.31 (Software) – Does not apply
  • 11.2.2.31 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 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

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product has shared navigation blocks and sections that are consistent in design and functionality across pages.

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

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.2.32 (Web)
  • 10.2.32 (non-web document) – Does not apply
  • 11.2.1.32 (Software) – Does not apply
  • 11.2.2.32 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 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 with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, several different versions of custom controls for email address list input and file upload functionality are used elsewhere in the product, widgets of each type having similar functionality to their related versions on other pages but variation in behaviors and divergent programmatic structuring.

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

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

Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria Conformance Level Remarks and Explanations

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

  • 9.2.35 (Web)
  • 10.2.35 (non-web document)
  • 11.2.1.35 (Software)
  • 11.2.2.35 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product provides error suggestion in cases where correction recommendations can be provided.

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

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.2.36 (Web)
  • 10.2.36 (non-web document)
  • 11.2.1.36 (Software)
  • 11.2.2.36 (Closed Software) – Does not apply
  • 11.6.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

2017 Section 508

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

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product provides methods for correction and editing of all submitted content and data.

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

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

Table 3: Success Criteria, Level AAA

Notes: Not Evaluated

2017 Section 508 Report

Notes:

Chapter 3: Functional Performance Criteria (FPC)

Notes: The requirements in WCAG 2.0 and Chapter 5 sufficiently address the functions of the product, and no instances of equivalent facilitation were observed in the product. Therefore, the conformance levels and remarks in this table are informative only.

Criteria Conformance Level Remarks and Explanations

302.1 Without Vision

Web: Supports with Exceptions

  • Sign Experience: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports with Exceptions

Web: 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.

However, other core features of the product are not sufficiently understandable or functionally inoperable using screen reader applications.

  • The product contains custom controls which are not programmatically identified for assistive technology.
  • The product contains critical image content which does not provide textual equivalent, including meaningful images applied using CSS background-image styling which are fully transparent to assistive technology.
  • The product’s core functionalities rely on visual presentation and layout positioning of components, without full equivalence provided for non-visual users.

Authored Content (HTML): Authored content presents Signature and Fill fields required for user interaction as HTML content floating over a thumbnail image, deriving critical meaning exclusively from their visual presentation and spatial location over the image without textual or programmatic equivalent. However the user is able to view the document in it’s entirety to read and understand context prior to signing.

Authored Content (PDF): In general, authors can ensure that content meets this criterion.
However, there are some notable exceptions:

  • 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.
  • As noted in 2.4.3 Focus Order, form fields added by the product may not receive focus in a meaningful order. However forms can be opened in a PDF reader to get the correct sequence.

302.2 With Limited Vision

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, the other parts of the product have core features that are designed in a manner which limits operability by users with limited vision.

  • The product makes heavy use of CSS applied background-image iconography for meaningful identification of controls and content, which may be purged by common accessibility configurations used by users with low vision (e.g., Windows High Contrast Mode).
  • The product contains a number of custom controls which are not operable using only keyboard input.
  • The product contains instances of controls which, while technically operable with keyboard input, do not provide visual indication of keyboard focus.

Authored Content (HTML): Authored content contains instances of fixed content utilizing CSS applied background-image iconography for meaningful identification of controls and content, which may be purged by common accessibility configurations used by users with low vision (e.g., Windows High Contrast Mode).

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

302.3 Without Perception of Color

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However other parts of the product contain sections of text, including labels for actionable controls, which do not meet minimum contrast requirements. The product additionally, in a small number of instances, utilizes color coding without direct non-color equivalence provided.

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

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

302.4 Without Hearing

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not have exclusively audible functionality or modes of operation.

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

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

302.5 With Limited Hearing

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not have exclusively audible functionality or modes of operation.

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

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

302.6 Without Speech

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not have interactions or functionality requiring speech control.

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

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

302.7 With Limited Manipulation

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports with Exceptions

Web: All parts of the Sign Experience supports this criterion. However other parts of the product contain instances of actionable controls and active functionalities of which are not operable exclusively using keyboard input. Examples include:

  • The product has custom controls which do not appear in the tab order and cannot be operated through keyboard input, including, in some instances, controls which are required for successful completion of process flows and/or for error correction.
  • The product has custom instructional tooltips and pop-out Help sections on multiple pages which are driven exclusively by mouse interactions, with no keyboard equivalent provided to access the content.

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

Authored Content (PDF): Most authored content is functional with limited manipulation. Exceptions include:

  • As noted in 2.4.3 Focus Order, form fields added by the product do not receive focus in a meaningful order. As a workaround, sighted keyboard-only users can tab through all fields to find the one they want to review.

302.8 With Limited Reach and Strength

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product is functional with limited reach and strength.

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

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: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. Some product functions are more difficult than necessary for users with limited language, cognitive, or learning abilities.

  • The product has pages that do not provide informative page titles, instead being generically titled as the Product name “Adobe Sign, an Adobe Document Cloud Solution”.
  • Focus order and programmatic order of content in some forms does not match the visually implied reading order.

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

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

Chapter 4: Hardware

Notes: Not Applicable

Chapter 5: Software

Notes:

501 General

Criteria Conformance Level Remarks and Explanations

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.0 section.

See information in the WCAG section

502 Interoperability with Assistive Technology

Criteria Conformance Level Remarks and Explanations

502.2 Documented Accessibility Features

See 502.2.1-502.2.2

502.2.1 User Control of Accessibility Features

Not Applicable

Not applicable to web pages

502.2.2 No Disruption of Accessibility Features

Not Applicable

Not applicable to web pages

502.3 Accessibility Services

See 502.3.1-502.3.14

502.3.1 Object Information

Not Applicable

Not applicable to web pages

502.3.2 Modification of Object Information

Not Applicable

Not applicable to web pages

502.3.3 Row, Column, and Headers

Not Applicable

Not applicable to web pages

502.3.4 Values

Not Applicable

Not applicable to web pages

502.3.5 Modification of Values

Not Applicable

Not applicable to web pages

502.3.6 Label Relationships

Not Applicable

Not applicable to web pages

502.3.7 Hierarchical Relationships

Not Applicable

Not applicable to web pages

502.3.8 Text

Not Applicable

Not applicable to web pages

502.3.9 Modification of Text

Not Applicable

Not applicable to web pages

502.3.10 List of Actions

Not Applicable

Not applicable to web pages

502.3.11 Actions on Objects

Not Applicable

Not applicable to web pages

502.3.12 Focus Cursor

Not Applicable

Not applicable to web pages

502.3.13 Modification of Focus Cursor

Not Applicable

Not applicable to web pages.

502.3.14 Event Notification

Not Applicable

Not applicable to web pages

502.4 Platform Accessibility Features

Not Applicable

Not applicable to web pages

503 Applications

503.1 General. Applications shall conform to 503.

Criteria Conformance Level Remarks and Explanations

503.2 User Preferences

Not Applicable

Not applicable to web pages

503.3 Alternative User Interfaces

Not Applicable

Not applicable to web pages

503.4 User Controls for Captions and Audio Description

See 503.4.1-503.4.2

503.4.1 Caption Controls

Not Applicable

Not applicable to web pages

503.4.2 Audio Description Controls

Not Applicable

Not applicable to web pages

504 Authoring Tools

504.1 General. Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.

Criteria Conformance Level Remarks and Explanations

504.2 Content Creation or Editing  (if not authoring tool, enter “not applicable”)

See WCAG 2.0 section

See information in the WCAG section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Authored Content (HTML): Does Not Support

Authored Content (PDF): Supports

Authored Content (HTML): When converting a source document to HTML, the product does not preserve most accessibility information. Examples include:

  • Most text is converted to images without text equivalents.
  • Most document structure is not preserved.

Authored Content (PDF): Accessibility information is preserved upon conversion.

504.2.2 PDF Export

Supports

Correctly authored content exports correctly.

504.3 Prompts

Does Not Support

The product prompts authors for some accessibility information, such as an accessible name for a custom form field. However, most authoring functions do not prompt authors to create content which conforms to WCAG 2.0 Levels A and AA. Examples include:

  • The product does not prompt users to upload source files containing accessibility information.
  • The product does not prompt for an accessible name for the various types of signature fields.

504.4 Templates

Not Applicable

The product does not provide templates. This requirement is not applicable to templates created by users.

Chapter 6: Support Documentation and Services

Notes: Information about documentation and support services is available in Adobe’s Accessibility Conformance Report for HelpX.

EN 301 549 Report

Notes:

Chapter 4: 4.2 Functional Performance Statements (FPS)

Notes: According to C.4 Functional Performance, this chapter is informative only.

Criteria Conformance Level Remarks and Explanations

4.2.1 Usage without vision

Web: Supports with Exceptions

  • Sign Experience: Supports with Exceptions

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports with Exceptions

Web: 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.

However, core features of other parts of the product are designed in a manner which limits operability by users with limited vision.

  • The product makes heavy use of CSS applied background-image iconography for meaningful identification of controls and content, which may be purged by common accessibility configurations used by users with low vision (e.g., Windows High Contrast Mode).
  • The product contains a number of custom controls which are not operable using only keyboard input.
  • The product contains instances of controls which, while technically operable with keyboard input, do not provide visual indication of keyboard focus.

Authored Content (PDF): In general, authors can ensure that content meets this criterion.

However, there are some notable exceptions:

  • 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.
  • As noted in 2.4.3 Focus Order, form fields added by the product may not receive focus in a meaningful order. However forms can be opened in a PDF reader to get the correct sequence.

4.2.2 Usage with limited vision

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports with Exceptions

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, other core features of the product are designed in a manner which limits operability by users with limited vision. Examples include:

  • The product makes heavy use of CSS applied background-image iconography for meaningful identification of controls and content, which may be purged by common accessibility configurations used by users with low vision (e.g., Windows High Contrast Mode).
  • The product contains a number of custom controls which are not operable using only keyboard input.
  • The product contains instances of controls which, while technically operable with keyboard input, do not provide visual indication of keyboard focus.

Authored Content (HTML): Authored content contains instances of fixed content utilizing CSS applied background-image iconography for meaningful identification of controls and content, which may be purged by common accessibility configurations used by users with low vision (e.g., Windows High Contrast Mode).

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

4.2.3 Usage without perception of colour

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web:All parts of the Sign Experience supports this criterion. However other parts of the product contain sections of text, including labels for actionable controls, which do not meet minimum contrast requirements. Additionally, the product, in a small number of instances, utilizes color coding without direct non-color equivalence provided.

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

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

4.2.4 Usage without hearing

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not have exclusively audible functionality or modes of operation.

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

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

4.2.5 Usage with limited hearing

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not have exclusively audible functionality or modes of operation.

Authored Content (HTML): Authors can create content that is functional with limited hearing.

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

4.2.6 Usage without vocal capability

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not have controls or functionality requiring vocal interaction.

Authored Content (HTML): Authors can create content that is functional without vocal capability.

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

4.2.7 Usage with limited manipulation or strength

Web: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports with Exceptions

Web: All parts of the Sign Experience supports this criterion. However other parts of the product contain instances of actionable controls and active functionalities of which are not operable exclusively using keyboard input. Examples include:

  • The product has custom controls which do not appear in the tab order and cannot be operated through keyboard input, including, in some instances, controls which are required for successful completion of process flows and/or for error correction.
  • The product has custom instructional tooltips and pop-out Help sections on multiple pages which are driven exclusively by mouse interactions, with no keyboard equivalent provided to access the content.

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

Authored Content (PDF): Most authored content is functional with limited manipulation or strength. Exceptions include:

  • As noted in 2.4.3 Focus Order, form fields added by the product do not receive focus in a meaningful order. As a workaround, sighted keyboard-only users can tab through all fields to find the one they want to review.  

4.2.8 Usage with limited reach

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product is functional with limited reach.

Authored Content (HTML): Authors can create content that is functional with limited reach.

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

4.2.9 Minimize photosensitive seizure

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: The product does not contain flashing content.

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

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: Supports with Exceptions

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

Web: All parts of the Sign Experience supports this criterion. However, some other product functions are more difficult than necessary for users with limited language, cognitive, or learning abilities. Exceptions include:

  • The product pages do not provide informative page titles, instead being generically titled as the product name “Adobe Sign, an Adobe Document Cloud Solution”.
  • Focus order and programmatic order of content in some forms does not match the visually implied reading order.

Authored Content (HTML): Authors can create content that is functional with limited cognition.

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

4.2.11 Privacy

Web: Supports

  • Sign Experience: Supports

Authored Content (HTML): Supports

Authored Content (PDF): Supports

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

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

Not Applicable

5.1.2.2-5.1.6.2 are not applicable for this product.

5.2 Activation of accessibility features

Not Applicable

The product relies on native accessibility features of the web browser and client operating system; it does not have accessibility features built into the product itself.

5.3 Biometrics

Not Applicable

The product does not rely on biological characteristics.

5.4 Preservation of accessibility information during conversion

Authored Content (HTML): Does Not Support

Authored Content (PDF): Supports

Authored Content (HTML): When converting a source document to HTML, the product does not preserve most accessibility information. Examples include:

  • Most text is converted to images without text equivalents.
  • Most document structure is not preserved.

Authored Content (PDF): Accessibility information is preserved upon conversion.

5.5 Operable parts

5.5.1 Means of operation

Not Applicable

The product does not contain operable parts.

5.5.2 Operable parts discernibility

Not Applicable

The product does not contain operable parts.

5.6 Locking or toggle controls

5.6.1 Tactile or auditory status

Not Applicable

The product does not contain locking or toggle controls.

5.6.2 Visual status

Not Applicable

The product does not contain locking or toggle controls.

5.7 Key repeat

Not Applicable

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

5.8 Double-strike key acceptance

Not Applicable

The product does not provide a keyboard or keypad.

5.9 Simultaneous user actions

Supports

The product relies on platform software features, such as Sticky Keys, to ensure simultaneous user actions are not required.

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

Notes: See WCAG 2.0 section.

Chapter 10: Non-web Documents

Notes: Not Applicable

Criteria Conformance Level Remarks and Explanations

10.1 General

10.2 Document success criteria

10.2.1 through 10.2.38

See WCAG 2.0 section.

See information in the WCAG section

10.2.39 Caption positioning

Not Applicable

The product does not enable authors to create or embed video.

10.2.40 Audio description timing

Not Applicable

The product does not enable authors to create or embed video.

Chapter 11: Software

Notes:

Criteria Conformance Level Remarks and Explanations

11.2.1 Non-web software success criteria (excluding closed functionality)

Not Applicable

Not applicable to web pages

11.2.2 Non-web software success criteria (closed functionality)

Not Applicable

Not applicable to web pages

11.3 Interoperability with assistive technology

11.3.1 Closed functionality

Not Applicable

Not applicable to web pages

11.3.2 Accessibility services

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

Not Applicable

Not applicable to web pages

11.3.2.2 Platform accessibility service support for assistive technologies

Not Applicable

Not applicable to web pages

11.3.2.3 Use of accessibility services

Not Applicable

Not applicable to web pages

11.3.2.4 Assistive technology

Not Applicable

Not applicable to web pages

11.3.2.5 Object information

Not Applicable

Not applicable to web pages

11.3.2.6 Row, column, and headers

Not Applicable

Not applicable to web pages

11.3.2.7 Values

Not Applicable

Not applicable to web pages

11.3.2.8 Label relationships

Not Applicable

Not applicable to web pages

11.3.2.9 Parent-child relationships

Not Applicable

Not applicable to web pages

11.3.2.10 Text

Not Applicable

Not applicable to web pages

11.3.2.11 List of available actions

Not Applicable

Not applicable to web pages

11.3.2.12 Execution of available actions

Not Applicable

Not applicable to web pages

11.3.2.13 Tracking of focus and selection attributes

Not Applicable

Not applicable to web pages

11.3.2.14 Modification of focus and selection attributes

Not Applicable

Not applicable to web pages

11.3.2.15 Change notification

Not Applicable

Not applicable to web pages

11.3.2.16 Modifications of states and properties

Not Applicable

Not applicable to web pages

11.3.2.17 Modifications of values and text

Not Applicable

Not applicable to web pages

11.4 Documented accessibility usage

11.4.1 User control of accessibility features

Not Applicable

The product is not platform software.

11.4.2 No disruption of accessibility features

Supports

The product does not disable or disrupt client-side accessibility configurations or features

11.5 User preferences

Not Applicable

Web content is isolated from its underlying platform.

11.6 Authoring tools

11.6.1 Content technology

11.6.2 Accessible content creation

See WCAG 2.0 section.

See information in the WCAG section

11.6.3 Preservation of accessibility information in transformations

Does Not Support

In restructuring transformations into HTML, the product does not preserve most accessibility information in the output. Examples include:

  • Most text is converted to images without text equivalents.
  • Most document structure is not preserved.

11.6.4 Repair assistance

Not Applicable

The product does not have accessibility checking functionality.

11.6.5 Templates

Not Applicable

The product does not provide templates. This requirement is not applicable to templates created by users.

Chapter 12: Documentation and Support Services

Notes: Information about documentation and support services is available in Adobe’s Accessibility Conformance Report for HelpX.

Chapter 13: ICT Providing Relay or Emergency Service Access

Notes: Not Applicable