Re: Getting VO to read static text
Re: Getting VO to read static text
- Subject: Re: Getting VO to read static text
- From: Patti Hoa <email@hidden>
- Date: Fri, 24 Oct 2008 15:02:52 -0700
Hi Scott,
See my comment below:
On Oct 24, 2008, at 2:13 PM, Scott McCormack wrote:
Hi James & list,
So if I understand you correctly there is no way for an application
to explicitly tell VO that something should be read at a particular
time? The application I am working on has a status message that
changes as the user works through the controls in the dialog and
while putting a hotspot on the status text does work quite well we
now have to inform the user via training or documentation that the
status text changes real-time and they should set a hotspot to get
real-time updates. I'll definitely check out bugreporter since there
are a lot of things I wish VO would do that it doesn't as of yet.
That's correct. What you are requesting is the ability for the
application to speak (via VoiceOver) what it wants the user to hear at
anytime. You can do that directly via speech synthesis. VoiceOver,
on the other hand, is solely controlled by the user. Just because the
application thinks the user may want to hear certain information
doesn't necessarily mean the user wants to hear it. So it's up to
the user to determine if he/she wants to set that status text as a
hotspot or not.
It is true that there is the extra step of exploring for that status
text, which application may have to note in the documentation. You
can file an enhancement request to see if there are ways for an
application to indicate a piece of text as an important dynamically
changing status through accessibility.
Is it possible for an application to cause the VO cursor to move to
another control without affecting the keyboard focus? If so this
could be a roundabout way of pointing something out to the user.
Also how exactly is Braille tracking handled? I don't have a USB
based Braille display so I am limited to using the viewer for
testing and so far the Braille just seems to just show what the VO
cursor is showing. Are there cases where the Braille can be
separated from the speech VO cursor?
Application cannot directly manipulate where the VO cursor goes.
Altering the keyboard focus is the closest you get to somewhat control
where the VO cursor goes, assuming the user has keyboard cursor
synched to the VO cursor.
Braille is essentially tracking the cursor that's triggering the
speech. So any VO cursor movement or keyboard focus change will cause
Braille to output. There is no case where braille can be separated
from speech, both are tied to VO cursor.
Patti Hoa
VoiceOver Engineering, Apple
Thanks
---
Scott McCormack
Senior Accessibility Consultant
SSB Bart Group
On Oct 23, 2008, at 4:28 PM, James Dempsey wrote:
Scott,
It sounds like the app is sending the correct notifications /
behaving as it should from an AX perspective.
The user has to explicitly choose to automatically hear changes for
a particular static text. The cool thing about setting this
static text as a hotspot is that VoiceOver will continue to watch
the changes for this hotspot without the need for the VoiceOver
cursor to be on top of it."
If you have any feedback on how this works in VO, please file a bug
or enhancement request at bugreporter.apple.com.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (Accessibility-
email@hidden)
Help/Unsubscribe/Update your Subscription:
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