WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: RE: Assistive Device Behaviour Chart

for

Number of posts in this thread: 2 (In chronological order)

From: Terence de Giere
Date: Fri, Aug 29 2003 7:41AM
Subject: RE: Assistive Device Behaviour Chart
No previous message | Next message →

Mary Martinson wrote:

I think your chart will be helpful to a lot of people. I have one
question. I thought that pwWebSpeak has not been supported for a couple
of years. Is this something that people can still get their hands on?

Mary,

pwWebSpeak stopped development in late 2000, so I suppose it should be
regulated to the category of legacy technology. It was a very good audio
browser, although it couldn't compete with screen readers as they
improved. In many respects it can still handle many structures in a web
page better than a screen reader. It is a good testing tool, and can
illustrate problems with pages relating to tables, images, and
scripting in a way that is different from screen readers, and give an
idea of why the W3C Level Triple-A accessibility compliance is sometimes
necessary.

It had stellar support for LONGDESC, would read the title on ACRONYM and
ABBR, and would renumber nested ordered lists in a coherent way. It did
not support CSS or scripting, but had an internal user configurable
style sheet system. At one point it was built into a rather large cell
phone. Compared to screen readers, and the version of IBM HPR available
at that time, it was easier to use. There is no longer any technical
support for the product. If the company had had the resources to add
scripting, and CSS and a couple of other things which they were
planning, it would have become a superb audio browser, and probably
would outperform today's screen readers on web pages by a significant
margin.

pwWebSpeak was in the price range of IBM Home Page Reader, about US$150,
although web developers could get it for US$75 or so.

The following links might lead to more information if you try to email
the company; the Chief Technology Officer was Mark Hakkinen.

http://www.issound.com/pwwebspeak/index.htm
http://www.issound.com/contact/index.htm

Terence de Giere
= EMAIL ADDRESS REMOVED =




----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/


From: Mary Martinson
Date: Wed, Sep 03 2003 12:15PM
Subject: RE: Assistive Device Behaviour Chart
← Previous message | No next message

Terrence, thanks for the information. I emailed pwWebSpeak after receiving
your message, but have not heard back from them. I wanted to know if people
could still download the product, even though it is not supported. I will
let you know, just FYI.
Mary

-----Original Message-----
From: Terence de Giere [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Friday, August 29, 2003 8:37 AM
To: = EMAIL ADDRESS REMOVED =
Subject: RE: Assistive Device Behaviour Chart


Mary Martinson wrote:

I think your chart will be helpful to a lot of people. I have one
question. I thought that pwWebSpeak has not been supported for a couple
of years. Is this something that people can still get their hands on?

Mary,

pwWebSpeak stopped development in late 2000, so I suppose it should be
regulated to the category of legacy technology. It was a very good audio
browser, although it couldn't compete with screen readers as they
improved. In many respects it can still handle many structures in a web
page better than a screen reader. It is a good testing tool, and can
illustrate problems with pages relating to tables, images, and
scripting in a way that is different from screen readers, and give an
idea of why the W3C Level Triple-A accessibility compliance is sometimes
necessary.

It had stellar support for LONGDESC, would read the title on ACRONYM and
ABBR, and would renumber nested ordered lists in a coherent way. It did
not support CSS or scripting, but had an internal user configurable
style sheet system. At one point it was built into a rather large cell
phone. Compared to screen readers, and the version of IBM HPR available
at that time, it was easier to use. There is no longer any technical
support for the product. If the company had had the resources to add
scripting, and CSS and a couple of other things which they were
planning, it would have become a superb audio browser, and probably
would outperform today's screen readers on web pages by a significant
margin.

pwWebSpeak was in the price range of IBM Home Page Reader, about US$150,
although web developers could get it for US$75 or so.

The following links might lead to more information if you try to email
the company; the Chief Technology Officer was Mark Hakkinen.

http://www.issound.com/pwwebspeak/index.htm
http://www.issound.com/contact/index.htm

Terence de Giere
= EMAIL ADDRESS REMOVED =




----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/



----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/