14:50:57 RRSAgent has joined #html-a11y 14:50:57 logging to http://www.w3.org/2015/07/30-html-a11y-irc 14:50:59 RRSAgent, make logs world 14:51:01 Zakim, this will be 2119 14:51:01 I do not see a conference matching that name scheduled within the next hour, trackbot 14:51:02 Meeting: HTML Accessibility Task Force Teleconference 14:51:02 Date: 30 July 2015 14:51:35 agenda? 14:51:41 zakim, clear agenda 14:51:41 agenda cleared 14:51:45 agenda+ Identify Scribe http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List 14:51:48 agenda+ Agenda Edits & Additions 14:51:51 agenda+ Web Payments Accessibility -- Shane, Manu 14:51:53 agenda+ Canvas 2D Level 1 Progress -- Rich, Mark, Janina, Paul, PLH 14:51:56 agenda+ Alt Doc Update -- Shane, Liam 14:51:58 agenda+ Transcript Support Update -- John, Chaals, Cynthia 14:52:01 agenda+ Tab Panels Update -- Leonie, Et Al 14:52:03 agenda+ Bug Triage -- Leonie 14:52:06 agenda+ TF Open Actions http://w3.org/wai/pf/html/track 14:52:08 agenda+ Other Business 14:52:11 agenda+ be done 14:52:24 present+ Janina 14:52:31 zakim, next item 14:52:31 agendum 1. "Identify Scribe http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List" taken up [from janina] 14:56:38 IanPouncey has joined #html-a11y 14:58:23 paulc has joined #html-a11y 14:58:40 Thanks, Shane. You're near the top on the TF agenda for Web Payments 14:59:01 We can take up other items until you get there. No one on the call just yet 14:59:41 Judy_ has joined #html-a11y 15:00:54 Judy_ has changed the topic to: HTML Accessibility TF 15:01:16 Ryladog_ has joined #html-a11y 15:02:31 uggh - what's the webex code 15:02:32 David_ has joined #html-a11y 15:02:55 its not in the agenda 15:03:32 manu has joined #html-a11y 15:03:41 present+ ShaneM 15:03:43 Present+ Manu 15:04:17 Present+ Judy 15:04:31 Scribe: David_ 15:04:35 present+ paulc 15:04:39 Present +David 15:05:09 zakim, next item 15:05:09 agendum 2. "Agenda Edits & Additions" taken up [from janina] 15:05:09 present +IanPouncey 15:05:55 Present+ Katie Haritos-Shea 15:05:55 zakim, next item 15:05:55 agendum 2 was just opened, janina 15:06:02 zakim, close this item 15:06:02 agendum 2 closed 15:06:03 I see 8 items remaining on the agenda; the next one is 15:06:03 3. Web Payments Accessibility -- Shane, Manu [from janina] 15:06:06 zakim, next item 15:06:06 agendum 3. "Web Payments Accessibility -- Shane, Manu" taken up [from janina] 15:06:46 Janina: Manu and shane will introduce web payments update. main topic today 15:07:44 present+ Liam 15:07:56 q+ for after Shane and Manu present 15:09:32 Shane: overview. lots of activity for years, there are two separate related activities, credential activity, web payment activity charter effort. a oot going on a11y concern from day 1 ive been involved from beginning. 15:11:12 Manu: thanks for the invite. there are 2 initiatives, 1)credentials, oroving who you are, drivers licences shipping address age, 2) payments both have community groups nad also a web payment working group and interest group 15:11:36 Payments is chartered, we know a11y is important, and looking for guidance form html5 15:12:30 Web Payments Interest Group 15:12:30 http://www.w3.org/Payments/IG/ 15:12:32 Manu: examples. request from staff contact web paments that it is clear that a11y group establish relationship, do reviews and provide advice for adequat if not exenlt way. 15:12:39 Present+ Rich 15:13:02 paymwents, goole, bloomber, rob a bank us treasury etc... wide interest from key players 15:13:21 Web Payments Vision 15:13:21 http://www.w3.org/Payments/IG/Vision 15:13:48 Web Payments Roadmap 15:13:48 http://www.w3.org/Payments/IG/Roadmap/ 15:13:56 The output has vbeen vision, roadmap , use cases http://www.w3.org/Payments/IG/ http://www.w3.org/Payments/IG/Vision notice access to all, have a road map for 1.0 15:14:06 http://www.w3.org/Payments/IG/Roadmap/ 15:14:09 q? 15:14:16 q+ 15:14:21 Msnu: big space, trying to be focused in v1 15:14:57 payment flow, unifying it, standard way to initiate, standard fromto wallet, standard response that payment has been made, 15:15:17 for a11y as part of the flow, want to provide hooks that people can use their own devices 15:15:47 concerned about commerce flow 15:16:24 Manu: Katie and Shane, and Leonie have all provided good feedback to group to date 15:16:42 s/good/excellent/ 15:17:34 s/Msnu/Manu/ 15:18:16 katie: want to build off what manu said about specifoc guidance and API being, have to go further for multiple form factors, I'm concerned stuff that gets in sometimes disappears, Manu has been great and won't let it slide ... sometimes perhpas critics feel it is too generic... but I'll fight for it because 15:18:43 q? 15:18:56 some on the groups feel a11y is fluff, but I try to ensure that banks understand thay they have accountabioity for this 15:19:04 ack Ryladog_ 15:19:04 Ryladog_, you wanted to discuss after Shane and Manu present 15:19:09 q+ to respond to Janina 15:19:14 JS: Process, scope and procedure questions to ask 15:19:38 ack r 15:19:41 JS:Process manu are all of the community groups under our care ... 15:19:41 ack j 15:20:10 LJWatson has joined #html-a11y 15:21:24 Manu: credentialling is at risk, trying to find a new way rather than all of the form field. a credential would have all that metadata, but browser vendors, very loud don't want credentials to get in the way of payments. f2f in NYC, this came up so we circled around and proved to w3C thqt credentially is important to web 15:21:44 Menu: Payments has quite a bit of steam W3C didn't want to interfere 15:22:08 We hope credentials will follow in 4-6 months, but no real relationship right now 15:22:36 JS: Scoping: do we use the same technology at the gas pump or only web sites 15:23:07 manu: careful about scoping ... today only about browsers, some group member hope it will become ubiqutous 15:23:30 but currently just the web,... for a11y it would be a huge issue. 15:24:29 National assoc of convenience store, nnexux, merchants advisory group, target and Wallmart... expectation is thatnpeople can bring their own divices and execute exchanges, this is the long term vision 15:25:08 JS: Suggestion- the media work we did specified user requiremnts for media, do we want to do something similar for web payments 15:25:10 q? 15:25:15 q- 15:25:55 Web Payments Working Group Draft Charter 15:25:55 http://www.w3.org/2015/06/payments-wg-charter.html 15:26:32 q+ 15:26:36 q? 15:26:45 Manu: a couple places, I went through docs to find discussion of a11y ... didn't find much in vision and roadmap, in charter only one place we call it out, where we discuss this groups participation. we are looking for charter suggestions in august for the review of the charter 15:27:09 Great idea Shane. +1 15:27:22 we don't have enough exoerts to push it as a main work product, so we want you to tell us what to do the stregnthen the relationship between our groups 15:28:32 q? 15:28:36 JB: Ian Jacobs met with me last week, ahead of Mgmt review, i concur the intent to work well. I support requiremtns doc shane mentioned, I feel that this is needed, and would like to translate it to work items 15:28:44 ack J 15:28:55 Web Payments Use Cases 15:28:55 https://dvcs.w3.org/hg/webpayments/raw-file/default/WD/use-cases/2015-07-28/Overview.html 15:29:28 Manu: Use cases document https://dvcs.w3.org/hg/webpayments/raw-file/default/WD/use-cases/2015-07-28/Overview.html this is where we start. the other docsare high level. Here we get more concrete 15:29:31 s/would like to/think it's needed in order to/ 15:30:32 every single use case, broken out two big sections, we discuss payment flows, one general abstract flow, 4 stages, negotition of terms... i'm offereing basket for 15Us accept bit coin 15:31:27 2) Customer selects payment means, if there is a match it goes ahead, we expect many wallets in market, expect some to have better a11y than others 15:31:56 q? 15:32:08 3) .... 4) machine readable. (see document for better desciption) 15:33:37 Manu: biometric use case, incurred biometric rather than password, ... give motivation, and add anote for a11y ... not everyone can provide fingerpring or e 15:34:02 or eyescanning.... therefore have mulitple modalities 15:34:15 q? 15:34:21 ask the group to look at all use cases and take them into account 15:34:24 q+ to ask about API specs 15:34:28 q+ 15:34:28 https://dvcs.w3.org/hg/webpayments/raw-file/default/WD/use-cases/2015-07-28/Overview.html#uc-biometric 15:34:35 ack sh 15:34:35 ShaneM, you wanted to ask about API specs 15:34:56 q+ 15:35:20 q+ to mention implementations being the best way to understand whether solutions are accessible. 15:35:48 shaneM: On Web payments, API specs, there are lots of specs that come out, and will have API, and we've had trouble, that we don't know what they do... 15:36:38 SM: If there is feedback we can give to help articulate requirements and pecs of the API please let us know (Ian Jacobs) 15:37:48 JS: We've seen tons ofncode but if wendon't wse the problem stated in prose, and manyna11y don't understand it and hard to know whether it meets what it sets out to meet. If the code is understandable but without text about what it is doing then problematic. 15:38:16 q? 15:38:20 ack r 15:38:24 JS: Spec writing with a11y in mind. We can create a document of how to lay out a11y soecs in specifications 15:39:19 +1 to Katie's suggestion - would love to see that. 15:39:20 Katie: Suggest, go to link manu gave, for the personas, if we could have this group provide a persona for each use case that could be a good starting place 15:39:21 ack ju 15:40:16 ack m 15:40:16 manu, you wanted to mention implementations being the best way to understand whether solutions are accessible. 15:40:29 I think that the AOI for IAN came from conversation last week, the way APis are written is evolving, i support shane's suggewtion of us spelling outnin a document what the AOI shpuld spell out a11y 15:40:29 q+ 15:41:15 q? 15:41:20 s/AOI/API/ 15:41:22 s/AOI/API/ 15:42:17 Manu: i get that, o don't know how to map the web IDL ... we don't really know that until we do an implementation. that's the best way to discover if the web IDL is ok, but that is moneyand time. Our org could work with this group to do this, but it's time and money and our org has shifting prioritites, so if this group could ask for implementation and ask for proof we could get some traction 15:42:29 q+ to talk about lack of robust a11y interfaces in mobile devices 15:42:33 of finding out if the API is accessiboe 15:42:36 ack ju 15:43:13 JB: I also concerned, we don't have a lot of resources, but we can provide good input if the work areas can share that work 15:44:50 JS: +1 PF have agreed we will morph, not sure how but expect there will be a TF or some way to review. Exciting to me.... use case suggested by Manu is a good place to start 15:45:13 JS: on mobile, i'm struck how interface is for critical things, in mynexperience 15:46:15 q? 15:46:19 ack ja 15:46:19 janina, you wanted to talk about lack of robust a11y interfaces in mobile devices 15:46:23 JS: example, hard to enter digist with a screen reader on a phone, times out early, unacceptable, can't have this lack of robustness, this doesn't happen on desktop anymore 15:46:34 Sounds like a requirement for the PAUR 15:46:52 yup 15:46:59 Manu: thanks tonshane for the invite, that's all for me, thanks to those who've 15:48:24 1) liaison w/ payments 15:48:31 2) liaison w/ credentialling 15:48:36 3) comments on charter 15:48:43 4) comments on use cases 15:49:03 Action item for this group figure out liaison with payments group (2) comment on charter 3) comment on use cases. And roll those into the credentials as they roll out) 15:49:03 Error finding 'item'. You can review and register nicknames at . 15:49:10 q? 15:49:30 s/figure/1) figure 15:49:55 JS: excited and interested to work together. I'm lookingnforward and others too 15:50:23 Shane: wep payments wil be a atoac as will we 15:50:44 s/atoac/TPAC 15:52:05 Suporo Japan 26 Oct 2015 15:52:20 agenda? 15:52:52 zakim, next item 15:52:52 agendum 4. "Canvas 2D Level 1 Progress -- Rich, Mark, Janina, Paul, PLH" taken up [from janina] 15:53:02 JS: Thanks to Shane and Manu 15:53:14 JS: Canvas 2D 15:53:52 See note/summary/ask from Philippe: https://lists.w3.org/Archives/Public/public-html-a11y/2015Jul/0047.html 15:54:01 https://lists.w3.org/Archives/Public/public-html-a11y/2015Jul/0047.html 15:54:59 First item in plh's email is https://github.com/w3c/2dcontext/issues/10 15:55:46 Rich: " Philippe... There's no "inform the user of the removal of the region" step, which 15:55:47 is odd, given the parallel for informing the user when it was added.update less of an issue, cause keep location" I don't think this is a big issue 15:56:46 We did report defect to google, dominique will get it fixed, which is good. athere is a feature in main html soec that says the content has to reside in fallback area 15:56:52 I have to look at that 15:58:04 JS: Philippe is checking this while on vacation can we move forward. Philippe hoping we could do that next week, 15:58:18 q? 15:58:19 Rich: I'll go with Ohilippe 15:58:56 that if Google knows its a bug and acknowledges then we can move forward 15:59:00 Plh gave ttps://github.com/cptvitamin/wpt-canvas/pulls but there are no pull requests there. 15:59:14 s/ttps/https/ 15:59:28 https://github.com/cptvitamin/wpt-canvas/pulls 15:59:40 s/ohilippe/Philippe 16:00:05 Rich: I'll test them... 16:00:31 https://www.w3.org/wiki/HTML/Canvas_Task_Force/CR-Test contains the test results and should be usable to find the "missing" 3 tests 16:00:39 Paulc: Rich please rely to phillipe online 16:00:54 s/rely/reply 16:01:55 Zakim, list attendees 16:01:55 sorry, David_, I don't know what conference this is 16:02:17 zakim, bye 16:02:17 Zakim has left #html-a11y 16:02:18 zakim, who's here? 16:03:33 Present+ Katie 16:03:39 Present+ Judy 16:03:44 Present+ Paul 16:03:50 Present+ Janina 16:03:56 Present+ Shane 16:04:10 Present: David_MacDonald 16:04:22 Present+ Leonie 16:04:49 Present+ Joanie 16:05:05 Present: Liam Quinn, David MacDonald, Paull Cotton, Shane Mc, Judy Brewer, Janina S, Rich S., ManuS, Ian Pucey Katie HS. , Leonie watson, 16:05:14 s/Quinn/Quin/ 16:05:28 s/Paull/Paul/ 16:05:43 s/Pucey/Pouncey,/ 16:06:00 s/Pucey/Pouncey 16:06:12 zakim, bye 16:06:24 rrsagent, make log public 16:06:32 rrsagent, make minutes 16:06:32 I have made the request to generate http://www.w3.org/2015/07/30-html-a11y-minutes.html David_ 16:11:02 I have made the request to generate http://www.w3.org/2015/07/30-html-a11y-minutes.html liam 16:28:50 MichielBijl has joined #html-a11y 18:40:10 Judy has joined #html-a11y 18:51:08 richardschwerdtfeger has joined #html-a11y 19:15:53 Judy_alt has joined #html-a11y 20:57:51 richardschwerdtfeger has joined #html-a11y 21:52:05 liam has joined #html-a11y 23:11:56 Judy has joined #html-a11y