- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Fri, 12 Oct 2018 15:57:45 +0000
- To: Jim Allan <jimallan@tsbvi.edu>
- CC: LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.org>
Received on Friday, 12 October 2018 15:58:18 UTC
Hi Jim (and LVTF), Pre-TPAC, it would be useful to know if there are any potential SCs you’d consider for a WCAG 2.2? We haven’t determined whether the group will tackle that yet, but part of the decision would be: Is it useful to do a 2.2? Looking back, I couldn’t see much in the LVTF ‘defer’ list here: https://github.com/w3c/wcag21/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3ALVTF+label%3ADefer+ Printing customised text perhaps? Given the shape of 2.1 now, are there gaps or things to tighten up that can work in the 2.x structure? Perhaps a couple of additional SCs that tighten up current ones? If there are others that didn’t make it to a github issue in the first place, now is the time to say so. I’m not sure who’s attending TPAC, but if there’s a short overview of 1-6 SCs I can run through them which would be very useful for the discussion. Kind regards, -Alastair -- www.nomensa.com<http://www.nomensa.com/> tel: +44 (0)117 929 7333 / 07970 879 653 follow us: @we_are_nomensa or me: @alastc Nomensa Ltd. King William House, 13 Queen Square, Bristol BS1 4NT Company number: 4214477 | UK VAT registration: GB 771727411
Received on Friday, 12 October 2018 15:58:18 UTC