W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > February 2018

Re: SC 1.3.4 - Understanding doc update

From: Alastair Campbell <acampbell@nomensa.com>
Date: Tue, 27 Feb 2018 10:04:21 +0000
To: John Foliot <john.foliot@deque.com>
CC: COGA TF <public-cognitive-a11y-tf@w3.org>
Message-ID: <01D6266D-CF1E-4DC3-B7B7-2AF7CBBEE32B@nomensa.com>
Hi John,

Thanks for the review, I’ve made updates, some comments/replies also:

1)  … HOWEVER both ways still use the @autocomplete attribute (only).
Good point, I got confused on that. It feels like there should be one for true/false, and one for the value, but never mind!

Updated.


2)  "... although it isn’t very helpful for personalisation..."

[JF] I STRONGLY reject that assertion (as did Jon Avila<https://lists.w3.org/Archives/Public/w3c-wai-gl/2018JanMar/1328.html>).

AC: That was from my email, which was describing the comments from the call last week (and not what I said in the understanding doc).

Whilst the attribute could be used as a basis for adding icons, what I mean (in the doc) is that the scope is not very wide. I.e. of all the attributes / purposes we could add, this is a small sub-set.

The second paragraph of the understanding talks about personalisation and being future-compatible. However, any suggestion that this would be the basis or reason for adding personalisation is likely to run into issues – it isn’t enough to justify it.


3) Metadata tokens

I’ll add a link to the semantics spec in the 2nd paragraph.


4) Housekeeping

Yea, I don’t find the non-hyphenated one as readable, but I think the US spelling aspect will win there.
Updated.

https://alastairc.ac/tmp/autocomplete.html


Thanks,

-Alastair
Received on Tuesday, 27 February 2018 10:05:07 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:00 UTC