W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2010

Re: Accesskey Discussion

From: Charles McCathieNevile <chaals@opera.com>
Date: Thu, 23 Sep 2010 14:44:14 -0400
To: simon.harper@manchester.ac.uk, "UAWG list" <w3c-wai-ua@w3.org>, "Egan, Bim" <Bim.Egan@rnib.org.uk>
Message-ID: <op.vjh0z02mwxe0ny@widsith.local>
On Thu, 23 Sep 2010 14:04:19 -0400, Egan, Bim <Bim.Egan@rnib.org.uk> wrote:

> Sorry to butt in here, but it concerns me that as accesskey bindings
> frequently conflict with keyboard access to browser  toolbars or
> plug-ins, and can also change settings in access technology that runs in
> the background while being sensitive to all keystrokes, such as screen
> readers, defined accesskeys could result in all HTML5 pages using them
> being inaccessible to people  who navigate via keyboard or use access
> tech software, instead of the current situation where it is difficult
> only on some sites using code that conforms to specification.

Actually, the problem is stupid browser implementation binding  
author-assigned accesskeys to something that normally has a different  
function.

There is also a problem of authors using javascript to trap the keyboard,  
which has the same effect.

> -----Original Message-----
...
> I seems to me that HTML5 is becoming increasingly platform like. In this
> case I suggest that HTML5 specify a number of predefined accesskeys for
> common functionality including those useful for WebApps.

No, that is what rel attributes are for. That allows browsers to define  
whatever activation they want, that will be common across sites, and won't  
interfere with the existing browser UI.

cheers

Chaals

-- 
Charles McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Thursday, 23 September 2010 18:45:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 September 2010 18:45:25 GMT