I've read that IBM has contributed to making Dojo accessible to blind and vision impaired users. It looks like they rely on ARIA for this support. Which is fine given that IE8 and the other recent browsers offer support.
Does anyone have any tips on testing for accessibility short of using a screenreader? (We will use a screenreader to test eventually, but that's tedious to do for every screen.)
For code we write ourselves (that predates ARIA), we've been using the technique of turning off the stylesheet and making sure the app is accessible with the keyboard. However, when I turn off the CSS, Dojo widgets degrade into very basic HTML. All the validation etc is gone. Not exactly what I call accessible. So I'm guessing there is a new technique for testing ARIA.
I did look at the source. IBM seems to have done a good job.
I also blogged about how to view the source to see the ARIA parts.
Hi Jeanne, he just woke up I have not been implementing and ARIA/WAI things myself, but if I remember corectly it results in a set of html properties and other things that guarantees a certain set of behavior. For example, Dojo can advertise that a certin number of elements are 'tabs', and then amkes sure that pressing the tab button circles between them.
There's a fairly technical discussion here on implementation, with some pointers;