Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Making the app bar accessible

The app bar is important because it gives the user easy access your app's commands.

If you use platform button elements (Windows Runtime button controls in HTML, any ButtonBase class in XAML, keyboard activation is already supported.

The app bar is also an excellent place to put alternatives for functionality that is otherwise difficult to expose for accessibility. For example, consider the transport controls in a custom media player app:

Transport controls and supported arrow keys for navigating the app bar

Because these controls are used frequently, the app designers decided to expose them in the app bar. Having these controls as buttons in the app bar gives the user an easy way to control music and videos with the keyboard and Narrator. This is especially convenient on touch-only devices. Finding on-screen transport controls can be a challenge for blind and visually impaired users because the default transport controls disappear after a few seconds while the media is playing. (This is the behavior of the built-in transport controls in the XAML MediaElement, with AreTransportControlsEnabled=true).

Related topics

AppBar control (XAML)
AppBar (HTML)
Implementing keyboard accessibility (HTML)
Implementing keyboard accessibility (XAML)



© 2015 Microsoft