Partilhar via

Declaring your app as accessible in the Windows Store (HTML)

  • Artigo

[This article is for Windows 8.x and Windows Phone 8.x developers writing Windows Runtime apps. If you’re developing for Windows 10, see the latest documentation]

Looking for the C#/VB/C++/XAML version of this topic? See Declaring your app as accessible in the Windows Store.

While submitting your app to the Windows Store, you can declare your app as accessible. Declaring your app as accessible makes it easier to discover for users who are interested in accessible apps, such as users who have visual impairments. Users discover accessible apps by using the Accessible filter while searching the Windows Store. Declaring your app as accessible also adds the Accessible tag to your app’s description.

By declaring your app as accessible, you state that it meets the basic accessibility requirements that users need for primary scenarios using one or more of the following:

  • the keyboard
  • a high contrast theme
  • a variable dots per inch (dpi) setting
  • assistive technology such as the Microsoft Windows accessibility features, including Narrator, Magnifier, and the On-Screen Keyboard.

You should declare your app as accessible if you built and tested it for accessibility. This means that you did the following:

  • Set all the relevant accessibility information for UI elements, including name, role, value, status, and so on.
  • Implemented full keyboard accessibility, enabling the user to:
    • Accomplish all app scenarios by using only the keyboard.
    • Tab among UI elements in a logical order.
    • Navigate among UI elements within a control by using the arrow keys.
    • Use keyboard shortcuts to reach primary app functionality.
  • Ensured that your app UI is visually accessible: has a minimum text contrast ratio of 4.5:1, does not rely on color alone to convey information, and so on.
  • Used accessibility testing tools such as Inspect and UI Accessibility Checker (AccChecker) to verify your accessibility implementation, and resolved all priority 1 errors reported by such tools.
  • Verified your app’s primary scenarios from end to end by using Narrator, Magnifier, On-Screen Keyboard, a high contrast theme, and adjusted dpi settings.

See Guidelines and checklist for accessibility for a review of these procedures and links to resources that will help you accomplish them.

Accessibility for Windows Runtime apps using JavaScript and HTML