On 7/07/2011 9:44 AM, Silvia Pfeiffer wrote: > I've not seen any cloud-based solutions for text descriptions. > While such an approach is possible, it relies on special services > offered by providers and is therefore not something that a Web browser > can rely on for having their content rendered. It also smells of non-standard to me, as well as requiring reliance on external services.
> I do indeed believe that screen reader handling of text descriptions is > the best way forward. I agree for the most part, though I'm still not so keen on the pause while description is catching up behaviour. Part of this is design/implementation concerns; I'm very concerned about this tight interaction between the screen reader and the system. Generally, a screen reader is fairly passive in terms of its affect on the application without user action. Also, it could sometimes be extremely disruptive for the user. > For non-deaf/blind users are there significant advantages of Braille > over TTS such that TTS would not be a viable solution for providing > text descriptions to a Braille user? It could actually be useful if the user doesn't want the disruption to the audio that audio/TTS description causes. Braille could be a nice way of silently accessing the descriptions. However, as I noted before, I think a scrolling transcript is the best way to do this. The user can always disable scrolling if they wish or scroll back to read something they missed. Jamie -- James Teh Vice President, Developer NV Access Inc, ABN 61773362390 Email: ja...@nvaccess.org Web site: http://www.nvaccess.org/ _______________________________________________ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
