Screen Readers and CAPS
| Quote: |
| For example, no support for aural CSS |
I'm reliably informed that FireVox does
But yes, the majors don't
... and Talklets doesn't yet
Share: 
| Phil Teare wrote: | ||
I'm reliably informed that FireVox does
But yes, the majors don't |
There have been a few user agents that support aural CSS over the years, most notable of which at the moment are Fire Vox and Opera.
Jon Gibbins, dotjay.co.uk, accessibility.co.uk wiki.
Share:
| Phil Teare wrote: |
| Something to remeber is that its not just down to your AT (assistive technology) it could well be decided by your choosen TTS engine. Not everyone plumps for the default voice that comes with the operating system. While they are getting a bit better, they still suck compared to the state of the art engines. If you buy one of those it may well choose to deal with capitals differently. e.g. one I'm using now is very good, and decides what to do based on whether it 'thinks' its a word or an acronym. You can force it to do either pronouce or spellout, and some AT may or may not force such behaviour using TTS engine APIs, and/or have settings to make the 'force consistant' or 'smart' behaviour optional. |
That's a very interesting point. Thanks, Phil. I tend to use the default engines for my testing, but I've listened to samples of the AT&T Natural Voices and they're pretty good.
Jon Gibbins, dotjay.co.uk, accessibility.co.uk wiki.
Share:
I've done a little write up for anyone who's interested in screen readers and abbreviations: Screen readers and abbreviations
Any comments or corrections gratefully received.
Jon Gibbins, dotjay.co.uk, accessibility.co.uk wiki.
Share: