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

Re: TTS from web content?

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Thu, 19 Aug 2010 12:07:25 -0500
To: David Bolter <david.bolter@gmail.com>
Cc: wai-xtech@w3.org, wai-xtech-request@w3.org
Message-ID: <OFF931B659.5D940740-ON86257784.005DDA0A-86257784.005E1066@us.ibm.com>

I agree. We should have a JavaScript API for doing TTS. This would aid in
cloud-based AT. In fact, as part of the National Public Inclusive
Infrastructure effort we were discussing forming an adaptive services
working group of which one of its deliverables would be a JavaScript TTS
API.

Rich

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	David Bolter <david.bolter@gmail.com>
To:	wai-xtech@w3.org
Date:	08/19/2010 10:23 AM
Subject:	TTS from web content?
Sent by:	wai-xtech-request@w3.org



  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 are:

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 right.

Are we ready? Please speak up.

cheers,
David






graycol.gif
(image/gif attachment: graycol.gif)

Received on Thursday, 19 August 2010 17:56:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:09 GMT