- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Wed, 6 Jul 2016 11:03:40 +0000
- To: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <19B3A9D6-60C6-4A67-990E-68A7EA760F8C@nomensa.com>
Hi everyone, I’ve started looking through some of the task force success criteria proposals and I have a high-level question: What do we do with SCs that seem best dealt with by user-agents? Just as an example, several of the low vision ones [1] definitely seem to be user-agent issues, such as the user being able to select line/word/letter spacing, justification, margins on text, etc. I assume other TFs will also have SCs best dealt with on the user-agent side. Are they likely to be moved back to post-WCAG 2.1? My intent was to try and see the shape forming from the new requirements, what kind of things are coming up and where are they fitting in to the 2.0 “POUR” structure. However, that’s tricky when you don’t think they should be in WCAG, but we also don’t have a UAAG anymore… Is it worth tagging these as user-agent focused in the meantime? Cheers, -Alastair 1] https://github.com/w3c/low-vision-SC/issues -- Alastair Campbell www.nomensa.com follow us: @we_are_nomensa or me: @alastc
Received on Wednesday, 6 July 2016 11:04:13 UTC