Re: hit testing and retained graphics

On Thu, Jun 30, 2011 at 10:45 PM, Benjamin Hawkes-Lewis
<bhawkeslewis@googlemail.com> wrote:

> But exposing "a11y information" in the case of Windows means
> exposing basically every API in the system, since in practice AT has to
> hack around the limitations of MSAA, e.g. using display hooks,
> mirror drivers, and application-specific APIs. Simply passing through UI
> Automation calls will not allow a remote JAWS instance (say) to access
> common Windows applications.

For those unfamiliar with the hoops Windows AT has to jump through,
there's a great talk about this by Doug Geoffray of GW-Micro:

http://www.yuiblog.com/blog/2007/03/28/video-geoffray/

--
Benjamin Hawkes-Lewis