Using the aria-owns attribute

When a parent/child relationship is evident on-screen, but it isn’t represented in the DOM, the aria-owns attribute can be used to establish that relationship in the accessibility layer.

Accessible timeout notifications

When a web application has a session timeout, it’s a good idea to warn users about the impending timeout and give them the opportunity to do something about it. It’s therefore important to make sure that all users know when the warning notification appears.

Using the aria-controls attribute

There are a handful of ARIA1.0 attributes that can be used to indicate relationships between elements, when those relationships can’t be ascertained easily from the DOM. One such attribute is aria-controls.

Understanding screen reader interaction modes

Traduction française Windows screen readers have multiple modes of interaction, and depending on the task being carried out they’ll automatically switch to the most appropriate mode. This post explains why Windows screen readers behave the way they do, and how your code can influence that behaviour.

Jaws, IE & the Forms region bug

There is an unusual problem with Jaws and Internet Explorer that causes the word “region” to be announced before every field in a form. Fortunately there is a workaround until the problem itself is resolved.

Screen readers, ARIA & HTML5 (too much information)

Most current screen readers support ARIA to one extent or another, and many now support some features of HTML5 as well. With ARIA and HTML5 making increasing amounts of semantic data available to screen reader users, it’s really easy to inadvertently overload people with too much information. Let’s take an example that crops up from […]