Questions about flow of accessibility enabled signing sessions
Thursday, January 10, 2019 at 04:46amGood Morning,
I am currently in the process of making modifications to exsiting signing ceremonies in order to use the WithAda() Flag and make the documents readable by software such as the JAWS reader. In the process of converting these over and after some initial testing, i have some questions about the flow.
From what I have gathered from the ceremonies that I have switched to accessability enable using the WithAda() flag, the eSign software will now display a link on the top right to "Enable Accessability Mode". It seems that a user wanting to use reader software would need to know to click that link.
The documents with a simple accept button at the bottom, such as the concent document, seem to work ok at this point, but documents with specific click to sign areas do not.
It seems to me that documents where a signature is required in a specific spot, there is no way to accept this document on the accessibility enabled screen and the user must then know they have to turn accessability mode back off and then click the signature.
This is further compounded by the fact that the header of the document, even in accessibility mode, still displays "Please review and sign this Document by scrolling and clicking on the "Click to Sign" or "Click to Initial" boxes. " even though those boxes do not exist.
One of the processes that i am converting to using ADA has multiple documents with multiple places for signatures and it seems the only way to get through these is to, turn on accessibility mode, read it, turn off accessibility mode, click to add signature, and then repeat each of those steps for every page (in this case 5 pages)
I showed this to one of the stakeholders of this process and they asked me if this was the only way it worked, to which i didnt know for sure. so my questions are as follows:
Can you confirm that the use of accessibility mode does make this process compliant to WCAG 2.0 Level AA?
Are there additional steps that need to be done in order to make my flow compliant? for instance, is the expectation that a compliant document only needs accepting and not a signature placement? Are there additional flags that need to be set? or other settings needed in BackOffice?
Is the flow above truly the correct flow or am i missing something?
Is it possible to get the signatures to be accepted in the accessibility mode so the user does not have to flip back and forth?
Is it possible to have the document heading different on the accessibility mode page so it doent cause user confusion? perhaps allowing the user know that in order to get to the next page they have to turn accessilibity back off?
Thank you for your time.
Reply to: Questions about flow of accessibility enabled signing sessions
Thursday, January 10, 2019 at 06:16amReply to: Questions about flow of accessibility enabled signing sessions
Thursday, January 10, 2019 at 07:59amReply to: Questions about flow of accessibility enabled signing sessions
Thursday, January 10, 2019 at 08:18amReply to: Questions about flow of accessibility enabled signing sessions
Thursday, January 10, 2019 at 08:26amReply to: Questions about flow of accessibility enabled signing sessions
Friday, January 11, 2019 at 04:55am