Steps to reproduce: 1. Load the page specified in the above URL 2. View the accessible hierarchy in Accerciser Expected results: The MathML objects would not be exposed as "dead" accessibles. Actual results: The MathML objects are all exposed as "dead" accessibles. When I view the accessible hierarchy via the DOM Inspector, I see the objects as expected.

the reason is accessible for math element is nsAccessibleWrap class that contains text children accessibles (text children of mathml:mi elements which arent' accessible). I'm not sure we should fix it in timeframe of firefox3 and until we have some accessible specification for mathml.

Mathtype + IE expose accessible for mathml:math element only and do not expose any its children. Also they provide description how the equation may be read. In description they use <silence msec=""/> tag to get pauses. It would be ideally if we get some specification from mathtype to be compatible. I think we can try to add base support in timeframe of gecko 1.9.1 Joanie, do you like if we will remove all dead children in the meantime and we will expose equation accessible object only and actually you can't do with it anything?

I don't like the way mathtype does it, because math braille translation is not supported. This is why a11y always keeps the model separate and let the AT create the view. I also don't think MathType can deal with mixed markup very well (e.g. form controls or links inside the math).

You're right mathtype way can work for simple equations. The complex equations should be unusable because it's impossible to represent in mind big formula at once. AT should be able to navigate through the formula to allow to sound interesting part of equation.

Assuming this bug is about the accessible object showing up as "dead".. I don't see it. They show up here as an object with a role of "unknown" which seems appropriate given that MathML is not implemented. As for actual accessible MathML support, that should be a separate bug that might exist out there.