13:52:32 RRSAgent has joined #rqtf 13:52:32 logging to http://www.w3.org/2017/02/15-rqtf-irc 13:52:34 RRSAgent, make logs world 13:52:34 Zakim has joined #rqtf 13:52:36 Zakim, this will be 13:52:36 I don't understand 'this will be', trackbot 13:52:37 Meeting: Accessible Platform Architectures Working Group Teleconference 13:52:37 Date: 15 February 2017 13:53:30 agenda+ Alternatives to CAPTCHA 13:54:37 agenda+ Web of Things - Use Cases and Requirements: Next Steps 13:55:09 agenda+ Miscellaneous topics, literature, etc. 13:55:20 present+ jasonjgw 13:58:14 scott_h has joined #rqtf 13:59:01 Judy has joined #rqtf 14:04:01 present+ 14:04:05 scribe: shadi 14:04:07 present+ 14:04:22 present+ 14:04:26 agenda? 14:05:02 zakim, take up next 14:05:02 agendum 1. "Alternatives to CAPTCHA" taken up [from jasonjgw] 14:05:08 zakim, take up agendum 1 14:05:08 agendum 1. "Alternatives to CAPTCHA" taken up [from jasonjgw] 14:06:01 JW: did some reading and added some reference sources to the wiki page 14:06:26 ...found master's thesis that attracted quite some citations 14:06:51 q+ 14:06:52 ...talking about biometric mechanisms for authentication 14:07:13 q+ to note Scott's updated collection of CAPTCHA alternatives 14:07:25 ...also another paper describing alternatives 14:07:40 ...including detecting the behaviour of scripts and programs 14:08:05 ...rather than trying to keep them out, try to detect them 14:09:01 ...like timing of key strokes and keyboard focus that could distinguish behaviour 14:09:18 ...but may also raise accessibility considerations in themsevles 14:09:46 ...for example interaction by assistive technologies could trigger the algorithms 14:09:55 ack j 14:09:55 Judy, you wanted to note Scott's updated collection of CAPTCHA alternatives 14:10:08 JB: Scott Hollier sent useful email last night 14:10:48 SH: went through all CAPTCHA references 14:11:09 ...existing CAPTCHAs are not as secure as they thought 14:11:26 ...research says ~20% can be cracked by mere brute force techniques 14:11:45 ...alternatives like visual identification could be problematic 14:12:25 ...anectodal evidence that reCAPTCHA is fairly accessible 14:12:51 ...one paper focused specifically on usability 14:13:07 ...current approaches mostly focused on desktop concept 14:13:24 ...also another approach of gamification seemed interesting 14:14:00 ...separated papers into "alternatives" and "issues with CAPTCHA" 14:14:04 q? 14:14:11 q+ 14:14:25 ack j 14:15:23 JB: what is the question we are trying to answer? 14:15:45 q+ 14:15:45 ...what are the better alternatives to elevate to APA? 14:15:48 q+ 14:17:05 JW: identifying alternatives 14:17:20 ...several areas where APA can update their materials 14:17:50 shwetank has joined #rqtf 14:18:01 scribe: janina 14:18:11 present+ shwetank 14:18:39 q? 14:19:12 SD: head of research and innovation at BarrierBreak 14:19:22 ...looking forward to contributing to this group 14:19:34 [welcome to the group shwetank] 14:19:58 shadi: Suggest identifying the available alternatives before raising to APA 14:21:03 shadi: Noting it's also good usability practice, and we should include usability in the scope of what we recommend to say 14:21:28 queue= 14:21:50 JS: existing APA document does explain the general usability issues 14:21:57 ...different remedies 14:22:15 ...most useful would be drafting up sections 14:22:24 q+ 14:22:25 ...can follow the existing approach and language 14:22:48 ack j 14:23:08 JB: putting draft work onto RQTF 14:23:20 ...trying to avoid this 14:23:29 ...don't want to add process issues 14:23:39 ...but want to manage scope of work 14:24:04 ...would it be sufficient to pass back the outcomes of the literature reviews? 14:24:05 q+ 14:24:49 JS: unless RQTF has concerns about the current structure 14:25:00 ...but drop off the references in the right location 14:25:28 ...in the same logical flow to highlight where the updating needs to happen 14:26:52 q+ 14:26:58 ack ja 14:28:25 queue= 14:28:35 JB: what are the candidates so far? 14:28:44 ...or maybe discuss this on the list 14:28:54 q+ 14:29:13 s/what are the candidates so far/which of the candidate options seem best so far? 14:29:23 ack sco 14:29:49 q+ 14:30:04 q+ 14:31:12 ack ju 14:32:11 JB: linking back to the statistical findings could be useful 14:32:29 ...maybe Google may be willing to share their accuracy rate 14:33:10 ...could be an important point to highlight 14:33:21 ...could also share with the community through WAI IG 14:33:29 ...often get questions on CAPTCHA 14:35:30 [side discussion on tooling] 14:35:51 SH: 20% figure comes from issues with current CAPTCHA 14:36:16 Judy has joined #rqtf 14:36:25 JB: so 20% inaccurate? 14:36:28 SH: yes 14:37:30 q? 14:38:02 The new captcha's sometimes use a different approach (like having a 3x3 grid of squares) with a different image in each sqaure. And then asking the user to click and highlight all the sqaures according to a certain criteria (like highlight all ones which contain a picture of a building) etc. It might be easy to internationalize it, but challenges should be there for cognitive disabilities 14:38:17 ack jas 14:38:34 JW: needing to move an object as CAPTCHA 14:38:50 ...was not accessible for many users 14:39:36 ...not clear to me which alternatives are most valuable 14:40:26 ...Google approach was cited several times 14:40:38 ...asks you to simply check a box 14:40:55 ...but tries to detect certain parameters 14:41:25 q? 14:41:28 ...with fallback procedure when there is suspicion 14:41:46 ...may be good to find documentation on that 14:42:04 JS: web authentication pointed out that it is always a balance 14:42:28 ...at the end it is a heuristic decision that is made 14:42:57 q+ 14:43:45 ...like the idea of just checking a box 14:44:09 ack me 14:45:22 SAZ: what was the primary target audience of the previous document and did it change? 14:45:36 ...think back then we assumed website owners provide CAPTCHAs 14:45:52 ...but meanwhile many third-party service providers 14:46:04 JS: good point, need to check that 14:46:31 JW: may also have privacy implications on third-party services 14:47:18 JS: good point too 14:48:44 zakim, take up next 14:48:44 agendum 2. "Web of Things - Use Cases and Requirements: Next Steps" taken up [from jasonjgw] 14:49:39 JW: so far analyzing use cases and put forward requirements 14:50:35 shadi: Believe we're still at least a step away from defining use cases 14:51:04 shadi: We need more detail 14:51:44 shadi: Also more examples and more situations 14:52:08 shadi: We want to highlight different aspects 14:53:07 JW: maybe action to elaborate these descriptions 14:53:36 s/defining use cases/defining requirements 14:55:36 SAZ: can we get to a point where can be comfortable sharing with the IG? 14:55:54 JW: maybe elaborate existing use cases first? 14:56:31 zakim, take up next 14:56:31 agendum 3. "Miscellaneous topics, literature, etc." taken up [from jasonjgw] 14:57:04 JW: didn't discuss web authentication, though touched on it 14:57:19 ...but also didn't discuss personalization 14:58:09 trackbot, end meeting 14:58:09 Zakim, list attendees 14:58:09 As of this point the attendees have been jasonjgw, shadi, scott_h, Judy, shwetank 14:58:17 RRSAgent, please draft minutes 14:58:17 I have made the request to generate http://www.w3.org/2017/02/15-rqtf-minutes.html trackbot 14:58:18 RRSAgent, bye 14:58:18 I see no action items