This is all quite interesting and relevant. I suspect that right attention has not been brought to bear on this issue by mozilla. I know for a fact for instance that Arron Leventhal has asked folk in the apple community to talk to apple about it. Messaege is an apple developper but I don't think he works for apple.
The message thread is an old one and it appears as though it has not been revisitted in over 2 years. I as unable to read the bug on the mozella pointer but it seems it was updated in september. I find it interesting that apple can make safari accessible and mozilla cannot make ff accessible. ----- Original Message ----- From: "Benjamin Hawkes-Lewis" <[email protected]> To: "General discussions on all topics relating to the use of Mac OS X by theblind" <[email protected]> Sent: Sunday, December 28, 2008 5:12 PM Subject: Re: firefox, mozilla and voiceover: On 28/12/08 17:54, David Poehlman wrote: > I kno no one at apple who has heard from them. Is that surprising? If you do have relevant contacts or influence at Apple, perhaps you could get them to look into the issue for themselves and fix the blocker bugs? 1. Mozilla developers have written to the Apple Developer support mailing lists. That's a matter of public record; for example: http://lists.apple.com/archives/accessibility-dev/2006/Oct/msg00005.html 2. They have unfixed bugs reported to Apple; Apple is aware of these problems because they're in the Apple bug tracker. https://wiki.mozilla.org/Mac:Accessibility_Tasks lists some relevant Apple bug numbers. 3. Aaron Leventhal talks regularly with WHATWG folks, who include Maciej, an Apple Safari developer. It's not like developers at Apple aren't aware of these problems. Henri Sivonen has suggested that the problem may be that individual Mozilla developers are trying to tackle these problems rather than Mozilla the corporation: http://tinyurl.com/5wrns3 If he's right, that might be part of the story of why Opera is ahead of this game. My impression, talking to WebKit developers, was that even WebKit accessibility work was horribly under resourced, so I'm not that surprised that Mozilla isn't getting much love. -- Benjamin Hawkes-Lewis
