To view parent comment, click here.
To read all comments associated with this story, please click here.
Text-to-speech isn't the only thing that's broken. They implemented some very basic accessibility API support on the Mac, but it's been extremely buggy ever since they've implemented it in the 9.5 betas and they've ignored all bug reports concerning it. To summarize, the DOM tree's accessible elements are presented in the wrong order, e.g. while reading Osnews, the comment titles all appear at the bottom of the DOM rather than with their associated comments. This makes screen reader support useless, as the page is so garbled anyway that it's difficult to comprehend. Further, most form controls don't work properly, the required output for lists is not spoken for example. It's not useable, I don't know why they even bothered to be honest. On Windows no such efforts have been made, and accessibility for the Linux version at least in terms of screen reader support is out of the question for the forseeable future as it uses QT for its interface. Guess all that time spent in complaining to the EU took away from the ever more important task of actually fixing the bugs in their own product.




Member since:
2005-11-13
In terms of accessibility, they broke the text-to-speech function in v9.5 and haven't fixed it yet (unless they did in the newest beta, which I highly doubt). Not only that, but they have ignored any threads created about it on their forums.
Anyway, I figured out how to get that working through other applications, so have happily switched back to Firefox:
http://my.opera.com/community/forums/topic.dml?id=285583
Opera is a TERRIBLE browser. It was this one feature that kept me using it, and I had to hack it just to get that one thing working right. I lament that I have to keep it installed to take advantage of the voice capability, but at least I don't have to use it anymore. Even if they did fix this, I don't think I'd ever go back.