Home Page Reader is definitely not any golden solution to web
accessibility.  I use the product daily and like it.  But it, just as any
other product, can't cope with inaccessible web design or the use of
technologies that simply don't work with accessibility aids.  And those
limitations alone increasingly exclude much of the web.  Just try and use a
screen reader with the Webpac library card catalog as just one example.

PW Webspeak is a dead product.  The company has discontinued development.

At 08:11 PM 2/8/01 -0500, you wrote:
>As Bruce mentioned Home Page Reader, I would like to say that the company
>I work for tests these types of products.  We are in the early days of
>looking at Home Page Reader, but the indications I'm hearing from
>colleagues is that this will truly be the answer to this dilemma.  I am
>really excited about that, because I teach students without vision to use
>screenreaders and the internet.  Therefore, just like many, I'm always
>looking for some relief.
>
>Karyl
>----- Original Message -----
>From: <mailto:[log in to unmask]>Bruce Coonce
>To: <mailto:[log in to unmask]>[log in to unmask]
>Sent: Thursday, February 08, 2001 2:07 PM
>Subject: re Graphic browsers v. Textual
>
>I use JAWS 3.7 at work, and use Internet Explorer 5.5. With the latest
>JAWS version, it works fairly well.
>
>When I first started browsing the Internet, in the days of DOS, I used
>Lynx. It worked great then. Most of the sites I went to wer text-based then.
>
>When I changed to Windows (very reluctantly, I might add) I started using
>JAWS with Internet Explorer.
>
>At home, I use both Netscape 4.61 and Internet Explorer 5.0. Netscape
>works fairly well on some sites, although it is not as accessible
>generally as Internet Explorer.
>
>I've used Lynx with JAWS also, but it doesn't work as well as it did in
>DOS. You either have to use the JAWS (review) cursor or set screen echo to all.
>
>Still, it works well on some sites and I still use it occasionally.
>
>I've played with PW Webspeak, which is a self-voicing text browser, a
>little bit. It seemed to work well. I have not tried Home Page Reader.
>
>
>
>-----Original Message-----
>
>From: * EASI: Equal Access to Software & Information
>
>[mailto:[log in to unmask]]On Behalf Of Sherman, Sarah
>
>Sent: Wednesday, February 07, 2001 3:00 PM
>
>To: [log in to unmask]
>
>Subject: Graphics-based browsers vs. text-based browsers with screen
>
>reade r
>
>
>
>My colleague Axel Schmetzke and I are pondering screen reader users'
>
>preference of browsers. Could you please share, in your experience (personal
>
>or otherwise), do you find more people using a screen reader with text-only
>
>browsers, or graphics-based browsers? If you use a screen reader, what is
>
>your preference? If you train others, do you train with the screen reader in
>
>conjunction with a text browser, or a graphics browser?
>
>We have found that often, it is much easier to navigate the WWW with a
>
>screen reader when a text-only browser like Lynx is used. You don't have to
>
>worry about structure as much, and anything that Lynx couldn't interpret,
>
>chances are JAWS (or another screen reader) wouldn't be able to interpret it
>
>anyway. On the other hand, graphics-based browsers such as Netscape and IE
>
>have structural designs that are harder to navigate with the screen reader
>
>(though if the site is generated with accessibility in mind, it can be
>
>done).
>
>My apologies for cross-posting. Thank you very much for any experiences you
>
>can share!
>
>Sarah Sherman
>
>Program Coordinator
>
>Assistive Technology Program
>
>UW-Stevens Point
>
>715-346-4980