Re: SC 1.3.4 - Understanding doc update

AWK: I don’t agree on calling it “autocomplete” as that is tied to the attribute name for HTML and we hope to not only allow other attributes at some point in HTML but also other technologies. I also am not thrilled with the idea of relegating this SC to “input assistance”, even though this is part of the benefit it isn’t everything, and it is paired with 1.3.5 which is not about input assistance at all.

Katie: The SC, in the stem sentence and both bullets talk about 'input field', or 'form input data'.....therefore I am unsure how you envision the requirements of this SC to ever cover anything other than form inputs, no matter what technology is used. As is, this SC is no longer about Purpose of Controls, but about helping users with memory or cognitive issues input repetitive content into form fields - and that is cognitive support I could get behind. (But we could also just suggest they use Autocomplete for this purpose without an SC)

I don’t say that this is about more than input fields (although 1.3.5 is) – I’m saying that this isn’t just about input assistance. This SC sets up to ability for personalization of inputs of different types and input assistance, and probably other things I’m not thinking about right now.

Received on Wednesday, 28 February 2018 18:14:21 UTC