You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hub/apps/design/input/access-keys.md
+39-39Lines changed: 39 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
description: Learn how to improve both the usability and the accessibility of your Windows app by providing an intuitive way for users to quickly navigate and interact with an app's visible UI through a keyboard instead of a pointer device (such as touch or mouse).
Access keys are keyboard shortcuts that improve the usability and the accessibility of your Windows applications by providing an intuitive way for users to quickly navigate and interact with an app's visible UI through a keyboard instead of a pointer device (such as touch or mouse).
18
18
19
-
The Windows app provides built-in support across platform controls for both keyboard-based access keys and associated UI feedback through visual cues called Key Tips.
19
+
The Windows app provides built-in support across platform controls for both keyboard-based access keys and associated UI feedback through visual cues called keytips.
20
20
21
21
> [!NOTE]
22
22
> A keyboard is indispensable for users with certain disabilities (see [Keyboard accessibility](../accessibility/keyboard-accessibility.md)), and is also an important tool for users who prefer it as a more efficient way to interact with an app.
@@ -29,20 +29,20 @@ To create your own custom keyboard shortcuts, see the [Keyboard events](keyboard
29
29
30
30
An access key is a combination of the Alt key and one or more alphanumeric keys—sometimes called a *mnemonic*—typically pressed sequentially, rather than simultaneously.
31
31
32
-
Key tips are badges displayed next to controls that support access keys when the user presses the Alt key. Each Key Tip contains the alphanumeric keys that activate the associated control.
32
+
Keytips are badges displayed next to controls that support access keys when the user presses the Alt key. Each keytip contains the alphanumeric keys that activate the associated control.
33
33
34
34
> [!NOTE]
35
-
> Keyboard shortcuts are automatically supported for access keys with a single alphanumeric character. For example, simultaneously pressing Alt+F in Word opens the File menu without displaying Key Tips.
35
+
> Keyboard shortcuts are automatically supported for access keys with a single alphanumeric character. For example, simultaneously pressing Alt+F in Word opens the File menu without displaying keytips.
36
36
37
-
Pressing the Alt key initializes access key functionality and displays all currently available key combinations in Key Tips. Subsequent keystrokes are handled by the access key framework, which rejects invalid keys until either a valid access key is pressed, or the Enter, Esc, Tab, or Arrow keys are pressed to deactivate access keys and return keystroke handling to the app.
37
+
Pressing the Alt key initializes access key functionality and displays all currently available key combinations in keytips. Subsequent keystrokes are handled by the access key framework, which rejects invalid keys until either a valid access key is pressed, or the Enter, Esc, Tab, or Arrow keys are pressed to deactivate access keys and return keystroke handling to the app.
38
38
39
39
Microsoft Office apps provide extensive support for access keys. The following image shows the Home tab of Word with access keys activated (note the support for both numbers and multiple keystrokes).
40
40
41
-

41
+

42
42
43
43
_KeyTip badges for access keys in Microsoft Word_
44
44
45
-
To add an access key to a control, use the **AccessKey property**. The value of this property specifies the access key sequence, the shortcut (if a single alphanumeric), and the Key Tip.
45
+
To add an access key to a control, use the **AccessKey property**. The value of this property specifies the access key sequence, the shortcut (if a single alphanumeric), and the keytip.
@@ -240,46 +240,46 @@ _Specify the AccessKey property specified in the resources.resw file_
240
240
241
241
For more info, see [Translating UI resources ](/previous-versions/windows/apps/hh965329(v=win.10))
242
242
243
-
## Key Tip positioning
243
+
## Keytip positioning
244
244
245
-
Key tips are displayed as floating badges relative to their corresponding UI element, taking into account the presence of other UI elements, other Key Tips, and the screen edge.
245
+
Keytips are displayed as floating badges relative to their corresponding UI element, taking into account the presence of other UI elements, other keytips, and the screen edge.
246
246
247
-
Typically, the default Key Tip location is sufficient and provides built-in support for adaptive UI.
247
+
Typically, the default keytip location is sufficient and provides built-in support for adaptive UI.
248
248
249
-

249
+

250
250
251
-
_Example of automatic Key Tip placement_
251
+
_Example of automatic keytip placement_
252
252
253
-
However, should you need more control over Key Tip positioning, we recommend the following:
253
+
However, should you need more control over keytip positioning, we recommend the following:
254
254
255
-
1.**Obvious association principle**: The user can associate the control with the Key Tip easily.
255
+
1.**Obvious association principle**: The user can associate the control with the keytip easily.
256
256
257
-
a. The Key Tip should be **close** to the element who have the access key (the owner).
258
-
b. The Key Tip should **avoid covering enabled elements** that have access keys.
259
-
c. If a Key Tip can't be placed close to its owner, it should overlap the owner.
257
+
a. The keytip should be **close** to the element who have the access key (the owner).
258
+
b. The keytip should **avoid covering enabled elements** that have access keys.
259
+
c. If a keytip can't be placed close to its owner, it should overlap the owner.
260
260
261
-
2.**Discoverability**: The user can discover the control with the Key Tip quickly.
261
+
2.**Discoverability**: The user can discover the control with the keytip quickly.
262
262
263
-
a. The Key Tip never **overlaps** other Key Tips.
263
+
a. The keytip never **overlaps** other keytips.
264
264
265
-
3.**Easy scanning:** The user can skim the Key Tips easily.
265
+
3.**Easy scanning:** The user can skim the keytips easily.
266
266
267
-
a. Key Tips should be **aligned** with each other and with the UI Element.
268
-
b. Key Tips should be **grouped** as much as possible.
267
+
a. keytips should be **aligned** with each other and with the UI Element.
268
+
b. keytips should be **grouped** as much as possible.
269
269
270
270
### Relative position
271
271
272
-
Use the **KeyTipPlacementMode** property to customize the placement of the Key Tip on a per element or per group basis.
272
+
Use the **KeyTipPlacementMode** property to customize the placement of the keytip on a per element or per group basis.
273
273
274
274
The placement modes are: Top, Bottom, Right, Left, Hidden, Center, and Auto.
275
275
276
-

276
+

277
277
278
-
_Key tip placement modes_
278
+
_keytip placement modes_
279
279
280
-
The center line of the control is used to calculate the vertical and horizontal alignment of the Key Tip.
280
+
The center line of the control is used to calculate the vertical and horizontal alignment of the keytip.
281
281
282
-
They following example shows how to set the Key Tip placement of a group of controls using the KeyTipPlacementMode property of a StackPanel container.
282
+
They following example shows how to set the keytip placement of a group of controls using the KeyTipPlacementMode property of a StackPanel container.
The location of a Key Tip is automatically adjusted based on the screen edge to ensure the Key Tip is fully visible. When this occurs, the distance between the control and Key Tip alignment point might differ from the values specified for the horizontal and vertical offsets .
316
+
The location of a keytip is automatically adjusted based on the screen edge to ensure the keytip is fully visible. When this occurs, the distance between the control and keytip alignment point might differ from the values specified for the horizontal and vertical offsets .
317
317
318
-

318
+

319
319
320
-
_Key Tips are automatically positioned based on the screen edge_
320
+
_keytips are automatically positioned based on the screen edge_
321
321
322
-
## Key Tip style
322
+
## Keytip style
323
323
324
-
We recommend using the built-in Key Tip support for platform themes, including high contrast.
324
+
We recommend using the built-in keytip support for platform themes, including high contrast.
325
325
326
-
If you need to specify your own Key Tip styles, use application resources such as KeyTipFontSize (font size), KeyTipFontFamily (font family), KeyTipBackground (background), KeyTipForeground (foreground), KeyTipPadding (padding), KeyTipBorderBrush(Border color), and KeyTipBorderThemeThickness (border thickness).
326
+
If you need to specify your own keytip styles, use application resources such as KeyTipFontSize (font size), KeyTipFontFamily (font family), KeyTipBackground (background), KeyTipForeground (foreground), KeyTipPadding (padding), KeyTipBorderBrush(Border color), and KeyTipBorderThemeThickness (border thickness).
327
327
328
-

328
+

329
329
330
-
_Key tip customization options_
330
+
_keytip customization options_
331
331
332
332
This example demonstrates how to change these application resources:
0 commit comments