The Accessibility Support Enables people with disabilities to use OneSpan Sign in accordance with the Americans with Disabilities Act of 1990 (ADA) and other global accessibility requirements. component enables people with disabilities to use OneSpan Sign in accordance with the Americans with Disabilities Act of 1990 (ADA) and other global accessibility requirements.
OneSpan has been extending its Accessibility Support's WCAG compliance to additional use cases for senders and signers. And we plan to do more.
Keep an eye on our Release Notes for updates on how we are continuing to update this feature.
The rest of this page discusses:
- Accessibility Features Available in OneSpan Sign
- Screen Readers
- Using the Signer Experience with a Screen Reader
- Supported Languages
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 a keyboard (no need to use a mouse).
- User interface pages are structured with hierarchical headers.
- Informative images are 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 that it's being opened.
- 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.
The following (screen reader, browser) combinations are supported on desktop and laptop computers:
- JAWS with Chrome
- JAWS with Edge
- 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
To sign a transaction using a screen reader, note the following:
- The transaction must first be made accessible. Accessible transactions must be created via the New User Experience or via integration.
- An accessible transaction can contain only 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 Signer Experience.
The HTML representation for screen readers preserves the structure and content of an original PDF, but not its appearance.
Screen readers can vocalize the content of OneSpan Sign in all supported languages.