It took me about 10 minutes of manually digging through W3C ARIA specification(s) when writing a paper before I decided to create a quick reference. The reference is organized into a table of contents that links to each ARIA definition on the same page.
I would like to create a menu for my Web app. I know the HTML markup to create a list, though I’m not sure about the ARIA semantics or the Javscript code.
I would like to add a descriptive label to my widget that is hidden from sited users but is accessible to AT though I’m not sure about the semantics.
I would like to add hot keys / access keys to my application though I’m not sure what the best method is or more importantly what my users will expect.
I have a web application and I’d like to let an AT know more about it. The tricky part is that documents are embeded in my application as well.
It took me about 10 minutes of manually digging through W3C WCAG2 spec. before I decided to create a quick reference. The reference is organized into a table of contents that links to each WCAG2 requirement on the same page. Note this reference doesn’t give a holistic approach on meeting WCAG2, only the specific W3C A, AA, and AAA requirements.
Abstract: The AJAX architecture has given rise to new levels of user interaction with Web pages. Many of these new extremely popular Web 2.0 pages are better classified as full-fledged applications; for example, Google Maps, Google Docs, Flickr, and so on. Unfortunately, accessibility support in most AJAX applications is lacking. WAI-ARIA markup presents a solution to making these applications accessible. This paper presents a real-life example of how ARIA Live Regions can greatly improve the accessibility of a Web 2.0 chat application (ReefChat) when used with a WAI-ARIA aware assistive technology (Fire Vox).
Abstract: To address the Web 2.0 accessibility problem we developed an Accessible Ajax chat application called ReefChat and the Fire Vox screen reader. Features include, chat message notification through live regions to notify the AT. As well as keying up and down messages to navigate through chat messages, and keying left and right to filter messages from specific users. In this paper after briefly discussing the problem of Web 2.0, we describe our accessible chat application and screen reader.
Abstract: Web 2.0 enabled by the Ajax architecture has given rise to a new level of user interactivity through web browsers. Many new and extremely popular Web applications have been introduced such as Google Maps, Google Docs, Flickr, and so on. Ajax Toolkits such as Dojo allow web developers to build Web 2.0 applications quickly and with little effort. Unfortunately, the accessibility support in most toolkits and Ajax applications overall is lacking. WAI-ARIA markup for live regions presents a solution to making these applications accessible. A chat example is presented that shows the live regions in action and demonstrates several limitations of ARIA live regions.