The biggest incompatability with vo is the preferences screen. Vo
thinks there's nothing on the screen, but obviously there is, because
your app is reading a pop-up box, but I can't get vo to admit there's
anything there.
Also, it seems that vo actually helps proquo in that while arrowing
through the list of files in the finder, vo reads an item, then
proquo does too. If I turn off proquo, then continue arrowing
through the list, proquo gives no feedback as to what's being
highlighted. I realize it's not meant to be a screen reader, but I
can see a couple circumstances when the extra feedback proquo gives
beyond what vo gives where this *could* be useful. I've noticed that
proquo seems to see things vo doesn't sometimes. Of course, there's
one or two things I've found that proquo reads wrong, but at least
it's something, and every little bit helps.
On Mar 16, 2006, at 3:36 AM, David Niemeijer wrote:
At 9:26 -0500 15/3/06, Travis Siegel wrote:
I know it states clearly that it's not a screen reader. But it is
a bit odd that a product meant to increase accessibility isn't
accessible itself.
*shrug*
Travis, as I mentioned in an earlier email, I am the developer of
the software. To my knowledge, but please correct me if I am wrong,
there is currently only one thing that does not work with VoiceOver
and that is the main text entry area. There are two reasons for
that, one is an Apple bug that prevents the text edit technology we
use (which predates Tiger for compatibility reasons) to work
correctly with VoiceOver and the other is that if that text entry
area would work with VoiceOver it would seriously screw up
functionality for other users of our application (because it would
cause the same kind of effect you would get when a mirror looks
into a mirror). For the next version we will again look into this
issue and see what can be done about it, if anything can be done
about it. Do note also that this software is aimed at people with
low vision, but not at blind people. It is aimed at the category of
users for whom VoiceOver is overkill and that navigate with the
mouse rather than with the keyboard. If you know any other areas
where Proloquo does not work with VoiceOver do let me know and we
will fix that.
Also, could you explain to me what benefits a blind user would have
when using Proloquo with VoiceOver, I mean, what Proloquo
functionality would enhance your VoiceOver experience? What
Proloquo features would fill up gaps in the VoiceOver functionality?
Thanks,
david.
--
--------------------------------------------------------------
David Niemeijer, CTO
AssistiveWare(R)
[EMAIL PROTECTED]
http://www.assistiveware.com/
--------------------------------------------------------------
