W3C home > Mailing lists > Public > public-bpwg@w3.org > March 2009

[Fwd: [wmlprogramming] I think we need to update GAP (accesskeys are now broken)]

From: Luca Passani <passani@eunet.no>
Date: Wed, 01 Apr 2009 00:31:50 +0200
Message-ID: <49D299D6.5090904@eunet.no>
To: MWI BPWG Public <public-bpwg@w3.org>


I know I promised I would not care about Best Practices anymore, but you 
may want to hear about this latest development in Safari on Nokia's 
devices, because it breaks one of the BPs. Specifically, the one about 


In short, accesskeys are no longer a good idea and their adoption 
shouldn't be advocated, regardless of the fact that XHTML Basic 1.1 
accounts for them.



-------- Original Message --------
Subject: 	[wmlprogramming] I think we need to update GAP (accesskeys are 
now broken)
Date: 	Wed, 01 Apr 2009 00:06:20 +0200
From: 	Luca Passani <passani@eunet.no>
Reply-To: 	wmlprogramming@yahoogroups.com
To: 	wmlprogramming@yahoogroups.com

People, I think I need to go back and change/remove one of the GAP 


"[ACCESS_KEYS] Use the 'accesskey' attribute to implement keyboard 
accelerators on menus."

I always knew that many browser/devices ignored accesskeys, but still 
adding accesskeys wouldn't hurt. In particular, I knew that Nokia's 
webkit did not support accesskeys.

It was brought to my attention that recent versions of the Safari 
browser on Nokia S60 devices now supports keyboard accelerators to 
implement browser functions (back, bookmarks, zoom in, zoom out, 


These keyboard accelerators rely on numeric keys, so programming access 
keys for a page is now effectively a bad practice. If you tell users to 
use access keys, they will get confused as hell on the Nokia webkit browser.

I tried this personally on the GAP templates with my newly re-flashed 
Nokia N95 8GB:


you press "3", and rather than  activating the third link, the browser 
will go back to the previous page.
For the record, here is the list of Safari new keyboard accelerators:

[0]: Home page
[1]: Bookmarks              
[2]: Search in current page
[3]: Back               
[8]: Page overview              
[9]: Web address field
[*]: Zoom in
[#]: Zoom out

<rant>Honestly, I don't like this. Unilateral attempts to re-define the 
way people programs mobile sites make the mobile web a progressively 
harder platform for everyone.</rant>

Having said this, what is to be done? my suggestion is that we change 
the [ACCESS_KEYS] GAP rule into [NO_ACCESS_KEYS] and explain why access 
keys are a bad idea for a whole bunch of mobile users.

BTW, should we have a capability: xhtml_support_accesskey to mark 
whether it's OK to use accesskeys for a given device?



As of July 14 2005, it's much easier to be banned from WMLProgramming!
Please fail to read http://groups.yahoo.com/group/wmlprogramming/ before you post.Yahoo! Groups Links

<*> To visit your group on the web, go to:

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    (Yahoo! ID required)

<*> To change settings via email:

<*> To unsubscribe from this group, send an email to:

<*> Your use of Yahoo! Groups is subject to:
Received on Tuesday, 31 March 2009 22:32:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:53 UTC