and they wouldn't experience the problems in mac os if tey used coco
and devellopped according to the accessibility api. You keep talking
about features and cross platform accessibility but from where I sit,
a browser is a browser and if Apple can make one accessible on the Mac
and opera can make one accessible on the mac, mozilla can.
On Dec 28, 2008, at 7:00 PM, Benjamin Hawkes-Lewis wrote:
On 28/12/08 22:46, David Poehlman wrote:
I find it interesting that apple can make safari accessible and
mozilla
cannot make ff accessible.
Well, Safari has fewer features, for example:
1. No special table navigation.
2. No ARIA live regions.
3. No extension framework making use of a widget set.
Personally, I think it would be pretty amazing if Apple couldn't make
their own browser accessible with their own accessibility API and
screen reader. (Kind of like it was pretty amazing when they failed to
make Numbers accessible.)
Mozilla does not experience these problems on GNOME or Windows.
--
Benjamin Hawkes-Lewis
