RE: Created branch with proposed wording for 1.3.4

Yes, if the content author were to apply it in contexts where it isn’t the user’s name that is wanted. HTML5 allows them to do this; so does the WCAG 2.1 proposal.

I would prefer to separate the metadata-bearing attributes that are used to convey a UI control’s purpose for reasons of accessibility, from the autocomplete feature of HTML. This is one of the reasons why I’m not supportive of the current 1.3.4 proposal – I’m worried about negative consequences of dual-purposing the HTML autocomplete feature as a makeshift accessibility tool when we don’t have proper, normative, metadata specifications to cite.

From: Michael Gower [mailto:michael.gower@ca.ibm.com]
Sent: Wednesday, January 17, 2018 11:49 AM
To: Alastair Campbell <acampbell@nomensa.com>
Cc: Andrew Kirkpatrick <akirkpat@adobe.com>; David MacDonald <david@can-adapt.com>; WCAG <w3c-wai-gl@w3.org>
Subject: Re: Created branch with proposed wording for 1.3.4

> Also, my understanding is that an author could use the ‘name’ autofill attribute on multiple inputs, WCAG would only require it on ones pertaining to the actual user.



Danger, WIll Robinson! That would seem to put us in the very unfortunate situation where someone depending on the name attribute conveying meaning will now be getting incorrect conversions happening.

That strikes me as singularly problematic. As you note, there is nothing in the html5 spec stating that applying the autofill to other entities is forbidden. In a situation where symbols are applied based on the autofill attribute values, will this not lead to potentially a much worse scenario for the user?

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com>
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:        Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
To:        Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>, David MacDonald <david@can-adapt.com<mailto:david@can-adapt.com>>
Cc:        WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Date:        2018-01-17 07:55 AM
Subject:        Re: Created branch with proposed wording for 1.3.4
________________________________



1.        The SC is scope to input controls, not controls writ large.



I’m not particularly bothered about creating a new SC later to cover other components, but it does seem forward compatible to have a wider SC text and a narrow list. I didn’t find it more (or less) confusing.



2.        The SC discussion has been about scoping this to information about the user. James raised the very valid point for situations like in an HR tool where there are many first name/last name/etc fields.



I agree with the point, but as I said to Mike, if we include the list we can include the paragraph at the top (which is there in the current version) which makes the purpose specific.



Also, my understanding is that an author could use the ‘name’ autofill attribute on multiple inputs, WCAG would only require it on ones pertaining to the actual user.



Oh, David – I think the version here is missing the “and” at the end of the first bullet:

http://rawgit.com/w3c/wcag21/1.3.4_autofill_david/guidelines/#identify-common-purpose<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__rawgit.com_w3c_wcag21_1.3.4-5Fautofill-5Fdavid_guidelines_-23identify-2Dcommon-2Dpurpose%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DSF82Z2La6oWL4e4ntolcLhofq297GpboRRRbapjQhPw%26s%3DvD1IY6n31NFn7RVeYXP20S7LqchdDIGoU6CvuGD88xI%26e%3D&data=02%7C01%7Cjjwhite%40ets.org%7C45c8f345ba734bc4f5e808d55dcac1cd%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636518047779971803&sdata=fnRCo%2BvR%2FFo9RlZY6Ph0UL88FoYHpjbyKQftUpHzPqo%3D&reserved=0>



Cheers,



-Alastair


________________________________

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.

________________________________