- From: Todd Kloots <kloots@yahoo-inc.com>
- Date: Wed, 9 Mar 2011 13:59:30 -0800
- To: James Craig <jcraig@apple.com>
- CC: W3C WAI-XTECH <wai-xtech@w3.org>
Thanks for the info James. Any sense of whether or not feature requests for aria-busy support have already been filed with NVDA, JAWS, VO, etc? If not, I'll start making the requests. On Mar 9, 2011, at 11:40 AM, James Craig wrote: > WebKit also exposes this to the OS X Accessibility API as AXAriaBusy. If you download the developer tools from developer.apple.com, they include a utility app called the Accessibility Inspector, which allows you to display the AX tree and node properties. > > So to answer your question, several *browsers* currently expose this to APIs, but to my knowledge, no *screen readers* expose it to the user yet. > > > On Mar 9, 2011, at 11:22 AM, David Bolter wrote: > >> Hi Todd, >> >> Did you really mean FF 3.5? That's pretty old now :) >> >> If you inspect Firefox via accprobe or Accerciser and look at the object properties you should see we expose a "busy" attribute for the accessible object, and "container-busy" for child objects. >> >> >> Cheers, >> David >> >> On 09/03/11 1:36 PM, Todd Kloots wrote: >>> I was recently re-reading the ARIA spec and came across the aria-busy state. Seems like a very useful state, but it doesn't seem like it is supported in any of the screen readers or browsers. I've tested in JAWS 12 + IE 8, JAWS 12 + FF 3.5, and NVDA + FF 3.5. Anyone have any working examples of aria-busy? >>> >>> Thanks, >>> Todd >> >> >
Received on Wednesday, 9 March 2011 22:00:26 UTC