#Build2016

What’s New in Accessibility(for Developers and Users)Jeff Petty, PMWindows Accessibility

What’s New for Developers?

What’s New for Developers?Improved documentationAccessibility Developer Hub launched to provide a one stop shop for accessibility contentWindows Dev Center > Design and UI > Usability > Accessibility integrates guidance and sample code

New XAML makes it easier to create accessible appsMnemonics in XAML in two easy steps

Edge improvementsNumerous improvements to deliver a modern platform and great user experience

New tools to make it easier to find and resolve issuesVisual Studio App Analysis makes it easier to build accessible appsNarrator Developer Mode (Shift+Caps+F12) makes it easier to test apps

Accessibility Developer Hubhttp://msdn.Microsoft.com/accessibility

[show me]

Design & UI @Windows Dev Centerhttps://dev.windows.com

[show me]

Mnemonics in XAMLAKA Access Keys

XAML<Button Content="MyButton"

AccessKey="B"

AccessKeyDisplayDismissed="OnAccessKeyDisplayDismissed"

AccessKeyDisplayRequested="OnAccessKeyDisplayRequested" />

Setup the mnemonic

Events to make developers can use their own visuals.

User taps ALT

C# Code Behind for the Handlers private void OnAccessKeyDisplayDismissed(UIElement sender, AccessKeyDisplayDismissedEventArgs args) { var tooltip = ToolTipService.GetToolTip(sender) as ToolTip;

if (tooltip == null) { tooltip = new ToolTip(); tooltip.Background = new SolidColorBrush(Windows.UI.Colors.Black); tooltip.Foreground = new SolidColorBrush(Windows.UI.Colors.White); tooltip.Padding = new Thickness(4, 4, 4, 4); tooltip.VerticalOffset = -10; tooltip.Placement = PlacementMode.Bottom;

ToolTipService.SetToolTip(sender, tooltip); tooltip.Content = sender.AccessKey; } tooltip.IsOpen = true; }

private void OnAccessKeyDisplayRequested(UIElement sender, AccessKeyDisplayRequestedEventArgs args) { var tooltip = ToolTipService.GetToolTip(sender) as ToolTip; if (tooltip != null) { tooltip.IsOpen = false; } }

Looking ahead: Microsoft Edge for developers in 2016https://blogs.windows.com/msedgedev/2016/02/03/2016-platform-priorities/#accessibility

[show me]

Edge Accessibility ImprovementsModernize our accessibility system to support HTML5 and CSS3 on Windows 10.Enable HTML and Core Accessibility API mappings.Provide Accessible Name and Description computation and API mappings.Add accessible HTML5 controls and new semantic elements.Improve high contrast support.Modernize caret browsing and new input modalities.Improve visual impairment readability, focus, and selection.Deliver developer tools for building and testing accessible sites.

Narrator Developer ModeWindows + Enter > Shift + Caps Lock + F12

• Launch Narrator… Windows + Enter

• Launch Dev Mode…Shift + Caps Lock +F12

• Screen masking for application in focus

• Highlight accessible objects

• See the text that is programmatically exposed

Visual Studio App Analysis

Tools for UI Optimization

Element with no automation name

What’s New for Users?

What’s New for Users? Improved Narrator…DocumentationNew tutorial (for new users) and product documentation (for a range of users)

PerformanceMore responsive Narrator experiences with Windows Shell and Apps

ReliabilityBetter reading and authoring experiences with Apps like Mail and Word

UsabilityImproved keyboard model that is more familiar, better ergonomically and that simplifies interactionsImproved text to speech, including additional voices and higher top speedsNew features, like accessible autosuggest that improves Cortana, Edge, Mail and other experiences

• Reach a broader audience and differentiate your applications with great accessibility

• Visit the Accessibility Developer Hub and Design & UI site for guidance

• Leverage new tooling to make it easier to deliver great experiences

Call to Action