An Overview of Accessibility for Windows IoT
Accessibility enables people of all abilities to intuitively and efficiently leverage all the functionalities that your applications or devices offer, regardless of a person interacts with your application or device.
It is essential that accessibility is considered during the design phase of the product as this will avoid many potential accessibility-related bugs. For example, during the design phase, consideration around the colors used and the size of text (and how those might be customized by the user) can help a great many customers. And for devices with a keyboard, during the design phase, consideration around how the keyboard can be used to leverage all the functionality in the product, and also how to access the most frequently accessed functionality with the fewest number of keystrokes.
For the developer, from an implementation perspective the good news is that Windows as a platform already does a lot of work to provide some level of accessibility by default. For example, standard controls are programmatically accessible by default through the UI Automation (UIA) API. If you choose not to use a standard control and instead build custom UI, the work required to make the UI accessibility can be much more time-consuming than simply building apps using standard controls provided by the platform.
Below are tools we recommend using while building your application. While these tools will help when it comes to auditing your own designs, please note that you will still need to account for features such as high contrast and text requirements.
The AccScope tool enables developers and testers to evaluate the accessibility of their app during the app's development and design, potentially in earlier prototype phases, rather than in the late testing phases of an app's development cycle. It's intended for testing Narrator accessibility scenarios with your app.
Inspect enables you to select any UI element and view its accessibility data. You can view Microsoft UI Automation properties and control patterns and test the navigational structure of the automation elements in the UI Automation tree. Use Inspect as you develop the UI to verify how accessibility attributes are exposed in UI Automation. In some cases, the attributes come from the UI Automation support that is already implemented for default XAML controls. In other cases the attributes come from specific values that you have set in your XAML markup, as AutomationProperties attached properties.
Want to learn more about accessibility testing? Read the Accessibility testing article for the full list.
Accessibility in UWP apps
The UWP team at Microsoft has put together a comprehensive guide on accessibility for UWP app design and development. For your convenience, we've included the list below, but you can also learn more by reading our overview on accessibility.
In addition, an introduction to the UI Automation API and some tools available to help you learn about the programmatic representation of your UI, is available below.
|Designing inclusive software||Learn about evolving inclusive design with UWP apps for Windows 10. Design and build inclusive software with accessibility in mind.|
|Developing inclusive Windows apps||This article is a roadmap for developing accessible UWP apps.|
|Accessibility checklist||Provides a checklist to help you ensure that your UWP app is accessible.|
|Expose basic accessibility information||Basic accessibility info is often categorized into name, role, and value. This topic describes code to help your app expose the basic information that assistive technologies need.|
|Keyboard accessibility||If your app does not provide good keyboard access, users who are blind or have mobility issues can have difficulty using your app or may not be able to use it at all.|
|High-contrast themes||Describes the steps needed to ensure your UWP app is usable when a high-contrast theme is active.|
|Accessible text requirements||This topic describes best practices for accessibility of text in an app, by assuring that colors and backgrounds satisfy the necessary contrast ratio. This topic also discusses the Microsoft UI Automation roles that text elements in a UWP app can have, and best practices for text in graphics.|
|Accessibility practices to avoid||Lists the practices to avoid if you want to create an accessible UWP app.|
|Custom automation peers||Describes the concept of automation peers for Microsoft UI Automation, and how you can provide automation support for your own custom UI class.|
Windows 10 IoT Enterprise includes accessibility features that can be integrated to further support where vision, hearing, physical, cognition, along with assistive technology is needed. This additional support makes it easier to customize devices and gives users with different abilities options to improve their experience with Windows.
- Be aware of Ease of Access settings – Understand how these devices are being used. Help people in your organization learn how they can customize Windows 10.
- Do not block settings – Avoid using Group Policy or MDM settings that override Ease of Access settings.
- Encourage choice – Allow for device customization based upon needs. That might mean installing an add-on for a browser, or a non-Microsoft assistive technology.