Following last weeks post about Google Chrome accessibility which was prompted by The Google Chrome Screen Reader Accessibility Petition created by Alex Hiironen, new information about Google Chrome screen reader support has been added to the Google Chrome (Chromium) wiki:
Supported Screen Readers
The latest versions of these screen readers have partial support for Chrome now:
System Access to Go (Windows)
VoiceOver (Mac OS X)
These [...]
The Microsoft MSAA API cannot provide mapping for all ARIA roles as it does not have defined roles and properties for all those defined by The ARIA specification, the Microsoft UI Automation API can. UI automation provides exposure of all WAI-ARIA roles and properties via the ControlType and AriaRole properties.
WAI-ARIA Landmark Roles
The WAI ARIA specification defines a set of specialised “landmark” roles. These roles provide a method to programmatically identify commonly found sections of web page content in a consistent way. they can be used now in whatever flavour of (X)HTML you prefer. This allows assistive technologies to provide users with features which they [...]
Todd Kloots provides valuable information on setting up JAWS, Window Eyes and NVDA in his article Configuring Your Machine For Testing With A Screen Reader.
Assistive technology such as screen readers provide keyboard short cuts for navigating the content of web pages. For user input controls such as radio buttons and edit boxes the user can navigate the controls sequentially using assigned ‘form field’ or ‘form control’ navigation keys: