CAPTCHA: reporting of findings

<scribe> scribe: janina

jgw: Scott has posted a draft of findings for the Captcha update
... Also good discussion in APA for process going forward
... Someone in APA will take ownership and will be responsible for liaison to RQTF

sh: Believe it's a summary of our discussions with references
... Also, people aren't necessarily users of English charset
... Also discusses other captcha types not referenced in the existing note

js: Asks for better word of classification than "English charset"

jgw: Also have references to add

[discussion re referencing style]

js: Suggesting we may want to add references last, after finalizing text

ds: Offering my help, as far as able

[discussion of process, github, wiki, editing email]

<jasonjgw> Janina: Once RQTF has completed the report, APA will consider it. Janina and any other editors on the APA side will then integrate its findings into a revision of the note, and thereafter it will be revised in response to comments from RQTF/APA. Ultimately it will lead to a Call for Consensus.

<jasonjgw> Janina: once consensus is reached, APA will publish a Note with appropriate attributions.

<scribe> ACTION: jasonjgw to add references and integrate Scott's material in Captcha report [recorded in http://www.w3.org/2017/04/19-rqtf-minutes.html#action01]

<trackbot> Error finding 'jasonjgw'. You can review and register nicknames at <http://www.w3.org/WAI/APA/track/users>.

Authentication: clarifying and discussing research questions

jgw: Noting that AGWG is discussing success criteria for authentication
... Traditional password, but also other strategies, especially those that require memorizing something
... Some issues re short term memory vs long term
... APA interest is in W3C specs for authentication, and in defining a11y reqs

<jasonjgw> Janina underlines the importance of use cases and requirements, supported by references to research. The issues are most likely to arise in implementations rather than in the specifications.

<jasonjgw> There is a parallel with media accessibility. A good specification needs to be implemented in an accessible manner in user agents, but for this to occur we need strong use cases and requirements.

<jasonjgw> Janina supports the involvement of the Accessibility Guidelines Working Group.

ds: Recalling I was looking at a learning example I will followup on
... We should remove the captcha ones to tighten our list

jgw: There's also the notion of continuous authentication
... If some heuristic determines the user is no longer the one who authenticated, a new authentication challenge is posed by the app
... W3C Authentication WG thinks in terms of risk analysis
... So we need to ask whether AT, or other a11y behavior might trigger this inappropriately

<sloandr> New section to build on in our existing Authentication reference list: https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Authentication_references#Emerging_uses_of_authentication_technology_to_focus_on

jgw: We just don't know about this

[discussion on our ability to share among our wg the copyrighted content we're examining]

jgw: There's a process
... It's a kind of digital inter-library loan
... Both EU's M376 and US Sec 508 require multiple biometric options, especially to not limit to a particular biometric

<jasonjgw> Jason suggests reading more of the authentication references and identifying further literature (as well as unresolved research questions) related to the topics arising in this discussion.

<scribe> ACTION: sloandr Work with Scott to continue review of authentication literature and reference listings due 2 weeks [recorded in http://www.w3.org/2017/04/19-rqtf-minutes.html#action02]

<trackbot> Created ACTION-2125 - Work with scott to continue review of authentication literature and reference listings due 2 weeks [on David Sloan - due 2017-04-26].

jgw: Can join this review once Captcha writeup is done

Miscellaneous research topics

ds: Will be reconnecting with Silver work

<jasonjgw> Janina: two areas that should be addressed as giving rise to research questions. (1) payments, and (2) automotive - autonomous vehicle accessibility is one use case; autonomous buses.

<jasonjgw> Janina doesn't know who is working on this in a cross-disability context.

<jasonjgw> APA hasn't had the resources to work on this adequately.

<jasonjgw> Janina notes the need to attend to both of these issues.

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: jasonjgw, janina, scott_h, sloandr
Present: jasonjgw janina scott_h sloandr
Found Scribe: janina
Inferring ScribeNick: janina

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

Found Date: 19 Apr 2017
Guessing minutes URL: http://www.w3.org/2017/04/19-rqtf-minutes.html
People with action items: jasonjgw scott sloandr with work

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