User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/16.0 Firefox/16.0 Build ID: 20120720042008 Steps to reproduce: Using Apples Accessibility Inspector App (included with XCode) and hovering over the Firefox window. Actual results: When using Apples Accessibility Inspector App (included with XCode) and hovering over the Firefox window it only shows very sparse information. (Screenshot: http://d.pr/i/863m/5WBoEfnD ) Expected results: It should at least give us the AXWindows like it did in previous versions (Screenshot of regular Firefox output: http://d.pr/i/Hqzw/3jIvdEhu ) This is important for many apps, e.g. apps that allow to move other apps windows like BetterSnapTool.

I think this is because we only whitelist VoiceOver currently. The performance penalty isn't worth it for other tools. Hub please reopen if I'm wrong.

Andi, due to various performance problems, accessibility is currently whitelisted for VoiceOver only. If you want accessibility enabled, you have to change the value of the about:config option accessibility.force_disabled to -1.

Ah yes good point - I forgot about the force config.

I just to be clear, I believe this is regression, convered by bug 781090 as well.

Comment on attachment 653001 [details] [diff] [review] Have minimum a11y support when we don't have Voice Over. r= Proposed patch: pass the a11y function if we don't have Voice Over. Also fix a (begnin) issue is [ChildView accessible]. I also would like to propose it to Aurora to get this fixed as it is a regression.

sorry, wrong bug...

Comment on attachment 653001 [details] [diff] [review] Have minimum a11y support when we don't have Voice Over. r= forget about that patch. Will attach to the right one.