The DOJ provides one software accessibility checklist that I’m aware of.
I’m also wondering about an established rubric for software accessibility in the vein of WCAG. I found this page from W3C on applying WCAG to non-web technology, but it’s a fair amount to go through, not quite the lesson format you were looking for.
In the meantime, I would test any applications through the lens of POUR: is it perceivable (through multiple senses), operable (through multiple modes of interaction), understandable (by the intended audience, content is presented in a logical order and so forth), and robust (it doesn’t break by itself or with assistive technologies)?
System Administrator for Accessibility Compliance
Cascadia College | Ext. 2-8550
Does anyone have any good guidance or instructional materials on how to do an accessibility evaluation (mainly screen reader evaluation) of a standalone application (i.e., one that is not on a website/accessed through a browser)? I know that the same principles are involved, but I need something more concrete. For example, what is the equivalent to a heading in an application? How are shortcut keys revealed? Etc. All of my previous screen reader training materials have focused on web pages only.
Inclusion & Accessibility Librarian
Syracuse University Libraries
222 Waverly Ave., Syracuse, NY 13244
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.