W3C home > Mailing lists > Public > wai-xtech@w3.org > August 2010

RE: TTS from web content?

From: Cain, Sally <sally.cain@rnib.org.uk>
Date: Tue, 24 Aug 2010 09:27:37 +0100
Message-ID: <F97D739047BF10458C2A6E71D8E5100B0356C5AF@brmmsx02.ads.rnib.org.uk>
To: "Sina Bahram" <sbahram@nc.rr.com>, "David Bolter" <david.bolter@gmail.com>, <wai-xtech@w3.org>
When we are looking at solutions, we also need to remember that not
everyone has the same level of technical ability.
-----Original Message-----
From: Sina Bahram [mailto:sbahram@nc.rr.com] 
Sent: 24 August 2010 09:16
To: Cain, Sally; 'David Bolter'; wai-xtech@w3.org
Subject: RE: TTS from web content?

With something like WebAnywhere, or to a lesser degree, at least less
completely free, SAToGo, this is not the case. I've started
these services tens of times on various machines ranging from netbooks
to laptops to desktops to servers, and have done so without
sighted assistance.

Take care,

-----Original Message-----
From: Cain, Sally [mailto:sally.cain@rnib.org.uk] 
Sent: Tuesday, August 24, 2010 4:11 AM
To: Sina Bahram; David Bolter; wai-xtech@w3.org
Subject: RE: TTS from web content?

Hi Sina,

I totally agree there are lots of people who can't afford an expensive
screen reader but in order to get to the internet they need
to use some sort of screen reader to start the PC and navigate around to
open the web browser. This will always be an issue for
access to the internet in a traditional way.


-----Original Message-----
From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of Sina Bahram
Sent: 23 August 2010 15:50
To: Cain, Sally; 'David Bolter'; wai-xtech@w3.org
Subject: RE: TTS from web content?

The first thing that comes to mind is that there are millions of
individuals who can't afford a screenreader in the Windows world,
and whose needs are not served by the state of accessibility offered to
them by, let's say Orca, in the open source free world.
There's therefore a need to facilitate those individuals' access to
information and the web as a whole. Web anywhere might actually
have some numbers on this in one of their papers?

Take care,

-----Original Message-----
From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of Cain, Sally
Sent: Monday, August 23, 2010 5:15 AM
To: David Bolter; wai-xtech@w3.org
Subject: RE: TTS from web content?

Hi all,

Everyone has been discussing the technical issues here which of course
are really important. However I think it is also important
that we consider the practical issues too. Just to play devil's
where would this sit in the market? Who would use it? Is the amount of
work that is required worth it for the amount of people who
would use it?

The answer to all of my questions may be that it would be used loads and
yes it is well worth it. However from the perspective of
blind and partially sighted people if you are using a screen reader, you
will probably continue to use your screen reader rather
than change to using the speech within the page. So I think it is
important to think about the other people who might want to use
it. Possibly one example would be those with dyslexia or other learning
difficulties. If they are struggling with a page then speech
would help them with the content.

However I do support the two main concerns that David has around quality
and clashing with screen readers.


-----Original Message-----
From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of David Bolter
Sent: 19 August 2010 16:22
To: wai-xtech@w3.org
Subject: TTS from web content?

  Hi all,

What do you think about having browsers provide built-in text-to-speech
capability to web content? While I imagine a declarative
approach might be quite interesting I think we can go farther faster
with a JavaScript API approach. The main two concerns I have

1. We don't want to encourage unpolished aural interfaces.
2. We don't want to conflict with traditional screen readers.

The biggest potential I see is:

1. Innovation in Aural interfaces. The same kind of innovation we see
happening in visual DHTML interfaces.
2. TTS solutions in places, and on devices where traditional screen
readers are problematic. For example, perhaps on some mobile
devices that are currently not accessible.
3. The TTS can be done in the browser, on the native platform (e.g. 
Voice Over on OSX), or 'in the cloud'. We just need to get the API

Are we ready? Please speak up.


 To report this e-mail as Spam, please forward it to:


NOTICE: The information contained in this email and any attachments is
confidential and may be privileged.  If you are not the
intended recipient you should not use, disclose, distribute or copy any
of the content of it or of any attachment; you are requested
to notify the sender immediately of your receipt of the email and then
to delete it and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.
However, it cannot accept any responsibility for any  such which are
We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk

This message has been scanned for viruses by Websense Hosted Security -
Received on Tuesday, 24 August 2010 08:29:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:25:29 UTC