18:46:43 RRSAgent has joined #silver 18:46:43 logging to https://www.w3.org/2021/02/05-silver-irc 18:46:46 RRSAgent, make logs Public 18:46:46 Meeting: Silver Task Force & Community Group 18:46:51 Meeting: Silver Task Force & Community Group 18:46:51 present: 18:46:51 chair: Shawn, jeanne 18:46:51 present+ 18:46:52 zakim, clear agenda 18:46:52 rrsagent, make minutes 18:46:52 I have made the request to generate https://www.w3.org/2021/02/05-silver-minutes.html jeanne 18:46:52 q? 18:46:52 agenda cleared 18:47:36 agenda+ More on the comment procedure 18:47:36 agenda+ asynchronous communication - ideas from other organizations 18:47:36 agenda+ subgroup updates 18:49:57 regrets+ Wilco, ChrisL, Peter, Bruce 18:49:58 Fazio has joined #silver 18:51:14 agenda+ Pre-CFC on Silver Requirements change 18:59:16 Chuck has joined #silver 18:59:48 agenda? 18:59:58 sajkaj has joined #silver 19:00:01 Lauriat has joined #silver 19:00:03 present+ 19:00:04 ToddLibby has joined #silver 19:00:12 Present+ 19:00:28 Present+ 19:00:32 agenda order is 4,2,1,3 19:00:41 present+ 19:00:52 KimD has joined #silver 19:01:24 I am mobile, I cannot scribe today 19:01:45 jennifer has joined #silver 19:01:50 present+ 19:01:51 Francis_Storr has joined #silver 19:01:56 present+ 19:02:20 zakim, take up next 19:02:20 agendum 4 -- Pre-CFC on Silver Requirements change -- taken up [from jeanne] 19:02:44 JF has joined #silver 19:02:50 Present+ 19:02:57 present+ 19:03:07 https://lists.w3.org/Archives/Public/public-silver/2021Feb/0023.html 19:03:24 Rick_B has joined #silver 19:03:40 scribe: Rick_B 19:03:44 Jeanne: is this the right place for notes? 19:03:57 broad accessibility support 19:04:00 All WCAG 3.0 guidance has tests or procedures so that the results can be verified. Some of this guidance uses true/false verification. In addition, WCAG 3.0 guidance includes other methods of measuring (for example, rubrics, sliding scale, task-completion, user research with people with disabilities, and more). This approach accommodates people whose needs are better reflected by a broad testing strategy, such as people with low vision, limited vis[CUT] 19:04:07 AngelaAccessForAll has joined #silver 19:04:07 present+ 19:04:14 present+ 19:04:15 and learning disabilities. 19:04:38 Azlan has joined #silver 19:05:23 zakim, take up next 19:05:23 agendum 2 -- asynchronous communication - ideas from other organizations -- taken up [from jeanne] 19:05:30 Jan has joined #silver 19:06:02 Ask: Pls share concerns re: above wording 19:06:59 SuzanneTaylor has joined #silver 19:07:13 Jeanne: l'ship has been reviewing survey & scheduling. Initial takeaway: people def want more async comms. 19:07:37 kirkwood has joined #silver 19:08:45 Jeanne: Not looking at this as a Tools problem since we have many tools, although some have A11y issues. 19:09:31 Jeanne: we're looking at other working groups for best practices around aync comms at global scale - where everyone can't make it to a specific meeting slot. 19:09:35 The same ways we currently do basically 19:09:41 q+ 19:09:53 ack Chuck 19:10:28 +1 to David F. 19:11:12 q+ 19:11:50 . hasn't got to level of meeting replacement (in fact it has created one extra mtg ;) 19:12:37 q+ 19:13:04 +1 with Slack and Chuck 19:13:04 ack Fax 19:13:09 ack Fazio 19:14:54 ack Rick_B 19:15:03 Rick_B: Quick intro, product accessibility at my org. 19:15:12 welcome rick 19:15:26 Welcome, Rick 19:15:28 Rick B: Similar to Oracle we have adopted Slack at scale. I don't think Slack has done away with any meetings, but it hasn't created any either. 19:15:57 Rick_B: It has potential. We may run an experiment where we run some channels for a meeting, and it would be time bound where individuals could contribute. 19:16:14 Rick_B: It's a complex endeavor. 19:16:21 The problem is how discussions might move around to different channels/tools and participants can't keep up 19:16:40 David Fazio: At airforce, create a suspense log with links to follow-ups. Perspective: current setup isn't too bad all things considered, v wary of adding additional tools. 19:17:21 Rick_B: Good things about slack, it looks pretty, and you can add work-flows and api's and 3rd party apps. Basically it's IRC in a new U/I. 19:17:27 q+ 19:17:40 +1 to DAvid - our communication is spread out *everywhere* 19:17:54 q+ 19:18:33 DavidFazio (I think): challenges from cognitive perspective. Slack = IRC with all its inherent limitations. 19:18:35 Present+ 19:19:00 ack Azlan 19:19:20 Azlan: need careful management vs. noise, easy to lose track. 19:19:57 Azland: combine Slack with RFC process @ Blackboard - has had some success. 19:20:19 Welcome and hello, Azlan! 19:20:55 ack KimD 19:20:56 ack kim 19:20:56 Commonwealth/UK/Aus accent takeover in process ;) 19:21:12 Hi Todd. Good to see a familiar face in the call. 19:21:39 Kim: use MS Teams. Great for single tool - meetings conducted within the tool. record in same channel. can also have conv there. highly integrated 19:21:41 that sounds a little better 19:21:59 RickB: Teams sounds v promising 19:22:16 Jeanne: will take back to l'ship. Thank you for ideas. 19:22:23 zakim, take up next 19:22:23 agendum 1 -- More on the comment procedure -- taken up [from jeanne] 19:22:35 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Procedure_for_Processing_Comments 19:22:42 We are also using Teams. It takes some getting used to coming from being used to Slack but yes it has good features. 19:22:47 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Procedure_for_Processing_Comments 19:23:32 Rachael: 1st working draft is out. We need to start processing feedback. Plan to do this a few times a year w standard process. 19:25:54 Rachael: Steps: (1) Triage - 2 or 3 people from l'ship team/assigned triagers, will add emails into github. add labels, relay to appropriate people. (2) Issues assigned to sub-groups - subgroup will create response in github/g docs. Add label and back to triage team. (3) Then weekly survey to task force to review all issues (4) any issues where concerns will be reviewed in AG meeting, possibly sent back to group (5) if approved, will merge in. 19:26:47 bravo Jeanne! 19:27:06 Jeanne: also - groups with a guideline or a section, I have created a section FPWD comments on your wiki page. Has link to filtered view in github. Hope makes github both more accessible and usable. 19:27:16 q? 19:29:02 Janina: labels function in github v handy to narrow scope. If you are brave - command line can also work 19:29:25 DavidFazio: training sounds great, takes some getting used to 19:29:55 Jeanne: will share existing training resources (Action Item) 19:30:13 action: jeanne to find the github training recordings and post them on the home page. 19:30:15 Janina: email is also a v handy interface for hithub 19:31:01 Jeanne: one of training sessions is for email as a UI for github 19:31:03 agenda? 19:31:40 that's ambitious LOL 19:31:50 Jeanne: will be asking for issue response turn-around in 2 weeks. 19:32:10 I know. Just workload 19:32:40 Jeanne: don't panic though - just email l'ship team to let them know if can't meet 2 week SLA and they can help 19:32:48 It's good to set deadlines though 19:33:21 We can also respond with "Golly, that's a big topic that'll take a bit longer." on the issue to not leave people in the dark. 19:33:22 Jeanne: for example - v complex issues may require a specific meeting (e.g. writing an new building code for the WWW ;) 19:33:22 We want to avoid items sitting in queue and the queue growing too large 19:33:40 +1 19:34:35 Jeanne: I am labeling issues, hard to keep up, have closed a bunch but still some gaps. Now @ 48 open issues 19:34:39 q? 19:34:43 q+ 19:35:20 Rick_B: If you need help with labelling, I'm available. Happy to help. One other thought... 19:35:35 Rick_B: Even if you don't send a detailed response, give some form of acknowledgement in a day or 2. 19:35:48 Can we set autoreply?? 19:35:59 q+ 19:36:04 ack Rick 19:36:37 Rick_B: A one sentence response is friendly and open. 19:36:42 Jeanne: goal is to do as much of review async as poss 19:36:51 q+ 19:37:04 Deadline is a couple of weeks out (Feb 21), prep yourselves for a deluge at the last minute 19:37:46 ack Chuck 19:38:26 Q+ 19:38:39 Chuck: good practice to add an auto-reply, a bit of a human touch. label is fine as a fall back. Nice to say "A human has heard this - we will work on it"! 19:38:49 ack Fazio 19:38:53 ack Faz 19:38:57 ack Rach 19:39:48 Rachael: Comments received around language use! Beware curse words 19:40:17 ? Will rename 'master' -> 'main' 19:40:20 ::applause:: 19:40:36 +1 on positive critique! 19:40:41 q+ 19:41:30 zakim, take up next 19:41:30 I see a speaker queue remaining and respectfully decline to close this agendum, jeanne 19:41:36 ack faz 19:41:38 Topic: updates from sub-groups 19:41:53 zakim, take up next 19:41:53 agendum 3 -- subgroup updates -- taken up [from jeanne] 19:42:05 Maturity model 19:43:20 David: Maturity model subgroup: moved from complex s'sheet to more readable working doc. Jake will review @ ING, created doc w scoring system which mirrors silver. Looking v good, goal is to flush out a dimension all the way through, then review w group. 19:43:56 Clear Words 19:44:43 Jan: Clear words subgroup - we are disbanding, moving on to coga guidelines will meet mid-feb on that. Also met w Wilco to get support from ACR re: testing. Pulling in research to guide testing. 19:45:30 @Jan - pls LMK if I didn't get the gist right in my notes 19:47:16 Latest Maturity Model Dochttps://docs.google.com/document/d/1NKp9iem6_ObNZJWbM7J6ZXJ2oNnW_eUT/edit It does not include the scoring spreadsheet yet though, which is very exciting 19:47:42 Jeanne - scheduled presos on WCAG 3, did 2 this week! Some tech challenges, but presos went v well, feedback v pos. V pos feedback re: point system. 19:47:44 https://docs.google.com/document/d/1NKp9iem6_ObNZJWbM7J6ZXJ2oNnW_eUT/edit 19:47:54 ^ Draft Maturity mode doc 19:48:15 ^^ Draft Maturity modeL doc 19:48:30 @Rick_B - you got it right. The only correction is ACT vs. ACR. Wilco is a chair of the Accessibility Conformance Testing (ACT) group and he's helping us pull together some research to help us address testing for cognitive guidelines 19:49:24 Final call for sub-groups ... 19:49:35 agenda? 19:49:38 Any questions for sub-groups? 19:49:46 zakim, close this item 19:49:46 agendum 3 closed 19:49:47 I see nothing remaining on the agenda 19:50:08 https://docs.google.com/document/d/1NKp9iem6_ObNZJWbM7J6ZXJ2oNnW_eUT/edit#heading=h.5xzi61jztuzi 19:51:15 q+ 19:51:58 David Fazio - maturity model doc, dimensions (see this specific heading link). Invites comments. Suggestion from Jeanne that doc could be clearer, she would be delighted to join mtg next week. 19:52:10 ack Chuck 19:52:59 Chuck: update from l'ship group - working on requirements for a product mgr role for silver task force, will share, and then if anyone is interested they can reach out. 19:53:54 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Substantial_Conformance 19:54:36 Janina: Conformance sub-group - discussing candidate use cases was extremely useful, led to creation of new ones. That is our focus right now. We are still on target for our published timeline. See wiki link above, key link is the G Doc link you can find there. Welcome to join at 12 noon EST. 19:55:01 Jeanne: let me know when you would like to join the main groups mtg to share 19:55:32 rrsagent, make minutes 19:55:32 I have made the request to generate https://www.w3.org/2021/02/05-silver-minutes.html jeanne 19:55:56 ToddLibby has joined #silver 19:56:25 rsagent,makeminutes 19:56:59 rrsagent, make minutes 19:56:59 I have made the request to generate https://www.w3.org/2021/02/05-silver-minutes.html Rick_B 19:57:54 https://docs.google.com/document/d/1zDV9uZEryZc2OeM88QLOYu9KCsqaUxspeBqc-foq648/ 20:55:50 kirkwood has joined #silver 21:05:51 jeanne has joined #silver