- From: Léonie Watson <tink@tink.uk>
- Date: Tue, 16 Jan 2018 14:29:08 +0000
- To: Andrew Kirkpatrick <akirkpat@adobe.com>, Joshue O Connor - InterAccess <josh@interaccess.ie>, "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
On 16/01/2018 13:58, Andrew Kirkpatrick wrote: > AT will need to know what tokens are supported in a given technology, and the AT will look at the PDF/OOXML/EPUB/etc spec to implement support. That's ok when you're talking about another technology that has an existing set of tokens that map to those in the HTML spec. The bit I'm worried about is what happens when there can be multiple sets of tokens for the same technology? It would be possible to meet this SC in HTML by using the set of tokens from the HTML spec, or by using the rel attribute with a set of tokens posted to the Microformats wiki that map to those defined in the HTML spec. You could even use the id attribute with a set of mapped tokens. These are all ways of identifying the expected purpose/meaning of things in HTML, but this level of potential fragmentation would make it near impossible for ATs to confidently determine the purpose/meaning of a given control. -- @LeonieWatson @tink@toot.cafe Carpe diem
Received on Tuesday, 16 January 2018 14:29:42 UTC