W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2018

Re: 1.3.4, autocomplete and esignatures

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Fri, 19 Jan 2018 16:22:05 +0000
To: James Nurthen <james.nurthen@oracle.com>, WCAG <w3c-wai-gl@w3.org>
Message-ID: <916DA57D-F863-4CA5-A814-8C8675DCAAE8@adobe.com>
I wouldn’t think that a drawn signature would need a “name” value, but if the prompt is “Indicate that you accept this contract by typing your name” then it seems that there is reasonable room for confusion, but I think that that too is being used as a “signature” rather than a name, so believe that we can clarify this in the understanding document.

You can see what the Adobe Sign process is by looking at this: https://www.adobesigndemo.com/en/demo/send


Andrew Kirkpatrick
Group Product Manager, Accessibility


From: James Nurthen <james.nurthen@oracle.com>
Date: Friday, January 19, 2018 at 11:05
To: WCAG <w3c-wai-gl@w3.org>
Subject: 1.3.4, autocomplete and esignatures
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Friday, January 19, 2018 at 11:04

I’m concerned that the current 1.3.4 could interfere with esignatures.
One of the requirements is:
Intent to sign.
Just as with a handwritten signature, a signer must show clear intention to electronically sign an agreement. is is usually an easy requirement to satisfy. For example, signers can show intention by using a mouse to draw their signature, typing their name or clicking a button clearly labeled “I Accept” or something similar.

Use of autocomplete on a name field would mean that we could not be sure that the user intended to sign. I think we need a “unless cannot be done due to regulatory requirements” statement.

Received on Friday, 19 January 2018 16:22:29 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:22 UTC