Accessibility in Windows Store apps using JavaScript

This topic describes the support for accessibility that is included in the Windows Store app using JavaScript platform, and explains how to take advantage of that support to create an accessible Windows Store app using JavaScript.

The topics in this section are designed for developers who are familiar with HTML, Cascading Style Sheets (CSS), and JavaScript.

To learn about accessibility for C#, Microsoft Visual Basic or Visual C++ component extensions (C++/CX), see Accessibility in Windows Store apps built for Windows using C++, C#, or Visual Basic.

Support for accessibility is built into the Windows Store app using JavaScript platform. As the Windows Store app using JavaScript host renders an app UI, accessibility information that is defined in the app markup is exposed through Microsoft UI Automation—the Microsoft accessibility API—and made available to assistive technology tools such as screen readers.

It's simple and easy to implement accessibility in Windows Store apps using JavaScript. Because all HTML tags and Microsoft Windows Store app using JavaScript controls are already accessible, implementing accessibility in Windows Store apps using JavaScript typically involves setting just a few HTML attributes.

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.

In this section

• 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
• Mapping HTML and ARIA properties to UI Automation

Additional resources

• ARIA sample — This sample app demonstrates how to use Accessible Rich Internet Applications (ARIA) tags to make a Windows Store app fully accessible.
• WAI-ARIA Reference — This page of the official World Wide Web Consortium (W3C) Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) specification provides links to reference information for all of the ARIA roles, states, and, properties.
• WAI-ARIA Authoring Practices — This page describes keyboard interaction and identifies the relevant WAI-ARIA roles, states, and properties for a set of widgets and structures.
• HTML5 Specification — This is the official W3C HTML5 specification that includes WAI-ARIA, which is now part of the HTML5 standard.
• OpenAjax Accessibility Examples — This site is an excellent resource for verifying the rules for WAI-ARIA and HTML5. It also contains a number of examples of WAI-ARIA implementations.

Related topics

Accessibility in Windows Store apps built for Windows using C++, C#, or Visual Basic

Accessibility in Windows Store apps

Build date: 6/19/2013