14:49:28 RRSAgent has joined #ag 14:49:28 logging to https://www.w3.org/2022/04/26-ag-irc 14:49:37 here too. 14:49:51 Agenda+ New members and topics 14:51:04 Agenda+ Announcements and Reminders 14:51:12 Agenda+ Proposal to update WCAG 3 editor's draft with test types https://www.w3.org/2002/09/wbs/35422/wcag3_test_section/results 14:51:21 Agenda+ Visible Controls https://www.w3.org/2002/09/wbs/35422/wcag22-visible-controls/results 14:51:30 Agenda+ WCAG 2.2 Page break locators https://www.w3.org/2002/09/wbs/35422/wcag22-page-break-nav/results 14:51:44 Agenda+ WCAG 2.2 Misc Issues https://www.w3.org/2002/09/wbs/35422/wcag22-misc/results 14:51:47 agenda? 14:52:02 regrets: Sarah H, Todd L 14:52:58 Agenda+ WCAG 2.2 Focus appearance https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced2/results 14:53:00 GreggVan has joined #ag 14:53:59 agenda- 2 14:54:20 zakim, agenda order 1, 3, 7, 4, 5, 6 14:54:20 ok, Rachael 14:54:22 agenda? 14:54:47 zakim, agenda order 1, 3, 4, 7, 5, 6 14:54:47 ok, Rachael 14:54:51 agenda? 14:55:48 Jennie has joined #ag 14:55:57 present+ 14:56:05 scribe: Jennie 14:56:15 present+ 14:56:29 laura has joined #ag 14:57:33 ToddL has joined #ag 14:57:37 present+ 14:57:56 present+ 14:57:58 present+ 14:58:05 regrets- Todd L 14:58:20 Thank you, Rachael. 14:58:33 present+ 14:58:48 JakeAbma has joined #ag 14:58:48 shadi has joined #ag 14:58:49 Rachael: We are looking for a scribe for hour 2 14:58:52 present+ 14:59:15 GN015 has joined #ag 14:59:15 ShawnT has joined #ag 14:59:22 present+ 14:59:29 present+ 14:59:43 bruce_bailey has joined #ag 14:59:57 JustineP has joined #ag 15:00:15 present+ 15:00:40 jweismantel_ has joined #ag 15:00:41 present+ 15:00:46 present+ 15:00:50 I'm Jo and am new 15:00:56 Rachael: Jo, welcome 15:01:01 zakim, take up item 1 15:01:01 agendum 1 -- New members and topics -- taken up [from Rachael] 15:01:01 Lauriat has joined #ag 15:01:05 Present+ 15:01:12 agenda? 15:01:21 Rachael: We ask new members to say their name, where you work, 1 sentence on your background 15:01:22 Jem has joined #ag 15:01:42 Jo: I work at Pearson. I am excited to be here and contribute 15:01:49 q+ 15:01:55 q+ to say something 15:01:59 ack Rachael 15:02:01 Rachael, you wanted to say something 15:02:13 present+ jaeunjemmaku 15:02:43 Wilco_ has joined #ag 15:02:47 Rachael: anyone else here that is new? 15:02:57 present+ 15:02:58 ...Any topics to bring to the attention of the chairs? 15:03:05 I'll be in a work meeting at the same time, so I won't be able to speak. 15:03:05 zakim, take up next item 15:03:05 agendum 3 -- Proposal to update WCAG 3 editor's draft with test types https://www.w3.org/2002/09/wbs/35422/wcag3_test_section/results -- taken up [from Rachael] 15:03:13 Welcome Jo and Pearson! 15:03:36 Rachael: 2 purposes - a new way of thinking about how we will handle expanding what we test in WCAG 3 15:03:42 ...We had explored scoring and rating 15:03:48 ...We are now exploring different types of tests 15:03:54 mbgower has joined #ag 15:04:21 ...We have broken down the tests into different levels of subjectivity 15:04:29 Raf has joined #ag 15:04:35 ...We are exploring how this impacts different SC - we are at the exploring phase 15:04:40 present+ 15:04:59 ...The editor's draft: shift what is in this draft and mark as exploratory 15:05:31 Detlev has joined #ag 15:05:33 ...Removing content, outstanding process (moving things from one level to the next, we need to capture information), and then make the content change 15:05:58 TOPIC: Agree with removing ratings, scorings, and critical errors 15:06:18 Rachael: 7 people agree, 1 with adjustments, no disagrees 15:06:23 ...Starting with the agrees 15:06:43 ...(reads from the survey) 15:06:58 present+ 15:07:36 Rachael: no further comments from those that agreed 15:07:46 ...(reads Sarah's suggested adjustments) 15:07:54 TOPIC: Should we leave in critical errors? 15:07:58 Rachael: Any other topics I missed on that? 15:08:08 q? 15:08:11 Rachael: queue is now open to general conversation 15:08:15 q+ 15:08:16 q+ to say that I like the idea of leaving critical errors 15:08:42 Rachael: Chair hat off - I think we should not leave off critical errors. My concern: that we have them to fit in for scoring, and we may adjust 15:08:47 ack Jennie 15:08:53 ack Rachael 15:08:55 ack jeanne 15:08:55 jeanne, you wanted to say that I like the idea of leaving critical errors 15:09:25 Jeanne: I like the idea of keeping it. I like Sarah's idea. 15:09:34 ...Because it is not directly related to the scoring we could leave it in 15:09:34 JF has joined #ag 15:09:39 q+ 15:09:40 Present+ 15:09:43 ...We need some way of addressing the issue. I could go either way 15:09:46 ack mbgower 15:10:01 Mbgower: I think the critical errors are still errors and will fail current SCs 15:10:07 ...Depending on how the assessments go 15:10:13 ...The roll up situation 15:10:26 ...Without talking about why you are including them, it is hard to explain why you are even mentioning them 15:10:28 Jon_avila has joined #ag 15:10:33 +1, they are fails, we don't need to call them out separately (until we get to the conformance/scoring aspect). 15:10:40 ..."These are critical errors" could be left there, but may raise more questions 15:10:42 q+ 15:10:47 ack bruce_bailey 15:10:59 Bruce: Is it possible to have an exposition on the critical errors 15:11:00 MelanieP has joined #ag 15:11:02 Jon_avila_ has joined #ag 15:11:06 present+ 15:11:10 ...To have the idea behind it, without saying which are critical errors? 15:11:11 q+ 15:11:16 ack Raf 15:11:22 Wouldn't that be part of explainer type content, rather than the spec? 15:11:29 jaunita_george has joined #ag 15:11:32 Present+ 15:11:40 Rachael: (chair hat off) I think that we could leave something small in, like an editor's note saying we are exploring it, but take it off elsewhere 15:11:46 q? 15:11:48 ...we could have it as exploratory 15:11:52 Present+jon_avila 15:11:55 +1 to critical errors as placeholder 15:12:12 Straw poll: 1. Remove critical errors 2. Critical Errors as placeholder 3. Keep critical errors in as is 15:12:17 1 or 2. 15:12:18 2 15:12:18 1 15:12:18 1 15:12:19 2 15:12:20 2 15:12:21 1 15:12:22 2 15:12:25 2 15:12:27 1 15:12:30 2 15:12:30 1 15:12:30 1 15:12:31 2 15:12:32 1 15:12:33 2 15:12:35 1 or 2 15:12:39 2 or 1 15:12:43 q+ 15:12:44 1 or 2 15:12:46 ack Raf 15:12:48 ack Rachael 15:12:50 present+ 15:12:57 7 1's 8 2's, and a bunch of eithers 15:12:58 1 preferred :) 15:13:07 ack GreggVan 15:13:10 Rachael: We have 7 for 1, 8 for 2 15:13:32 GreggVan: In the old way we were talking, and until we have the new mechanism, I think critical errors was a way to cover a big hole in the old approach 15:13:41 ...If we revisit it, they may come back again 15:13:50 ...It is kind of like having another layer, like the A and AA 15:13:57 ...If you have critical errors and non critical errors 15:14:01 q+ 15:14:10 ...Until we decide we are labeling the others as "not critical errors" is my concern 15:14:19 q+ 15:14:20 ack Chuck 15:14:25 ...Pushes all the other provisions down into another layer 15:14:33 We have non interference in the conformance requirements. 15:14:34 Can't any error be critical for a specific user? 15:14:38 Chuck: We seem to have consensus that we are removing option 3 15:14:49 ...There are a variety of people who put either / or 15:14:55 In reality, we also call "critical error" as a deal breaker. What is the downside if we leave it as "placeholder"? 15:14:58 ...Could we see if people tolerate 1 or the other 15:14:59 ack Detlev 15:15:16 q+ 15:15:19 Detlev: I don't think it is necessary that the concept of critical error means everything else is not critical 15:15:38 q+ to say i think concept of critical error is new and different and important 15:15:41 Yes. We also require full process today. 15:15:43 ...3rd category: non-critical - is a formal problem, but doesn't constitute a serious barrier - I find the concept quite useful 15:15:43 ack MelanieP 15:15:45 + 1 to Deltev 15:16:07 JakeAbma_ has joined #Ag 15:16:10 Melanie: I thought I heard including an editor's note, but then the straw poll said placeholder. 15:16:24 ack bruce_bailey 15:16:24 bruce_bailey, you wanted to say i think concept of critical error is new and different and important 15:16:26 Rachael: I can separate in the next straw poll 15:16:38 Bruce: Critical errors is new and different, not something we have in 2x 15:16:45 ...It is more than the blockers in the conformance report 15:17:03 ...I favor having something 15:17:07 straw poll: 1) remove critical errors, 2) critical errors in editors note 3) critical errors as placeholder content w/ editors note 15:17:15 1 15:17:16 1 15:17:17 I would like to shed light on Greg's point - "critical error" helps to complement the downside of current WCAG. 15:17:17 2 15:17:19 2 15:17:19 Rachael: Pick which one you most prefer 15:17:20 2 15:17:21 2 15:17:22 2 15:17:24 1 15:17:24 qq? 15:17:24 3 15:17:25 2 ok with any 15:17:25 q? 15:17:30 2 or 3 15:17:30 2 15:17:32 1 15:17:38 2, 1 15:17:41 1 15:17:44 Suggest: Critical errors was introduced as a concept in the FPWD. Although it will not be a focus of discussion in the next charter, it is intended to re-asses this concept in the future" 15:17:47 Rachael: (read Jemma's comment) 15:17:47 2 oe 3 15:17:52 2 okay with any 15:18:08 2 15:18:18 Jemma: Yes, I think Gregg's comment about critical errors is important 15:18:19 q+ to clarify 15:18:28 ...It is very practical for use to use in reality 15:18:33 ack GreggVan 15:18:33 GreggVan, you wanted to clarify 15:18:46 GreggVan: The critical error, when we had something you didn't have to pass everything 15:18:58 q+ 15:19:02 ...Like scoring, if you do 90% but you did none of some for a disability group 15:19:06 5 1's, 10 2's, then mixes. Working on mixes 15:19:11 ...That is where critical error came in 15:19:18 a single 3 15:19:21 ...You have a way of "passing is good enough" without doing them 15:19:27 ...Without doing them all 15:19:36 ...Hyper A - you just can't not do something 15:19:39 Possible note (based on mike's suggestion): Critical errors was introduced as a concept in the FPWD. Although it not currently included, AGWG intends to re-asses this concept in the future. 15:19:42 Here is link to CC5 Non Interference, but I understand WCAG3 idea of Critical Error to be broader 15:19:44 https://www.w3.org/TR/WCAG22/#cc5 15:19:49 ...If we have taken scoring out, there is no longer a need for critical errors at this time 15:19:55 ...We should bring it back in the future 15:19:56 a few 2's with lesser preferences to either 1 or 3. 15:20:19 ...The As would need to be a critical error 15:20:32 q+ to explain critical errors 15:20:33 ...If there isn't scoring at this time, then there isn't a need for critical errors 15:20:41 5 1's, 13 2's, 1 3 15:20:44 Rachael: Before we go further, we did have a preference towards 2 15:20:48 q- 15:20:48 I think Greg is voting for #2 ;-) 15:20:48 ...The editor's note 15:20:54 ...a strong preference 15:21:01 ...Would anyone object to an editor's note? 15:21:18 Possible note (based on mike's suggestion): Critical errors was introduced as a concept in the FPWD. Although it not currently included, AGWG intends to re-asses this concept in the future. 15:21:19 no objection. 15:21:27 no 15:21:29 Rachael: I think we will talk about the wording in a moment 15:21:31 I could live with #2 depending on what it said 15:21:34 ...Sounds like no objections 15:21:41 no 15:21:47 ...Mike put in a suggestion tied to the charter, which I slightly reworded 15:21:55 ...(reads Mike's suggestion) 15:21:55 q- 15:21:59 q? 15:22:01 ...What else would people like to see? 15:22:08 q+ 15:22:11 ack mbgower 15:22:12 +1 15:22:27 Mbgower: Thank you for doing that. I think everyone understands the basic concept 15:22:35 q+ to say that works for me 15:22:38 ...Is it something we can have a few people review, and bring it back? 15:22:39 present+ Laura_Carlson 15:22:51 + 1 to Mbgower's approach 15:22:51 Rachael: Absolutely, I just want to be sure that people share any feelings about it 15:22:55 GreggVan: That works for me 15:23:02 ...In terms of language. It is also good the way it is 15:23:26 ...We can figure out what we do later, and use that short description. 15:23:32 draft resolution: Remove ratings, critical errors, and scorings. Add editor's note similar to Critical errors was introduced as a concept in the FPWD. Although it not currently included, AGWG intends to re-asses this concept in the future. 15:23:49 0 15:23:51 +1 15:23:52 +1 15:23:52 +1 15:23:54 +1 15:23:55 +1 15:23:56 +1 15:23:57 1 15:23:59 +1 15:24:00 +1 15:24:00 +1 15:24:00 +1 15:24:03 +1 15:24:03 +1 15:24:04 +1 15:24:07 +1 15:24:08 +1 15:24:09 +1 15:24:10 +1 15:24:24 +1 15:24:39 RESOLUTION: Remove ratings, critical errors, and scorings. Add editor's note similar to Critical errors was introduced as a concept in the FPWD. Although it not currently included, AGWG intends to re-asses this concept in the future. 15:24:39 RESOLUTION: Remove ratings, critical errors, and scorings. Add editor's note similar to Critical errors was introduced as a concept in the FPWD. Although it not currently included, AGWG intends to re-asses this concept in the future. 15:24:43 JakeAbma__ has joined #Ag 15:24:46 0 15:24:50 TOPIC: What are outstanding questions on the new approach? 15:25:04 Chuck has changed the topic to: What are outstanding questions on the new approach? 15:25:23 Rachael: (reads from the survey) 15:26:01 Q+ 15:26:17 q- GreggVan 15:26:48 not atthis time 15:27:09 Rachael: no other comments from Todd 15:27:21 ...Mike can you clarify your statement? 15:27:42 mbgower: Personally it is extremely hard to deep dive into 2.2 then go into Silver - hard to go back and forth 15:27:52 ...Hopefully we can get 2.2 to the next stage, then pivot 15:27:56 Rachael: I concur 15:28:01 +1 to MG 15:28:06 Rachael: (reads from the survey) 15:28:14 Regarding Gundula's comment, Makoto and I had the same feedback regarding the "naming" of the various test approaches. 15:28:25 Gundula: no futher commens 15:28:39 Jeanne: no further comments 15:28:53 Rachael: I think we have a list with some rewording from Todd, 2 further questions from Gundula 15:28:58 q? 15:28:59 ...And I am now opening the queue 15:29:02 ack jf 15:29:16 JF: This may be a minor point, but I am concerned that things that are not tests we are calling tests 15:29:24 ...Gregg referenced this in an earlier comment 15:29:33 ...Evaluation is a good word, but I am struggling with "test" 15:29:43 ...Can we remove "test" and instead reference "evaluations" instead? 15:29:46 q+ to answer 15:29:47 q+ to say almost every existing SC includes subjective wording that is 'tested' 15:29:51 q+ 15:29:57 ack Rachael 15:29:57 Rachael, you wanted to answer 15:30:20 Rachael: (chair hat off) the intent of this approach was "could we expand tests" if we took the assumption that what was pass or fail would change 15:30:25 ...The use of "test" is intentional 15:30:38 ...We are trying to see if we can fit an expanded set of requirements into what is pass or fail 15:30:45 ack mbgower 15:30:45 mbgower, you wanted to say almost every existing SC includes subjective wording that is 'tested' 15:30:46 ...Open to other ideas 15:31:01 Q+ 15:31:07 could we have a link to the poll? 15:31:08 mbgower: I read the comments posted. Every success criteria in 2.x - almost all have some subjective components 15:31:21 ...I think that test evaluations has the same idea 15:31:27 kirkwood - the survey? https://www.w3.org/2002/09/wbs/35422/wcag3_test_section/results 15:31:36 ...Is there an alt text programmatic indicator here, and does it meet 15:31:36 thank you! 15:31:48 ...The way forward is to see if we can make both testable 15:31:55 ack GreggVan 15:31:57 ...I think the direction is clear from the current wording 15:32:16 not true!! 15:32:19 OliverK has joined #ag 15:32:21 GreggVan: The requirement is only that there is alt text. Not that the alt text has to be good - that would be subjective 15:32:22 +1 and BINGO to Gregg 15:32:29 ...Placeholders are clearly defined 15:32:41 "serves the equivalent purpose" - goes beyond just existing 15:32:42 "All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below." 15:32:47 ...That's been the hallmark of things being testable 15:32:55 ...When you are done, you need to be able to determine you are done 15:32:56 +1 to Gregg 15:33:01 ...It depends on who is doing the judging 15:33:09 ...With multiple testers... 15:33:15 q? 15:33:24 ...You can't require someone to do something, then they cannot determine they are done when they are done 15:33:31 ...Lines are always blurry 15:33:43 ...Talks about being on both sides of a line or border 15:33:43 q+ 15:33:56 ...It should be clear if you are on one side or the other 15:34:04 ack JF 15:34:04 ...It should have high inter-rater reliability 15:34:10 JF: Exactly what Gregg said 15:34:16 1.2.1 "presents equivalent information "; 1.3.1 "Information, structure, and relationships conveyed through presentation " 15:34:24 ...Mike talked about success criteria in 2.x - those are all testable statements 15:34:35 1.3.2 "When the sequence in which content is presented affects its meaning," 15:34:38 ...When we talked about these in the past, COGA talked about wanting other aspects added 15:34:47 ...They created Creating Content Usable 15:35:01 ...Example: having a definition of beautiful or delicious depends on what you think it is 15:35:02 q+ 15:35:07 ack Wilco_ 15:35:10 q+ to say "that serves the equivalent purpose" 15:35:21 Wilco: Nobody is proposing to have tests with low inter-rater reliability 15:35:25 +1 to Wilco 15:35:25 q+ to suggest solution 15:35:30 +1, this is a tangent 15:35:33 ...I think we should agree that because this is exploratory, we should let the work continue 15:35:35 Francis_Storr has joined #ag 15:35:36 q- 15:35:55 Rachael: 1 option - Are these tests or evaluations? 15:35:58 ack jeanne 15:35:58 jeanne, you wanted to say "that serves the equivalent purpose" 15:36:03 +1 this is a tangent 15:36:05 jon_avila has joined #ag 15:36:19 Jeanne: To answer Gregg, that serves the equivalent purpose in 1.1.1 is subjective condition 15:36:27 ...It is not like we don't have subjectivity in WCAG 2 15:36:31 Today WCAG 2.x does require equivalent purpose and not just alt. 15:36:42 ...What will help is if we can tease them apart, and start doing more reliable testing of the subjective things 15:36:53 +1 to Jeanne and Wilco 15:37:02 ...As Wilco says, we are just starting. Let's explore it, it could solve some major problems, and I would like to see it keep going 15:37:06 +1 that text alternative serves equivalent purpose is not so objective 15:37:13 GreggVan: I have the same answer later in the questionnaire 15:37:25 ...Categories are things you sort things into, rather than tags 15:37:38 ...Everything not in the 1st category is by definition not subjective 15:37:44 “Qualitative scoring cannot be used for conformance testing; a test must comprise criteria that either fail or pass if said criteria are to be employed in any legislative manner. Otherwise, two testers may produce altogether different results, which is unacceptable for WCAG in its present role in European legislation.” (SiteImprove - https://github.com/w3c/silver/issues/509) 15:37:55 ...Conditional, not conditional - leaving out subjective as something that all the others are not 15:38:10 q? 15:38:13 ack Gregg 15:38:13 GreggVan, you wanted to suggest solution 15:38:20 Rachael: We did collect terminology, and I am seeing that suggestion here. We will survey that in a future survey 15:38:29 q? 15:38:42 GreggVan: If you say there are going to be types, everyone will go back to the types that are named 15:38:49 ...We could add a note 15:39:04 ...If the note says "we are going to go forward, but have not yet found the right categories" 15:39:12 ...The whole conversation has been what are the categories 15:39:28 Rachael: let's go back to - we are looking at adding exploratory content into the draft 15:39:34 ...We are just thinking about these ideas 15:39:47 ...In the process we agreed on is that we would capture all the things we think we should work on 15:40:03 ...Gundula has asked is the naming of test approaches appropriate? 15:40:19 ...By having the question in we are acknowledging it is not yet right, but we are exploring it 15:40:27 ...That we are continuing in the direction 15:40:39 ...Is there another question that we can capture that we know is an issue with this direction? 15:40:46 q? 15:40:48 ...Does that make sense Gregg? 15:40:50 q+ to suggest that if we know we don't have the types - we don't put anything in 15:40:53 ack GreggVan 15:40:53 GreggVan, you wanted to suggest that if we know we don't have the types - we don't put anything in 15:41:07 GreggVan: If we know we don't have the types right...if you want to put something in 15:41:25 +1 to Gregg 15:41:26 ...Are you saying that we are going to go forward having 4 types, 3 of which are absolutely not objective 15:41:40 ...Then there would be 3 more types that are not exclusive 15:41:45 ...I think we rename the 1st one 15:41:59 ...These are the kind that are unconditional 15:42:02 q? 15:42:19 ...If you have not determined that they are not objective, we should change the terms 15:42:21 "Objective Tests" and "Subjective Evaluations" 15:42:33 q+ to say we've discussed the types quite a lot, we know the categories, it's the names that we haven't settled on 15:42:39 Gregg: I think this would address several of the issues 15:42:41 Q+ 15:42:49 ack alastairc 15:42:49 alastairc, you wanted to say we've discussed the types quite a lot, we know the categories, it's the names that we haven't settled on 15:42:50 ...Finding new ways of looking at this, other than the ways we have 15:43:00 Alastairc: We have discussed these types of tests in other meetings 15:43:09 ...We know the categories - it is the names we haven't settled on 15:43:19 JF: I keep coming back to the fact that words are important 15:43:24 ack JF 15:43:38 ...I have proposed a way to have other ways of measuring 15:43:46 +1 to "Objective Tests" and "Subjective Evaluations" 15:43:46 q+ I suggest reordering the order you handle the questionaire. you need to proces the other question first 15:43:46 ...But gets us out of the objective vs subjective 15:44:19 ack GreggVan 15:44:25 GreggVan: You said we would make a decision first - I think the order is incorrect. I think we figure out the words first but I will review the draft resolution 15:44:34 are we then saying all user tests are subjective? 15:44:52 Rachael: I will attempt to write the resolution to address that 15:45:38 Draft RESOLUTION: Accept new questions in survey along with the question of whether to use test or evaluation. Change the first test name to Unconditional while we continue to evaluate terminology. 15:45:39 ...this is just around which questions should be in the editor's note 15:45:40 @Kirkwood that would seem logical to me. Each user is unique, and their approach to interaction as well. I want to be sure we are evaluating content, and not users! 15:45:52 Rachael: Please give comments before voting 15:46:04 ...Do I need to reword it? 15:46:12 I prefer 'objective' 15:46:24 Rachael: These categories are defined in the document 15:46:36 Draft RESOLUTION: Accept new questions in survey, accept editorial content, along with the question of whether to use test or evaluation. Change the name of first test type to Unconditional while we continue to evaluate terminology. 15:46:38 I prefer objective 15:46:55 +1 15:47:04 +1 15:47:04 +1 15:47:04 Rachael: Let's go ahead and vote 15:47:09 +1 15:47:09 +1 15:47:10 +1 15:47:10 +1 15:47:11 +1 15:47:14 -0.5 15:47:15 +1 15:47:16 +1 15:47:18 +1 15:47:18 -1 to "unconditional" - I understand the intent, do not like the term 15:47:21 0 I'm not sure where 'unconditional' came from 15:47:25 0 15:47:30 +1 15:47:39 +0 unconditional is not the same as subjective 15:47:58 Gundula: On the one hand I prefer objective, there are fixed rules that could be automized 15:48:09 ...Renaming before the overall discussion on renaming the categories 15:48:15 0 also unclear about unconditional 15:48:22 JF: Pretty much the same as Gungula 15:48:31 ...I would prefer objective testing, where it is objective 15:48:36 q+ 15:48:38 q+ to answer 15:48:40 ...Anyone running the tests should be able to get the same results 15:48:42 +1 to objective 15:48:58 Mbgower: I know that we are looking at a greater means of granularity 15:49:16 ...If we adopt splitting it into 2 for now, we might be able to get this in, and worry about the details as we progress 15:49:18 +1 15:49:40 GreggVan: Remembering that these are types that you sort into 15:49:45 ...If you call them tags, you can more than one 15:49:59 q+ 15:50:03 ack mbgower 15:50:04 Q+ 15:50:06 ack GreggVan 15:50:06 GreggVan, you wanted to answer 15:50:25 ...I have a concern about one of the types being objective 15:50:35 ...If you do that, then nothing else can be objective 15:50:41 ...Unless we are thinking of these as tags 15:50:58 ...Will everything be one of the types? Or as tags or descriptors, so some things can be more than one 15:51:01 this is a matrix, not a 1-dimensional approach 15:51:02 ...Or characteristics 15:51:12 ack me 15:51:14 q+ 15:51:15 ...Then something could be objective, and conditional, and could be a procedure 15:51:29 ...Then I think we would be ok 15:51:39 this is already done with alt text. objective tests (presence of alt text) and subjective evaluations (relevant alt text) 15:51:41 -1 its too confusing if these are tags 15:51:49 Rachael: A lot of this has happened in previous meetings, they are meant to be categories or types 15:51:56 Gregg, have you read this https://rawgit.com/w3c/silver/update_test_section/guidelines/index.html#objective-tests 15:51:58 ...These are the different ways you can test a particular objective 15:52:07 ...They are exclusive of each other 15:52:13 GreggVan: That's what I thought 15:52:29 Rachael: I think your point is valid 15:52:36 GreggVan: This is the most important topic 15:52:43 ...I think putting this into the draft 15:52:56 ...Saying this group has formally decided that 3/4ths not be testable 15:52:59 Gregg, we've been discussing this for several meetings 15:53:00 ...That is monumental 15:53:04 ack Rachael 15:53:09 +1 to Gregg 15:53:16 +1 to Kirk's example 15:53:25 Rachael: The premise of this is that all of them are testable, but what is tested was different 15:53:40 ...We were not saying that anything is more subjective than anything in 2.x 15:53:46 ...That is why we spent several meetings on this 15:53:53 ...We will not get to the next question 15:54:03 ...Is everyone comfortable with the questions we have - to get them into the draft note 15:54:03 rrsagent, make minutes 15:54:03 I have made the request to generate https://www.w3.org/2022/04/26-ag-minutes.html laura 15:54:03 +1 comfortable with questions 15:54:05 ack mbgower 15:54:21 mbgower: Just acknowledge that we have had a number of meetings on this 15:54:28 ...This is a matrix 15:54:34 ...Things are going across 2 different directions 15:54:37 ...It is not linear 15:54:54 ...If you divide things into 4, you inferred that it means that only a quarter of them will be assessed in one area 15:54:57 ...That is not correct 15:55:17 ...A certain amount will be subjective, and we are attempting to categorize in different ways 15:55:19 Q+ 15:55:22 Draft RESOLUTION: Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation". 15:55:33 ack JF 15:55:51 JF: Part of the problem here is we also need to be thinking about conformance 15:56:02 Q+ saying there are different things we are going to test -- is not the same as saying that only one of the things will actually be tested 15:56:05 ...We have had feedback about subjective 15:56:10 ack GreggVan 15:56:16 Rachael: any feedback on the draft resolution? 15:56:31 GreggVan: You are talking about another one of our surveys or going into the editorial draft? 15:56:41 Rachael: We have an editor's draft, with different levels of maturity 15:57:01 ...We agreed as a group to have a bottom level of maturity, and to capture questions 15:57:10 ...We have a list of questions we don't think we have the answers to 15:57:16 ...This meeting brought up another question 15:57:37 ...I am asking if we are ok adding the questions 15:57:44 JF: I am looking for the questions 15:58:07 https://rawgit.com/w3c/silver/update_test_section/guidelines/index.html 15:58:19 Rachael: The survey has the full list as well 15:58:24 https://rawgit.com/w3c/silver/update_test_section/guidelines/index.html#testing 15:58:30 Rachael: We are talking about the editor's note 15:58:39 Regardig resolution, are we voting for "objective test" or "subjective evaluation" instead of outstanding question of wehther to use "test" or "evaluation"? Would the fomer be more closer to the consensus? 15:58:42 ...Section 4, testing section, editor's note has the list of questions 15:58:48 +1 15:58:56 +1 15:59:14 +1 15:59:19 q+ to add a question 15:59:19 +1 15:59:27 q+ to ask for scribe change 15:59:32 +1 15:59:40 +1 15:59:49 GreggVan: One of the questions should be: we may have different types of tests, but should any of them be not objective? 16:00:01 Rachael: OK, perfect 16:00:06 Draft RESOLUTION: Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation", add a question of "should any test be not objective" 16:00:07 *Scribe change soon? 16:00:16 ack Ch 16:00:16 Chuck, you wanted to ask for scribe change 16:00:28 ack GreggVan 16:00:28 GreggVan, you wanted to add a question 16:00:29 q+ for my blunt suggestion is for AGWG to focus more on prose and less on what regulators or litigation might find attractive 16:00:32 +1 16:00:39 +1 16:00:42 +1 16:00:45 +1 16:00:46 +1 16:00:47 +1 16:00:47 +1 16:00:49 +1 16:00:51 ack bruce_bailey 16:00:51 bruce_bailey, you wanted to discuss my blunt suggestion is for AGWG to focus more on prose and less on what regulators or litigation might find attractive 16:00:54 +1 16:00:56 +1 16:00:58 scribe: Rachael 16:00:59 +1 16:00:59 Bruce: things should be objective 16:01:05 0 16:01:16 ...I think the question is is the group's tolerance for less objective 16:01:26 q+ 16:01:26 ...I think about how much due diligence the group has given 16:01:31 +1 16:01:33 ...That are attractive to regulators 16:01:41 +1 to Bruce 16:01:50 ...My advice to the group is to worry less about that, and concentrate 16:01:53 +1 to Bruce 16:01:54 ...On writing good prose 16:01:56 +1 to Bruce 16:01:58 q+ question to bruce 16:02:00 +1 to bruce 16:02:13 0 16:02:16 zakim, close queue 16:02:16 ok, Rachael, the speaker queue is closed 16:02:18 Rachael: I see we have a queue and am closing queue 16:02:21 0 16:02:22 ...We need a new scribe 16:02:26 q- 16:02:31 q- question 16:03:05 zakim, pick a scribe 16:03:05 Not knowing who is chairing or who scribed recently, I propose kirkwood 16:03:27 zakim, pick a scribe 16:03:27 Not knowing who is chairing or who scribed recently, I propose ToddL 16:03:29 I can scribe 16:03:35 Scribe: Detlev 16:03:50 present+ 16:04:07 +1 16:04:09 Rachael: Any objections to the queston on the list? 16:04:11 +1 to question, my concern was for "should" 16:04:44 draft RESOLUTION: Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation", add a question of "How tolerant of we of subjective tests" 16:04:51 +1 16:04:52 Bruce: "should be objective" is easy, it is more how tolerant of subj, tests are we 16:04:53 +1 16:04:53 draft RESOLUTION: Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation", add a question of "How tolerant are we of we of subjective tests" 16:04:53 +1 16:04:53 +1 16:04:55 +1 16:04:56 +1 16:04:58 +100 16:04:59 0 16:05:01 +1 16:05:02 0 16:05:02 +1 16:05:03 +1 16:05:39 Gregg: The other question should not be taken out - should there be things in it that are not objective should be retained 16:05:43 +1 16:05:44 +1 16:05:50 +1 16:05:51 +1 16:05:55 draft RESOLUTION: Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation", add a question of "How tolerant are we of we of subjective tests (aka should any test be not objective)" 16:06:01 Rachael: Putting the question back in 16:06:20 +1 let's live with this 16:06:22 draft RESOLUTION: Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation", add a question of "How tolerant are we of we of subjective tests and Should any test be not objective? 16:06:28 Gregg: Can live withit, Bruce's point should be a separate question 16:06:37 Bruce: no problem 16:06:40 no objection 16:06:42 no 16:06:54 RESOLUTION: Accept new questions in the survey, accept editorial content from the survey, add an outstanding question of whether to use "test" or "evaluation", add a question of "How tolerant are we of we of subjective tests and Should any test be not objective? 16:07:02 +1 16:07:34 Gregg: Bruce, you said whe should focus on good prose even if that is a problem to regulators 16:07:36 agenda? 16:07:40 zakim, take up next item 16:07:42 agendum 4 -- Visible Controls https://www.w3.org/2002/09/wbs/35422/wcag22-visible-controls/results -- taken up [from Rachael] 16:07:49 Rachael: should not cover this here now, letÄs move to 2.2. 16:07:55 we already have SC which we characterize as being objective -- but are more subjective in actual practice than we would like 16:08:42 To GV, imho we should not let quest for objective prevent us from developing good guidelines 16:09:05 Rachael: What are next steps on Visible controls - left it for COga to review, that happened - AAA not a direction to take according to them - instead proposing several other options limiting the scope 16:09:24 Survey asked about the exceptions and other approaches to Visible Controls 16:09:36 Rachael: Mike, Alastair, anything toadd? 16:09:44 Alastair: No 16:10:30 AWK has joined #ag 16:10:31 regrets+ Todd Libby 16:10:37 +AWK 16:10:56 MikeG: The key thing is that the current wording demonstrably does not work - any choice except removing requires more work and someone needs to do that 16:11:12 @Chuck I'm still here. :) 16:11:30 Rachael (going through people's survey results, asking for any additions) 16:11:58 Rachael: Reading Sara's comments 16:12:01 jon_avila_ has joined #ag 16:12:29 Rachael: Reading Bruces's comments, Jon's comments 16:12:41 Rachael: Reading AWK's comments 16:13:30 q+ 16:13:37 3 people supported removing the SC 16:14:03 Rachael: Reading Alastair's comments 16:14:52 ALastair: Comes down to issue of affordance and expectations, people asee that differently 16:15:04 BTW, the 'editable' bit was in a different branch, not in the survey question. 16:15:06 Q+ to say I put in pursuing alternative 1 as my choice, assuming that we are pursuing this SC for WCAG 2.2. I do think that it is a separate discussion as to whether we have time and resources to get to a solution. 16:15:16 Rachael: (Reading MikeG's comments) 16:15:30 MikeG: The hard thing is to define visual indicators 16:16:25 MelanieP has joined #ag 16:16:28 TOPIC: Pursue or remove 16:16:32 Rachael: Should we remove or pursue - if the latter, we need volunteers to work on it 16:16:38 q+ 16:16:57 ack GreggVan 16:17:44 Gregg, it's in the first line 16:18:01 Gregg: Visual indicator only appears in the exceptions - it should say 'visually hiding the control' is essential, that would remove 'visual indicators 16:18:41 ...is this really a critical problem? Are there examples for the issue, beyond skiplinks 16:18:51 Rachael: has been identified as an issue 16:19:10 ack AWK 16:19:10 AWK, you wanted to say I put in pursuing alternative 1 as my choice, assuming that we are pursuing this SC for WCAG 2.2. I do think that it is a separate discussion as to whether 16:19:13 ... we have time and resources to get to a solution. 16:19:13 Gregg: Hiding controls addresses the problem (?) 16:20:05 AWK: pursuing Alternative 1 is my choice - but it may not feasible in the time frame - wasn't thinking about it in terms of the time constraints 16:20:11 ack mbgower 16:20:54 MikeG: The next survey question "What counts as Vissible indicator" - there was only agreement on one of the example, demonstrating the difficulty 16:21:18 q+ 16:21:27 Rachael: Straw poll whether we should continue or not - if the former, we need people to step in and work on it 16:21:43 straw poll: 1) Continue to pursue 2) Remove 16:21:46 1 16:21:48 2 16:21:48 2 16:21:52 2 16:21:55 2 16:21:56 1) 16:22:03 2 16:22:03 1 16:22:05 ack Wilco_ 16:22:06 2, unfortunately I've tried many ways, can't see a way forward. 16:22:21 3 1's, 6 2's 16:22:22 Want to say 1 but suspect that it is time to say 2 16:22:23 MelanieP_ has joined #ag 16:22:39 Nicaise has joined #ag 16:22:41 Wilco: e need to know time lines before the decision - do we need 2.2 recommendations before the end of the charter? 16:22:42 present+ 16:22:58 Rachael: We need to close out issues this week 16:23:12 2 unless someone volunteers 16:23:28 Gregg: Volunteers to take a crack on making this make sense 16:23:42 ...need help with filling in the background 16:23:45 1 16:23:46 Would like to say 1, but voting 2 16:24:00 Rachael: Who else would be available? 16:24:12 ...Coga may involve several people 16:24:35 Gregg: Tell me what I missed (background) then rephrase 16:24:42 Given all we have left on 2.2, I don't see how we can even afford another meeting on this. 16:25:00 Rachael: We can give you the info - Alastair or MikeG might be the ones 16:25:27 MikeG: Needs all the time on focus appearance 16:25:37 q? 16:25:45 Alastair: can give background 16:25:47 q+ 16:25:50 I think i objet 16:25:58 ack Wilco_ 16:26:02 Rachael: Any objections to pursue this for one final week 16:26:19 Wilco: We have a bunch of other thing sdtoo - but no objection 16:26:41 q+ 16:26:46 Alastair: Will need to send out CfCs for other SCs that have been talked about already 16:26:47 ack mbgower 16:27:44 straw poll: 1) Gregg will pursue for one more week 2) Remove 16:27:50 MikeG: Clarifying why I objected - with focus appearance, we had iterations for months - how can we do that for Visual Controls which has lots of affordance aspects that are difficult to puin down - that's why said disontinue 16:27:52 lets call it a strong caution over an objection 16:28:09 2 16:28:12 2 16:28:13 2 16:28:14 2 16:28:17 2, and I don't like it... 16:28:20 1 16:28:21 1 16:28:24 1 16:28:27 2 and I agree with Wilco, I don't like it 16:28:27 opt 1 16:28:33 1, but I think the likely outcome is that I will brief Gregg, and it won't go any further :-( so 2 is just as realistic. 16:28:37 2 16:28:40 2 16:28:48 agreeing with Wilco. 2 16:28:48 q+ 16:28:48 2 16:28:52 ack Chuck 16:29:21 Chuck: We need consensus by next week 16:29:31 jon_avila has joined #ag 16:29:38 draft RESOLUTION: We will try one last time but if no quick consensus next week, we will drop for 2.2 16:29:41 0 16:29:41 +1 16:29:46 +1 16:29:48 +1 16:29:49 0 16:29:53 Rachael: Good example for one of the 'less objective' test types... 16:29:53 +1 16:29:54 +1 16:29:56 -.5 16:29:57 +1 16:29:59 +1 16:30:03 +1 16:30:04 +1 16:30:04 0 16:30:05 +1 (see it as a form of due diligence. ) 16:30:13 Rachael: Gregg please send out draft early to group can vet it 16:30:24 +1 16:30:41 Rachael: Melanie - does it mean .5 menas can live with it? 16:30:47 Melanie: truw 16:30:51 ...true 16:31:05 RESOLUTION: We will try one last time but if no quick consensus next week, we will drop for 2.2 16:31:16 zakim, take up next item 16:31:16 agendum 7 -- WCAG 2.2 Focus appearance https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced2/results -- taken up [from Rachael] 16:31:17 Rachael: Agrees it is good for of due diligence 16:31:30 Rachael: Focus appearance now... 16:31:40 TOPIC: Updated understanding document for "encloses" 16:31:53 Rachael: Updating understanding doc regarding the term "encloses" 16:32:31 Alastairs: builds on discussions of last 2 weeks - if it is better than before we can move forward - last chance on this SC 16:32:39 https://raw.githack.com/w3c/wcag/focus-appearance-encompass/understanding/22/focus-appearance-minimum.html 16:32:57 Rachael: (reads survey results) 16:33:22 MikeG: No additions... 16:33:37 Bruce: no comment 16:33:48 q+ 16:34:13 Rachael: (reads Gundula's comment disjoint bounding boxes) 16:34:56 Rachael: (reding Wilco's comment) 16:35:17 Wilco: Thi sis about the exception clause, not relevant to the first part 16:35:45 Rachael: This is just about the Understanding doc - assume normative changes have been agreed 16:36:03 Alastair: normative hasn't changed right MikeG? 16:36:30 Alastair: normative text has nit changed 16:36:46 s/nit changed/not changed 16:37:21 yes, I'm seeing it in the preview 16:37:22 Michael: There has been one addition to the normative text, which was "instead" at the very end. The 16:37:31 MikeG: There was no intention of having a normative change in survey - but one change yet to be discussed, may need to be pulled out and checked 16:38:01 Rachael: (reading AWK's comment) 16:38:33 +1 to AWK 16:38:36 AWK: not a good idea to be too prescriptive (?) 16:38:37 themes: bounding box definition, against adjacent colors, normative change of word "instead", exception language 16:39:03 Rachael: Did I miss any themes? 16:39:06 q+ 16:39:07 +1 themes 16:39:22 TOPIC: bounding box defintion 16:39:23 Rachael: Starting with bounding box definition 16:39:33 ack mbgower 16:40:03 MikeG: There is no change of bounding box - understands what's being said, but this is pre-exisiting - can be created as issue but not part of thid change 16:40:15 Rachael: Gundula, can you create an issue for that? 16:40:41 Gundula: Will create issue 16:40:45 RESOLUTION: GN will create an issue for the bounding box definition 16:41:02 TOPIC: Against adjacent colors 16:41:09 q+ 16:41:15 Rachael: Next "Against adjacent colours" 16:41:22 ack alastairc 16:41:45 q+ 16:41:58 q+ 16:42:09 ack mbgower 16:42:09 Alastair: question for Wilco: do not think adj color prohibit halo or gradient typefocus indicators 16:42:41 What is meant by fading? Halo or non-persistent indicator? 16:42:43 MikeG: I thin it does - if you have a fading focus indicator it will fail adjacent colors 16:43:04 Alastair: Talking about fading in time or visually 16:43:12 Alastair :not time 16:43:14 ack Wilco_ 16:43:52 q+ to refer to use of 'adjacent' in 1.4.11 16:44:02 ack GN 16:44:02 GN, you wanted to refer to use of 'adjacent' in 1.4.11 16:44:03 Wilco: You need to define what the indicator is adjacent to - so it is unclear what os measured against what with glows and the like (?) 16:44:09 q+ 16:44:25 q+ 16:44:46 ack alastairc 16:44:52 Gundula: Weused the term adjacent coloralso in 1.4.11 - there it states that intermediate pixels in between color areas cna be neglected 16:45:14 "Where the area is adjacent to the component" 16:45:32 +1 16:45:32 ack mbgower 16:45:39 Alastair: Whas discussed recently; the solution was an aspect to incorporate "where the area is adjacent to the component" 16:46:46 MikeG: The difference between this one and 1.4.11 was whether the indicator stays contrasty - if you add a halo it doesn't make the indicator imperceptible 16:47:25 ...Here we are not talking not about the component but the indicator, which can be a few pixels away from the component 16:48:04 q+ 16:48:26 q+ to say - can we agree the understanding doc updates? And comment on adjacent. 16:48:34 q+ to answer to Mike 16:48:34 ...1. the overall area needs sufficient suze; 2. That area has enough contrast between focused and unfocused state; 3. where it is abutting, it needs to be thimk enough so beople perceive it (thickness) 16:48:57 ...even with halo you need at least 2px thickness requirement anyway 16:49:19 ack alastairc 16:49:19 alastairc, you wanted to say - can we agree the understanding doc updates? And comment on adjacent. 16:49:29 Alastair: no one was objecting o Understandign update 16:49:53 ...we have a slightly simplified version for the adjacent part 16:50:09 "Where the area is adjacent to the component, it has a contrast ratio of at least 3:1 against the component or a thickness of at least 2 CSS pixels." 16:50:34 If I'm not mistaken, we voted against that simplified version a few weeks back 16:50:57 ...either 2 pixels thickness requirement, or revert to prior version where there was a requirement 'where the indicator is adjacent to the component' 16:51:14 ack GN 16:51:14 GN, you wanted to answer to Mike 16:51:25 That would fail 16:51:32 Gundula: Agrees there needs a contrasting area , but also true for 1 pixel 16:51:45 draft RESOLUTION: Accept the understanding document update and survey Adjacent Colors, normative change of word "instead", and exception language (assuming we haven't surveyed it recently in which case we will move them to issues) 16:52:00 +1 16:52:04 (sorry unable to fdully capture details of this technical discussion above) 16:52:13 q+ 16:52:16 +1 16:52:18 +1 16:52:21 +1 16:52:22 +1 16:52:23 +1 16:52:34 ack mbgower 16:52:53 MikeG: Adjacent colors has not changed here, was resolutin from last week 16:53:04 q+ 16:53:12 Minutes with that resolution: https://www.w3.org/2022/04/19-ag-minutes#item07 16:53:30 draft RESOLUTION: Accept the understanding document update and survey Adjacent Colors, normative change of word "instead", and exception language (assuming we haven't surveyed it recently, if surveyed recently it will move to an issue) 16:53:30 Wilco: my recollection: We did not have the final wording of this 16:53:40 Rachael: Need to go back and check 16:53:44 This is the diff we were looking at: https://github.com/w3c/wcag/pull/2283/files#diff-444c5829eebc004b2bed36e50ccd93bbc460c08d46c2bf15d4675daa34bfd9bf 16:53:48 RESOLUTION: Approve the change to use "Encloses" and "adjacent colors" in the SC text. 16:53:50 draft RESOLUTION: Accept the understanding document update and survey Adjacent Colors, normative change of word "instead", and exception language (assuming we haven't surveyed them recently, if surveyed recently it will move to an issue) 16:54:25 Rachael: Mike pasted from the previous notes? 16:54:32 s/RESOLUTION: Approve the change to use/ 16:54:37 Rachael: Open an issue (Wilco) 16:54:44 +1 to draft resolution 16:55:00 q+ 16:55:06 Rachael: Mike agree with this resolution? 16:55:11 ack me 16:55:13 ack Wilco_ 16:55:17 ack alastairc 16:55:36 Alastair: We included that change, have covered it 16:55:49 +1 16:55:57 RESOLUTION: Accept the understanding document update and survey Adjacent Colors, normative change of word "instead", and exception language (assuming we haven't surveyed them recently, if surveyed recently it will move to an issue) 16:56:04 q+ 16:56:10 Rachael: Use the last few minutes to discuss adjacent colors 16:56:13 ack mbgower 16:56:26 q- 16:56:32 MikeG: Let's better talk about the use of the word 'instead'? 16:57:01 Draft poll: Use current 'adjacent colors' (1), or revert to the previous version (2) 16:57:13 Rachael: Do we need adjecent colors or revert to 'adjacent to the component' do we need to straw poll that 16:57:13 2 16:57:19 2 16:57:25 please paste 16:57:41 straw poll: 1) Keep adjacent colors 2) Change back to Where the area is adjacent to the component 16:57:54 2 (soft) 16:57:57 "Where the area is adjacent to the component, it has a contrast ratio of at least 3:1 against the component or a thickness of at least 2 CSS pixels." 16:58:00 Mike: Pleas aste wording 16:58:08 q+ 16:58:08 1 16:58:11 1 prefered, but not against 2 16:58:14 ack jon_avila 16:58:35 q+ 16:58:41 Jon: Is it that the secnd applies to both sides of the indicator? 16:59:07 2) 16:59:11 q+ 16:59:12 2 16:59:15 ack Wilco_ 16:59:22 1 16:59:25 Alastair: Yes - if it is a big indicator you need the 2 pixel thickness, the older one allowed one picel with gradient 17:00:12 Wilco: The high opacity part of the indicator should contrast to its low opacity part - is that it? 17:00:48 MikeG: The indicator can cut though other things on the page - the wording does not cove that well now 17:00:52 Thank you 17:01:04 present+ 17:01:09 rrsagent, make minutes 17:01:09 I have made the request to generate https://www.w3.org/2022/04/26-ag-minutes.html alastairc 17:01:24 zakim, make logs world 17:01:27 I don't understand 'make logs world', Rachael 17:01:33 rrsagent, make logs world 17:27:09 maryjom has joined #ag 17:55:31 mbgower has joined #ag 18:04:06 mbgower has joined #ag 18:45:13 jamesn has joined #ag 20:20:31 maryjom has joined #ag