|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
 |
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
| |
|||
|
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
Dev Articles Community Forums Sponsor:
|
|
|
|
#1
April 27th, 2004, 02:30 PM
|
|||
|
|||
|
Improving my Accesskeys
I am redesigning my website and I began implementing the accesskeys, using numbers instead of letters, to avoid conflicts as described here:
Accesskeys and Reserved Keystroke Combinations http://www.wats.ca/resources/accesskeysandkeystrokes/38 But later I discovered that using numbers for accesskeys is not the solution: More reasons why we don't use accesskeys (accesskeyconflicts) http://www.wats.ca/articles/accesskeyconflicts/37 And after all, I was confronted with the solution below: Link Relationships as an Alternative to Accesskeys http://www.wats.ca/articles/accesskeyalternatives/52 But I am still not satisfied. Therefore, I still want to use them. So while I would like to improve my Access Keys functionality, I would like to ask here, what do you think about this code example? Code:
<a href="http://www.webnauts.net/index1.html" accesskey="1" onFocus="window.satus='Webnauts (accesskey = 1)'; return true" onBlur="window.satus=''; return true" onMouseOver="window.satus='Webnauts (access key = 1)'; return true" onMouseOut="window.satus=''; return true"><img src="http://www.webnauts.net/css_final/images/accessibility.gif" width="248" height="65" alt="Webnauts logo"></a> Your opinion or comments would be warmly appreciated.
__________________
For people without disabilities, technology makes things convenient. For people with disabilities, it makes things possible. - ACCESSIBILITY & USABILITY INITIATIVE FORUM http://www.webnauts.net/phpBB2/index.php
|
|
#2
April 27th, 2004, 09:24 PM
|
||||
|
||||
|
Yeah - the whole access key thing is a bit of a mess atm. It was mentioned recently on the WSG list that until an official standard is created, they are a bit of a pain to implement. I don't really see the point of them if there is no standard, as it means people will have to learn a new set of commands for each site. Personally, I'd like to the the UK method implemented (using 0-9 numbers). This of course means that some screen reader app's will have to change (and it appears Opera also), but it is in their best interests.
|
|
#3
April 27th, 2004, 09:49 PM
|
|||
|
|||
|
Thanks stumpy.
The only thing I can tell at the moment, is, that I would like to use temporaly accesskeys with support of style sheets as: Code:
a[accesskey]:after {content: " (" attr(accesskey) ")"}
which works excellent tested with Opera 7.11, to avoid any problems, if users browser does not support the "title" tag, but support this function. Why, you can see at my under construction web site here: http://www.webnauts.net/index1.html What do you about think this?
|
|
#4
April 27th, 2004, 10:06 PM
|
||||
|
||||
|
Great idea webnauts!
Pity Opera is about the only browser that supports your CSS. While testing with FireFox I found that due to your long "title" fields, some text is being chopped off... what about placing the access key text first?
|
|
| Viewing: Dev Articles Community Forums > Databases > Microsoft Access Development > Improving my Accesskeys |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
