Re: Getting notified when VoiceOver cursor changes?
Re: Getting notified when VoiceOver cursor changes?
- Subject: Re: Getting notified when VoiceOver cursor changes?
- From: "Eric T. Seymour" <email@hidden>
- Date: Mon, 13 Mar 2006 11:30:02 -0800
On Mar 13, 2006, at 11:20 AM, Mike Engber wrote:
Is kAXFocusedUIElementChangedNotification intended for such purposes?
No. This notifications tells you when the keyboard focus has changed.
If not, is there a way how to find out that the VO cursor has moved?
No. You can file a feature request, but the VO cursor is a concept
specific to the Voice Over application and I doubt they are
planning to expose it.
Can you please explain what you are trying to accomplish? We
currently do not expose it, nor would the current AX protocol help
you because the VO Cursor (usually) moves as a result of the user
interacting with VoiceOver.
--E.
I don't know what your needs are, but the VO cursor is built on top
of the public accessibility APIs. You should be able to do the same.
I've just noticed that descriptions in my app that are entered as
"A-D", "E-J" are improperly read. Do I have to set descriptions to
"ay to dee" or "ee to jay" instead of nice "A-D" to achieve proper
reading?
Can be role descriptions and element descriptions shown somewhere
or are just for reading purposes so it would be OK to do what I do?
Is there some alternative to get "A-D" properly read?
AXDecriptions are supposed to be regular text (not phonetic). Voice
Over does "read" the AXDescriptions, but other accessibility apps
treat them as text.
That being said, I don't think it would be unreasonable for a
button labeled "n-m" to have a description that was "n to m" or
even "en to em". Note - I picked the letters "n" and "m" because
those are among the few letters whose name I know how to spell
(thanks to playing scrabble).
There is definitely precedent for this. I would consider it akin to
having the button text contain an abbreviation and the description
providing the full term. E.g. a natural logarithm button ("ln")
would have a description of "natural log".
Obviously, this doesn't handle every case. A way for assistive apps
to provide phonemes has been discussed, but it puts yet another
burden on apps trying to accessorize themselves.
Go ahead and file a feature request. I'm pretty sure this is
already a bug about this, but it can't hurt to ask again.
-ME
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (Accessibility-
email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
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