- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 23 Feb 2016 17:56:19 +0000
- To: 'GLWAI Guidelines WG org' <w3c-wai-gl@w3.org>
- Message-ID: <2D25C479-5194-44A6-B4F8-DD58C2F49119@nomensa.com>
Hi everyone, I think the crux of the issues with extensions on the call is at the next stage – when we are happy with the SCs that come out of the task forces and we want people to use them. In the requirements doc this is covered in 2.4: https://www.w3.org/TR/2016/WD-wcag2-ext-req-20160105/#h-define-a-clear-conformance-model-for-wcag-2.0-plus-extensions Perhaps we need to add something like “The success criteria developed in the extensions will be evaluated in conjunction with WCAG 2.0 and a decision will be made about the conformance model necessary. It may be a WCAG 2.0 with extensions, or a new version of WCAG.” Note that I missed the previous arguments about WCAG.next so I’m blissfully ignorant about that part of WAI history! Personally, I don’t think WCAG2 + extensions would get much traction outside of the core accessibility community. It would be equivalent to AAA SCs, known but rarely used. The task forces exist because people recognise the weaknesses of WCAG2, for them to have impact the results need to be part of WCAG.next (2.1, 3.0, whatever). Given a timeline that is likely to extend to 2017/18, we could aim for the 10 year anniversary of WCAG 2.0? I think most people will expect an update by then?! Cheers, -Alastair -- Alastair Campbell www.nomensa.com follow us: @we_are_nomensa or me: @alastc
Received on Tuesday, 23 February 2016 17:56:54 UTC