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
[log in to unmask]
222 Waverly Ave., Syracuse, NY 13244