- From: Denis Boudreau (Deque) <denis.boudreau@deque.com>
- Date: Mon, 14 Aug 2017 08:01:13 -0400
- To: "Alastair Campbell" <acampbell@nomensa.com>
- Cc: "" <w3c-wai-gl@w3.org>
- Message-ID: <905dfb6e-2355-40d0-90b5-d4d7b84f2b0f@getmailbird.com>
>> Putting the entire list in the Understanding document seems like a more viable approach. > I would agree, except that it is then not normative and therefore not testable. > I do agree they should be moved out of the SC text, into a definition (which is normative I think). Fair point, though I'm not sure this impacts testability in any way. I could live with the list being part of the definitions (which ARE normative) if we prefer, but again, this will make for a painfully long list, as part of the WCAG document itself - which is what I was tryng to prevent by suggesting the Understanding document... /Denis -- Denis Boudreau, Principal accessibility consultant & trainer Deque Systems, Inc. Cell: +1-514-730-9168 Email: denis.boudreau@deque.com [mailto:denis.boudreau@deque.com] Keep in touch: @dboudreau [http://www.twitter.com/dboudreau] On 2017-08-14 5:13:37 AM, Alastair Campbell <acampbell@nomensa.com> wrote: Denis wrote: > Putting the entire list in the Understanding document seems like a more viable approach. I would agree, except that it is then not normative and therefore not testable. I do agree they should be moved out of the SC text, into a definition (which is normative I think). > I just can't picture myself teaching about this SC with the list included in front of clients, let alone defend the working group in the fact that this was the right approach. It is a much smaller hurdle than ARIA, and even now a lot easier to understand & implement. Rather than saying: “If your widget matches a particular pattern, go look at the ARIA practices and work on the JS needed to implement keyboard controls and ARIA attributes.” You would be saying: “If your link/input/button matches one of these, include this meta-data or associate an explanation.” It is much closer to landmarks than widgets. More explanation about the approach: https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JulSep/0400.html [https://lists.w3.org/Archives/Public/w3c-wai-gl/2017JulSep/0400.html] Examples that could fulfil it (according to me so far, so open to argument/update): https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017Aug/0010.html [https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2017Aug/0010.html] Cheers, -Alastair
Received on Monday, 14 August 2017 12:01:25 UTC