Accessibility transaction
Friday, July 31, 2020 at 10:29amHi,
I tried to create accessibility transaction in sandbox, and follow the instruction from this link(https://community.onespan.com/documentation/onespan-sign/guides/admin-guides/user/creating-accessible-transaction), and I got stuck in step 4, as I have no way to add signature to the signer. the 'add signature' button is disabled.
what's the issue then?
Also I tried to create accessibility transaction via API in on-prem v11.25, and seems signer only can sign the document in "turn off accessibility mode', once "turn on accessiblity mode", the form became plain text, but screen reader is able to read out the PDF content, but signer is not able to sign there? is it expected result?
thanks,
Cindy
Reply to: Accessibility transaction
Friday, July 31, 2020 at 10:50amHi Cindy,
Before you start to design the transaction, you need to prepare a tagged PDF and use position extraction to match Adobe Fields with OneSpan Sign fields, it's a mandatory way to add fields.
Unlike to design a non-ada PDF, you need to use specific Adobe Fields to match with particular fields - Adobe Signature represents signature field, Adobe Text Box represents input field, and Adobe Radio Button represents radio field.
Here's a guide for creating an ADA PDF.
I also have a blog introducing how to use sender UI to design an ADA package. (I've attached the PDF I used in the blog)
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Hi Cindy, Before you…
Friday, July 31, 2020 at 12:52pmDuo,
for the sample ADA form you attached, for the signature form field, if I want to use API call to create ADA transaction, what signer information should I put? how does OneSpan know this is signature field or something else?
thanks,
Cindy
Reply to: Accessibility transaction
Friday, July 31, 2020 at 01:14pmHi Cindy,
As below screenshot resembles,
(1)approval ID, approval Name, signature field ID, signature field Name better to be the same as the property name of Adobe Signature ("SIGNATURE1" in my example)
(2)for other fields, field ID and Name need to be the same as the corresponding property name of the Adobe Fields ("DATE1" and "NAME1")
I've also attached the completed JSON to create an ADA package with my sample PDF.
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Accessibility transaction
Friday, July 31, 2020 at 02:27pmDuo,
do you have the sample tagged PDF used in this post? the reason is I want to get some tagged text as well.
https://community.onespan.com/documentation/onespan-sign/guides/admin-guides/user/creating-accessible-pdf
thanks,
Cindy
Reply to: Accessibility transaction
Tuesday, August 4, 2020 at 08:34amHi Duo,
I saw your blog (https://www.onespan.com/blog/onespan-sign-release-1124-upload-accessible-document-sender-ui) and it says 11.24, does it mean our on-prem v11.25 already have the same feature as well? and only available in new sender UI not classic one?
thanks,
Cindy
Reply to: Accessibility transaction
Tuesday, November 2, 2021 at 08:57amHi Duo,
Hope you are doing well!
I still have question about the accessibility testing. I created non-accessibility transaction (ada=false) with the attached form. when I go through the signing process with screen reader, it seems everything can be read such as menu, button, document self and signature field etc without turn on "enable accessibility".
I tested the following scenario:
1) ADA = false, non-tag form (attachment): without "enable accessibility", everything can be read include menu, document self and signature field etc
2) ADA = true, non-tag form (attachment): without "enable accessibility", everything can be read include menu, document self and signature field etc
3) ADA = true, non-tag form (attachment): with "enable accessibility", everything can be read include menu, document self except signature field as it re-format the way as screen reader can read
4) ADA = true, tagged form (the one you used in the blog): with "enable accessibility", everything can be read include menu, document self and signature field etc
To me, it seems scenario #1/#2 and #4 are same, why we need to use tagged form for accessibility ?
thanks,
Cindy
Reply to: Hi Duo, Hope you are doing…
Tuesday, November 2, 2021 at 09:08amHi Cindy,
I am doing well, thanks for asking!
It's documented in the "Creating an Accessible PDF" guide that:
The concept of a "tagged PDF" is central to OneSpan Sign's accessibility solution, since only tagged PDF elements are included in its WCAG HTML representation. Thus all elements intended for accessible content and signing must be tagged (including Signature Fields and those "automatic fields" whose content is triggered by signing).
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Accessibility transaction
Tuesday, November 2, 2021 at 12:13pmHi Duo,
from my scenario(non-tagged PDF with non-ADA transaction), the screen reader still can read for signing ceremony process such as buttons, document, and signature field inside of the document etc. then what's the difference between non-tagged PDF with non-ADA transaction vs tagged PDF with ADA transaction.
As I tested, from sender UI, you have to have tagged form to create ADA transaction.
thanks,
Cindy
Reply to: Hi Duo, from my scenario…
Tuesday, November 2, 2021 at 12:33pmHi Cindy,
Although I am not an expert in ADA area, but from the best of my understanding, even though some modern PDF viewers are able to recognize the text in a PDF, still it splits the word wrongly sometimes (see below screenshot), versus the ADA transaction where the PDF reader reads the text directly from the tags
Duo
Duo Liang OneSpan Evangelism and Partner Integrations Developer
Reply to: Accessibility transaction
Tuesday, November 2, 2021 at 01:35pmthanks Duo for the information.