- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 20 Jun 2000 09:45:48 -0400
- To: Jon Gunderson <jongund@uiuc.edu>
- CC: w3c-wai-ua@w3.org
Jon Gunderson wrote: > > Ian, > I don't think we only need to look at speech browsers for implementation > experience, but any technology that uses speech including screen readers > and OCR technologies like Open Book Ruby Edition and Kurzweil 1000/3000. I said "speech technologies".... - Ian > At 10:12 PM 6/19/00 -0400, Ian Jacobs wrote: > >Jon Gunderson wrote: > > > > > > On control over speech rate and other characteristics all of our > > > implementation experience is based not on CSS principles, but on > > > enumeration of the ranges of speech technologies and providing controls > > > that reflect the enumerated values. I think this approach should be the > > > first priority, since we can show that it can be implemented. The > > > secondary consideration if information can not be enumerated. > > > >I agree with Jon that we should find out what we can about > >existing speech technologies and the ranges that are offered > >(as Gregory examined for speech rate [1]). > > > >Gregory, would you take an action to report back ranges of values > >for the various speech characteristic properties (excluding emacspeak, > >which I guess conforms to CSS2's properties in this case, but is > >not a browser)? > > > > - Ian > > > >[1] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0482.html -- Ian Jacobs (jacobs@w3.org) http://www.w3.org/People/Jacobs Tel: +1 831 457-2842 Cell: +1 917 450-8783
Received on Tuesday, 20 June 2000 09:45:53 UTC