Hi Rick, I don't believe there's any specific app involved here, as the functionality you describe is part of the basic Window-Eyes.
I did write a word related app named Word Advanced Features, and AI has written one named Word Navigation; so I guess the best thing to try is to disable these if you have installed them, to see if the problem is fixed. If disabling Word Advanced Features fixes the issue, then let me know; otherwise, I think (assuming you aren't using the free version of Window-Eyes), however your test turns out, or if you don't have these installed, I'd let AI support know about the problem by emailing them the document to their support email. I've never seen this happen, and have no ideas as to what could be wrong. Sorry I can't be of more help. Chip Chip Orange Florida Public Service Commission Computer Systems Analyst 850-413-6314 -----Original Message----- From: Talk [mailto:[email protected]] On Behalf Of Rick Blair via Talk Sent: Friday, September 25, 2015 11:25 AM To: 'Window-Eyes Discussion List' Subject: Microsof Word Problem I have a Microsoft Word document that I created that contains 21 pages, 5600 words, 47 comments, numerous perceived misspellings (since it contains XML code samples), some tracked changes and a couple of graphics. If I open this document by itself, I have no problem navigating and having WE read the document. I should mention that some of the comments are quite extensive, often several paragraphs long. I can use the Insert-Tab keyboard shortcut to view the various components of the word document. I am not sure what app provides this functionality, but it works as long as this is the only Word document open. If I open a second Word document, the Insert-Tab shortcut no longer works on the aforementioned document and scrolling through the document produces no speech. This is not the case for the second opened word document, which works just fine. If I open two small word documents on my PC, WE behaves as expected. I can switch between the documents and WE reads the text and the Inset-Tab shortcut works. The problem seems to be related to the document that I created. I cannot isolate the aspect of that document that causes this misbehavior. This happens on my work PC running office 2010, Windows 7 Pro, 12 G RAM as well as my home PC, Office 2013, Win 7 Pro, 18 G Ram. I have the latest version of WE (9.2 for office) with all updates and correct set files. I also have Zoom Text, Version 10.0 running on both PCs. Zoom Text can read the document when WE does not. Rick _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/corange%40psc.state.fl.us. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
