Adobe Accessibility Conformance Report International Edition

Web: Partially Supports

Web: The product provides sufficient text alternatives for most instances of non-text content. Exceptions include:

Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: Share / Unshare Agreement modal; Send page - Document uploaded; Delegate agreement modal; Add A Reminder Modal; Send in Bulk-Upload(Add recipients section); Track this agreement page.

A decorative image is not hidden from assistive technologies, so a screen reader will announce it unnecessarily. This occurs on the following page: Confirmation to Sign.

Some images do not have a text alternative that contains essential text from the visual image, so people who are blind and/or use a screen reader will not understand the information available in the image. This occurs on the following page: Login.

Web: Supports (Not Applicable)

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

Web: Partially Supports

Web: The product contains audio content in media and closed captions are provided for most instances. Exception includes:

Captions are not provided for media that includes audio and video, so the information provided by the audio track is not available to people who are deaf or hard of hearing. This occurs on the following page: Workflows page.

Web: Supports

Web: The product provides audio description for prerecorded video.

Web: Partially Supports

Web: Most visual structure and relationship information is provided through semantics. Exceptions include:

An HTML list element contains content that is visually presented as a part of the list, but the content's HTML coding does not include it programmatically in that list, so the structure of the list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Track this agreement page.

Some content that is visually presented as a list is not properly marked up as a list, so the structures of those lists are not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Track this agreement page; E-Sign Documents Page.

Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Track this agreement page.

Some text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs in the following component: Right pane (New authoring page) and following pages: Document properties modal; Track this agreement page; E-Sign Documents Page; New Authoring Page; Manage.

Some heading levels are out of order, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: New Authoring Page; Manage; Track this agreement page.

One or more data cells is incorrectly marked up as a header cell in some tables, so the table structure and the header/data relationship between the cell(s) and other cells in those tables will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Manage; Request e-Signatures modal.

Some blocks of text are marked up as headings but are not headings, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Send page - Document uploaded; Request e-Signatures modal; E-Sign Documents Page; Confirmation to Sign; Reports; Admin - Global Settings; Recipient Group modal; Edit agreement settings modal; Workflows page; Send in Bulk-Upload(Add recipients section); Track this agreement page; e-Signature; Send page - default view.

Some groups of form controls are not programmatically associated with their group label, so the purpose of individual controls in each group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following pages: Add A Reminder Modal; E-Sign Documents Page; Workflows page.

A set of radio buttons is not programmatically grouped, so the group label for the set of radio buttons will not be conveyed to people who are blind and/or use a screen reader, and they will not understand the purpose of the individual radio buttons. This occurs on the following page: Admin - Global Settings.

Some sets of checkboxes are not programmatically grouped, so the group label for each set of checkboxes will not be conveyed to people who are blind and/or use a screen reader, and they will not understand the purpose of the individual checkboxes. This occurs on the following pages: Admin - Global Settings; Add A Reminder Modal; Share / Unshare Agreement modal.

Web: Partially Supports

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

The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: New Authoring Page; E-Sign Documents Page; Track this agreement page.

Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following pages: Request e-Signatures modal; Send in Bulk-Upload(Add recipients section); Send page - Document uploaded; Send page - default view; E-Sign Documents Page.

The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following page: E-Sign Documents Page.

Web: Supports

Web: Instructions do not rely solely on sensory characteristics.

Web: Partially Supports

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

Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of some controls, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs in the following component: Right pane (New authoring page) and following pages: Manage; E-Sign Documents Page; Admin - Global Settings.

Color is used as the only method to convey information so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following page: New Authoring Page.

Color is used as the only method to identify errors on a form field, so the error will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs in the following component: Left pane (New authoring page).

Color is the only visual method used to identify a link, and the contrast ratio of some links' text with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify those links. This occurs on the following pages: Admin - Global Settings; Legal Notices' modal; Reports.

Web: Supports

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

Web: Partially Supports

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

Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs in the following component: Left pane (New authoring page) and following pages: Document properties modal; Admin - Global Settings; New Authoring Page; Track this agreement page; Manage; Add A Reminder Modal; E-Sign Documents Page; Reports.

Web: Supports

Web: The product does not include keyboard traps.

Web: Supports

Web: The product does not provide character key shortcuts.

Web: Supports

Web: The product supports the adjustment or cancellation of time-based limits.

Web: Partially Supports

Web: On most pages, where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. Exceptions include:

The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs in the following component: Left pane (New authoring page).

The user cannot pause, stop, or hide moving or blinking content, so people who cannot read text quickly or track moving objects, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following page: e-Signature.

Web: Supports (Not Applicable)

Web: The product does not contain flashing content.

Web: Supports

Web: The product provides mechanism to bypass repeated blocks.

Web: Partially Supports

Web: Most pages have descriptive and informative titles. Exception includes:

The page's programmatic title does not identify the purpose of the page, so people who use a screen reader will not know the purpose of the page without reading its content. This occurs on the following pages: Send page - Document uploaded; New Authoring Page; Workflows page; Send in Bulk-Upload(Add recipients section); Review and Sign email; Send page - default view; Send successful.

Web: Partially Supports

Web: Most components receive focus in a meaningful order. Exceptions include:

Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following page: Manage.

Keyboard focus or touch screen swiping goes to multiple elements that are hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs in the following component: Header (Post Login) and following pages: Send in Bulk-Upload(Add recipients section); Send page - default view; New Authoring Page; Request e-Signatures modal; Send page - Document uploaded.

When a modal closes, keyboard focus is not returned to the control that opened the modal or to another logical location, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following page: Manage.

Web: Partially Supports

Web: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. Most components receive focus in a meaningful order.

Exceptions include:

The purpose of multiple links is not made clear by each link's text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where each link goes. This occurs in the following component: Header (Post Login) and following pages: Home; E-Sign Documents Page; Send in Bulk-Upload(Add recipients section).

Web: Supports

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

Web: Supports

Web: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click.

Web: Partially Supports

Web: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:

Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Add A Reminder Modal; Admin - Global Settings; Confirmation to Sign.

The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Manage; Add A Reminder Modal; Edit agreement settings modal; Send page - Document uploaded; Admin - Global Settings; Recipient Group modal; Login; E-Sign Documents Page; New Authoring Page.

Web: Supports

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

Web: Supports

Web: The language is programmatically determinable within the product.

Web: Supports

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

Web: Partially Supports

Web: In most cases, when a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user, or the user is informed about the change ahead of time. Exception includes:

When a user changes the setting of a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriented. This occurs in the following component: Right pane (New authoring page).

Web: Supports

Web: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.

Web: Partially Supports

Web: Most input errors are identified and described to the users in text. Exception includes:

Errors for some form inputs (such as text input fields, radio buttons, select dropdowns, or checkboxes) are not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs in the following component: Left pane (New authoring page) and following pages: Send page - Document uploaded; Add A Reminder Modal; Share / Unshare Agreement modal.

Web: Partially Supports

Web: Labels are provided for most input fields. Exceptions include:

The labels for some form fields are missing, so each field's purpose is not clear. This occurs on the following pages: Send in Bulk-Upload(Add recipients section); E-Sign Documents Page; Share / Unshare Agreement modal; Manage; Request e-Signatures modal; e-Signature.

Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following pages: Login; Cancel Modal; Share / Unshare Agreement modal; Delegate agreement modal.

Select or dropdown control missing a visible label so the purpose of the Select or dropdown control is not clear. This occurs on the following page: Send in Bulk-Upload(Add recipients section).

Web: Supports

Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.

Web: Does Not Support

Web: User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include:

Multiple form input elements do not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of each element and may not understand its purpose or how to interact with it. This occurs on the following pages: Add A Reminder Modal; Share / Unshare Agreement modal.

An element functions as if it has two programmatic roles, so one or both roles may be incorrectly conveyed to people who are blind and/or use a screen reader or other assistive technology, since assistive technology can convey only one role for any single element. This occurs on the following page: Track this agreement page.

Multiple buttons do not have a programmatic name, so each button's name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: New Authoring Page; Home; Track this agreement page; Send in Bulk-Upload(Add recipients section); e-Signature; Reports; Upload Signed Document modal; Manage.

A select element does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the select control. This occurs on the following page: Confirmation to Sign.

Multiple elements that appear and function like a slider control does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, or current value or how to interact with it. This occurs on the following page: Workflows page.

The content of multiple tooltips cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content. This occurs in the following component: Right pane (New authoring page) and following pages: Manage; Track this agreement page.

An element that appears and functions like a combo box does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: e-Signature.

A control that expands or collapses an accordion (to show or hide its content) is missing one or more attributes in its HTML code that provides its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or current state of the control or how to interact with it. This occurs on the following page: Reports.

In a table that can be sorted by column, the sorted state (ascending or descending) of the table's columns is not conveyed to assistive technology or the state conveyed is incorrect, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the order in which the table's content is presented and whether that order is meaningful when interpreting the data. This occurs on the following page: Manage.

An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Add A Reminder Modal.

Elements that are focusable or contain one or more focusable elements are programmatically hidden, so people who use the keyboard to navigate, as well as people who are blind and/or use a screen reader or other assistive technology, will not be able to perceive or interact with the elements. This occurs on the following pages: Track this agreement page; Manage.

Multiple elements do not have an attribute in their HTML code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs in the following components: Left pane (New authoring page); Right pane (New authoring page) and following pages: New Authoring Page; Send in Bulk-Upload(Add recipients section); Track this agreement page; E-Sign Documents Page; Recipient Group modal.

A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page: Admin - Global Settings.

The HTML code for some links or buttons is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of these elements. This occurs on the following pages: Workflows page; Home.

A form field does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the form field or what input it requires. This occurs on the following page: Send in Bulk-Upload(Add recipients section).

Multiple buttons do not have a programmatic role, so each button's role (usually button, but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Admin - Global Settings; Request e-Signatures modal; Track this agreement page; E-Sign Documents Page; Manage.

When a button is pressed, its pressed state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the button is pressed. This occurs in the following component: Left pane (New authoring page).

When some controls are disabled, their disabled state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the controls are disabled. This occurs on the following pages: Track this agreement page; E-Sign Documents Page; Admin - Global Settings.

Multiple buttons do not have a programmatic role and name, so each button's role (usually button, but sometimes link or something else) and its name (such as "Submit" or "Cancel") are not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs in the following component: Left pane (New authoring page) and following page: New Authoring Page.

Multiple elements do not have an attribute in their HTML code that will provide its programmatic state (such as "checked"/"not checked") to assistive technology or the state assigned is not correct, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the current state of the element or how to interact with it. This occurs on the following pages: Add A Reminder Modal; Edit Recipient settings modal; E-Sign Documents Page.

For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked. This occurs in the following component: Right pane (New authoring page) and following pages: Track this agreement page; Admin - Global Settings; Workflows page; Document properties modal.

The programmatic state of an element that reveals or hides content ("expanded" or "collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of the element or the state will be misrepresented. This occurs in the following components: Left pane (New authoring page); Right pane (New authoring page) and following pages: Workflows page; Manage; Admin - Global Settings; New Authoring Page; Home; Track this agreement page.

Element contains ARIA attributes not allowed for its role. This occurs on the following page: E-Sign Documents Page.

Web: Supports (Not Applicable)

Web: The product does not contain live synchronized media.

Web: Supports

Web: The product provides audio description for prerecorded video.

Web: Supports

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

Web: Partially Supports

Web: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Exception includes:

No programmatic purpose is provided for an input element (like a text input field), so browsers or assistive technology are not able to automatically suggest information to fill in the input. This occurs on the following page: Login.

Web: Partially Supports

Web: Most text meets minimum contrast requirements. Exceptions include:

The color contrast ratio between text and its background is less than 4.5:1 (or less than 3:1 for large text), so people who are colorblind or have low vision may have difficulty reading the text. This occurs in the following component: Header (Post Login) and following pages: Individual Documents modal; Admin - Global Settings.

The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs in the following component: Right pane (New authoring page) and following pages: Legal Notices' modal; E-Sign Documents Page; Login; Manage; Admin - Global Settings; Add A Reminder Modal; Send in Bulk-Upload(Add recipients section); e-Signature; Recipients modal.

The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of each control. This occurs in the following component: Left pane (New authoring page) and following pages: Manage; e-Signature; Login.

The color contrast ratio between text placed over an image and that image is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following page: Login.

The color contrast ratio between placeholder text in multiple inputs and each input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following pages: Share / Unshare Agreement modal; Cancel Modal; Manage; E-Sign Documents Page; Add A Reminder Modal.

Web: Partially Supports

Web: Most content is readable and functional when browser zoom is set to 200% of its initial size. Exceptions include:

Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following pages: Review and Sign email; Send page - Document uploaded; Add A Reminder Modal; Track this agreement page; E-Sign Documents Page.

Functionality is lost when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to this functionality. This occurs on the following page: Add A Reminder Modal.

Web: Partially Supports

Web: On most pages, when content can be presented visually using only text, an image of text is not used to present that text. Exception includes:

Text on the page is text embedded in an image instead of actual text. An image of text is difficult to zoom or otherwise modify, so people who have low vision and need to enlarge text to read it may not be able to read the text. People with other disabilities that need to otherwise modify text to read it also may not be able to read this text. This occurs on the following pages: Login; E-Sign Documents Page; Track this agreement page; New Authoring Page.

Web: Partially Supports

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

When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following pages: E-Sign Documents Page; Add A Reminder Modal; Document properties modal.

When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs in the following component: Left pane (New authoring page) and following pages: E-Sign Documents Page; Send in Bulk-Upload(Add recipients section); Individual Documents modal; Review and Sign email; Document properties modal; Track this agreement page; Send page - default view; Send page - Document uploaded; Share / Unshare Agreement modal.

When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs in the following components: Right pane (New authoring page); Header (Pre Login); Header (Post Login); Left pane (New authoring page) and following pages: Admin - Global Settings; Review and Sign email; Share / Unshare Agreement modal; E-Sign Documents Page; Add A Reminder Modal; Hide Agreement Modal; Document properties modal; New Authoring Page; e-Signature; Upload Signed Document modal.

Web: Partially Supports

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

The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs in the following component: Right pane (New authoring page) and following pages: Login; E-Sign Documents Page; Cancel Modal; e-Signature; New Authoring Page; Workflows page; Share / Unshare Agreement modal; Admin - Global Settings; Add A Reminder Modal; Send page - Document uploaded; Manage; Decline agreement modal.

The focus indicators of some interactive elements (like buttons or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when each interactive element is receiving focus. This occurs in the following component: Left pane (New authoring page) and following pages: Workflows page; Admin - Global Settings; e-Signature; E-Sign Documents Page.

The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements. This occurs on the following pages: Add A Reminder Modal; E-Sign Documents Page; Document properties modal; Workflows page.

An image or graphic (like a chart) or part of the image/graphic required to understand its content does not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by the image/graphic. This occurs on the following page: E-Sign Documents Page.

An icon (or part of the icon required to understand its content) does not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by the icon. This occurs on the following page: E-Sign Documents Page.

Web: Partially Supports

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

When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following page: Home.

Web: Partially Supports

Web: In most cases, when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. Exceptions include:

Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs in the following component: Header (Post Login) and following pages: E-Sign Documents Page; Workflows page.

Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs on the following page: E-Sign Documents Page.

Web: Supports

Web: Users can locate web pages in the product through multiple ways in the site.

Web: Partially Supports

Web: Most headings and labels for form and interactive controls are informative. Exceptions include:

Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs in the following component: Left pane (New authoring page) and following pages: Send page - Document uploaded; Recipient Group modal; Reports; Send in Bulk-Upload(Add recipients section); Manage.

Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs in the following component: Left pane (New authoring page) and following pages: E-Sign Documents Page; New Authoring Page; Manage; Admin - Global Settings; Add A Reminder Modal; Review and Sign email; Send page - Document uploaded; e-Signature; Workflows page; Edit agreement settings modal.

Web: Partially Supports

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

Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs in the following components: Right pane (New authoring page); Left pane (New authoring page) and following pages: e-Signature; Recipients modal; E-Sign Documents Page.

The visual focus indicator for multiple interactive elements (such as links, buttons, or form inputs) is not visible, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following pages: Cancel Modal; Manage; Add A Reminder Modal; Share / Unshare Agreement modal.

Web: Supports

Web: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

Web: Partially Supports

Web: Most functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. Exception includes:

Some functionality relies on a dragging movement with no single-pointer, single-touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture. This occurs in the following component: Left pane (New authoring page) and following pages: Send page - default view; Send page - Document uploaded; New Authoring Page.

Web: Partially Supports

Web: The size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Exception includes:

Multiple target hit areas do not meet a minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs on the following pages: Legal Notices' modal; Admin - Global Settings; Workflows page.

Web: Partially Supports

Web:On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. Exception includes:

Portions of content on multiple pages that are in a different language from the rest of the content on the page are not programmatically assigned the language for the portion of content, so screen readers may mispronounce those parts of the content. This occurs in the following components: Header (Post Login); Header (Pre Login) and following page: E-Sign Documents Page.

Web: Supports

Web: When navigational mechanisms are repeated in the product, such as the primary navigation menu and the sub menu in settings, they occur in a consistent relative order.

Web: Supports

Web: Components with the same functionality are identified consistently.

Web: Partially Supports

Web: Where input errors are automatically detected, suggestions for correction are provided to the user in most cases. Exception includes:

A form field's error message does not suggest how to correct the error, so users may have difficulty determining how to complete the form successfully. This occurs on the following page: Send page - Document uploaded.

Web: Supports

Web: The product does not process legal commitments or financial transactions. When editing files changes to user-controllable data are reversible or can be confirmed before finalizing.

Web: Supports

Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the website.

Web: Partially Supports

Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptionsincludes:

Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages, or they may not hear them in a timely fashion. This occurs in the following component: Left pane (New authoring page) and following pages: Send page - Document uploaded; Manage; Cancel Modal; Recipient Group modal; Send in Bulk-Upload(Add recipients section); Share / Unshare Agreement modal; Request e-Signatures modal; E-Sign Documents Page; Upload Signed Document modal; Delegate agreement modal; Add A Reminder Modal; e-Signature; Send page - default view; Admin - Global Settings; Individual Documents modal.

Web: Partially Supports

Web: Most functionality is usable without vision. Exceptions include:

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 2.1.1 Keyboard

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 3.1.2 Language of Parts

As noted in 3.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 3.3.3 Error Suggestion

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: Most functionality is usable with limited vision. Exceptions include:

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.4 Resize text

As noted in 1.4.5 Images of Text

As noted in 2.1.1 Keyboard

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.1.2 Language of Parts

As noted in 3.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 3.3.3 Error Suggestion

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: Most functionality is usable without perception of color. Exceptions include:

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 3.3.1 Error Identification

Web: Partially Supports

Web: Most functionality is usable without hearing. Exceptions include:

As noted in 1.2.2 Captions (Prerecorded)

As noted in 3.1.2 Language of Parts

Web: Partially Supports

Web: Most functionality is usable with limited hearing. Exceptions include:

As noted in 1.2.2 Captions (Prerecorded)

As noted in 3.1.2 Language of Parts

Web: Supports

Web: All functionality is usable without speech.

Web: Partially Supports

Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.3.3 Error Suggestion

As noted in 4.1.2 Name, Role, Value

Web: Supports

Web: All functionality is usable with limited reach and strength.

Web: Partially Supports

Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions include:

As noted in 1.1.1 Non-text Content

As noted in 1.2.2 Captions (Prerecorded)

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.5 Images of Text

As noted in 2.1.1 Keyboard

As noted in 2.2.2 Pause, Stop, Hide

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.1.2 Language of Parts

As noted in 3.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 3.3.3 Error Suggestion

As noted in 4.1.2 Name, Role, Value

Web: Not Applicable

Web: The product is not platform software.

Web: Not Applicable

Web: The product is not platform software.

Web: Partially Supports

Web: The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: In most instances, when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exception includes:

As noted in 1.3.1 Info and Relationships

Web: Partially Supports

Web:For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 4.1.2 Name, Role, Value

Web: Supports

Web: When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology.

Web: Supports

Web: All text, text attributes (such as whether text is static or editable), and text boundaries (such as text that receives visual focus) are programmatically determinable, so they can be perceived and conveyed by assistive technology.

Web: Supports

Web: When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology.

Web: Supports

Web: When one or more actions may be performed on an element, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology.

Web: Partially Supports

Web: For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exception includes:

As noted in 2.1.1 Keyboard

Web: Partially Supports

Web: On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exception includes:

As noted in 2.4.7 Focus Visible

Web: Supports

Web: When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.

Web: Supports

Web: In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exception includes:

As noted in 4.1.3 Status Messages

Web: Not Applicable

Web: The product is not platform software.

Web: Not Applicable

Web: Not Applicable to Web.

Web: Not Applicable

Web: The product does not provide an alternative user interface that functions as assistive technology.

Web: Does Not Support

Web: The multimedia player does not provide closed caption controls.

Web: Not Applicable

Web: The product does not contain media with a video component that offers audio descriptions controls.

Web: Not Applicable

Web: This product is not an authoring tool.

Web: Not Applicable

Web: This product is not an authoring tool.

Web: Not Applicable

Web: This product is not an authoring tool.

Web: Not Applicable

Web: This product is not an authoring tool.

Web: Partially Supports

Web: Most functionality is usable without vision. Exceptions include:

As noted in 1.1.1 Non-text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 2.1.1 Keyboard

As noted in 2.2.2 Pause, Stop, Hide

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 3.1.2 Language of Parts

As noted in 3.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 3.3.3 Error Suggestion

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

Web: Partially Supports

Web: Most functionality is usable with limited vision. Exceptions include:

As noted in 1.1.1 Non-text Content

As noted in 1.3.5 Identify Input Purpose

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.4 Resize text

As noted in 1.4.5 Images of Text

As noted in 1.4.10 Reflow

As noted in 1.4.11 Non-text Contrast

As noted in 1.4.12 Text Spacing

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.1.1 Keyboard

As noted in 2.2.2 Pause, Stop, Hide

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 3.3.3 Error Suggestion

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: Most functionality is usable without perception of color. Exceptions include:

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (Minimum)

As noted in 1.4.11 Non-Text Contrast

As noted in 3.3.1 Error Identification

Web: Partially Supports

Web: Most functionality is usable without hearing. Exceptions include:

As noted in 1.1.1 Non-text Content

As noted in 1.2.2 Captions (Prerecorded)

As noted in 2.2.2 Pause, Stop, Hide

Web: Partially Supports

Web: Most functionality is usable with limited hearing. Exceptions include:

As noted in 1.2.2 Captions (Prerecorded)

As noted in 2.2.2 Pause, Stop, Hide

Web: Supports

Web: All functionality is usable without speech or other vocal output.

Web: Partially Supports

Web: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.2.2 Pause, Stop, Hide

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 2.5.3 Label in Name

As noted in 3.2.2 On Input

As noted in 4.1.2 Name, Role, Value

Web: Partially Supports

Web: Most functionality is usable by people with limited reach. Exceptions include:

As noted in 2.5.3 Label in Name

Web: Supports

Web: All functionality may be operated in a mode that minimizes the potential for triggering photosensitive seizures.

Web: Partially Supports

Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions include:

As noted in 1.4.12 Text Spacing

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.2.2 Pause, Stop, Hide

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (In Context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 3.3.3 Error Suggestion

As noted in 4.1.3 Status Messages

Web: Supports

Web: Where the product provides features for accessibility, it maintains the privacy of people who use these features at the same level as other users.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have closed functionality.

Web: Not Applicable

Web: The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features.
instead relies upon platform accessibility features.

Web: Not Applicable

Web: Biometrics are not used to access or use the product.

Web: Not Applicable

Web: The product does not convert content.

Web: Not Applicable

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

Web: Not Applicable

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

Web: Not Applicable

Web: Tactile or auditory status is not included in the product.

Web: Not Applicable

Web: Visual status of controls is discernible in the product.

Web: Not Applicable

Web: Key repeat functionality is not found in the product.

Web: Not Applicable

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

Web: Not Applicable

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

Web: Does Not Supports

Web: The product does not display closed captions. Example includes:

Workflows page (Video)

Web: Not Applicable

Web: The product does not support closed captions.

Web: Not Applicable

Web: The product does not transmit, convert, or record video with synchronized audio.

Web: Not Applicable

Web: The product does not support closed captions.

Web: Not Applicable

Web: The product does not support closed captions.

Web: Does Not Support

Web: The product does not provide a mechanism to select and play audio description. Example includes:

Workflows page (Video)

Web: Not Applicable

Web: The product does not have a mechanism to play audio description.

Web: Not Applicable

Web: The product does not transmit, convert, or record video with synchronized audio.

Web: Not Applicable

Web: The product does not provide user controls for captions and audio descriptions.