This document discusses the following aspects of OneSpan Sign's compliance with accessibility standards:
Our Commitment
OneSpan is committed to providing best-in-class electronic signature services that are accessible to people of all abilities, including blind and visually impaired signers. The company currently does this by complying with the Web Content Accessibility Guidelines of WCAG 2.1 Level AA.
Accordingly, our OneSpan Sign product has an Accessibility Support component that enables blind and visually impaired signers to review and click-to-sign PDF documents that are presented in a supported browser.
Because OneSpan Sign is compliant with WCAG 2.1 AA , it automatically complies with many local regulations. Among those are the following:
US ADA
US Section 508
Canadian Standard on Web Accessibility
Ontario AODA
Quebec SGQRI 008
ISO/IEC 40500
European Directive (EU) 2016/2102
French RGAA
Supported Readers and Browsers
OneSpan Sign supports the (screen reader, browser) combinations listed below. Their selection was based on the results of the most recent WebAIM survey.
Desktops & Laptops
JAWS with Chrome (PC)
JAWS with Edge (PC)
NVDA with Firefox (PC)
NVDA with Chrome (PC)
VoiceOver with Safari (Mac)
Mobile Devices
VoiceOver/iOS with Safari (iPhone)
Talkback/Android with Chrome and Firefox (Smartphone)
We regularly update each screen reader and browser in the above lists and usually support a product's two most recent versions.
Accessibility Conformance Reports (VPAT)
OneSpan provides an Accessibility Conformance Report based on VPAT® Version 2.4 Rev - WCAG Edition.
The most recent reports were created by testing the English and French versions of the Signer Experience in OneSpan Sign's 11.50 release. Those reports can be accessed by clicking Accessibility Conformance Report for WCAG 2.0 and Accessibility Conformance Report for WCAG 2.1.
External Audits
If you want to run an external audit of OneSpan Sign, please follow these guidelines:
Don’t use automatic tools, as these may generate many false positives.
Inform your tester about the context in which tests will occur (e.g., testing the Professional Edition of OneSpan Sign in a well-defined environment).
Provide a fully accessible PDF document, as described in the section Creating an Accessible PDF. Also identify the tester who created the PDF, so they can be consulted if necessary.
If your auditor thinks they have found a bug, please send OneSpan a detailed report with:
A description of the bug, including its context
A description of the steps needed to reproduce the bug
Relevant screenshots of the Signer Experience
Screenshots of any relevant code
The exact URL of any relevant webpage
Any other information that might be helpful