- From: Charles McCathieNevile <chaals@opera.com>
- Date: Sat, 29 Sep 2007 14:39:00 +1000
- To: "L. David Baron" <dbaron@dbaron.org>, public-html@w3.org
On Sat, 29 Sep 2007 06:58:50 +1000, L. David Baron <dbaron@dbaron.org> wrote: > On Friday 2007-09-28 11:57 +0100, Daniel Land wrote: >> however, access >> keys interfere with some assistive technology devices by overriding >> the built-in/preset shortcut keys of such devices (which are probably >> what the assistive device users would prefer to use if given the >> choice). > > We shouldn't assume that this will always be the case; in fact, we > should try to fix it. Indeed. > Maybe the spec should state that user agents SHOULD NOT (or MUST > NOT) assign author-specified access keys to sequences that overlap > with existing functionality? (In other words, that they SHOULD/MUST > use a key space that doesn't have anything in it already.) Doing so is impossible. You don't even know what keys the device reading your page actually *has*, let alone what applications might be collecting them on the device already. A user agent needs to handle this itself. cheers Chaals -- Charles McCathieNevile, Opera Software: Standards Group hablo español - je parle français - jeg lærer norsk chaals@opera.com http://snapshot.opera.com - Kestrel (9.5α1)
Received on Saturday, 29 September 2007 04:39:15 UTC