aria

In our page.tpl.php theme override, there exists the following line.

In order to correctly insert Aira Landmarks, am I correct in assuming the following:

This is Todd at the University of Iowa.

We're just scratching the surface of Drupal here--three or four departments are letting our central web group pilot. We have a couple of really sharp developers and a deep commitment to accessibility. What we're missing is a good understanding of our options for integrating the two. Some things I'd very much like to know--an incomplete list:

How to add uncommon attributes to HTML tags (e.g., scope="col" to a

Setting divs and other regions as ARIA landmarks (aria-live, aria-required)

while i am biased towards early ARIA adaptation, having worked on the ARIA spec for longer than i'd care to remember, i would counsel both early adaptation AND redundancy for graceful degredation, for, as everett has consitently and correctly pointed out, implementation of ARIA is incomplete and inconsistent...

Not much to say here, but perhaps this would be a good place to hash out what we know and need to know about doing accessibility tests on ARIA-based interfaces. It's a real challenge.

A good place for background information is Jared Smith's presentation at the November 2009 Accessing Higher Ground Conference, Accessibility of Rich Internet Applications.

Overview: I propose to increase the accessibility of important Drupal interfaces for people with various impairments. Specifically, I want to modify Drupal 7's core themes, the WYSIWYG module's TinyMCE configuration options, and View's interface and output to be more accessible.

I'm using the Password Policy module to enforce strong passwords. When a user changes their password, the module displays a password strength indicator via Javascript. I'd like to add the ARIA live region role to the span that contains the strength indication and error message.

Hacking the Javascript is pretty simple. I'd like to consider the options for doing this the "best" way.