Slashdot Mirror
Benefits of Using Access Keys in HTML?
kandresen asks: "I have been considering the use of access keys in my web site as an accessibility feature, and was originally looking at possible side effects this could have for people with PCs and Macs, however in my search I found the problem was far wider than just that, as people with different language version of these OS'es may have different key bindings. Many of the websites I deal with have an International reach, so I can see this may limit the available keys quite a bit. The better approach, which would avoid the entire problem, unfortunately does not seem to be a reality, even in the upcoming version of XHTML 2. So, I wonder whether other webmasters have had many complaints from their users regarding the use of access keys interfering with system specific shortcuts, such as bookmarking, help functions, accessing of favorites, and so forth. Do you have any tips as for how to avoid negative side effects? Are there some keys that do not cause much problems regardless of language, OS, or the client being used? Is there a way to use Javascript to take care of such problems?"
Sounds like a good idea, and as a keyboard cowboy I appreciate it, but the first time I tried to leave a webpage by hitting alt+d to go to the address bar to type a url and got a donation page I was instantly turned off by the idea. While you can do it right, its rarely worth the effort unless you're doing a full out web app, and even then keep it optional.
Pain lasts, kid. Its how you know you're alive. Sometimes I think this growing up thing is just pain management-TheMaxx
It changes from one browser to the next. I believe in Opera you need to press Shift-ESC then the access key. Others may use ALT or some kind of platform-specific modifier key.
A program theoretically shouldn't interfere with the system commands, but...
In a world where we assume ALT is the access key modifier, and Alt-F is one of the shortcuts, does that deny them the ability to press Alt-F to access the File menu? I don't think there is any consistent behavior at all.
Check out this page. It has a table of known conflicts or potential problems.
I tried using on a company intranet site, simply for my own amusement, and gave up. While I thought it was nice to press Alt-N to view the news page, nobody else knew how to use it or cared to learn. Most of them never take their hand off the mouse anyway (if they are physically able to choose).
Access keys can conflict with short cuts already defined by the browser. See this entry at accessify.com about the problem. Also read this article.
Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
I tried using on a company intranet site, simply for my own amusement, and gave up. While I thought it was nice to press Alt-N to view the news page, nobody else knew how to use it or cared to learn.
Did they even know they were there? I find that many sites use AccessKeys but give no indication that they do or what they are. Luckily you can use a handy bit of CSS to help out.
Using the selector before pseudo selector, you have have the accesskey shown automatically displayed before the element. For example, I have this in my Mozilla userContent.css:
a[accesskey]:before {
content: " " attr(accesskey) " ";
text-transform: uppercase;
white-space: pre;
border: thin solid;
font-family: sans-serif;
text-decoration: underline overline;
margin-right: 0.5ex;
}
The first two lines are the important part, the rest is just styling to make it look nice. Specifically, it adds a small box with the capitalized access key character before any link that uses one.
For example, when I visit Freshmeat, the menu at the top looks something like this:
[H] home | [B] browse | [A] articles | contact | chat | submit
It's a neat trick and can be very handy. While it's true most sites don't use accesskeys, there's more out there than you might expect, and the ones that do almost never advertise it.
No point in making a web browser use the same keys for navigation as for itself. Too bad only the KDE developers have really thought this through so far.
Because of this, the only browser to properly implement it so far is Konqueror. Press control, and access key labels appear over the appropriate links. Press that key.
Help us build a better map!
you could always make a form based navigation system that is a command line. ^^
i do know that with javascript you can specify actions for various keys like arrows and such. you could make a "virtual mouse pointer" that you can control with arrow keys if it is absolutely imperitive to be able to navigate without a mouse. i suggest if you are going to make a menu that is keyboard activated, you use the underline scheme like File. ive never considered of keyboard only interface as a must.
Anons need not reply. Questions end with a question mark.
The way I see it, those that want to browse with keyboard shortcuts already have them. As an avid user of the Mozilla typeaheadfind I have usable shortcut keys that are standardized from page to page. All I do is type the text of what I want. Why would I want to learn a new way that will only only work on your page?
So essentially, the users that want this added efficiency already have it, in lynx/firefox/browser of choice, and those that don't probably wouldn't bother to learn the page specific keys anyway.
Or am I missing a category of people?
Maybe it's just me, but I've always felt that numbers were the natural access key for web applications.
International reach? You know any keyboards that DON'T use arabic numerals in the same place on the keyboard?
As for program conflicts, You need to make the site distinguish between firefox on linux and on other systems, since I believe the default on linux to switch between tabs is alt-(number key). You also need to
give users the option to turn it off if they are using windows readers such as JAWS. But other then that, there are no conflicts.
http://www.santacruzbynight.com/index.shtml Santa Cruz By Night Vampire Larp
Keep in mind that nobody wants to learn new shortcuts for every website. Some users might not be able to navigate a page if their navigation keys are reprogrammed. If you want to make your pages more accessible then make sure that your pages use "strict" xhtml and css. Then visitors who need additional accessibility don't run into problems with their browser-modifications.
Obscure keyboard shortcuts are convenient for blog/cms-administrators. And administrators can tweak the shortcuts if they don't like them. Regular users don't have this option, so they might be annoyed.
The plone folks have spent some real time & energy on accessibility as well as standard based design. The nice part is this leads the way for anyone building their own site with plone to get to these standards quickly - esp. in their latest release.
If you are trying to tackle accessibility, I recommend using plone, or at least looking at their code (you wouldn't be the first to use plone 'code' outside plone - I remember wikipedia css crediting plone... http://en.wikipedia.org/skins-1.5/monobook/main.cs s?5 )
Not only do they have hotkeys and use valid xhtml and css, they also explain all this, list the (numeric based) keys, differences between browsers, and link this info from every page (upper right) as prominently as the site-map and contact links.
(And no, I am not a plone committer/member, just an occasional user.)
...begins in wonder
Just put a tag at the bottom of your site that says Best Viewed in English Language. ;-)
I think most people who like to avoid using the mouse and stick to the keyboard will already have something set up. I use conkeror for example. If I was more extreme I'd be using something like ratpoison too. You don't need to provide this for people, they can arrange it themselves.
Yes, I know CTRL-L is the correct way to get to the address bar, but pressing ALT-D is a tough habit to break
Karma: Excellent (fuck, even in the future moderation doesn't work!)
How about using the Scroll Lock to toggle between web app and OS app?
ayottesoftware.com
MacOS X has a very thoughtful feature for people like me who have been using emacs virtually since birth.
/want/ to log out. (I always use my own computer to compose articles, and I really, really HATE typing in passwords).
In Cocoa text boxes, the standard emacs keystrokes - Control-N for next line, Control-P for previous, etc - work just as they do in emacs. So I can edit my text more or less as I do in emacs, which is a great blessing for me because the keystrokes are truly embedded in my fingertips.
Well, Wikipedia uses AccessKeys, and this absolutely ruins my browsing experience. I was typing merrily away writing an entry when I hit Control-O to open a new line.
Wikipedia interpreted this as my desire to log out, and I couldn't even use the back button to get my document back. I lost an hour of work and was fuming at the people who designed it.
Why would you have an accesskey for the logout function, anyway? It's not like I ever actually
I actually created a Wikipedia bug request about this. It's something a very small number of people are extremely angry about, but the administration doesn't care since it's so few people. But I sure wish I could turn off the feature because it has sabotaged my entries many times.
I suppose I could use a regular text editor to write my entries and then post them but that's a bit of a bother, at least for me.
D
I have been participating in the development of the web guidelines for Sweden's public sector. In that document we recommend using a specific set of access keys (of which most are numeric) to make the user experience consistent between sites.
Using numeric access keys reduce potential conflicts with other access keys in the browser.
Standards Schmandards
WTF are "Access Keys"? I thought Doom-style keycards for a second.
kthx
It's 10 PM. Do you know if you're un-American?
No. Possibly. Maybe.