|Method for making screen readers shut up?|
| 7:46 pm on Feb 23, 2010 (gmt 0)|
For those that are totally blind and rely on screenreaders, what
happens when the site serves up audio that plays automatically, and
how can I make CSS that will not be read by screen readers?
For example, if I display some text on screen in large print, I also
want a sound file reading that text, rather than having an automated
screen reader do it. I thought the media=screen css value would do it,
but my demo of Jaws 11 quite happily carries on reading over the top
of the audio.
For example, does Homer, WebbIE, Webanywhere or whatever,
pause before reading? I am trying to avoid "sound collisions".
There's a demo I could show you, but links aren't allowed, so I can't, so I hope this is enough info. Thanks.
| 8:03 pm on Feb 23, 2010 (gmt 0)|
I don't think there's a way to override people's AT.
Perhaps don't autoplay? It's not just about AT users, some users will be listening to music, some will be in a quiet office, some just get annoyed as hell by autoplaying... you can't prevent sound collisions unless you give the user full control.
|...we discourage the practice of automatically starting sounds ... and encourage that the sound be started by an action initiated by the user after they reach the page, rather than requiring that the sound be stopped by an action of the user after they land on the page. |
| 3:24 pm on Apr 5, 2010 (gmt 0)|
Thank you. I've done what you suggested - on the entry screen, the user chooses between audio guide, or text with optional audio. This stays for the session, or the user can bookmark the next page and their prefs are stored in the bookmark.
I'd show you what I'd done, but WebmasterWorld doesn't allow me to do that.
Thanks for the suggestion and link.