When it comes to the future, both JFW and Window-eyes (as well as any 
other third-party screen readers out there) had better be looking over 
their shoulder.  Microsoft is reported to be working on its own screen 
readers for Windows products.  If and when they succeed, the scheisse 
will hit the fan!

>From: David Poehlman <[EMAIL PROTECTED]>
>To: jaws for windows mailing list <[EMAIL PROTECTED]>
>Subject: [Fwd: Fwd: A comparative review of Windoweyes and JFW's 
>Date: Sat, 20 Mar 1999 06:50:30 -0500
>Play nice Please I do not necessarily disagree with this hasty
>conclusion but it has implications for the future.
>-------- Original Message --------
>Subject: Fwd: A comparative review of Windowless and JFW's
>Date: Sat, 20 Mar 1999 20:39:10 +1100
>From: [EMAIL PROTECTED] (pattist)
>From: Jonathan Mosen <[EMAIL PROTECTED]>
>With the recent release of Internet Explorer 5.0, there has naturally
>discussion about screen readers for Windows and Internet access. A
>number of
>generalist statements have been made, resulting in some list members
>for substantiation of those statements. For what it is worth, here is
>view, complete with feature examples, on why Windoweyes provides
>access to the Internet than JFW. This comparison looks at IE 5.0 using
>beta scripts on the JFW Mailing List home page. These scripts are
>essentially slightly modified versions of the IE 4 scripts,
>compensating for
>the fact that the IE 4 scripts mistakenly think that IE 5 is IE 3. So
>functionality when using JFW with the IE 5 scripts mirrors that of IE
>access with JFW. Apart from a huge speed improvement when using IE 5,
>to the Net with Internet Explorer, Windoweyes offers the same feature
>under IE 4 and IE 5. On this basis then, I believe the feature
>comparison is
>I should also add that Window Bridge and Winvision, having made
>use of Active Accessibility, offer similar functionality to
>Windoweyes. In
>some areas there are differences though, and while I have used
>versions of these two products, I don't feel proficient enough with
>packages to make comment.
>The heart of the superiority of Windoweyes over JFW for Internet
>access is
>the fact that the entire HTML document, or web page, is loaded by
>into a buffer, which it calls the MSAA buffer. This allows the user to
>a web page as if it were a document in Notepad or Word. This means,
>example, that the continuous read feature reads a web page from top to
>bottom in Windoweyes.
>This web page loading process eliminates the need for any reformatting
>to be
>done on a web page, as is necessary with pages with a complex visual
>in JFW.
>Windoweyes has a feature which immediately alerts you to the fact that
>page has frames when it appears on the screen, thus reminding you that
>can use control+tab to move quickly between frames. A status hot key
>specific to the MSAA buffer will tell you the line of the page you're
>which frame you are in, and how many frames there are on the page.
>Both Windoweyes and JFW have the excellent feature allowing you to
>bring up
>a listview containing all the links on a page. However, Windoweyes
>two choices within this list view. One choice executes the link, in
>words it takes you to the page pointed to. The other option puts the
>cursor on the link, allowing you to move your cursor around the
>current page
>to get an idea of the context of the current link. This is a great
>for all those obscure links that say things like "click here".
>Searching an entire web page is significantly better with Windoweyes.
>Instead of using the standard Internet Explorer search, one instead
>uses the
>Windoweyes search. In most circumstances, this searches only the
>screen, but
>when the MSAA buffer is turned on, you can search the entire buffer.
>means that you can search for text on the entire web page, and have
>the MSAA
>cursor placed right at the result for you to continuously read from
>there or
>for you to explore the context further.
>Filling in forms is about even in my view. It is annoying and
>confusing to novice computer users that one has to turn MSAA mode off
>Windoweyes when filling in a form, then turn it back on again when
>submitted the form. I hope this will be remedied in a version of
>in the not too distant future.
>Finally, and I've saved the best for last, there is no comparison
>the ease with which the screen readers get you past those annoying
>margins. By this, I refer to the list of common links you so often
>taking up at least a screen full at the top of each web page. With one
>simple key press, Windoweyes will instantly take your cursor past that
>material and straight onto the stuff you want to read. It literally
>you hours over a few days of surfing, and makes the web a much more
>experience. This feature works well about 90 percent of the time, with
>occasional requirement for several presses of this key combination to
>you past several contents margins.
>In conclusion, I think the gamble GW Micro took in relying on Active
>Accessibility to provide Internet access is starting to pay off. They
>tolerated many angry customers saying, "JFW supports IE 4, why don't
>There is no doubt in my mind that a blind person will be more
>productive and
>efficient with Windoweyes than they will with JFW when surfing the
>JFW will have to at least match these features in 3.3 in order to be a
>contender as a screen reader for serious surfers.
>Regards Steve,
>Visit the jfw ml web page: http://jfw.cjb.net

Get Your Private, Free Email at http://www.hotmail.com
Visit the jfw ml web page: http://jfw.cjb.net

Reply via email to