W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

31 Oct 2018

Attendees

Present
jasonjgw, sloandr, janina, scott_h, Judy
Regrets
Chair
jasonjgw
Scribe
scott_h

Contents


Updates from TPAC 2018.

<sloandr> janina: felt this was a successful TPAC, lots of interest in accessibility. Will pull together and share a set of links to minutes of meetings that were relevant to RQTF

<sloandr> janina: meetings included Math on the Web Community Group, interested in new focus on SVG in math content, but also a group still focusing on MathML. Divergence in approaches has implications for accessibility approaches

<sloandr> janina: involved in other discussions on domain-specific notation including publisher-led discussion. Will share more details of what was discussed (links to minutes plus a summary of discussions)

<sloandr> janina: other notes on topics that were covered—Pronunciation TF approaches on pronunciation and CSS speech, received positive feedback on objectives.

<sloandr> janina: Publishing-led proposal for another markup language to sync text and speech, driven by technical limitations of SMIL and other current approaches to same challenge.

<sloandr> judy: regarding knowledge-specific domain topic, has had further discussions on the different approaches that have been suggested. May be useful to form a CG on knowledge-specific domains, build a mechanism-agnostic discussion space, with links to other groups that have their own approaches, track discussions in a central place and liaise with relevant WGs.

<sloandr> janina: agree important to keep different players involved in discussions; would be willing to start effort to establish a CG

<sloandr> judy: CG effort would also need input from an internationalisation/localisation perspective

<sloandr> scott_h: was MathJax discussed at TPAC?

<sloandr> judy: have been discussions, but there are different kinds of misunderstanding over what MathML and MathJax do/do not do with regard to accessibility; would be helpful to provide background on accessibility issues to help inform discussion on knowledge-specific domain notation

<sloandr> janina: important to have approach-agnostic advice to inform discussions

<scribe> scribe: scott_h

jason: progressing to next item
... looking at literature, refs on math accessibility
... chemitcal diagrahsm, data visaulisaiton accessibility, some mateiral limited to music accessibility
... most literature on math though
... spent time drawing on theems while reading, semantic enrichment
... waht is is: taking source markeup, enrich it semantically before performing presenaiton you're interested in
... sematic not alwasy encoded in source is consistent issue
... eg spoken presentation of math, MathML doesn't disambiguate meaning sufficiently to provide spoken rendering that is appropriate ot knowledge domain
... so various techniques/heuristics have tried ot work around that
... some work wit things like MathJax is also interesting, have a way of representing mathematical expression for spoken presentaiton
... otehr accessibility features including semantically aware line breaking and synchronised highlighting
... helpful for learning disabilities: text-to-speech accompanied to proivde spoken with visual

janina: mentioned that visual could support spoken, i.e. vice-versa

jason: idea of reflow with smart line breaking an important thing, especially in WCAG 2.1 relating to reflow and scrolling
... and large text fonts

janina: reason wny important is to prove theorum: step through in fashion that establishes a proof

scott-H: picked up some great htings in your reading, great work

janina: asked about cmplaint about MathML: main issue is diffiuclty in layout main argument ofr moving to SVG

jason: main criticism is opposite: doesn't captchure semantics for conversion i.e. presenation MathML

janina: argument that presentation and accessiiblity/understanidng both need to be solved for accessiiblity

jason: scrolling/layout accessiblity issue needs ot be addresed
... second item: recognition of importance of manipulaiton of content, not just being able to read it
... many efforts looking to address this, but not clear aobut what good user interactions would be needed ot perform with several different appraoches to that problem
... clear though that copying an expressin that's written, then modifying it, is a fairly common operation - semantic operation, seleciton of things between ( ) and presentation of 2D materials difficult
... e.g. matricies, polynominal, long divison, wasy of grpahs edge/node

One promising approach: Mathematical Working Envrionment: looking at learning in math books and figure out accessible straeties needed in user interface

jason: then looking at different output methods

janina: lillipond emac music

jason: enother emerging theme: how to present overviews of materials/summaries so larger structure can be understood before finer details
... research on user interface, e.g. accessible chart tool and browser interface that were automatically generated by statistics package

Donal frm RQTF wrote paper on this - RQTF member

jason: interesting on how to move around ot read individual values while grasping overview, SVG-based, innovative as charts were autogenerated and accessibility built-into generaiton proces
... chemecial work interesting, extracted sematics converted into CML , semantically enriched and presented in accessible in browser
... again sematic enrichment and importance of interaciton/navigation
... adied comprehension

scott_h: great detail

janina: likewise, unlikely to find more than that

jason: projects vary quite a bit in inerface and approach, but eneral requirement is clear although detailed work

janina: Microsoft $25m AI accessibility fund, interesting to see work in this space

scott_h: have now tracked down music domain papers, will write up a summary for future RQTF meeting
... CAPTCHA: any examples woudl be great for OZeWAI presentation

jason: CSUN presentaiton accepted relating ot RQTF work

scott_h: apologies for typos in my first minutes!

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2018/10/31 14:03:30 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: jasonjgw, sloandr, janina, scott_h, Judy
Present: jasonjgw sloandr janina scott_h Judy
Found Scribe: scott_h
Inferring ScribeNick: scott_h
Found Date: 31 Oct 2018
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]