11:49:37 RRSAgent has joined #silver 11:49:37 logging to https://www.w3.org/2022/08/12-silver-irc 11:49:40 RRSAgent, make logs Public 11:49:40 Meeting: Silver Task Force & Community Group 11:49:50 present: 11:49:50 chair: Shawn, jeanne 11:49:50 present+ 11:49:50 zakim, clear agenda 11:49:50 rrsagent, make minutes 11:49:50 I have made the request to generate https://www.w3.org/2022/08/12-silver-minutes.html jeanne 11:49:50 q? 11:49:50 agenda cleared 11:50:10 agenda+ AG WG agenda preview 11:51:27 agenda+ announce digital publishing salon on 8 September 11:53:09 agenda+ Use functional needs or user needs to develop the Exploratory material? 11:53:22 Do we write Outcomes before tests? 12:12:54 agenda+ Do we write Outcomes before tests? 12:12:59 s/ Do we write Outcomes before tests?// 12:13:06 rrsagent, make minutes 12:13:06 I have made the request to generate https://www.w3.org/2022/08/12-silver-minutes.html jeanne 12:13:57 regrets+ Jemma, Makoto 13:28:23 stevelee has joined #silver 13:54:15 Lauriat has joined #silver 13:54:19 agenda? 13:54:27 Present+ 13:58:52 Chuck_ has joined #silver 13:59:32 Azlan has joined #silver 14:00:38 Poornima has joined #silver 14:01:45 present+ 14:02:29 janina has joined #silver 14:02:32 present+ 14:02:32 present+ 14:02:47 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Scribe_List 14:03:28 scribe: janina 14:03:28 present+ 14:04:44 zakim, next item 14:04:44 agendum 1 -- AG WG agenda preview -- taken up [from jeanne] 14:04:45 maryjom has joined #silver 14:05:03 present+ 14:05:21 jeanne: AG hosting an extended time mtg next week beginning 10:30 Boston, all on WCAG 2.2. So, FYI! 14:05:22 q+ 14:05:34 jeanne: Meeting will run until 13:30 with a break midway. 14:05:56 ack Ch 14:06:10 Chuck_: Notes no WCAG 3 content, but anyone with 2.2 interest, it's important to come! 14:06:13 zakim, next item 14:06:13 agendum 2 -- announce digital publishing salon on 8 September -- taken up [from jeanne] 14:06:25 https://www.w3.org/2022/09/digpubsalon 14:06:39 jeanne: Looking at the future of digital publishing 14:06:45 ToddL has joined #silver 14:07:02 Tuesday September 8, 8 AM - 12 PM PDT 14:07:06 jeanne: Tuesday 8 September, 08:00-Noon PT (UTC -700) 14:07:22 present+ 14:07:33 janina: Is this during TPAC? 14:07:42 Jeanne: No, this is the Thursday before TPAC. 14:08:10 janina: Notes confusing calendering! 14:08:15 jeanne: We'll have to find out! 14:08:19 Jeanne will look into the correct time/date 14:08:53 jeanne: Covering many innovative issues which are likely to have an impact on WCAG 3. 14:09:02 janina: +1; knowing about some of those issues! 14:09:19 zakim, next item 14:09:19 agendum 3 -- Use functional needs or user needs to develop the Exploratory material? -- taken up [from jeanne] 14:09:48 Writing Process home page -> https://github.com/w3c/silver/wiki/Writing-Process 14:10:00 jeanne: Notes above URI is writing process page 14:10:18 Overview of WCAG3 Writing Process by Maturity Levels -> https://docs.google.com/document/d/1iu3-vr2vMoDxr0YjwSEQsuOMjTzQxh1ODgRd57Ea-i8/ 14:10:46 jeanne: Notes last week we stopped on a todo item deep in the weeds -- we'll get there shortly 14:11:07 jeanne: Instead look by maturity models and note grid: 14:11:17 Table -> https://docs.google.com/document/d/1iu3-vr2vMoDxr0YjwSEQsuOMjTzQxh1ODgRd57Ea-i8/edit# 14:11:31 jeanne: Hopes this makes the process more understandable 14:11:36 Corrected link to table -> https://docs.google.com/document/d/1iu3-vr2vMoDxr0YjwSEQsuOMjTzQxh1ODgRd57Ea-i8/edit#heading=h.rzl1gosh09i3 14:12:54 jeanne: Notes proposal is to use migration doc for 2.x content being migrated -- to bring in as placeholder content 14:13:12 jeanne: i.e. the work is already done 14:13:33 jeanne: Then for exploratory, we'll take user needs identified through migration review and refine them 14:13:59 jeanne: Notes we had specific user needs; very detailed 14:14:08 jeanne: Seems appropriate to Exploratory 14:15:14 jeanne: guidelines may migrate--so we do them later 14:15:56 jeanne: asks whether this explains things? 14:16:06 jeanne: Specifically asks SL 14:16:19 Lauriat: Table breakout is really helpful 14:16:43 Lauriat: Might also help to get into doing some by way of example 14:17:12 jeanne: Functional Needs or User Needs to develop examples? 14:17:20 Last weeks example 1.4.2 -> https://docs.google.com/document/d/1oXqNZ22r1qDToD1mP0-0h3dOe9JqHkO09o9o2vcWJYc/edit 14:18:10 jeanne: notes 1.4.2 audio controls 14:18:12 q+ 14:18:42 jeanne: Am struggling with the functional needs as currently setup 14:19:09 q+ to say I think we need the intersections, not one or the other 14:19:14 ack janina 14:19:19 Janina: I think brought up a point that is a valid point and it's missing in 2.2. 14:19:44 Janina: It wasn't specifically an audio control. Navigate semantically. 14:20:04 Janina: We won't succeed if we have "next" and "previous". 14:20:16 Janina: There's been more than this for the past 25 years. 14:20:41 Janina: Not specifically an audio control. Video controls and media in controls in general, don't know if we have it broken out that way. 14:21:00 Jeanne: Only audio controls by definition. 14:21:12 Jeanne: Are you suggesting we add a new guideline or subguideline? 14:21:21 Janina: If we are migrating existing content, let's leave it. 14:21:37 Janina: We will need a better concept of semantic navigation at some point. 14:21:49 Janina: CSS is ready to talk to APA about this. 14:22:02 Jeanne: That gets away from the question. 14:22:26 Janina: If we are migrating, let's stick to audio. We do need a plan for other stuff, but for now we are migrating what's available. 14:23:00 Jeanne: For this project, it's to update the writing process. 1.4.2 is just an example for the writing process. to make it more agile. The original writing process was very waterfall. 14:23:27 Jeanne: We want to make sure that how we are doing the writing process going forward is more agile that maps to the maturity levels that AG has agreed to for how we develop content for WCAG 3. 14:23:35 Jeanne: 1.4.2 is an example. 14:23:55 Jeanne: Are functional or user needs sufficient to be developing the user needs we need for the writing process? 14:24:03 q+ 14:24:21 jeanne: Notes looking at 1.4.2 as an example of how the writing process works 14:24:36 ack Lau 14:24:36 Lauriat, you wanted to say I think we need the intersections, not one or the other 14:24:37 ack laur 14:24:54 Lauriat: think we need both functional and user needs in order to capture the important intersections 14:25:08 ack Ch 14:25:18 Lauriat: will help us test what needs coverage 14:25:19 Shawn touched on my points. 14:25:19 Example of what Errors subgroup did on User Needs -> https://docs.google.com/spreadsheets/d/1BEzSKUsoMQZAwLY5uM5T4Jk7vqKruQT8EaheijQJ7nk/edit#gid=1269671282 14:26:22 Janina: In the functional needs or user needs, do they capture...? 14:26:40 Shawn: Getting more specific is boiling the ocean, and we may cover some things and miss others. 14:26:55 Lauriat: concerned that becoming more specific would be boiling the ocean 14:27:05 Chuck_: Do both have value? 14:27:44 jeanne: reads from user needs 14:28:08 janina: so users need to be able to navigate through semantic structures semantically; not just by time offsets 14:28:24 +1 14:29:07 Janina: My response is it's not boiling the ocean, there's a lot of art and specificity built in. If you have semantic structures, you need to cover the details. 14:29:49 Janina: I can provide a specific example. I obtained a book that had only "next" and "previous" chapter of bible, it's not very usable. 14:30:16 Jeanne: Are you recommending we write on the user process? Are you suggesting we need more detailed user needs? 14:30:33 Janina: In the audio example this whole concept was missing. This was a major enhancement that was missing. 14:30:49 q+ to ask what research we have from the original SC that we can reference for this 14:30:56 Janina: This was needed in 1996. We can go to specific semantic structures. 14:31:16 Jeanne: We added this as a new sub guideline in 1.4.2. 14:31:29 Jeanne: We are using this as an example of the writing process. 14:31:53 jeanne: reassures janina need for semantic nav is captured 14:31:53 Jeanne: Do we want to use this more detailed user needs at the exploratory level? We could look at it and say maybe it needs to be in the developing level. 14:32:02 jeanne: question is whether this writing approach worksxz 14:32:03 Jeanne: At some point we do need to go to that level. Where is the question. 14:32:43 Lauriat: looking to see what we had from ux research for existing sc; will be important when we go to wider review 14:33:19 Lauriat: ex. might be nontext contrast; e.g. recognizing buttons and their states 14:33:30 q+ to ask the question I think we are trying to answer 14:33:38 Lauriat: we need to avoid repeating former mistakes 14:33:51 ack me 14:33:51 Lauriat, you wanted to ask what research we have from the original SC that we can reference for this 14:33:56 Lauriat: we shouldn't need to redo research that has well informed sc; but also to do research not done 14:34:22 Chuck_: believe we're trying to answer whether we need more detailed user needs at the exploratory level 14:34:46 jeanne: suggesting exploratory should look at existing research 14:35:20 q+ 14:35:50 ack Chuck_ 14:35:50 Chuck_, you wanted to ask the question I think we are trying to answer and to 14:35:51 jeanne: then for developing we're writing the detailed user needs 14:36:24 Chuck_: i expect no one individual can understand all the research; but we should have it very available 14:36:41 jeanne: notes section in howto that links to research--so we could mine that as needed 14:36:46 q+ to say we need it to show our work and have our work evidence and research-based, not just that it'll help to reference 14:37:42 +1 to shawn's reframing of the need for research 14:37:47 Lauriat: we need research to backup the guidance we put in wcag 3; we need to be evidence based; it's our principle and we need to stick to it 14:38:02 Lauriat: opinions are not as persuasive as research outcomes 14:38:42 Lauriat: even documenting "this sc has no research" is still helpful 14:38:46 q+ that "no research" is a useful data point 14:39:03 +1 that "no research" is a very useful data point 14:39:04 Lauriat: we will need to work in parallel, of course 14:39:13 q+ 14:39:24 ack me 14:39:24 Lauriat, you wanted to say we need it to show our work and have our work evidence and research-based, not just that it'll help to reference 14:39:26 ack lau 14:39:28 ack janina 14:39:30 ack jan 14:39:39 Janina: Want to point out that APA research questions task force has been doing this! 14:40:02 Janina: I think they've been doing pretty good. Will put link in. 14:40:15 Excellent! That'll help immensely. 14:40:40 https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Main_Page 14:40:49 janina: RQTF does this kind of work 14:41:20 q+ 14:42:02 Chuck_: We've had just a few of us in this conversation--other people here; any thoughts? 14:42:08 ack Ch 14:42:27 ToddL: Good so far! 14:42:36 jeanne: notes Todd lead errors group 14:42:55 ToddL: Says Sarah! But, I'll take some credit 14:42:59 I'm good so far too. 14:43:02 zakim, next item 14:43:02 agendum 4 -- Do we write Outcomes before tests? -- taken up [from jeanne] 14:43:30 jeanne: what comes first? Outcomes? Test? 14:43:40 jeanne: this topic likely controversial 14:43:57 jeanne: how do we test a user need is met? 14:44:10 q+ 14:44:33 ack Ch 14:44:45 jeanne: we can also say there are certain outcomes based on the user need, i.e. what does the outcome need to be to satisfy the user need? 14:45:17 Chuck_: asks what are the pro/con arguments for tests first vs outcomes first 14:46:29 jeanne: original idea is user need; then ask how to tell it's fulfilled 14:46:44 jeanne: based on how it's fulfilled drives defining the outcome 14:46:58 q+ to ask for a comparative example 14:47:18 jeanne: based on the user need, what's the outcome we desire and then how do we test that outcome 14:47:33 Janina: That's where I'm at, I'm having trouble seeing the other approach. 14:47:38 ack me 14:47:38 Lauriat, you wanted to ask for a comparative example 14:48:01 jeanne: by example 1.4.2 -- users can customize functionality in settings 14:48:16 jeanne: who to test? then we derive an outcome of what we want 14:48:28 q+ 14:48:52 q+ to add to that example 14:49:25 jeanne: or ... 14:49:25 ack Chuck_ 14:49:45 Chuck_: chair hat off -- completely not understanding tests first 14:50:04 Chuck_: because i can see how that builds and works; but not if we say tests first 14:50:04 q+ to answer chuck 14:50:05 q+ 14:50:35 jeanne: reason is more historic; what we found during wcag 2.1 14:50:57 jeanne: the SC (approx outcomes); tests written later and that exposed errors in the sc 14:51:14 q+ 14:51:24 ack jeanne 14:51:24 jeanne, you wanted to answer chuck 14:51:30 ack jeann 14:51:54 Lauriat: wanted to build on example because thought it incomplete 14:52:11 Lauriat: users can make audio settings; they're saved; they're applied when users go to something audio 14:52:26 Under Shawn's example, you need the outcome first. That's how I'm interpreting the statement. 14:53:13 Lauriat: we need to understand what it is we want to test before we can write them; they will be context specific 14:53:30 Lauriat: will be different in trad website than online game 14:53:52 Lauriat: tests will need to be platform specific 14:54:34 Janina: I think it's correct Shawn. I don't think it invalidates that we discovered gaps, I don't think that this invalidates coming up with outcomes first. APA wants to talk about verifiable credentials. 14:54:46 +1 to using tests to further refine outcomes 14:55:05 +1 to using tests to further refine outcomes 14:55:15 Janina: This is a very important conversation to have. 14:55:49 janina: suggests outcomes first doesn't invalidate tests exposing what was missed in defining outcomes 14:55:52 q+ to note early and also evolving 14:55:54 jeanne: agrees 14:55:55 +1 That was what I was going to say - do tests early after outcomes 14:56:04 ack me 14:56:04 Lauriat, you wanted to add to that example and to note early and also evolving 14:56:04 +1 14:56:07 q+ to note early and also evolving 14:56:10 +1 14:56:13 ack maryjom 14:56:16 +1 14:56:25 +1 14:56:43 maryjom: important to think about testing shortly after writing outcomes, to be sure the outcomes are fully fleshed out 14:57:24 rrsagent, make minutes 14:57:24 I have made the request to generate https://www.w3.org/2022/08/12-silver-minutes.html janina 14:57:41 ack janina 14:57:46 ack laur 14:57:46 Lauriat, you wanted to note early and also evolving 14:58:13 Lauriat: early writing tests; but we need to reiterate the process as tech evolves; it's a constant cycle 14:58:35 zakim, bye 14:58:35 leaving. As of this point the attendees have been jeanne, Lauriat, Azlan, MichaelC, janina, Poornima, maryjom, ToddL 14:58:35 Zakim has left #silver 14:58:39 rrsagent, make minutes 14:58:39 I have made the request to generate https://www.w3.org/2022/08/12-silver-minutes.html janina 15:06:28 kirkwood has joined #silver 15:08:39 kirkwood has joined #silver 15:09:18 maryjom has joined #silver 15:23:10 janina has left #silver 15:55:55 kirkwood has joined #silver 22:13:25 MichaelC has joined #silver