Alex: within cr community there have been further discussions.... on mathml... idea here now is if folks want to implement it we [Chrome] need e.g. full test suite, etc...

Alex: no layering story - no way to plyg in - maybe this is solved by custom elements. we have an opportunity to raise that as an issue from the TAG.

Hadley: +1 from me - someone said "we can get rid of it" and that has spawned a signfigant set of discussions refuting that. We can bring the communities together - which would be great for the web.

Alex: math on the web CG - not pusing mathml - looking for accessibility hooks and can't do it with mathml. ohealing that rift and gettign both sides what they want...

Hadley: do we have what we need?

Peter: next steps?

Alex: let's talk about the quality, explainer, users, motivation, quality in terms of modernization (extensibility)... rendering section.

Alex: I'll draft something.

Resolved: we all love Alex and Travis and want them to stick around.

Peter: you never the TAG

All: Woot!!

Alex: Since TPAC, conversation is Chrome is not generally opposed. Want to ensure good layering in platform. Also want to ensure spec is better (e.g., the rendering section). Also, we want to see tests.

Dan: We've heard this several times, have we delivered the feedback to someone that can take this and make something happen with it? If work is happening, we should let it happen.

Alex: Is there a WG?

Dan: There's a CG.

Kenneth: many folks are looking at our issue, we could give it there?

Dan: Well, we're not interested in having an "etherial" discussion, but rather "here's out guideance".

Alex: Perhaps we can start with a series of concrete areas that we'd like to see improved. (That's really our job.). Travis you filed this...

Travis: I can start on a doc that we can all contribute to (that outlines the high-level feedback)

Dan: Might be good to collaborate on something (in private) and then paste into the issue where everyone is already looking.

Tess: I too would like to see a Rendering section that is useful for implementations ;-)

Kenneth: restarting a community group?

Sangwhan: the repository was deleted, then re-added--and no one noticed ;)

Travis: posted a link to a response on the issue in a Google Doc (link in Slack). Has anyone other than Alice seen this?

Tess: Pretty good overall. Would love to see Gap analysis for CSS/MathML?

Alice: How would the gap be useful outside of MathML, if any?

Tess: Tables could be relevant?

Sangwhan: Accessibility is hard for Math (hard to read out). Not sure MathML provides an out-text or long-desc equiv.

Alice: Been awhile for me. When asking teammates, they said MathJax is really good at rendering as Braille and spoken feedback. Additional some non-web-based tools do a good job. Wondering what scenarios folks would use it?

Sangwhan: MathJax has little to do with MathML. Inside the a11y tree it's not.

Alice: MathJax provides its own assistive version. Also has hidden content that provides the MathML.

Travis: propose moving to F2F. I'll try to incorporate Tess' feedback, and we can try to push public at the F2F.