Re: Not reading the text on screen.
Re: Not reading the text on screen.
- Subject: Re: Not reading the text on screen.
- From: Benjamin Hawkes-Lewis <email@hidden>
- Date: Wed, 09 May 2007 00:04:14 +0100
David Niemeijer wrote:
> To me your case shows that there should be a way for applications to
> provide pronunciation hints for their own interface so that you could
> stick to the ISBN label, yet provide a pronunciation dictionary or so
> with your app that VoiceOver or other assistive apps could use (or not
> use). What do you think?
A possible language for doing this:
http://www.w3.org/TR/pronunciation-lexicon/
Uli Kusterer wrote:
Or not. I've heard from a linguist that many people who need things
like VoiceOver have their voice settings set up to very weird settings.
E.g. very fast and such. They hear that voice so often that they can
understand it very well, and are aware of its pronunciation quirks. So
your fixing up "ISBN" may be very confusing, and may not actually be a
problem to your users because they know the voice.
That sounds debatable. Just because advanced users gradually become
aware of the pronunciation failings of a version of their screen reader
does not mean that they lose the ability to understand the same words
correctly pronounced. Reading speed, selective pronunciation, and voice
settings are quite a different matter from broken pronunciation.
--
Benjamin Hawkes-Lewis
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden