Raised by: Bjorn in mail.
Raised by: Dominic in mail.
Discussion: Bjorn: I can't see any easy way to do programmatic TTS. The TTS element is at least missing the attributes @text and @lang. Without those, it's pretty hard to do the very simple use case of generating a string and speaking it. It's possible, but you need to build a whole SSML document. For use cases, see the samples I sent earlier today.
Dominic: For TTS, I don't understand where the content to be spoken is supposed to go if it's not specified in the inner HTML. Are the only options to use <tts>Hello, world</tts> which inserts undesired text in older browsers, or <tts src="text.ssml"/>, which forces me to put the text in a separate document or use a cumbersome data url? The previous draft from a year ago that I had looked at previously had a value attribute, so I could write <tts value="Hello, world"/> - why was that deprecated?
Michael: We earlier wanted to stick with HTMLMediaElement, which meant we needed a src to be defined. We claimed (perhaps wrongly) that you could always use a data: uri (especially since text/plain was a required supported type). Perhapse we should add not a text property, but a text method that sticks a data:text/plain; on the front (possibly base64 encoding it if we have character concerns) and then assigns it to the src?
Resolution: Add an attribute, text, which is setable and automatically fills in the src attribute. Note we should also explain how the source works. Add a comment that lang from the TTS should be passed to synthesizer.
Dan: Michael to do this.