<scribe> scribe: janina

CAPTCHA: preparation of research findings

jgw: Have written and posted an outline based on the existing APA Teuring note.
... Noting where our findings might put.
... It's now on github, and we have a gh pages branch
... So, now we need to write up our notes

<jasonjgw> Janina: thinks Michael should be able to assist with meeting W3C style guidelines.

sh: Have signed up and have github account, talking with jgw about how to use

jgw: Has anyone had opportunity to review the doc?

[crickets]

jgw: Asking about dividing the commentary? Anyone on particular topics/portions of the note?

[crickets]

jgw: Asks Scott about writing

sh: Yes, need to learn the ropes of github

jgw: Discussing process with Scott ...

Updates on other research topics

jgw: Current plan is that we could make good progress on authentication as related to captcha ...
... I'll be discussing priorities with APA next week
... There's also personalization, which will be coming up for overview in APA during April
... Any others of particular concern?

<jasonjgw> Janina: APA has set up a community group to work on the accessibility of Web Payments. APA is striving to ensure that accessibility is fully covered. This technology will revolutionize how money is exchanged on the Web. It has the potential to bring new participants into the global economy.

<jasonjgw> Janina maintains taht we need to develop use cases and requirements related to the exchange of value - how it works and waht problems can arise for people with diverse needs and circumstances. This is an FYI for RQTF at present.

APA Decision on Payments CG is at:

http://lists.w3.org/Archives/Public/public-apa/2017Mar/0016.html

Web Technology Accessibility Guidelines checklist - request for review

https://www.w3.org/blog/?p=15777&shareadraft=baba15777_58ab5dba90f4e

<jasonjgw> http://w3c.github.io/pfwg/wtag/checklist.html

Emerging research questions: transformation of media to enhance accessibility

jb: There's a continuing suggestion being raised that W3C has left accessibility issues in EME unaddressed
... Every time we look at the specifics, this proves untrue
... However, interesting use cases have emerged
... Some of these use cases are apparently better dealt with at the OS level
... But there may be a browser role as well on some
... Meanwhile, there have recently been news stories where some ptople have tried to exploit certain vulnerabilities

<jasonjgw> Janina: a small amount of buffering would mitigate the computational load required.

jb: Wondering whether there's reasearch RQTF should review in this area?
... Suggest we return to this topic in upcoming mtgs.

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)

Present: shadi janina scott_h jasonjgw Judy
Found Scribe: janina
Inferring ScribeNick: janina

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

Found Date: 22 Mar 2017
Guessing minutes URL: http://www.w3.org/2017/03/22-rqtf-minutes.html
People with action items: 

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