Synonyms for keyboard shortcuts: Key combination, keyboard combination, keyboard command, keyboard equivalents, key sequence, access key, hot key, shortcut
Synonyms for shortcut keys: Mnemonic, acceleration key, shortcut key, menu accelerator
Keyboard shortcuts are keys or combinations of keys with which functions can be initialized or elements can be focused from within the application. The keyboard shortcuts can be initialized regardless of the current focus position. Keyboard shortcuts often consist of a combination of a printable character (letter, number, special character) with one or more modifier keys (e.g. CTRL or ALT). Keyboard shortcuts must be unique.
Shortcut keys are keys that can only be used within an element for the purpose of efficient navigation. They are usually used in menus. The shortcut key is usually the first letter of the corresponding element (e.g. menu item). Shortcut keys do not have to be unique: If, for example, different entries within a menu have the same shortcut key, the entries can be focused one after the other by pressing the key. Shortcut keys are used without modifier keys.
Presentation
Permalink "Presentation"| No. | Property | Description | Classification | Reference |
|---|---|---|---|---|
| 105 | Documentation | Keyboard shortcuts that are necessary for exiting a keyboard trap must be documented in the application in such a way that they are perceptible before the keyboard trap or when it is reached. | Must | EN 301 549: 9.2.1.2, 11.2.1.2 |
| 106 | Documentation | Keyboard shortcuts that are necessary for operating the application must be documented in the Help option. | Must | EN 301 549: 12.1.1 |
| 107 | Documentation | All keyboard shortcuts and shortcut keys should be documented in the application. | Should | WCAG 2.1: 3.3.5 (AAA) |
Operation
Permalink "Operation"| No. | Property | Description | Classification | Reference |
|---|---|---|---|---|
| 108 | Keyboard shortcut | If printable characters are used as keyboard shortcuts without a modifier key, it must be possible to:
| Must | EN 301 549: 9.2.1.4, 11.2.1.4.1 |
| 109 | Keyboard shortcut | Keyboard shortcuts should not be the only way of using the keyboard, but an additional method. Note: all control elements should therefore receive the focus with TAB or arrow keys. | Should | DIN EN ISO 9241-171: 9.3.10 |
Programming/interfaces
Permalink "Programming/interfaces"| No. | Property | Description | Classification | Reference |
|---|---|---|---|---|
| 110 | Documentation | Keyboard shortcuts that are necessary for exiting a keyboard trap must be communicated to the Accessibility API in the application in such a way that they are perceptible before the keyboard trap or when it is reached. | Must | EN 301 549: 9.2.1.2, 11.2.1.2 |
| 111 | Documentation | Keyboard shortcuts and shortcut keys that are visually perceptible in the application must also be communicated to the Accessibility API. | Must | EN 301 549: 9.1.3.1, 11.1.3.1 |
Practical tip: keyboard shortcuts and shortcut keys
Permalink "Practical tip: keyboard shortcuts and shortcut keys"Platform-specific keyboard shortcuts
Permalink "Platform-specific keyboard shortcuts"The keyboard shortcuts of the platform (of the Windows operating system, for example) should not be overridden or disabled in your application. i.e. the keyboard shortcuts of the platform should also work in the application (e.g. CTRL+X and CTRL+V to cut and paste text).
Keyboard shortcuts of assistive technology
Permalink "Keyboard shortcuts of assistive technology"The assistive technology uses several keyboard shortcuts. These keyboard shortcuts should not be used in the application, as otherwise the assistive technology or the application won’t work with these keyboard shortcuts.
The screen readers use the INSERT key as a modifier key for several of their keyboard shortcuts, for example. Therefore, the INSERT key should not be used as a modifier key for the keyboard shortcuts of the application.
As assistive technology also uses additional modifier keys and keyboard shortcuts without modifier keys, it should be possible to redefine or disable application-specific keyboard shortcuts.
Configuring keyboard shortcuts
Permalink "Configuring keyboard shortcuts"Regardless of the assistive technology which is used, keyboard shortcuts are important for people who depend on the use of the keyboard. The application should therefore make it possible to define special keyboard shortcuts for all functions, even if they are not provided with any keyboard shortcuts by default. Where this is possible, the Help option should make reference to it.
Documentation of the keyboard shortcuts and shortcut keys
Permalink "Documentation of the keyboard shortcuts and shortcut keys"The keyboard shortcuts should be explicitly documented in the application, i.e. in text form at the respective element (permanently visible or in a tooltip), e.g. “Print (CTRL+D)”.
The shortcut keys should be implicitly documented in the application, by underlining the letter for example, such as “Print”.
The shortcut keys within selection lists and drop-down lists are not generally documented – there, the first letter of the respective list entry acts as the shortcut key.
In the Help option, the keyboard shortcuts should be documented as follows:
- Documentation of the respective keyboard shortcuts within the topic-specific sections (description of a screen, function, elements etc.) as well as
- Documentation of all keyboard shortcuts on a separate page with instructions for the use of the keyboard.
Information about this article
You are welcome to send feedback by email about our handout!