Who rules? Component or VO?
Who rules? Component or VO?
- Subject: Who rules? Component or VO?
- From: "Saqib Shaikh" <email@hidden>
- Date: Sun, 8 May 2005 22:38:41 +0100
Hi
I'm a VoiceOver
user, and one thing which this initial release lacks is the ability for
VoiceOver (VO) to do different things depending on context. A key example
is the knowledge that in the Terminal text field, or the iChat message history
text field, it would be ncie to have everything spoken as it comes into the
window. I was talking to a sighted friend of mine about this, and I said
that I hoped it would appear in a future version of VO.
He responded that in
fact the component had the ability to tell VO what to do with the information -
he said this was based on his brief knowledge of the accessibility API, and not
on any work done. So he was implying that not only can a component report
what it contains, it can also tell VoiceOver every time it changes, and maybe
even tell VO that the text should be read...
I'd be surprised if
this was the case, but as is often the case, it may be based on some truth that
had been misinterpreted. So, is there something that can be done on the
iChat/Terminal end, or must it be done at the VoiceOver end? Just
interested as I have no ability to change either (except file bug reports which
I have done).
Before I go, I'd
just like to shamelessly advertise my web site, www.MacVisionaries.com, aimed at people
interested in the use of Macs by the blind.
Regards,
Saqib
_______________________________________________
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