Hello! Thanks for your reply. I had a look at the setup window, and it appears that some MSAA-information is still available, I hope it's enough to write a simple script to "catch" that info and speak it. It's not the best solution, but if it gets me going that's good enough. And if not there are still some alternatives. You could ask for some sighted assistance, or if you have an Office volume license you could use the Setup Customization Tool, or you might even be able to edit the various setup.xml files.
Thanks, Davy ----- Original Message ----- From: Chip Orange To: [email protected] Sent: Monday, October 18, 2010 12:06 AM Subject: RE: Office 2010 custom setup I'm afraid it's a known issue for all screen readers. It's part of a bigger known issue; MS is switching from MSAA to something called UIA for providing accessibility information, and screen readers and MS both have work left to do in order to make this work out. they all know it, but it means office 2010, and visual studio 2010 (and applications written using it), all may be problematic for awhile. you should send your report to the [email protected] email though. sorry I don't have anything more helpful to add. Chip ------------------------------------------------------------------------------ From: Davy Kager [mailto:[email protected]] Sent: Saturday, October 16, 2010 10:37 AM To: GW-Info Subject: Office 2010 custom setup Hello! Yesterday I tried to install Microsoft Office 2010 Professional Plus, and found out that the custom setup window isn't read correctly by Window-Eyes. Doing a Google search on this topic brought up an NVDA bug report that described a similar problem, and a message from the beginning of this year that was sent to this list that talked about this issue in the beta-version of Office 2010. Is this a known problem in the final version too, and if so, is there a solution? Just to be clear, I mean the screen that appears when you click the Customize-button when installing Office. It usually appears after accepting the license agreement. That screen is divided into different tabs. Window-Eyes recognizes these tab controls, but it doesn't speak the tab's title (although you can get to that information using a braille display or the mouse hotkeys). Window-Eyes also displays the contents of the treeview where you can choose which components to install, but it looks completely garbled, and you don't seem to be able to interact with the treeview elements or get their status. I use Window-Eyes on Windows 7, but I also went back to Windows XP and gave SuperNova a try. It kept putting the focus back on one particular control, and it saw at least three different windows at once. JAWS did considerably better, in fact the setup was sort of usable, although JAWS also blended individual lines into one garbled phrase. Any help or information will be appreciated! Thanks, Davy If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
