Hi Rick,
In order to determine if the issue is related to Window-Eyes or the program's design, you will need to do some additional investigation. The technical approach would be to use one or more developer tools to analyze the application and try to verify if the program is exposing the information needed for Window-Eyes to do its job. I used the WEEvent app to determine what events are fired by Notepad and Microsoft Word when text is selected. In both applications, there is a Window object event called OnChildSelect that is fired by Notepad and Word when text is selected. This leads me to believe that Window-Eyes uses this event to identify when it should go in and figure out what text is selected and speak the selected text. If this event is not fired, then Window-Eyes might not know it is supposed to be looking for and announcing selected text. Please keep in mind that these are just educated guesses about how Window-Eyes works under the hood. So, you could try this investigative procedure with the XML Copy program and see if it fires the OnChildSelect event when you select text. If the program doesn't fire this event, you would have more evidence that the problem lies in the application's design. A much simpler approach would be to test the application with another screen reader. If you can duplicate the problem with another screen reader, then it is more likely that the problem is related to the program's design and not specific to Window-Eyes. If the problem is related to the application's design, I would recommend you reach out and notify the manufacturer. If they aren't willing or able to fix the problem on their end, it might be possible to develop a Window-Eyes app to enhance the accessibility of the application. I hope you find this information helpful. Regards, Marc Solomon Sales & Accessibility Engineer Ai Squared - GW Micro is now part of the Ai Squared family! 725 Airport North Office Park Fort Wayne, IN 46825 Phone: 802 362-3612 Email: [email protected]<mailto:[email protected]> Web: www.aisquared.com<http://www.aisquared.com> From: Rick Blair <[email protected]<mailto:[email protected]>> Date: Tue, 6 Jan 2015 07:09:44 -0500 Hello Rod: I understand that a new method using F8 has been implemented. I was under the impression that this was specific to browsers. The old method of copying using the shift and arrow keys works just fine in programs like Word, Notepad, etc. In fact, when I hit F8 in the XML Copy program, it brings up a dialog for that program rather than starting a copy operation. The problem that I am describing is not that the method for selecting text using shift and arrow keys does not work. It does. What I am complaining about is the fact that the text, as it is being selected, is not spoken. When slecting text in Word, Notepad, etc. using the shift and arrow keys, text is spoken as it is slected or unselected, along with the word selected or unselected. With XML Copy, there is only silence. The text is actually being selected (and with my limited vision, I see it highlighted) and then control C works to select it. The question is: Is this a problem with WE or is this just a poor or non-standard implementation within the XML Copy program? Rick 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.
