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

RE: Issue 948 SC 1.3.5 Identify Input Purpose - autocomplete technique VS Privacy/Security

From: White, Jason J <jjwhite@ets.org>
Date: Tue, 5 Jun 2018 22:57:22 +0000
To: Alastair Campbell <acampbell@nomensa.com>
CC: WCAG <w3c-wai-gl@w3.org>
Message-ID: <DM5PR07MB38683E963796F0DB91B5A4B4AB660@DM5PR07MB3868.namprd07.prod.outlook.com>
I think the note would be more beneficial to organizations that are in a position to educate users in taking precautions with their “autocomplete” data, than to Web content developers. However, including such a note with the technique and enabling the EO working group to take the issue into account is the most that this working group could reasonably do under the circumtances.

From: Alastair Campbell <acampbell@nomensa.com>
Sent: Tuesday, June 5, 2018 6:17 PM
To: White, Jason J <JJWHITE@ets.org>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: RE: Issue 948 SC 1.3.5 Identify Input Purpose - autocomplete technique VS Privacy/Security

Hi Jason,

That’s a slightly different issue, and one that has been raised and answered previously:

It generated a bug on HTML, which was resolved by including in HTML5.3(?) that “User agents should verify that all fields with the [autocomplete] attribute  wearing the <a>autofill expectation mantle</a> are visible within the viewport before automatically entering data.”

Adding a note is fine, I think it would be most appropriate on the technique for autofill.

However, I’m not sure what it would say as we don’t currently have an alternative (accessibility supported) technique to propose. So it would basically say: Use this technique, but just so you know here are some privacy & security issues with it… but you still have to use it.

One of the issues is something that the user-agents will have to tackle regardless of WCAG 2.1, and this latest one doesn’t really seem to be an issue.

Is it worth a note?


From: White, Jason J

Safari under Mac OS doesn’t complete form fields unless I move focus to the field and explicitly choose to invoke the automatic completion.

I don’t know whether other browsers will follow this example. Privacy concerns associated with autocomplete have surfaced recently, focusing on exploitation by third-party tracking scripts associated, presumably, with advertising.

It should be noted that, as emphasized in the article, the feature is working as designed – there’s no hitherto unknown vulnerability here.

I would suggest including the “autocomplete” technique as planned, but adding a note (if it isn’t already in the draft) on its privacy and security implications.


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Tuesday, 5 June 2018 22:57:51 UTC

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