Accessibility
Accessibility is about building experiences that make your Windows application usable by people who use technology in a wide range of environments and approach your UI with a range of needs and experiences. For some situations, accessibility requirements are imposed by law. However, it's a good idea to address accessibility issues regardless of legal requirements so that your apps have the largest possible audience.
There's also a Microsoft Store declaration regarding accessibility for your app!
Article | Description |
---|---|
Accessibility overview | This article is an overview of the concepts and technologies related to accessibility scenarios for Windows apps. |
Designing inclusive software | Learn about evolving inclusive design with Windows apps for Windows. Design and build inclusive software with accessibility in mind. |
Developing inclusive Windows apps | This article is a roadmap for developing accessible Windows apps. |
Accessibility testing | Testing procedures to follow to ensure that your Windows app is accessible. |
Accessibility in the Store | Describes the requirements for declaring your Windows app as accessible in the Microsoft Store. |
Accessibility checklist | Provides a checklist to help you ensure that your Windows 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. |
Screen readers and hardware system buttons | Screen-readers, such as Narrator, must be able to recognize and handle hardware system button events and communicate their state to users. In some cases, the screen reader might need to handle button events exclusively and not let them bubble up to other handlers. |
Landmarks and Headings | Landmarks and headings define sections of a user interface that aid in efficient navigation for users of assistive technology such as screen readers. |
High-contrast themes | Describes the steps needed to ensure your Windows 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 Windows 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 Windows app. |
Custom automation peers | Describes the concept of automation peers for UI Automation, and how you can provide automation support for your own custom UI class. |
Control patterns and interfaces | Lists the Microsoft UI Automation control patterns, the classes that clients use to access them, and the interfaces providers use to implement them. |
Related topics
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
Windows developer