Accessibility of domain-specific notations and content - literature and discussion.

jgw: Scott has been finding relevant literature

https://lists.w3.org/Archives/Public/public-rqtf/2018Sep/0010.html

sh: Want to do one more pass

jgw: suggest one more week of reference hunting

<jasonjgw> Janina: agrees that this progress is promising. It would be useful early on to maintain a list of the knowledge domains that the literature addresses. A short problem statement would be useful as well.

<jasonjgw> Janina: we can't expect AT and browser development communities to address this alone - we need specialist expertise in the knowledge domains to be involved.

<jasonjgw> Taking up a theme form last week, in a problem statement we need to discuss input as well as presentation. For example, it's obvious that mathematical input is different from text input. Having a list of knowledge domains would b a good start.

sh: Lots of discussion on how a11y interaction can be architected
... Especially for STEM

<jasonjgw> Janina: there would also be interest in any accessibility research related to language acquisition - input methods, spoken presentation and other issues.

<jasonjgw> Janina: notes work undertaken at ETS on spoken presentation and SSML, which is currently engaged with APA.

<jasonjgw> Janina notes the plan to establish a Task Force to specify a JavaScript-based and extensible mechanism to enable authoring of correct pronunciation and spoken presentation.

jgw: Notes additional emphasis on grammar in language textbooks, so more than just pronunciation

<jasonjgw> Janina notes limited success so far with the "lang" attribute.

js: Notes issues with U.S. NLS BARD not using lang

[discussion on whether AT follow through]

jgw: Also interesting issues in voicing math, different pitch, pause, etc

<jasonjgw> Janina: the immediate objective is to set up a meaningful discussion at the TPAC meeting - including the spoken presentation discussion and the mathematics. Janina plans to set aside substantial APA meeting time for it and to refer participants to useful resources.

<jasonjgw> Janina: given that this is about a month away, we should seek to organize what we've found in the research so that others can take advantage of it. After TPAC, we can undertake a deeper reading/review of the literature.

Any other updates and discussion

<sloandr> APA Verticals and RQTF update: https://www.w3.org/WAI/APA/wiki/Verticals_to_Track#Research_Questions_Task_Force_work

ds: Incorporated RQTF commentary as request at above URI
... Notes we have references to research, and also issue digests

<jasonjgw> Janina hopes for another CAPTCHA Note draft before TAC.

jgw: Anything else today?

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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: scott_h
Present: scott_h

WARNING: Fewer than 3 people found for Present list!

No ScribeNick specified.  Guessing ScribeNick: janina
Inferring Scribes: janina

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 12 Sep 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.)