Re: MathML proposed checkpoints:

At 11:58 AM 3/3/99 -0400, Tom Wlodkowski wrote:
>
>Last summer Jon Gunderson asked for a subgroup to be formed
>to look at MathML from the user agent perspective. Below are
>three proposed checkpoints on which we'd like your feedback.
>Since MathML implementation is still pretty vague at this point,
>our checkpoints are extremely broad.
>
>Last summer Jon Gunderson asked me to head up a WAI-UA subgroup to look at
MathML. Below are some proposed checkpoints. Since MathML implementation is
still pretty vague, our recommendations are very broad. Please send any
feedback to the list.
>
> Thanks!
>
>Tom Wlodkowski
>CPB/WGBH National Center for Accessible Media
>
>Checkpoints:
>
>1. Mainstream browsers should implement MathML rendering.

How is the MathML embedded in the HTML?  Is a plugin an option?  Desirable?
 What do browser vendors have to say about the pros and cons of asking
authors to use XHTML if there is going to be MathML in the document, vs.
some other way
of embedding MathML in vanilla HTML4?
 
>2. Allow keyboard access to components of MathML equations
>comparable to the way access is provided to objects in forms.

"Comparable" may need to be broadly interpreted, here.  Math expressions
form much deeper trees than forms and form controls.  So keying your way
around to isolate a particular subexpression is more like walking the Hn
hierarchy of a document than form element access, in some respects.  Those
with AsTeR experience can probably say this more clearly.

>3. MathML objects should be available as part of the DOM, so
>that assistive technologies can use that content to effectively
>convey the math to users of access technology.

MathML is XML and per DOM1 has that much support in the DOM.  To decide if
more is needed we may need to work in terms of a specific audio interface
representation and interaction strategy, or Braille, or some other
alternative morph of the MathML content.

Al

>

Received on Wednesday, 3 March 1999 13:37:05 UTC