Closed karlgroves closed 10 years ago
Because you know better than me, probably. Does ChromeVis or ChromeShades communicate any of this? https://code.google.com/p/google-axs-chrome/
I haven't looked specifically at those two. I spent a little time looking at ChromeVox which appears to purely use the DOM to communicate UI object info. Chrome itself does implement accessibility APIs so if there was some way to get hooks into Chrome's AAPI implementation, that would be ideal.
I think if anyone would know it might be Dominic Mazzoni (@minorninth)
We're working on integrating the A11y DevTools extension into Chrome DevTools proper. :) It's gonna be awesome.
Star this: https://code.google.com/p/chromium/issues/detail?id=390254
Starred!
We're also working on exposing the accessibility API to extension developers!
Awesome!
On Mon, Sep 22, 2014 at 5:10 PM, dmazzoni-google notifications@github.com wrote:
We're also working on exposing the accessibility API to extension developers!
— Reply to this email directly or view it on GitHub https://github.com/h5bp/lazyweb-requests/issues/147#issuecomment-56443646 .
Karl Groves www.karlgroves.com @karlgroves http://www.linkedin.com/in/karlgroves Phone: +1 410.541.6829
Modern Web Toolsets and Accessibility https://www.youtube.com/watch?v=_uq6Db47-Ks
www.tenon.io
All modern browsers now have some form of developer tools. Each of them, in their own way can expose DOM information for each node in the DOM.
Also, modern browsers implement accessibility APIs such as MSAA, UIAutomation, or IAccessible2
Unfortunately, getting the Accessibility API info for web UI elements requires the use of a tool that exists outside of the browser, such as AViewer or the Accessibility Inspector.
Chrome has the ability to dump the accessibility tree, but that's about as useful as a concrete parachute. It vomits out the tree info into a new screen with no ability to correlate the data to the node.
Chrome's Accessibility Developer Tools do give you extra information on Accessibility Properties, and gives you the node's text information and relevant aria information but this still doesn't include the actual Name, State, Role, Value information from accessibility APIs.
Adding information like this would be invaluable, especially if you could also inspect what events were bound to each node, as developers would then have important information available to help them know how accessible their UI is.