Re: SC 1.3.4 - Understanding doc update

AWK wrote:
The site shows one example of this, but doesn’t cover all HTML autocomplete attribute values though.

AC: I think it uses the coga or aui attribute though?  Not to be picky, but if the implementation sites we have use the autocomplete attribute, that won’t match the a11y-resources UA. It’s an easy(ish) change, but would need to be made soon, I assume?

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.

AC: Fair enough, happy to change it.

AWK: 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.

AC: For the current SC, the input assistance is the primary thing, as it is the benefit we can show now.

Katie wrote:
But we could also just suggest they use Autocomplete for this purpose without an SC)

AC: Do you mean ‘they’, as-in: an education process for end-users to learn about autocomplete in the browser? That’s useful, but we would also need the sites to use it. If the authors don’t add the meta-data, the results are rather hit & miss. There still needs to be a requirement to use the attributes.

Katie: We will need to be explaining to people why we have this SC and who it is for.

Are there any additions you could suggest?



Received on Wednesday, 28 February 2018 17:48:14 UTC