Hi Edward, speaking of Word support, I just released the version of the MS Word script which fixes the bug where WE mis-reports the font size as you change it via a command key.
Are there any other Word issues which still need attention? Speaking of this, I can't emphasize how important it is to have the ability to address these types of issues in your screen reader. I also can't get across how difficult I found it, when I tried to do anything like this in the jaws scripting environment, and how relatively easy it is in WE, and how much support I receive from WE (both their support people and their developers) for each and every one of my scripting projects. Perhaps I found jaws so difficult simply because I had no such support, at all, from the FS folks. I want to write scripts for myself of course, which I personally find interesting, but I write them for projects such as Word in part, to help GW and help return something for all that free support I've received from them as I've learned scripting. Jay McCarty's script which gives java support to WE is the ultimate example of what's possible here in having scripts dramatically increase accessibility. It's not that FS couldn't do something similar, but I think few jaws users could. Chip -----Original Message----- From: Edward Marquette [mailto:[email protected]] Sent: Sunday, July 05, 2009 7:43 PM To: [email protected] Subject: WE Vrs. JFW Everyone is probably tired of this by now, but the comment about technical support at WE was nothing short of astounding. When was the last time anyone saw an FS employee on a listserv helping users? I never, ever, ever saw that. Yet, GW Micro employees, like Aaron Smith, are often on this listserv (and often on weekends and holidays). I've been through just about all the screen readers. I started with PC Speak. Most of the listers never even heard of that one. Then, there was the PC Talking program. Then, there was Vocal-Eyes, and next Window Bridge. I was a faithful Window-Eyes user until 2004, when I had to have support for colors, track changes, and many of the editing features in MS Word that WE didn't support. I bought JFW, and used it happily until a year ago. I switched, not necessarily because I wanted to, but because the tech support people at my firm (more than 800 lawyers) asked me if there were not some alternative to JFW. It all centered around remote access through Citrix. It wasn't that the FS people didn't try; however, afer escalation after escalation, the dopy protection scheme just failed, right in the middle of a remote access session -- proclaiming that my version wasn't properly authorized. Our tech support people are very good. One worked at Citrix. So, after verifying that WE had the support for MS Word that I needed, I switched back a year ago, and WOW. The remote access is incredible. Even our tech support people are amazed at how responsive WE is. I'm not saying it was a walk in the park to get it working, but compared to he headaches we had with JFW, it was a walk in the park. That's my story. 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. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message. 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. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [email protected] and include leave gw-info in the body of the message.
