Re: Not reading the text on screen.
Re: Not reading the text on screen.
- Subject: Re: Not reading the text on screen.
- From: David Niemeijer <email@hidden>
- Date: Tue, 8 May 2007 06:47:15 +0200
Greg,
At 11:33 -0600 20/4/07, Greg Kearney wrote:
I have a situation where I do not want VoiceOver to read the text
on the screen but rather to read the AXdiscription field instead.
What I have is a window with a series of text fields each with
labels to the right of them. One of these labels is "ISBN" which
VoiceOver will attempt to read as a single word. In the
AXdiscription field I have the following string: [[char
LTRL]]ISBN[[char NORM]] number
My problem is that VoiceOver now reads ISBN as a world followed by
I-S-B-N number. So my question is how do I keep VoiceOver from first
trying to read ISBN as a word but then go on to read the
AXdiscription?
Is see your problem and I see why you would want to solve it this
way, but I personally do not think it is the right solution. There is
more software out there then just VoiceOver that uses AXDescriptions.
I may be wrong, but I always thought an AXDescription was supposed to
contain textual information which an assistive application might want
to show to the user (text zoom feature such as in our VisioVoice
software), might want to speak to the user (VoiceOver or for example
Talking Interface in VisioVoice), or might want to output tactile
(e.g., braille). You seem to be assuming two things here: 1) that
your description will only be used for voice output (as it would look
really weird to display those embedded commands to the user or turn
them into braille); 2) that all applications generating voice output
based on AXDescriptions would use voices that know how to handle such
Speech Manager embedded commands or are expecting them in
AXDescriptions and will thus strip them.
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?
Cheers,
david.
_______________________________________________
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