Hi. My name is Teri Brown. I am the the Adaptive Technology
Coordinator at
University of Georgia. We currently support WinEyes and JAWS in our
Adaptive
Technology Resource Center. I have yet to discover a student who
prefers WinEyes
over JAWS. We have had many students enter our department that have
never used
either one. We expose both of them to the student to let them decide
which one
they feel more comfortable with and the decision so far has always been
JAWS.
Kevin Doucet wrote:
> Hi,
>
> Don't be fooled in to thinking hj and JAWS for windows is the only
> option. WinEyes from GWmicro is as good if not better and you don't
> have to use only soft-ware synthesizers etc. purchased from GWmicro to
> work with this reader as you do with HJ products.
>
> HJ likes to lock it's users in to a situation whare they can only use what
> HJ sells for addaptive soft-ware.
>
> On Mon, 7 Jun 1999, Chris
> Hofstader wrote:
>
> > Hi,
> >
> > I would have to say that the best screen reader for the www is, of course,
> > JAWS for Windows. Some folks, who prefer fully textual interfaces, might
> > suggest Lynx or another DOS like browser. JFW, however, gives full access
> > to IE 4.01 and IE 5. our next release, 3.31, due out later this summer,
> > will offer the most comprehensive support for the internet to blind users
> > ever.
> >
> > The text based browsers are nice for reading and following links. JFW gives
> > you all of this plus much more. In fact, with a single keystroke, the JFW
> > user can "flatten" out a page in IE and read it the same way as one would
> > with a text browser. JFW also provides very easy use of forms, frames,
> > tables, combo boxes, radio buttons and a whole lot of other controls which
> > are often difficult for text based browsers.
> >
> > JFW 3.31 will also provide full support for the Java Access Bridge from Sun
> > Microsystems. This, in my opinion, is the coolest accessibility API ever
> > built A number of applications have already been built with the Swing
> > classes and will be available to JFW users when the new release ships.
> >
> > We are also working to become the only Windows based screen reader to fully
> > support the entire WAI specification for accessible web pages. This
> > includes all of the nifty items added to describe tables in web pages.
> >
> > Thanks,
> > Chris Hofstader
> > Development Manager
> > Henter-Joyce, Inc.
> > http://www.hj.com
> > [log in to unmask]
> > (727)803-8000 x1061
> >
> > -----Original Message-----
> > From: BLIND-DEV: Development of Adaptive Hardware & Software for the
> > Blind/VI [mailto:[log in to unmask]]On Behalf Of Lila Laux
> > Sent: Monday, June 07, 1999 10:51 AM
> > To: [log in to unmask]
> > Subject: Screen readers for web sites
> >
> >
> > This is a multi-part message in MIME format.
> > --------------182612E474CE96A762CA97DA
> > Content-Type: text/plain; charset=us-ascii
> > Content-Transfer-Encoding: 7bit
> >
> > If you were recommending screen readers for
> > web sites, what would you recommend? Is it
> > better to use a reader that works well with
> > Windows, too, or is it better to have a web
> > reader and a reader for graphical user
> > interfaces such as Windows?
> > Lila Laux
> >
> >
> > Lila Laux, PhD
> > Human Factors Engineering, US WEST IT
> > 1475 Lawrence St., Suite 210, Denver, CO,
> > 80220
> > 303 624 0503
> > --------------182612E474CE96A762CA97DA
> > Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
> > Content-Transfer-Encoding: 7bit
> > Content-Description: Card for [log in to unmask]
> > Content-Disposition: attachment; filename="vcard.vcf"
> >
> > begin: vcard
> > fn: [log in to unmask]
> > n: ;[log in to unmask]
> > email;internet: [log in to unmask]
> > x-mozilla-cpt: ;0
> > x-mozilla-html: FALSE
> > version: 2.1
> > end: vcard
> >
> >
> > --------------182612E474CE96A762CA97DA--
> >
>
> Kevin
> the original cajun
> [log in to unmask]
> http://www.zebra.net/~kdoucet
> Cogito ergo loon. (I think, therefore I'm crazy)
--
Teri Brown
Adaptive Technology Coordinator
Disability Services
University of Georgia
|
