Re: What is a failure of 1.3.5 Identify Input Purpose?

I hope we think carefully about the confusion this SC has caused when we
look to a possible 2.2. Either we are writing well-vetted SCs that have a
long shelf life, or we are doing less-vetted quick iterations that address
current issues. Can we do both?

On Mon, Jan 21, 2019, 6:30 PM John Foliot <john.foliot@deque.com wrote:

> > that collects user data, without an autocomplete - and relevant
>
> I'd re-write that slightly Josh, to say instead "...that collects data
> about the user..."
>
> I'd agree that looking for @autocomplete would be important as part of a
> testing strategy, but, just as how we also say "look for @alt" for images,
> we all know that, while in the early days, that WAS the recommended
> technique,  additionally today we can't fail <img src="..."
> aria-label="photo of Josh">.
>
> HTH
>
> JF
>
> (Sent from my mobile, apologies for any spelling mistakes)
>
> On Mon, Jan 21, 2019, 4:22 AM Patrick H. Lauke <redux@splintered.co.uk
> wrote:
>
>> On 21/01/2019 09:11, Joshue O Connor - InterAccess wrote:
>> [...]
>> > For most forms capturing 'user data' will this be a case of mapping the
>> > relevant form inputs defined here to the inputs in the form. Correct?
>> [1]
>> >
>> > I need to recommend a coping strategy for government. I don't think,
>> for
>> > auditing purposes we can say the answer is actually nuanced here. It
>> > either is or it isn't conformant to WCAG and from my reading, a form
>> > that collects user data, without an autocomplete - and relevant
>> > appropriate tokens is a fail.
>> [...]
>> > [1]
>> >
>> https://www.w3.org/TR/html52/sec-forms.html#autofilling-form-controls-the-autocomplete-attribute
>>
>> I'd say yes. At least, that's been my pragmatic take on it at the moment.
>>
>> P
>> --
>> Patrick H. Lauke
>>
>> www.splintered.co.uk | https://github.com/patrickhlauke
>> http://flickr.com/photos/redux/ | http://redux.deviantart.com
>> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>>
>>