- From: Satish Sampath <satish@google.com>
- Date: Fri, 8 Oct 2010 10:24:02 +0100
- To: Andy Mauro <Andy.Mauro@nuance.com>
- Cc: Michael Bodell <mbodell@microsoft.com>, "public-xg-htmlspeech@w3.org" <public-xg-htmlspeech@w3.org>
> That said, I’m not sure I agree with having the recognizer/speech-synthesis > be a browser setting. A browser setting is a user control, and users aren’t > going to care about the recognizer/speech-sythesis they use, they’re just > going to expect speech features to work. However, certain types of > developers are going to care about the recognizer/speech-synthesis they use, > and as such it makes sense for this to be an (optional) facet of the > markup/language. I think users will care about speech recognition the same way they care about having a good input device/keyboard, installing the right voice recognition software or selecting the right operating system based on their needs. And users need consistency in terms of recognition for every website, it would be weird to have one website understand my voice perfectly fine and another to have problems with the same text. -- Cheers Satish
Received on Friday, 8 October 2010 09:24:33 UTC