- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 16 Jan 2018 12:43:13 +0000
- To: "tink@tink.uk" <tink@tink.uk>, Joshue O Connor - InterAccess <josh@interaccess.ie>, Andrew Kirkpatrick <akirkpat@adobe.com>, "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
> If the intent of this SC is to enable an AT to concretely determine the > purpose of qualifying controls, then we need to define the set of > possible tokens Yes, but not *in* the success criteria, otherwise 4.1.2 would have to define which ARIA attributes to use, and 1.3.1 which HTML elements to use. At the SC level it should define the requirement, at the technique level (and separate specs) it should define the mapping. The difference (and compromise) compared to ARIA is that there needs to be a list of purposes/meanings, as the external specs are not dedicated to providing this and HTML is much wider than accessibility. -Alastair
Received on Tuesday, 16 January 2018 12:43:44 UTC