> >OOo can be run as a service and manipulated from a script or program. >See, for instance, ><http://www.artofsolving.com/opensource/pyodconverter>. I'm not sure >what MSAA compliance entails, but maybe this could be used as a >starting point.
That's interesting. Unfortunately, users need this capacity "yesterday" and so I need a ready-made solution. MSAA compliance is built into all visual controls in Windows. All one has to do to get the benefits of MSAA in Windows is to use native Windows controls in one's applications, or alternatively, use controls that provide the same MSAA interface that native Windows controls do (as do VFP controls in Version 7 SP 1 and later). The developers of Open Office refuse to do this. They claim the product is accessible because it uses some sort of Java-related accessibility feature, but it's not MSAA-compliant. Screen-reading software can read the actual text of documents in Open Office, but it cannot read any of the buttons, menus etc., so users cannot control the thing. (Yes, Ed, dabo uses wxwidgets which are wrappers for OS-native controls and so they should work in Windows or wherever. ;).) Thanks. Ken Dibble www.stic-cil.org _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
