W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2006

[whatwg] On accessibility

From: Brandon <brandon@devbanana.com>
Date: Fri, 16 Jun 2006 13:39:13 -0400
Message-ID: <017b01c6916b$cb2e86b0$8c84ef04@Bob>

I'm the one who was quoted in the original post on this subject.

I know that there are some problems with accesskeys clashing with other command keys, but I truly think it'd be a shame to drop them just because of this clash, or just because they aren't used much. It really does make things much easier for navigating around a web page when accesskeys are implemented.

----- Original Message ----- 
From: "Michel Fortin" <michel.fortin@michelf.com>
To: "whatwg List" <whatwg at whatwg.org>
Sent: Friday, June 16, 2006 1:31 PM
Subject: Re: [whatwg] On accessibility

Le 14 juin 2006 ? 21:09, Lachlan Hunt a ?crit :

> If implementations can be modified so that accesskeys do not  
> interfere with existing shortcut keys, then that's great.   Perhaps  
> they could offer a kind of web-apps mode where all Alt+[key]  
> combinations are safe to be used by the web page, and then another  
> mode where they retain their normal browser functions.  But until  
> something like that happens and proves successful, accesskeys  
> should not be retained.

I'd like to point out that accesskeys are working very well on the  
Mac. Application commands are issued using the Command key and most  
browsers bind accesskeys to the minimally-used Control key.  
Accesskeys do not conflict with other system and application  
shortcuts unless the user defines his own conflicting shortcuts in  
the system preferences.

It would be sad to see accesskeys disappear just because they are  
hard to implement elsewhere. But I acknowledge most other computers  
don't have a "spare" key which can be used for that.

Michel Fortin
michel.fortin at michelf.com
Received on Friday, 16 June 2006 10:39:13 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:47 UTC