This post begins a series of entries regarding the implementation of Accessible Rich Internet Applications (ARIA) specification in the real world. There are a number of factors that impact ARIA geared development and the user experiences of Assistive Technology users. For example, differing user agents and versions combined with various ...
Lesser known details that seriously impact the usage of dynamically generated ARIA behaviors
Sun, 04 Dec 2011 22:47:57 GMT
The W3C's ARIA specification gives web developers a way to annotate pages, assigning "roles" to HTML elements. Now that screen readers actually support ARIA, roles offer an easy way to create a more accessible web.
WAI-ARIA Gets Ready for a Starring Role in HTML5
Scott Gilbertson
Tue, 29 Nov 2011 15:19:00 GMT
Noting that the landmark support test results I conducted back in July 2011 were being tweeted recently, I though it would be good to update the results. ChromeVox support data has been added, thanks to @KevinChao89 for the ChromeVox keystroke info. VoiceOver testing on OSX lion has been added, thanks to @hanshillen for testing.
ARIA landmark support summary data
- Jaws 11/12/13 has complete support.
- ChromeVox has complete support.
- VoiceOver supports all landmarks except “form”.
- NVDA supports all landmarks except “application” and “form”.
- Window Eyes does not support ARIA landmarks.
ARIA landmark support details:
Latest ARIA landmark support data
Steve Faulkner
Mon, 21 Nov 2011 14:39:48 GMT
