It is up to the software vendors and authors to write their programs
so that they support the Apple's Accessibility API. These API have
been published for all to see by apple for several years now. Firefox
uses it's own GUI system called XUL which needs to be modified so that
VoiceOVer can read the controls and content. When you do not follow
the Apple API's you pay the price in having to do a lot of extra work
to get your program to work right in the OS and this is but one
example of that.
Greg Kearney
535 S. Jackson St.
Casper, Wyoming 82601
307-224-4022
[EMAIL PROTECTED]
On Feb 29, 2008, at 6:55 AM, Benjamin Hawkes-Lewis wrote:
L. T. Reed wrote:
Although no help was available thanks to David and Benjamin for
replying.
Inevitably, we tend to dwell on negatives on this list but it's
difficult not to conclude that we've been sold a sub-standard
product in Voice Over for Leopard.
I'm not sure what you mean, at least as far as Firefox goes.
Firefox doesn't support Apple's Accessibility API yet, just as on
Windows the current release of Opera does not support Microsoft's
Active Accessibility API or the GNOME AT-SPI API. That's basically
Mozilla's and Opera's responsibilities more than Apple's,
Microsoft's, or GNOME's responsibilities.
Far from there being no help available, you can turn Firefox into a
self-voicing browser using Fire Vox.
--
Benjamin Hawkes-Lewis
