OneSpan Sign and Accessibility

Accessibility Support for Senders has been implemented throughout OneSpan Sign using the strategies, standards, and resources developed by the World Wide Web Consortium (W3C). Currently, OneSpan Sign is almost compliant with the 2.0 AA version of the Web Content Accessibility Guidelines (WCAG). In the near future, we will meet the 2.1 version of the WCAG at the AA level (and some guidelines at the AAA level).

Accessibility Features Available in OneSpan Sign

Here are some of the features we have implemented to make OneSpan Sign accessible:

  • All OneSpan Sign features and actions are available through the use of keyboard (no need to use a mouse).
  • User interface pages are structured with hierarchical headers.
  • Informative images are also accompanied by descriptive text.
  • In forms, labels are explicitly associated with form fields.
  • In data tables, header cells and data cells are linked to each other.
  • Links have explicit titles, which clearly describe the content of the link.
  • Links that open in a new window are tagged. This means that when a new window is opened the reader is explicitly told so.
  • User interface pages can be magnified, up to 200% of the original size.
  • The contrast between text colors and background colors are compliant with accessibility standards.

Screen Readers

The following (screen-reader, browser) combinations are supported on desktop and laptop computers:

  • JAWS with Chrome
  • NVDA with Chrome
  • NVDA with Firefox
  • VoiceOver with Safari

We strongly recommend that desktops and laptops use JAWS/NVDA with Chrome or NVDA with Firefox.

The following (screen-reader. mobile-device) combinations are supported:

  • VoiceOver with iOS
  • TalkBack with Android

Using the Signing Ceremony with a Screen Reader

To sign a transaction using a screen reader note the following:

  • The transaction must first be made accessible. Accessible transactions must be created using either the New User Experience or via integration.
  • An accessible transaction can only contain PDF files that have been tagged in conformity with ISO 14289-1:2012. These PDFs must be tagged outside of OneSpan Sign.
  • The signer must enable accessibility from within the Signing Ceremony.

The HTML representation for screen readers preserves the structure and the content of the original PDF, but not its appearance.

Supported Languages

Screen readers can vocalize the content of OneSpan Sign in all supported languages (though some text is currently available only in English and French).

Was this information helpful?