W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2006

Re: Accesskeyus interruptus: another real-world case

From: Charles McCathieNevile <chaals@opera.com>
Date: Sat, 18 Feb 2006 18:48:41 +0100
To: "Alastair Campbell" <ac@nomensa.com>, "John Foliot - WATS.ca" <foliot@wats.ca>
Cc: w3c-wai-ig@w3.org
Message-ID: <op.s46jrfjhwxe0ny@widsith.local>

UB Access implemented essentially this functionality (although using a  
server-side proxy - this was before the days of userJS/Greasemonkey and  
other simple extension mechanisms).

There are two fundamental problems with accesskeys. One is that the  
specification implicitly gives bad advice to authors, and the other is  
that it gives bad advice to implementors.

Unfortunately, so far many authors have followed that advice, and at least  
two major implementors (Explorer and Netscape/Mozilla/Firefox). There are  
simple ways of implementing accesskeys, and making existing code more or  
less work (as Gez said, there are limits to what you can do with things  
which also have other errors, of course), and fixing the specifications.  
But actually doing that is another thing. (Unfortunately I spent the last  
few days with no connectivity to speak of, which got in the way of my  
fulfilling a commitment to pick this up in a place that might help. More  
fun for my weekend... :| )



On Thu, 16 Feb 2006 14:21:19 +0100, Alastair Campbell <ac@nomensa.com>  

> John Foliot wrote:
> "imagine if next generation browsers pre-shipped with this type of
> functionality
> (internal scripting?) out of the box.  Developers would then simply need
> to declare the "hooks" and the browser would take over from there."
> Perhaps a proof of concept might help?
> For example, Firefox(*) extension that:
> - Detects when accesskeys are used on a page.
> - Disables them!
> - Shows an indication that accesskeys are available (I'm thinking along
> the lines of the pop-up indicator).
> - Provides a (keyboard accessible) menu for setting them for this site.
> - Saves that as a site-based preference.
> That could help people make better use of them now, and help show how
> they can best be used in future?
> I wish I could volunteer to develop that, but I just don't have time at
> the moment. (Although if I did, I'd start with a Greasemonkey script
> that Mark Pilgrim developed...)
> Kind regards,
> -Alastair
> * Firefox has the obvious extension mechanism, but this applies equally
> for other browsers, and would be most useful/used in Internet Explorer
> for the target audience.

Charles McCathieNevile                     chaals@opera.com
   hablo español  -  je parle français  -  jeg lærer norsk
      Peek into the kitchen: http://snapshot.opera.com/
Received on Saturday, 18 February 2006 17:48:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:33 UTC