Re: hit testing and retained graphics

hi Ben,

I thought I was clear, I have been talking about the screen magnifier case ,
not the general AT case. The only information that would need to be provided
from the remote machine is the size and position of the focused object, this
could then be used to provide the focus information to the local
accessibility layer.

regards
Stevef

On 3 July 2011 02:54, Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>wrote:

> On Sat, Jul 2, 2011 at 3:06 PM, Steve Faulkner
> <faulkner.steve@gmail.com> wrote:
> > I don't see why you would have to duplicate the whole accessibility
> > stack  to provide focus tracking for a screen magnifier, can you
> > explain this a bit further?
>
> The remote system access server would need to translate the remote
> applications (as accessed by the accessibility tree plus custom hooks)
> into DOM. To support custom views/controls for which we do not have
> semantics in the web stack or to provide any application-specific
> customizations, local AT would have to make special interpretations of
> the DOM (either directly or as exposed to the accessibility API). Thus,
> the accessibility stack (converting remote applications into accessible
> interfaces) would need to be duplicated.
>
> If you disagree, can you explain precisely what you think the remote
> system access server on the one hand, and local AT on the other, would
> need to do?
>
> --
> Benjamin Hawkes-Lewis
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html