RE:More data on accesskeys (New article written Nov. 1)

> When asked after the tasks if they noticed the accesskeys or used them
> on other sites, replies varied between "what accesskeys", "what are
> accesskeys", and "yes, but I've never used them". Given the poor
> implementations both in browsers and in sites (e.g. one that gave
> 'helpful' hidden text that spelt them phonetically, but then they didn't
> work anyway), those type of results are hardly surprising.

A simple fix for the problem of access keys would be to allow the user to 
define their own access keys for, say, "home", "next", "previous", 
"search" "copyright info", "contents", etc.; and then to map these, for 
any given page, to the target pages specified in the "link" headers, e.g.:
 
        <link rel="home" href="http://www.example.com/index.htm">
        <link rel="search" href="http://www.example.com/search.htm">

[Note: I'm only sending this to the one mailing list to which I'm 
subscribed; please feel free to forward it to the others]

-- 
Andy Mabbett

***********************************************************************
The information contained within this e-mail (and any attachment) sent by Birmingham City Council is confidential and may be legally privileged. It is intended only for the named recipient or entity to whom it is addressed. If you are not the intended recipient please accept our apologies and notify the sender immediately, or telephone +(44)(0)121 464 4444. Unauthorised access, use, disclosure, storage or copying is not permitted and may be unlawful. Any e-mail including its content may be monitored and used by Birmingham City Council for reasons of security and for monitoring internal compliance with the office policy on staff use. E-mail blocking software may also be used. Any views or opinions presented are solely those of the originator and do not necessarily represent those of Birmingham City Council. We cannot guarantee that this message or any attachment is virus free or has not been intercepted and amended.
***********************************************************************

Received on Friday, 3 November 2006 11:47:17 UTC