I have to say that because it is wrapped up in so much proprietary software, I have not been able to try this, but it has the potential to be useful from an accessibility point of view. If you try it, please leave a comment and let me know how it works. In the meantime, I'll stick with Odiogo, for all it's faults.
Update: I received an email from the Odiogo support team. Impressive, it's good to know they are listening. "If there are areas we can improve our system, please don’t hesitate to let us know." My response to this was:
The main difficulties I have with Odiogo are:
- The American accent of the voice, which is great for a North American audience, but tends to be off-putting for European listeners. The solution to this could be to allow subscribers a choice of synthesized voices.
- Occasional difficulties with mispronunciation of technical words. It's hard to see how to get around this one, but since this blog is technical in nature, the specialized jargon is important to the audience, and mispronunciation in technical spheres quickly destroys confidence the content. Hopefully this issue will improve as the sophistication and technical vocabulary of the voices increases.