Peter Trudelle wrote:I just meant that MSAA clients can seamlessly navigate between the embedding client and the embedded Gecko, which means a switch from getting info from their MSAA server, to getting it from ours. The MSAA server exposes info about the various UI elements, including their location, and enables accessibility aids to navigate between them and manipulate them.[EMAIL PROTECTED]">. What is meant by the "embedding boundary" in this context? Is the MSAA server some daemon we implement that uses win32 apis to drive accessibility things? What would these "things" be?Judson Valeski wrote:
That's what I'm getting at. Cool, so nsIPref sounds like it will be your "this is how the global accessibilty settings are changed," solution. I'm lost WRT what there is beyond that. I guess my confusion is coming from what an MSAA server is and does.Sure, we'll use prefs just like everything else does. The MSAA server (as I understand it) basically says to any screen reader that invokes it "Hi, I'm making this app accessible. Here are all the elements in the UI, so you can navigate and query them. Oh, this thing? Its the File menu, accessed by Alt-F. That there? It's a push button, labeled "Okay", accessed by the enter Key. " The MSAA SDK (http://www.microsoft.com/enable) has some tools for INSPECTing MSAA servers, so you can see what is exposed. The major screen readers have demos of their products available for download. Eric can give a demo of how our server works.
Peter
