OneSpan Sign Release 11.12: Accessibility Support
Version 11.12 of OneSpan Sign has recently been deployed to the preview environment where we've added an Accessibility Support component that enables blind and visually impaired signers to review and sign documents in accordance with WCAG 2.0 Level AA, in addition of a couple of bug fixes. You can find the deployment dates for all our environments on our Trust Center page. Let's get into it.
The OneSpan Sign Signing Ceremony has been extended to enable blind and visually impaired signers to review and sign documents. In particular, this feature transforms a standard PDF document into an audible HTML file that can be reviewed and signed by blind and visually impaired signers using OneSpan Sign. In order to make use of this feature, you will need to do the following:
- Create an accessible PDF
- Create an accessible transaction
To create an accessible PDF, you will need to add tags. A tagged PDF is a PDF file that contains meta-information around certain groups of PDF instructions inside a page content. You can find detailed instructions on how to create such a PDF in our documentation page. The next step is to create the accessible package. Mainly, you will need to turn on the "ada" flag in the package settings and ensure that the signature names and fields in your PDF match your code. You can find an example with our REST API here. Additionally, if you want to use the accessibility feature with our SDKs, you will have to download the latest version of the SDKs(11.12). You can find examples with our Java and .NET SDK on our GitHub page.
A couple of bugs have also been fixed in this release. Most notably, we've fixed an issue where you could not upload multiple documents in an existing transaction with a JSON payload using our REST API. In addition, we've also fixed an issue that was causing a Text Tag's maximum length (maxlen) to be ignored during extraction. You can find examples of this attribute here. You can also find the complete list of bug fixes on our documentation page. If you have questions regarding this blog or anything else concerning integrating OneSpan Sign into your application, visit the developer community forums: developer.esignlive.com. That's it from me. Thank you for reading! If you found this post helpful, please share it on Facebook, Twitter, or LinkedIn.