That's really good of you to do that, and I think you are doing a good job of explaining things so most people will understand. Keep it up. Kevin Huber
On 6/22/11, Cory Martin <[email protected]> wrote: > Oh of course, I don't expect them to comment or explain anything > about this. I'm sure they'll find a way to make it work just as they > always have. But I also know how people tend to get carried away with > things especially if they don't understand something. I just want to > help explain the issue to people in hopefully a way that makes sense, so > that people don't get all crazy and get the wrong idea. Microsoft > already has the necessary tools in place to make it work as I > understand, so they just have to adapt a few things. Window Eyes > already relies on API a lot and probably more than Jaws does, this is > especially true for things like IE9 or Office, as earlier messages from > today indicate, since IE9 has no off-screen model for WE to rely on, and > the Office support relies on an API plugin to gather information. This > obviously is better anyway since the data an API returns will be more > reliable than that from a video intercept by nature. Just like hearing > the news story from the source itself rather than through a third > party. So as long as application developers stick to guidelines that > Microsoft puts in place (something they should be doing anyway), then > Window Eyes should be fine. I'm just trying to educate people about > this and as to why it is true. > Cory > > > On 22/06/2011 12:29 PM, Kevin Huber wrote: >> HI Cory: >> I think that information is very revalent to Window-eyes, or, it will >> become relatent very soon, since, from what I read, Windows 8 is not >> very far in the future. However,, ot os sp early in the game that GW >> may not be able to comment because if they are working with Microsoft, >> they could very well be bound by a nondisclosure agreement. >> Kevin Huber >> >> >> On 6/21/11, Cory Martin<[email protected]> wrote: >>> You may not feel that this is appropriate for this list and if >>> GW-Micro does not want me posting this information I certainly will stop >>> however I think people might find it interesting to read this article: >>> http://www.inclusiveplanet.com/en/channelpost/4663704 >>> >>> The part which is most interesting here I have pasted as follows: >>> >>> As mentioned, JAWS and Window-eyes have come to over-use video hooks. >>> This makes >>> them nothing more than a nice dummy screen reader, as they can only read >>> basic and >>> very little information. In fact, JAWS, when restarted a second time, is >>> known to >>> cause a nice memory dump which lasts a total of 8 minutes and 13 >>> seconds. During >>> this time, my computer's processor overheats, so I do not advise running >>> windows >>> 8 and JAWS much. GWMicro has a better fait, as Window-eyes runs fine and >>> is very >>> responsive. It can provide much more detail about screens than could >>> JAWS, and overall >>> I would rank it as the 3rd best screen reader, NVDA and System Access >>> still being >>> the first 2. >>> >>> Ok, back to my commentary. As noted the only things NVDA and System >>> Access have going for them here are their simplicity and their lack of >>> need for a mirror driver which Window Eyes presently uses. However >>> those of you concerned should take comfort in the fact that given >>> GW-Micro's current initiative to support the latest accessibility >>> standards Microsoft is introducing, I'm confident that in a year's time >>> the problem of mirror drivers will be overcome. >>> >>> This article, while dated and rather byassed given its author, outlines >>> the problems with the current approach of using DCM or a Mirror driver >>> for those who don't understand how this works. It gives you an idea of >>> how the information is gathered on the screen behind the scenes. >>> >>> http://www.serotek.com/mirror-driver-paper.html >>> >>> Given that Window Eyes already supports these new standards, with some >>> changes I'm sure it will fit right in with the new windows despite what >>> Microsoft is doing to the interface. >>> Cory >>> 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. >>> >>> >> 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. >> > 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. > > 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.
