Geek Answers Handbook

What key codes can I safely use to make my site accessible?

update: it turned out to be a beautiful application with exclusive shortcuts for each view, all javascript. I'm going to take a peek at Fogbugz, I like suggestive shortcut codes, thanks for the link.

I want to make my site accessible and more convenient for visitors. What key codes can be safely used to handle certain javascript actions?

With confidence, I mean:

  • keyCodes that do not interrupt the default browser
    • There is no direct functionality (e.g. pressing F1 for reference)
    • There are no indirect functions (for example, pressing Ctrl + C to copy)

Or do I need to prevent the execution of default actions?

+4
source share
6 answers

I personally avoid using these key codes or AccessKeys for an open access site, since there is no way to find out if you are inconsistent with some predefined shortcuts in user software, such as firmware software, etc.

+3
source

Perhaps you should take a look at these questions:

Key shortcuts in a web application Creating a keyboard-accessible web application

+1
source

What accessibility do you want to achieve?

Accessible software, for example, will have its own key actions.

Different browsers have their own key actions.

Some of them are even customizable.

I think you are asking for what you are doing.

Edit: Good, so for some reason this was unclear. Here is what I tried to say:

The browser and access software have an unlimited range of options for which key combinations can be used. If you try to catch a key combination, you will interfere with those along the line.

Sigh.

+1
source

Just stick to letters and numbers.

Here is a link to the shortcuts used by gmail, for example: http://mail.google.com/support/bin/answer.py?hl=en-uk&answer=6594

Just make sure that you are not stopping people from entering forms in the fields.

0
source

This can be a difficult problem to solve in the long run, as browsers sometimes have new keyboard shortcuts in newer versions, which can lead to conflicts with shortcuts that you may have assigned for use in your application. A few such examples that I know of:

  • In the old version of the Google Toolbar , which started in Firefox 1, the Alt + s key was used to set the focus to the Search Box on the toolbar. However, when Firefox 2 was introduced, the Alt + s passkey was added to the History menu, which broke the Alt + s key combination on the Google toolbar. ( Additional Information )

  • An older version of the Firefox Duplicate Tab extension used the keyboard shortcut Ctrl + Shift + T to duplicate the current tab. However, Firefox 2 introduced the new “reopen closed tab” feature and assigned it to Ctrl + Shift + T , which broke the Duplicate Tab. Duplicate Tab has completed replacing the duplicate tab shortcut with Ctrl + Shift + U. ( Additional Information )

0
source

You will also be happy to learn about the existence of WCAG and WCAG 2.0 from W3 to assist you in your accessibility mission.

0
source

More articles:


All Articles