Minutes: MathML intent meeting, 20 May

Agenda:

1.  Announcements/updates
NS: Should we record the meetings?
BB: You can record but you must have everyone’s agreement because it is
made public.

 a) accessible alternatives to irc/google docs for minutes

PL: Considered bridges between IRC and other systems. It might be possible
with slack and matrix. We would like to have a web based IRC.  He wants to
find someone with a Matrix account for experiments.

A bridge would make minutes show up in IRC and Slack at the same time.

NS: Can people send out short messages with the minutes system instead of
using emails?

PL: knows cryptPad.

LM: The CryptPad web buttons are not accessibly labeled.

PL: Said it would be easy to get labels put on the CryptPad buttons.

NS: We will start using CryptPad for minutes on June 3.

PL: will help LM set up a minutes system in CryptPad.

2. Revisiting 'intent' and deciding how to move forward with this or some
alternative

NS: Discussed having intent MathML use CSS.

NS: is not in favor of using CSS with intent mathML.

PL: is in favor of CSS.

PL: My attempt: https://mathmlmuses.netlify.app/intents-as-css-styles/

DG: Do we push intent into ARIA?

NS: An aria braille label has been created.  May not work perfectly.

NS: Hard to traverse trees using aria labels.

There is trouble with pronunciation.  You can not force the pronunciations
for things like long A.

NS: Said aria would not accept new math roles.

NS: Intent is different from most things in HTML.

CL: Discussed having the purpose attribute in aria. This approach was
rejected.

DG: Search engines can not pick up micro data.

Search may be a problem with the intent MathML specification.

NS: Authoring tools should produce useful intent MathML.

DG: You want your authoring tool to make things accessible.

DG: A selector has to explain mathematical structures

The selector is a pattern.  If your structure matches the pattern, it is
identified and can be written.

DG: We must write down the structure of the various mathematical objects so
that they can be identified.

The selector is a pattern that is used to represent a math structure.

DG: the patterns must be written in the specification.

BB: You can not select on the content of an element.

NS: What do we talk about next week?

PL: has topics.

DC  We should have a roadmap for the deliverables in the charter.

NS: Go through the charter and see what will be worked on, and who will do
it.

NS: We have two tracks.  The browser writers will join the core group and
not the intent group.

Hopefully we can get people in from Apple and Google for the core group.