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
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:   Alastair Campbell <acampbell@nomensa.com>
To:     Andrew Kirkpatrick <akirkpat@adobe.com>, David MacDonald 
<david@can-adapt.com>
Cc:     WCAG <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 

 
Cheers,
 
-Alastair