Re: 1.3.4, autocomplete and esignatures

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:


Andrew Kirkpatrick
Group Product Manager, Accessibility

From: James Nurthen <>
Date: Friday, January 19, 2018 at 11:05
To: WCAG <>
Subject: 1.3.4, autocomplete and esignatures
Resent-From: WCAG <>
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