activateAccessKey 

The Web Dynpro framework supports the function of access keys if the WDLIGHTSPEED parameter is active.

Access keys are keys or key combinations that a user uses to set the focus directly on a UI element without triggering the defined function.

Access keys can be activated or deactivated in general using personalization.

Visualization

The visualization of the activeAccessKey takes place partly on the UI element itself (for example, for a button) or on the title of the UI element (for example, the header of a group or a tray) or on a label (for example, for an InputField).

The key combination for an access key is always ALT + [first letter of text of UI element/title/label] for the purposes of Web Dynpro ABAP:

To prevent possible inconsistencies during translation, the key combination for an access key cannot be personalized.

The key combination ALT + d is an exception; it does not work in Internet Explorer. The Web Dynpro framework automatically assigns an alternative key combination.

You can view all access keys for your application in the browser by holding down the ALT key. The AccessKey letter for the UI element in question is underlined.

When you press an access key, the focus changes to the next UI element with the AccessKey in question. If you press the access key multiple times, the focus moves through all UI elements with the corresponding AccessKey.

Always pay attention to the focus for keyboard navigation and dynamic programming.

Note the following for hotkeys, access keys, and other types of keyboard navigation: The application itself is responsible for ensuring that the focus is set in the correct place for dynamic programming so that keyboard handling works correctly.

Assignment to UI Elements

The activateAccessKey property is offered for the following UI elements:

activateAccessKey

UI Element	Visualization
AbstractButton	In the UI element
AbstractDropDown	On the label
AbstractInputField	On the label
AbstractToggle	For ToggleLink and AbstractToggleButton, the visualization takes place in the UI element; however, for CheckBox, the following applies: If a label exists, the visualization takes place on the label; otherwise, it takes place in the UI element itself.
AbstractActionChoice	In the UI element
CheckBoxGroup	Each individual CheckBox gets an AccessKey, but not the CheckBoxGroup itself (the label)
FileUpload	On the label
Group	On the ‘header’ aggregation (caption)
ItemListBox	On the label
Link	If a label exists, the visualization takes place on the label; otherwise, it takes place on the link itself.
RadioButton	On the label
RadioButtonGroupByIndex	If a label exists, the visualization takes place on the label; otherwise, it takes place in the UI element itself.
RadioButtonGroupByKey	If a label exists, the visualization takes place on the label; otherwise, it takes place in the UI element itself.
Table	On the ‘header’ aggregation (caption)
TabStrip	Each tab gets an AccessKey; the visualization takes place on the ‘header’ aggregation.
TextEdit	On the label
Tray	On the header
TriStateCheckBox	If a label exists, the visualization takes place on the label; otherwise, it takes place in the UI element itself.