After running my site through powermapper tools, they present this issue:

All ONCLICK handlers should have an equivalent ONKEYPRESS handler. Section 508 1194.22 (l) WCAG 2.0 A F54
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.

Now I feel I should do it since some minor sections of my site are inaccessible with a keyboard only (unless JavaScript is turned off and tab key was used).

My question then is, what is the standard way to craft buttons to identify the keyboard-only users what key to press to use a button? Should I follow the Microsoft Windows format where the key to press is underlined in the button name, or is there a better way to do this?


The alternative to "the Microsoft way" is the Android way. Have the active letter as a superscript on the button.

Android Keyboard

| improve this answer | |
  • Which part of the image you included is relevant? I'm not seeing any superscripts in it. – Stephen Ostermiller Jul 21 '16 at 11:51
  • Taker the g for example, a long press changes it to % which you can see in the image above the g – Steve Jul 22 '16 at 2:14
  • OK, I see what you are saying. Your example isn't perfect. That is labeling buttons for alternate behavior rather than specifying a shortcut key for them. Still, it's a usable idea. – Stephen Ostermiller Jul 22 '16 at 2:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.