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

RE: Accesskeys (was RE: Accessibility features)

From: John Foliot - WATS.ca <foliot@wats.ca>
Date: Wed, 1 Feb 2006 23:15:39 -0500
To: "'Charles McCathieNevile'" <chaals@opera.com>, "'Martin Stehle'" <pewtah@snafu.de>, <w3c-wai-ig@w3.org>
Message-ID: <007601c627af$57d1dfd0$6401a8c0@bosshog>

Charles McCathieNevile wrote:
> By the way, Opera is actively pushing W3C to fix Accesskey
> specifications in a way that doesn't require changing the markup, and
> will hopefully mean that all you have to do to update your pages
> about accesskey in the future will be to note that "new browsers
> fixed this, will show you the key you need and how to activate it"...


This is interesting news.  When you say "fix" Accesskey specifications,
1) which specifications, and 2) how do you propose they are "fixed"?
Are you talking at the UAAG level?  Are you saying that it would also be
backward compatable?  Is there a time-line? (I know that one's tough)

If you are not already aware of the new crop of scripts around that hand
the "power" to users, you should look at them.  I referenced the URLs
earlier in this thread (or can provide off list).  


John Foliot  foliot@wats.ca
Web Accessibility Specialist
Web Accessibility Testing and Services
Phone: 1-613-482-7053  
Received on Thursday, 2 February 2006 04:15:55 UTC

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