[WEB4LIB] Re: Jaws Web Page readers' comments?

[Richard Wiggins]

Forgive the late reply to this, but recently I arranged a demonstration with
Michael Hudson, who heads the Resource Center for Persons with Disabilities
at Michigan State.  Mike is severely visually impaired and has used talker
technology since 1986.  He uses JAWS and finds it the best tool to meet his
needs.

We had about 20 folks who navigate visually observing as Mike navigated a
set of university sites (including some of our own) demonstrating how things
work -- and don't work -- for him as he used JAWS.

It was quite literally eye-opening for all involved.  I strongly suggest to
anyone who is trying to build accessible pages that they do a similar
exercise.  WATCH as someone uses talker technology to navigate.  You can't
appreciate all the subtleties by running Bobby.

Mike runs the talker at 55% of possible speed.  No one in the room could
follow at that rate.  He dialed it down to 35% and the rest of us were then
able to follow.  :-)

/rich



Chris Murphy wrote:

> 
> We use JAWS (Job Assistant for Windows Software) on our Assistive
Technology 
> Workstation (<a
href="http://mail.richardwiggins.com//jump/http://www.thecommunitylibrary.org/reference/atw.html">http://www.thecommunitylibrary.org/reference/atw.html</a>).
> 
> Although JAWS is reasonably useful for reading web pages, I find it
somewhat 
> weak at translating HTML not optimized for accessibility (e.g., tables used
> for 
> layout). I demo'd IBM's Home Page Reader and found it better at presenting 
> information in tables, for example.
> 
> We chose JAWS based on our visits with staff from the Idaho Commission for
> the 
> Blind, many of whom are blind and use JAWS in the workplace. We wanted
> reader 
> software that could be used with word processors and spreadsheets as well
as 
> browsers, and JAWS fit that bill. JAWS has a steep learning curve for
> newbies, 
> but it is probably the most widely used reader.
> 
> JAWS does not get used often on our workstation, and our magnification
tools
> are 
> used more frequently. Most of its use is for demonstration, often to blind
> or 
> visually impaired people who come to check it out before deciding whether
to 
> purchase it for themselves.
> 
> For more information on designing accessible web pages, check out the
WebAIM 
> (Web Accessibility In Mind) site: <a
href="http://mail.richardwiggins.com//jump/http://www.webaim.org">http://www.webaim.org</a>. Their mailing list
> is 
> information rich, although very busy. (I had to unsubscribe because I could
> not 
> keep up with the messages.)
> 
> If you would like more information, let me know.
> 
> Best regards,
> 
> Chris Murphy
> 
> -- 
> Christopher Murphy
> Information Systems Manager
> The Community Library, Ketchum, Idaho
> chrism at thecommunitylibrary.org
> <a
href="http://mail.richardwiggins.com//jump/http://www.thecommunitylibrary.org">http://www.thecommunitylibrary.org</a>
> 
> 
> David Johnson wrote:
> &gt; Hi folks
> &gt; 
> &gt; Can anyone comment upon the operations of Jaws text to speech
conversion 
> &gt; application made for use on web pages?
> &gt; 
> &gt; I am particularly interested in hearing from library staff where this 
> &gt; application is in place on a public workstation, and where patrons
with 
> &gt; visual disabilities actually utilize Jaws.
> &gt; 
> &gt; Any comments upon Kurzwiel, text to speech conversion (model 1000 or
3000) 
> &gt; would be appreciated, although I know the Kurzwiel is not for web
page use 
> &gt; only, and thus is &quot;off topic&quot; for this list.
> &gt; 
> &gt; DCJ
> &gt; 
> &gt; 
> &gt; 
> &gt; 

____________________________________________________
Richard Wiggins
Writing, Speaking, and Consulting on Internet Topics
rich at richardwiggins.com       www.richardwiggins.com