Re: Getting notified when VoiceOver cursor changes?
Re: Getting notified when VoiceOver cursor changes?
- Subject: Re: Getting notified when VoiceOver cursor changes?
- From: Tomas Zahradnicky <email@hidden>
- Date: Mon, 13 Mar 2006 21:51:00 +0100
Hi Eric & Mike,
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.
I'd like to know when WO cursor changes so I am able to update the
control hierarchy and control locations.
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.
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.
Well, I could work around that by supporting keyboard focus in each
of the panes that are in my window and watch for focus changes but
I'd rather avoid this weird solution hence it requires sync VO and
KBD focus option be turned on.
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 ...
...snip...
... 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.
Would be better to add a phonetic AXPhoneticDescription then?
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"
Indeed, however this does not apply to my situation, see below.
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.
I will try to describe my problem:
I'm currently accessorizing a mix table window. Each audio track has
a column in that window. I've overlayed each audio track with a user
pane control which embeds 3 other user panes. These embedded user
panes have installed accessibility handlers and provide dynamically
their role and description. Each of the three user panes embeds my
custom HIView that provides access to a matrix completely
nonaccessible buttons.
These matrices are named Inserts A-E, Sends A-E and Sends F-J. It
makes sense to have VO read "Sends ef to jay" because it makes sense
to read what matches the hardware mix table that is attached.
Since tracks may change under my hands on the fly, it would be good
if I was able to tell whether the VO cursor changes so I am able to
let it advance to the next appropriate control and reshuffle the
control hierarchy when necessary.
I'm also not sure what happens if the control that has VO cursor
moves and it would be very reasonable to reset the VO cursor or have
it focus the new location such as when someone deletes the audio
track that currently has the VO cursor.
Tomas
--
# Ing. Tomas Zahradnicky, Jr.
# The Czech Technical University
# Dept of Computer Science, FEE-CTU Prague
_______________________________________________
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