Download the PDF

The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding the availability of commercial Electronic and Information Technology products and services with features that support accessibility. It is assumed that offerers will provide additional contact information to facilitate more detailed inquiries.

The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table. Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.

Date: May 10, 2016

Name of product: Adobe Sign (formerly known as: Adobe EchoSign, Adobe Document Cloud eSign Services)

Contact for more information: access@adobe.com

 

Summary
Guideline Applicable Compliance

Section 1194.21 – Software Applications and Operating Systems

Not Applicable

Section 1194.22 – Web-based Intranet and Internet Information and Systems

Applicable

Supports with Exceptions

Section 1194.23 – Telecommunications Products

Not Applicable

Section 1194.24 – Video and Multimedia Products

Not Applicable

Section 1194.25 – Self-Contained, Closed Products

Not Applicable

Section 1194.26 – Desktop and Portable Computers

Not Applicable

Section 1194.31 – Functional Performance Criteria

Applicable

Supports with Exceptions

Section 1194.41 – Information, Documentation, Support

Applicable

Supports

 
Section 1194.22 Web-based Intranet and Internet Information and Applications — Detail
Criteria Supporting features Remarks and explanations

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

Supports with exceptions

The Adobe Sign web application provides text equivalent for some user interface components. However, a rating of Supports with Exceptions is assigned due to the following exceptions:

  • The documents to be signed are rendered as images without textual equivalents.

  • Background images used for actionable elements such as check boxes and radio buttons do not have textual alternatives.

  • Multiple images and image links lack meaningful alternative text.

  • Simulated dialogs do not textually indicate the beginning and end of the dialog content.

  • Many page tab elements lack textual descriptions indicating state and role.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Not Applicable

The Adobe Sign web application does not provide multimedia presentations.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Supports with exceptions

The Adobe Sign web application does not always use color as the sole means to convey information. A rating of Supports with Exception is made because many page tab elements provided in the site rely on color to indicate the active state.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Supports with exceptions

The Adobe Sign web application does not require an associated style sheet to be read. A rating of Supports with Exceptions is assigned due to the following exceptions:

  • Multiple actionable elements, such as the radio buttons and checkboxes in the Send module, are provided as background images. When CSS and Background images are disabled, these controls disappear.

  • The site has some pages that use bold and larger fonts as implicit section headings.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not Applicable

The Adobe Sign web application does not utilize server-side image maps.

(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Not Applicable

The Adobe Sign web application does not utilize client-side image maps.

(g) Row and column headers shall be identified for data tables.

Supports

The Adobe Sign web application contains modules that display information in a tabular format. The row and column headers are correctly identified.

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

Supports

The Adobe Sign web application contains modules that display information in a tabular format. The data cells are properly associated to the data headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation

Does not support

The Adobe Sign web application has modules that contain frames. A determination of Does Not Support is made because almost all of the frames do not provide a valid title attribute.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Supports

The Adobe Sign web application does not display blinking or flickering page elements.

(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

Not Applicable 

The Adobe Sign web application does not utilize a text-only alternative page.

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.

Supports with exceptions

The Adobe Sign web application utilizes JavaScript to display content; although some information provided can be rendered by assistive technologies, a determination of Supports with Exceptions is made due to the following exceptions:

  • Multiple simulated controls implemented with div tags, such as the Show Me How right menu link, and anchor tags without href attributes, such as the account holder name menu link in the top navigation bar, are not keyboard accessible.

  • Simulated dialogs do not textually indicate the beginning and end of the dialog content.

  • Many actionable elements spawn simulated dialogs without alerting users of assistive technologies of the change.

  • Keyboard focus does not return properly from simulated dialogs.

  • Simulated dialogs, such as the fields’ context menus when editing a document, cannot be closed from the keyboard.

(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).

Supports with exceptions

The Adobe Sign web application does not require an applet or plug-in to interpret all of the pages’ content. However, a rating of Supports with Exceptions is given because the application provides an actionable element to open a PDF version of documents without a link to download the reader.

(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Supports with exceptions

Some form elements in The Adobe Sign web application are accessible to users of assistive technologies. However, a rating of Supports with Exceptions is given due to the following issues: 

  • Multiple form field elements lack meaningful explicit labels.

  • Many fieldset elements do not have legend elements.

  • Some groups of form controls are missing fieldset and legend elements.

  • Some form elements are assigned positive tabindex attribute which causes an illogical tab order on some pages.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Does not support

A determination of Does Not Support is made because The Adobe Sign web application does not provide a mechanism for skipping past repetitive navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supports

The Adobe Sign web application warns users before logging them off after a certain period of inactivity.

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following Priority 1 checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) – 1.1, (b) – 1.4, (c) – 2.1, (d) – 6.1, (e) – 1.2, (f) – 9.1, (g) – 5.1, (h) – 5.2, (i) – 12.1, (j) – 7.1, (k) – 11.4.

 
Section 1194.31 Functional Performance Criteria - Detail
Criteria Supporting features Remarks and explanations

(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.

Supports with exceptions

The Adobe Sign web application provides accessibility information about some of its controls. It also allows keyboard access to some active elements.

Notably, users without vision are now able to access and interact with all functionality needed to sign and submit a signed document. Because documents for signing are rendered as images, as noted in 1194.22 (a), users without vision will need to download the document to be signed in Adobe Reader to review the document and then return to the web version to complete the signing process.

However, the rating of Supports with Exceptions is assigned due to the following issues:

  • As stated in §1194.22 (a), (d), (i), (n), and  (l), when information about user interface elements is not available to assistive technologies, users of screen readers may not be able to render or interact appropriately with the controls.

  • The accessibility issues listed in §1194.22 (l) affect people who are blind or visually impaired because they navigate through the application exclusively with the keyboard. 

  • Due to the accessibility violation stated in §1194.22 (o), users of screen readers will be unable to skip past repetitive links.

  • As stated in §1194.22 (n), when the tab order is not logical, users of screen readers may not understand the organization or content of the page.

  • As stated in §1194.22 (m), users of screen readers who do not have the required version of the plug-in may have difficulty navigating to the site to download the plug-in.

  • Throughout the Adobe Sign web application, there are multiple same link text elements targeting different pages.

  • Keyboard focus that is provided to inactive elements creates confusion for users of screen reader.

  • Information provided in title attributes for simulated controls (i.e., div) throughout the web application are not rendered by screen readers. Users who are blind will not receive the information.

  • In the Send module, a data table is used to lay out the page content. This is confusing to users who cannot see the visual display.

  • In the Send – Preview Document – Formula Dialog module, there are two sets of lists for the same list. This may cause issues for users of screen readers, who may have difficulty distinguishing between and navigating through the lists.

(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.

Supports with exceptions

The Adobe Sign application generally provides modes of use for users with limited vision. It is assigned a rating of Supports with Exceptions because of the following exceptions:

  • Some accessibility issues as listed in §1194.22 (l) affect people with low vision because they often navigate through the application exclusively from the keyboard.

  • In various modules within Adobe Sign, the contrast between the foreground and background colors of text is not sufficient (i.e., it is below the recommended ratio of 4.5:1). Sufficient color contrast ensures that people with low vision or color perception deficiencies and users viewing the page without color can understand page content.

  • As stated in §1194.22 (a) and (d), users with low vision cannot access all information when CSS and background image are disabled.

  • As stated in §1194.22 (l), the visual keyboard focus issue affects keyboard-only users who use visual keyboard focus to determine which element has focus and what action to perform on it.

(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided

Supports

The Adobe Sign web application does not require user hearing for information retrieval.

(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

Supports

The Adobe Sign web application does not require user hearing for information retrieval.

(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.

Supports

The Adobe Sign web application does not require user speech for information retrieval.

(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Supports with exceptions

The Adobe Sign web application provides access to multiple user interface controls to users with mobility impairment.

Notably, users are now able to access and interact via the keyboard with all functionality needed to sign and submit a signed document.

However, a rating of Supports with Exceptions is assigned due to the following issues:

  • If form fields lack information such as labels and group labels as stated in §1194.22 (n), users of voice recognition software such as Dragon Naturally Speaking cannot access them by voicing the information about the controls. The only method to access the controls that lack accessible information is with simulated mouse actions and by navigating with the mouse grid functionality, which is tedious.

  • Due to the accessibility violations stated §1194.22 (o), (l), and (d), keyboard-only users are unable to access some parts of the application and cannot interact with the interface elements.

  • As stated in §1194.22 (l), the visual keyboard focus issue affects users with mobility impairments who use visual keyboard focus to determine which element has focus and what action to perform on it.