- From: <alands289@gmail.com>
- Date: Wed, 8 Mar 2017 08:36:01 -0500
- To: Alastair Campbell <acampbell@nomensa.com>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <58c008c0.172bc80a.79b8c.d3af@mx.google.com>
+1 Great modification that communicates the intent much better Alan Smith From: Alastair Campbell Sent: Wednesday, March 8, 2017 8:21 AM To: WCAG Subject: Support as an SC prefix? Hi everyone, There is an interesting point raised on github for the SCs which are aimed at authors enabling something without (necessarily) adding on-screen widgets: https://github.com/w3c/wcag21/issues/159#issuecomment-285020097 “Maybe the use of the "Support" prefix would be a useful standard to set for the SC titles if an on-screen widget is not required, so that in this case it would be "Support Reflow to Single Column", just as we have "Support Personalization". This would also suggest a rename of 1.4.13 to "Support Printing", for example.” It would be an alternative to the “mechanism is available” language, hopefully leading people away from assuming there would be on-screen widgets. If that were taking on, I think it would lead to: • Support linearization (Or ‘Support reflow to single column’) • Support printing (Or ‘Support adaptations when printing’ might be more accurate.) • Support adapting text • Support extra symbols. And possibly others from COGA that didn’t make it to the FPWD. So two questions: 1. Do you think this approach is helpful? And if so, 2. Is “support” the right prefix? Kind regards, -Alastair -- 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 Wednesday, 8 March 2017 13:36:34 UTC