This documentation focuses on the markup and code that developers need to implement to support the following key accessibility scenarios.
- Screen reading—Users who are blind or visually impaired rely on screen readers to interpret and interact with your app's UI. Interpreting involves reading the UI element names, roles, values, and so on, and interacting with the UI involves moving the focus from one element to another and invoking app functionality.
- Keyboard accessibility—Many accessibility users rely on the keyboard to navigate and operate the UI by:
- Moving focus among elements by using the Tab key.
- Navigating in container elements such as lists, grids, and tree views by using the arrow keys.
- Activating functionality by using the Enter or Space key.
- Using shortcut keys to efficiently invoke app functionality.
- Accessible visual experience—Users who are visually impaired need a sufficient text contrast ratio and a good visual experience with High Contrast themes. Users who are color blind need information to be conveyed in ways other than through color.
- Meeting basic accessibility requirements
- Implementing accessibility for particular content types
- Practices to avoid
- Testing your app for accessibility
- Declaring your app as accessible in the Windows Store
- Guidelines and checklist for accessibility
Build date: 11/28/2012