More tips on the use of LiveRegions in your WinJS app

Hi, A while back I described some of my experiences with LiveRegions in a WinJS app, at http://blogs.msdn.com/b/winuiautomation/archive/2013/08/04/an-accessibility-case-study-reading-list-part-5-live-regions.aspx. I recently got to do some more experiments involving LiveRegions, so I thought it’d be worth sharing my thoughts on those. My situation was that I had a “label” HTML element, and it was marked as aria-live=”assertive”. When…

0

An accessibility case study – Reading List. Part 6: Using Narrator with touch input only

This post discusses accessibility considerations around the use of touch input to control the Narrator screen reader while interacting with the Reading List app available in the Windows 8.1 Preview. The ability to use touch alone to interact with the Reading List app when using the Narrator screen reader is a very important scenario. The…

1

An accessibility case study – Reading List. Part 5: Live Regions

This post discusses accessibility considerations around the use of Live Regions in the Reading List app available in the Windows 8.1 Preview. Typically, assistive technology tools such as screen readers will report information relating to the visuals shown on the screen near the point where the customer is working. That point may be the element…

0

An accessibility case study – Reading List. Part 4: Programmatic accessibility

This post discusses accessibility considerations around programmatic accessibility of the Reading List app available in the Windows 8.1 Preview. Programmatic access allows software tools to report details relating to visual elements shown on the screen, and to interact with those elements. This allows assistive technology (AT) tools such as screen readers or magnifiers to interact…

0

An accessibility case study – Reading List. Part 3: Keyboard accessibility

This post discusses accessibility considerations around keyboard accessibility of the Reading List app available in the Windows 8.1 Preview. The series of posts, “An accessibility case study – Reading List”, highlights work the Reading List team did to enhance the accessibility of the Reading List app beyond the level provided by default by the WinJS…

0

An accessibility case study – Reading List. Part 2: Colours and Contrast

This post discusses accessibility considerations around colours and contrast shown in the UI of the Reading List app available in the Windows 8.1 Preview. The Reading List team’s first considerations here were around the default colours shown in the app. The result was that we felt the colours shown wouldn’t introduce challenges working at the…

0

An accessibility case study – Reading List. Part 1: Introduction

Reading List is an app introduced with the Windows 8.1 Preview. During development of the app, the Reading List team focused carefully on its accessibility, to make sure customers of all abilities can fully leverage the app’s features. This series of blog posts details the things we considered, and how we implemented specific accessibility-related functionality…

0

A little UIA Q&A

Hi, over the last six months I’ve been in contact with a developer who builds Assistive Technology (AT) apps which use the Windows 8 UI Automation (UIA) client API. It’s been really exciting for me to see the results of his great work, as those results will be extremely helpful to his customers. It’s also been…


Reusing one of your strings shown visually in your Windows 8 app as the accessible name for another element

The XAML and WinJS UI frameworks do some great things for the default accessibility of your Windows 8 app. This includes setting the accessible name of your element from the text shown on it. For example, if you had a couple of buttons which show “Save” and “Cancel” (say), then a screen reader would find…