Minutes: MathML intent meeting, 5 Aug

   - Bert Bos
   - Christopher Comninel
   - Sam Dooley
   - David Farmer
   - Deyan Ginev
   - Patrick Ion
   - Louis Maher
   - Bruce Miller
   - Murray Sargent
   - Moritz Schubotz
   - Cary Supalo
   - Neil Soiffer

Regrets:

   - David Carlisle
   - Paul Libbrecht
   - Laurence Zaysser

Announcements/updates

NS: reached out to ARIA co-chairs about ARIA and a TPAC meeting and did not
get a response yet.

NS: Spoke to an accessibility expert and he felt that ARIA was not the
correct method for making things accessible.

NS: there has been more progress on the Chrome MathML implementation front.
Stretchy chars have started to work (I needed to force it to use the
Cambria or STIX Two fonts via .math { font-family: Cambria Math; }).
https://codepen.io/rema/pen/YQyYoJ is a version of the old Mozilla torture
test that allows font selection if you want to check out Chrome Canary.
Gap Analysis Doc

The Gap Analysis document is at
https://docs.google.com/document/d/1Pzsf2dqTkbYXFmoKCLzvtrNERNmtF2MHX1WtugB3PfA/edit#heading=h.k21427jotzf1

*ACTION ITEM:* NS: will send out reminders to those who had action items
from last week.

NS: The vertical bar can mean "such that" or divide. Accessibility needs to
know the intent of vertical bars.

An example is : the set of all x such that x divides ten.

DF: In an email, he showed an example where bars had six different meanings
in one expression.

DF: In TeX, authors should use macros instead of using bars.

NS: 'such that' has lower priority than 'divides. Are there editors that
can automatically group terms into mrows in an expression by honoring the
precedence of operators?

MUS: has added macros that can help some vertical bar uses.

NS: Unicode says that "such that" and divides uses the same symbol.

NS: asked if more headings should be added to the gap document.

MUS: works with MathML enable products like Word. If you have a WYSIWYG
editor, and you make a change, there needs to be a selection mechanism that
tells your internal code where the changes are being made.

SD: There is a selection mechanism in the DOM that can be used to indicate
the boundaries of terms such as integrands.

There is a selection start and end, and a set selection range.

This is defined for HTML input.

*ACTION ITEM:* MUS: will update the selection entry in the gap document.

NS: may edit this entry to make it clear what the accessibility use case is.

NS: selection is an issue that should be explored but has not yet been
studied.

MUS: we need selection and it should be mentioned in the gap document.

NS: selection has to do with accessibility, but we should not spend much
time on it.

DG: said that chemistry was out of bounds for us.

DG: wants to focus the gap document more precisely.

BM: We do not want the gap document to become the group charter.

NS: The gap document should not be more than fifteen pages long.

SD: how do we get information into the document which would enable search
and computation?

*ACTION ITEM:* NS: will write up the MathML subject area.

*ACTION ITEM:* SD: will write up the parallel markup section.

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>