W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: Issue #69: Character key commands

From: Gregg C Vanderheiden <greggvan@umd.edu>
Date: Tue, 16 May 2017 09:28:36 -0400
Message-Id: <C6BC4F9E-9C2E-44F8-BDE0-CF5EB0140BE4@umd.edu>
Cc: "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
To: "Patrick H. Lauke" <redux@splintered.co.uk>
and what is the damage if they do?     All actions are reversible that I can see.   Maybe change this to  “if not reversible"

how is this different than many other places that are MUCH more catastrophic — like  when it says  “DELETE ALL? “   OK CANCEL   and bumping the  spacebar or  return   (or  “o”?)  will delete all? 

I am not sure I have seen a serious enough problem to write an SC to solve it.

REMEMBER - every SC you add weakens all the rest.    There were several things that we did not make an SC out of in WCAG 2.0 because we didn’t think the problem was worth it.     WCAG was already long enough - and each SC we added made it harder to sell.    2.1 should not make WCAG 2.0 longer except for good reasons— addressing real problems. 

I’m not judging this one yet — still waiting for comments.  But as a matter of principle, we should make sure that there is a real demonstrable problem before we create another SC.


 anyone else have any examples of where this is a real problem that can’t be solved with a  simple keystroke to reverse it?

g 

Gregg C Vanderheiden
greggvan@umd.edu




> On May 16, 2017, at 3:48 AM, Patrick H. Lauke <redux@splintered.co.uk> wrote:
> 
> On 16/05/2017 06:45, Gregg C Vanderheiden wrote:
> [...]
>> But I can’t think of the disadvantage.
>> 
>> can someone help me here?
>> 
> [...]
>>  * it prevents the user from using the ‘e’ key for anything else — but
>>    (since this only happens if they have focus on the page — and there
>>    is nothing that the ‘e’ key can do on the page when not in edit mode
>>    — I’m missing the problem.
> 
> I have made this particular point many times before as well...these single-key commands would only trigger accidentally in situations where the user is not on a control/element that is editable. However, it seems that the main concern is accidental unintended triggering (e.g. by overeager speech recognition, or by unintentionally hitting a key on the keyboard).
> 
> P
> -- 
> Patrick H. Lauke
> 
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> 


Received on Tuesday, 16 May 2017 13:29:30 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:13 UTC