Re: MathML Accessibility in Gecko

MathML token or MathML glyph could be exposed as object attributes I guess
if necessary.

I agree It's good idea if AccessibleTable interface is reused for MathML
tables. However if it's good to show the difference between tables if
exists.

Having relations might be nicer since it's not MathML tree dependent. Say
if ARIA got math extension and author starts to not follow MathML tree
conventions.


On Tue, Apr 1, 2014 at 4:38 PM, Jonathan Wei <[email protected]> wrote:

> On Tuesday, April 1, 2014 12:13:00 PM UTC-4, Trevor Saunders wrote:
>
> > do we really want to add another interface? It'll take time before we
> >
> > can assume its available everywhere, and more importantly it runs the
> >
> > risk of baking equation == mathml, and if people want to expose
> >
> > equations accessibly but don't start with mathml they'll have to fake it
> >
> > somehow.
>
> Currently, it doesn't appear we use the equation role for anything other
> than the <math> tag, so if people want to write equations in HTML or
> something else, they can do so anyway.
>
> With regards to the addition of another interface, I'm not sure why it
> would matter if it's not immediately available everywhere, apart from
> maintenance of an implementation that no one is using yet - unless that was
> your point, as you've mentioned before in the meta-bug.
>
> I think most of the useful functionality can be exposed solely through
> roles and relations, so it's possible we don't need a dedicated public
> interface.  The only thing in the interface right now is the tokenValue
> attribute for obtaining the value of a MathML token element or MathML glyph.
>
> > Why do we need this? it seems like its the same exact interface as
> >
> > nsIAccessibleTable with some stuff removed.
>
> It is indeed basically the same, to the point that the implementation
> borrows quite a bit of code from the HTML table implementation.  I added it
> because I thought it might be useful to have a like interface to
> nsIAccessibleTable that allows you to iterate over the table returning
> objects implementing the MathML accessible interface.  The single
> differentiating method to get the row label relies on a MathML feature that
> isn't supported in Gecko yet anyway, so the MathML table interface could
> probably be scrapped and the regular nsIAccessibleTable interface used if
> necessary.
>
> > More roles seem fine, and relations might be good but I think your wiki
> >
> > page may be adding too many, e.g. do we really need all the fraction
> stuff? or
> >
> > can we just say for an accessiblewith ROLE_FRACTION child[0] is the
> >
> > numerator and child[1] is the denominator and that's it?
>
> For the simple structures like fractions, I agree that half the relations
> aren't really needed, since MathML rigidly defines which child must
> represent what part of the structure.  My general idea with the relations
> was to have them be a fairly comprehensive set for the structures, with
> both forward and backwards relationships.  This was addressing a point
> brought up offhand by Jamie in comment 23 on the meta bug (
> https://bugzilla.mozilla.org/show_bug.cgi?id=916419#c23).  I guess we
> could just have the backwards (e.g. numerator to fraction) relationships,
> but it seems unbalanced.  Maybe that doesn't really matter, though.
>
> For more complicated structures like <mmultiscripts>, we'll still need
> relationships going forwards and backwards to be able to give useful
> information about the structures.
> _______________________________________________
> dev-accessibility mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-accessibility
>