Accessible Platform Architectures Working Group Teleconference

12 Dec 2018


jasonjgw, janina, scott_h, Judy


<scribe> scribe: janina

chair jason

jgw: Reviews today's agenda ...

<jasonjgw> Janina is making progress on the CAPTCHA draft revisions.

jgw: Found a chemical molecule browser
... Need help understanding navigation models

sh: Cudoos to Jason on Knowledge Domain write up
... Well laid out
... Strongly visual in math

jgw: Non visual access seems to have generated the most work in this area

sh: Noting not nearly as much literature on chemical formulae

jgw: Need help with implications/conclusions for browsing--even the researches were befuddled by that
... clear that hierarchical in structure was important, and als moving focus to any node connected to the current focus
... But I think we need a second opinion
... Second paper more general, diff between visual readers and visual readers n skimming strategies, esp re scientific and textbook materials
... Visual readers first note block level elements; then on closer reading font changes, etc.
... Nonvisual readers tend to jump pages, or push reading rate
... But, they may have been using untagged PDF in their study--a weakness

<scott_h> great work on domain content Jason

jgw: Noting work at ETS on better non visual recognition of block level elements in a skim read

js: Notes complaints during our sessions at TPAC with Math on the Web CG that MathML does not present well visually
... That group prefers SVG

jgw: Notes there are actually two MathML, one presentational, the other content focussed for a11y
... Semantically meangingful line breaks seem to be a weakness

<jasonjgw> Janina notes the value, which is significant, of this work.

<jasonjgw> Janina: navigation strategies are a key focus.

sh: Wonders whether our findings might become a W3C note?

jgw: Certainly need to incorporate this into a doc of some kind

sh: NOtes also nav implications of music

jgw: Yes, the linear, but also individual score parts

sh: Navigation, entry points, and how to linearize seems to be the common cross domain issue

js: Editing approach also depends on one's nav model

jgw: Notably different from text editing

<jasonjgw> Janina notes the contrast with text editing, which is essentially linear.


<jasonjgw> Janina: has a revised draft that is mostly completed. There is a note to be removed/edited.

<jasonjgw> Janina covered the issues that needed to be addressed in the draft. Some relatively extensive rewriting was necessary, particularly related to ReCAPTCHA.

<scott_h> Thanks Janina for the update, looking forward to reading it!

<jasonjgw> Janina thinks we're on track to publish early January.

<jasonjgw> Janina: we need time for us to review, then for APA to review. We can leave time through February for external reviewers to respond.

<jasonjgw> Janina notes a kind of CAPTCHA challenge in which you're asked to write the words that you hear. It doesn't seem necessary to write all of the words, in the correct order, or to spell them correctly.

<jasonjgw> Scott demonstrated an audio CAPTCHA in his conference presentation, which dramatically demonstrated the difficulties of responding to them.

<jasonjgw> Janina is interested in adding material to address these refinements to audio CAPTCHA.

<jasonjgw> Janina notes interesting work on public-key infrastructure.

<jasonjgw> Janina expects to circulate a URI today.

Next Meeting

jgw: I will continue to annotate wiki, may be ready for review

<jasonjgw> Janina will circulate the CAPTCHA URI; we should be able to determine by next week wehther we should bring our comments to a meeting.

sh: Notes ability to make Dec 19, and then 9 Jan

jgw: So, leave open 19 Dec call to discuss captcha, if needed

<jasonjgw> By early next week, Jason in consultation with Janina will determine whether our comments on CAPTCHA would benefit from discussion at a meeting on Wednesday, and publish the agenda (or postpone the meeting) as appropriate.

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/12/12 14:50:48 $

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, janina, scott_h, Judy
Present: jasonjgw janina scott_h Judy
Found Scribe: janina
Inferring ScribeNick: janina
Found Date: 12 Dec 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]