Keyboard accelerators make your app more accessible for users with motor disabilities, including those users who can press only one key at a time or have difficulty using a mouse.**Ī well-designed keyboard UI is an important aspect of software accessibility.
We recommend that you specify keyboard accelerators wherever appropriate in your UI, and support accelerators in all custom controls. Keyboard accelerators described in a menu item label When to use keyboard accelerators However, because users rely on an application's menus to discover and learn the available command set, you should try to make discovery of accelerators as easy as possible (using labels or established patterns can help with this).Īn accelerator auto-repeats (for example, when the user presses Ctrl+Shift and then holds down M, the accelerator is invoked repeatedly until M is released). Keyboard accelerators are not available for every action but are often associated with commands exposed in menus (and should be specified with the menu item content). Accelerators can also be associated with actions that do not have equivalent menu items. Accelerators defined by you using the keyboard accelerator APIs discussed here are referred to as app accelerators. These built-in keyboard accelerators are referred to as control accelerators and are executed only if the focus is on the element or one of its children. For example, ListView supports Ctrl+A for selecting all the items in the list, and RichEditBox supports Ctrl+Tab for inserting a Tab in the text box. Many XAML controls have built-in keyboard accelerators. For example, if a user presses Ctrl+Shift+M, the framework checks the modifiers (Ctrl and Shift) and fires the accelerator, if it exists. Accelerators typically include the function keys F1 through F12 or some combination of a standard key paired with one or more modifier keys (CTRL, Shift).
Many fonts improperly display Alt 166 as ｪ rather than, and Alt 167 as ｺ rather than. Some word processing programs will not recognize these Alt functions. There are some gaps in the numerical sequence of Alt character codes, because either those elements do not exist, or they are duplicates of elements listed elsewhere.
0 kommentar(er)
