Guidelines for touch keyboard and handwriting panel (Windows Store apps)
The touch keyboard enables text entry for Windows Store apps on devices that support touch and don’t have a built-in or peripheral keyboard. The touch keyboard is invoked when a user taps on an editable input field, and is dismissed when the input field loses focus. The touch keyboard is used for text entry only.
Here are our recommendations for supporting the touch keyboard in your Windows Store apps.
- Display the touch keyboard for text input only.
The touch keyboard doesn't provide many of the accelerators or command keys found on a hardware keyboard, such as alt, the function keys, or the Windows Logo key.
Don't make users navigate their application by using the keyboard.
Don't redefine input from the touch keyboard into commands or shortcuts.
- Continue displaying keyboard throughout the entire interaction with your form.
If you're creating custom UI, make sure your custom controls have the proper UI Automation ControlType to ensure keyboard persistence when focus moves from a text input field while in the context of text entry. For example, if you have a menu that's opened in the middle of a text-entry scenario, and you want the keyboard to persist, the menu must have the ControlType Menu.
- Ensure that users can always see the input field that they're typing into.
The touch keyboard occludes half of the screen. Windows Store apps provide a default experience for managing UI when the touch keyboard appears, by ensuring that the input field with focus scrolls into view. Handle the Showing and Hiding events exposed by the InputPane object to customize your app’s reaction to the keyboard’s appearance.
- Implement UI Automation properties for custom controls that have text input.
Standard controls for Windows Store apps have these properties, but custom controls require you to implement TextPattern. For the keyboard to persist contextually as focus changes to different controls, a custom control must have one of the following properties:
- Check box
- Combo box
- Radio button
- Scroll bar
- Tree item
- Menu item
- Don't manipulate UI Automation properties to control the touch keyboard.
Other accessibility tools rely on the accuracy of UI Automation properties.
The following article provides guidance for writing secure code.
Build date: 11/16/2013