15:27:38 RRSAgent has joined #ag 15:27:43 logging to https://www.w3.org/2025/01/28-ag-irc 15:27:43 RRSAgent, make logs Public 15:27:44 Meeting: AGWG Teleconference 15:28:04 meeting: AGWG-2025-01-28 15:28:13 rrsagent, generate minutes 15:28:14 I have made the request to generate https://www.w3.org/2025/01/28-ag-minutes.html Chuck 15:28:23 agenda+ Assertions and Best Practices https://github.com/w3c/wcag3/discussions/120#discussioncomment-11854616 15:28:35 zakim, clear agenda 15:28:35 agenda cleared 15:28:40 agenda+ Assertions and Best Practices https://github.com/w3c/wcag3/discussions/120#discussioncomment-11854616 15:28:58 agenda+ Follow Up on Paths 15:29:09 agenda+ Subgroup working sessions 15:37:22 Laura_Carlson has joined #ag 15:37:50 regrets: Todd Libby, Roberto Scano 15:45:32 kirkwood_ has joined #AG 15:55:31 Francis_Storr has joined #ag 15:55:43 filippo-zorzi has joined #ag 15:58:04 present+ 15:58:15 Can only stay for 30 minutes as have conflicting customer call. 15:59:20 Tananda has joined #ag 15:59:42 present + 16:00:02 present+ 16:00:10 Jem has joined #ag 16:00:15 bruce_bailey has joined #ag 16:00:48 ShawnT has joined #ag 16:00:58 present+ 16:01:00 julierawe has joined #ag 16:01:02 DJ has joined #ag 16:01:05 present+ 16:01:06 present+ 16:01:10 filippo-zorzi has joined #ag 16:01:11 giacomo-petri has joined #ag 16:01:11 shadi has joined #ag 16:01:15 present+ 16:01:25 present+ 16:01:28 present+ 16:01:31 present+ 16:01:41 wendyreid has joined #ag 16:01:44 present+ 16:01:54 present+ 16:01:56 Makoto has joined #ag 16:01:58 Kimberly has joined #ag 16:01:59 Jennie_Delisi has joined #ag 16:01:59 present+ 16:02:06 present+ 16:02:09 present+ 16:02:20 Azlan has joined #ag 16:02:28 Graham has joined #ag 16:02:29 scribe+ 16:02:39 present+ 16:02:41 present+ 16:02:45 Chuck: Hello everyone and welcome 16:02:50 present+ 16:02:57 ... introductions, anyone new or with a new affiliation/role? 16:03:00 present+ 16:03:12 AlinaV has joined #ag 16:03:27 Melanie: Hi, Melanie Philipp, I formerly presented Deque, now with USAA as an invited expert 16:03:29 present+ 16:04:12 sarahhorton has joined #ag 16:04:13 Jem: Hi, I have missed you all for a year, I work for University of Illinois, I co-facilitate the ARIA authoring group, and I'm an AC rep 16:04:15 present+ 16:04:23 Chuck: Welcome back! 16:04:23 present+ 16:04:31 Rain has joined #ag 16:04:33 Chuck: Announcements 16:04:36 present+ 16:04:48 ... a couple of weeks ago we discussed hosting an onboarding call before the AGWG call 16:04:58 ... we are going to have the first one next week, first meeting of Feb 16:05:08 ... we'll send out an announcement, 30min before the AGWG call 16:05:12 Glenda has joined #ag 16:05:21 ... MJ has agreed to run it, but asked for a chair to help facilitate 16:05:21 MJ and I are cohosting 16:05:24 https://drive.google.com/drive/folders/1iF_B77uZk9tEYXpdeVLR3Q-FmHw66611 16:05:25 ... we are working on that 16:05:29 mbgower has joined #ag 16:05:32 present+ 16:05:37 ... I pasted a link in IRC for our training materials 16:05:51 jtoles has joined #ag 16:05:54 ... I've hosted and recorded an onboarding session in the past, content and recording is in the link as well 16:05:59 ... any questions? 16:06:16 kevin: Related to IRC dropping 16:06:26 present+ 16:06:27 ... systeam worked out what was going on 16:06:33 ... we have a solution which we will try 16:06:44 ... will kick in starting thursday, related to our cloudflare services 16:06:52 present+ Laura_Carlson 16:06:56 Frankie has joined #ag 16:07:01 Gez has joined #AG 16:07:02 present+ 16:07:02 maryjom has joined #ag 16:07:04 ... if folks who have issues, pay attention after thursday, let systeam know 16:07:07 present+ 16:07:15 present+ 16:07:27 Chuck: Good news, looking forward to it 16:07:32 kevin: Sorry its taken so long 16:07:33 q+ 16:07:48 ack Rah 16:07:50 ack Rac 16:07:52 ack bru 16:07:54 bruce_bailey: Just checking that we're keeping the new client? 16:08:14 kevin: Yes, this is specifically related to the lounge, there are other clients out there that handle the drops more effectively 16:08:16 stevef8 has joined #ag 16:08:17 ... like IRCCloud 16:08:28 ... the lounge makes it difficult, so it's not ideal 16:08:30 stevef8 has left #ag 16:08:33 zakim, take up item 1 16:08:33 agendum 1 -- Assertions and Best Practices https://github.com/w3c/wcag3/discussions/120#discussioncomment-11854616 -- taken up [from Chuck] 16:08:48 Chuck: Starting with the agenda, first item, to discuss recommendations and best practices 16:08:57 ... will be sharing my screen, let me know if there are any issues 16:08:58 SteveF has joined #ag 16:09:10 present+ 16:09:11 ... first thing I'd like to do is review a summary of the conversation in this issue 16:09:22 ... go through some exemplars 16:09:30 ... Rachael did a summary on Jan 16 16:10:17 ... Gregg proposed recommendations, Shawn suggested Best Practices since recommendations is loaded, Jon suggested "Advisory Techniques" 16:10:26 ... we've had a rich conversation about assertions 16:10:39 ... differences between supplemental requirements, assertions, and best practices 16:10:45 ... some people offered feedback 16:11:32 wendyreid7 has joined #ag 16:11:41 scribe+ 16:11:44 scribe+ 16:11:57 Chuck: [continued reading off page] 16:12:11 ... Chris offered an analogy 16:12:18 https://github.com/w3c/wcag3/discussions/120#discussioncomment-11855122 16:12:34 Jen_G has joined #ag 16:12:48 ... based on basketball 16:13:10 ... Alastair also provided some examples 16:13:23 ... alt text requirement, non-decorative images require alt 16:13:25 roldon_b has joined #ag 16:13:46 ... best practice, images part of a wrapper have no alt 16:14:04 ... further discussion of supplemental requirements 16:14:16 Detlev has joined #ag 16:14:19 ... these are examples that were part of the online discussion 16:14:25 ... any clarifications or comments? 16:14:26 present+ 16:14:35 Chuck: Any questions? 16:14:38 q+ on how this relates to conformance 16:14:45 ack ala 16:14:45 alastairc, you wanted to comment on how this relates to conformance 16:14:45 ... bruce_bailey I know you provided a lot of questions 16:14:54 present+ 16:14:57 alastairc: Just wanted to relate this to the conformance discussions at TPAC 16:15:05 ... foundational requirements in a decision tree 16:15:20 ... we've also got supplemental requirements, objectively testable, but part of scoring 16:15:31 ... meet foundational, and then add those to meet high levels of conformance 16:15:47 ... where I see best practices fitting in, you don't want it part of scoring, they're highly dependent on context 16:16:08 ... the example I gave was "in this specific scenario", but it would not be universally applicable 16:16:19 ... the difference with assertions is that they are more process-based 16:16:34 ... it's not something that a random third-party could confirm 16:16:41 q+ to ask about best practices and the decision tree 16:16:47 ... it's tied to the conformance, we'd not be using bestp ractices for scoring 16:16:53 Hello, please excuse this late entry about this topic. However, I feel that “Best Practice” is something that is clearly based in evidence or an industry standard which can provide a benchmark. While a recommendation is a suggestion, if it isn’t suggesting evidence and what can be seen as a benchmark, it can’t have the title of “Best 16:16:53 Practice”. 16:16:53 Chuck: Raises a question for me 16:17:10 ... best practices, where would they live? I don't think they belong in the decision tree 16:17:38 alastairc: The things we have been putting in the decision tree are things applicable to the scenario, they are all required, just helps form the scenario 16:18:06 ... but since we committed to a scoring mechanism for supplemental requirements, they can't go in the tree, it could be in a flat list outside of the tree 16:18:26 Chuck: What we're looking to decide here is whether we should include best practices 16:18:31 ... I haven't seen any objections 16:18:37 +1 to best practices 16:18:42 q+ 16:18:45 q+ 16:18:46 ack Ch 16:18:46 Chuck: Does anyone have any concerns about best practices 16:18:46 Chuck, you wanted to ask about best practices and the decision tree 16:18:48 ack rach 16:19:09 Rachael: I don't have a concern, I think we should include them, I am struggling with where they sit, they feel more method level than requirement lelve 16:19:19 ... and potentially better handled by assertions 16:19:27 ack jtoles 16:19:50 q+ to suggest we ask sub-groups to gather / mark things as best practices, see where they fit 16:19:58 jtoles: I don't have any concerns, I think they should be included, I work with people in education, they take it as "things you should be doing", whereas we understand it as "above and beyond" 16:20:09 ack ala 16:20:09 alastairc, you wanted to suggest we ask sub-groups to gather / mark things as best practices, see where they fit 16:20:10 ... it can be a point of confusion between people in accessibility vs outside of it 16:20:11 +1 to Jon 16:20:28 alastairc: I would suggest we allow for sub-groups to mark things as best practices and see where they fit 16:20:29 +1 to Alastair's suggestion 16:20:31 q+ to mention USAB "best practices" webinar series 16:20:37 q+ to address terminology 16:21:03 ... I'm fairly sure that we have had things we've discussed where we like it but it's not a requirement, but noting them down, we can work out where they might fit 16:21:11 ... potential for them to highly context-specific 16:21:26 ... on the terminology, I'd like to call them recommendations, but Shawn is right, it's a loaded term 16:21:36 ack bruce 16:21:36 bruce_bailey, you wanted to mention USAB "best practices" webinar series 16:21:38 ... if anyone has a suggestion that doesn't clash, I'd love to hear it 16:21:46 bruce_bailey: +1 to jtoles' comment 16:22:01 q+ 16:22:02 ack Ch 16:22:11 wendyreid has joined #ag 16:22:16 scribe+ 16:22:23 Chuck: Another term is "advisory technique" 16:22:31 s/+1 to Jon/+1 to John Toles 16:22:35 ... lots of options, but they can be used for other purposes 16:22:45 q+ to frame of reference 16:22:49 ack Ch 16:22:49 Chuck, you wanted to address terminology 16:22:54 ack DJ 16:22:54 DJ, you wanted to frame of reference 16:23:06 DJ: Sticking to one term as a frame of reference, but we have 2 definitions right now 16:23:08 q+ 16:23:18 ... we should first decide what we are talking about as a frame of reference 16:23:19 ack Chris 16:23:52 ChrisLoiselle: What comes to mind is word soup, we have "recommendation" as in the document, but outside of W3C, when I'm thinking about best practice is the method to do something 16:23:58 ... the method to accomplish a goal 16:24:10 ... if we're in WCAG3 and we have the ability to reset where we're going 16:24:29 q+ on terminology, we're differentiating from 'requirements'. 16:24:32 ... to DJ's point, understanding terms and how they are used, pinpointing how we want to use terms 16:24:51 ... there's still a blur to the applicability of each and what you can use contextually 16:24:53 q+ 16:25:14 alastairc: I think in this group, anything that improves accessibility that we can ask people to do will be a requirement 16:25:23 scribe+ Chuck 16:25:32 ... these things are required but you don't have to do all of them, and these things are recommended 16:25:36 ... thats the term I get stuck on 16:25:40 ack ala 16:25:40 alastairc, you wanted to comment on terminology, we're differentiating from 'requirements'. 16:25:50 ... for the moment as the people working on the content, there is this other bucket we can put things in 16:25:57 scribe+ 16:26:46 wendyreid: we might define best practices differently from others, but i think we all have the same intentions 16:26:51 sarahhorton has joined #ag 16:26:58 ... we want people to make things as accessible as possible 16:26:59 I asked AI to give some options which differentiate between those which are requirements. Some options suggested included: situational recommendations, context-specific suggestions, recommended approaches, context-based recommendations 16:27:19 ... by putting these in the document, we give people the tools to do that without requiring specific solutions 16:27:26 julierawe has joined #ag 16:27:39 q? 16:27:41 q+ to mention explainer and doesn't need to be fixed in stone? 16:27:42 ... i think having all that information in one place will be extremely helpful 16:27:44 scribe: wendyreid 16:27:46 ack wendy 16:27:52 kevin: A few thoughts 16:28:03 q+ for point of order 16:28:06 ack kevin 16:28:06 kevin, you wanted to mention explainer and doesn't need to be fixed in stone? 16:28:08 ... we don't necessarily need to carve a term in stone, we can agree to use best practice for now 16:28:27 ... the key part mentioned in a few comments, being clear about our definitions in our explainer/introduction 16:28:34 ... we can define how we use the term 16:28:36 q+ to different term 16:28:39 q+ 16:28:40 ack Ch 16:28:40 Chuck, you wanted to discuss point of order 16:29:06 ack DJ 16:29:06 DJ, you wanted to different term 16:29:06 Chuck: point of order, chairs I am working on a resolution for this conversation since we're approaching consensus 16:29:32 DJ: I agree with everyone, fully in favour of including this, I'd like to propose "suggested techniques" in order to avoid terms with other meanings 16:29:36 Need to leave for a customer call. I will follow the minutes. 16:29:49 q? 16:29:49 ... not requiring this solution, but accommodates other terms 16:29:53 ack jtoles 16:29:55 Frankie has joined #ag 16:30:19 jtoles: We should definitely include best practice, and even use the term, we just need to clearly define it in the document to avoid confusion 16:31:03 q? 16:31:03 ... a technique we have as a best practice, then trying to find another name, for example, controls should have text labels, but if not, here's some other things you can do that are acceptable 16:31:18 +1 to providing a plain text glossary item for "best practice" or whatever our selected term will be 16:31:26 q+ 16:31:26 proposed RESOLUTION: We agree to allow for "best practices", sub-groups will collect things that fit the approach, and we will review those in a future meeting 16:31:27 present+ 16:31:38 Chuck: reads resolution 16:31:43 +1 16:31:44 Akash-shukla has joined #ag 16:31:44 -1 16:31:45 +1 16:31:56 AlinaV has joined #ag 16:32:07 kevin: Point of order, do we want to add in something about reviewing the terminology 16:32:07 +0 abstain 16:32:14 +1 16:32:48 proposed RESOLUTION: We agree to allow for "best practices", sub-groups will collect things that fit the approach, and we will review those and the terminology in a future meeting 16:32:56 +1 16:32:59 +1, First thing will be - update to the sub-group handbook & template 16:33:01 +1 16:33:03 +1 16:33:03 wendyreid8 has joined #ag 16:33:05 +1 16:33:07 +1 16:33:07 +1 16:33:09 +1 16:33:09 +1 16:33:10 +1 16:33:10 scribe+ 16:33:12 +1 16:33:13 +1 16:33:13 +1 16:33:13 +1 16:33:14 +1 16:33:14 +1 16:33:19 +1\ 16:33:24 Chuck: Any objections? 16:33:24 +1 16:33:29 +1 16:33:41 RESOLUTION: We agree to allow for "best practices", sub-groups will collect things that fit the approach, and we will review those and the terminology in a future meeting 16:33:45 Tananda has joined #ag 16:33:46 zakim, take up next item 16:33:46 I see a speaker queue remaining and respectfully decline to close this agendum, Chuck 16:33:49 ack Ch 16:33:58 ack kevin 16:34:05 zakim, take up next item 16:34:05 agendum 2 -- Follow Up on Paths -- taken up [from Chuck] 16:34:12 Chuck: Follow up on pths 16:34:23 ... a funny thing happened on our way to running the subgroups last week 16:34:31 ... my group didn't have enough participation 16:34:46 ... people came back to the main room asking for materials to help define all the paths 16:34:54 s/pths/paths 16:34:56 ... in between last week and this week, we've updated the handbook 16:35:14 ... and we have provided a link to a document that has some related content regarding the requirements 16:35:17 https://docs.google.com/spreadsheets/d/1Ecg9qFIUVCUQfAPgNSEZ8MmsCSjbAynK8hbGBU8NrzQ/edit?gid=2035961492#gid=2035961492 16:35:23 https://docs.google.com/document/d/1ByDvegN1EpA1rSWXPUAWmX_MGgXJlIgm/edit#heading=h.gjdgxs 16:35:26 ... first thing I would like to do is add the link to the handbook 16:35:35 ... spreadsheet and handbook link is in IRC 16:35:44 ... Rachael, you were updating the handbook, anything to cover? 16:35:59 Rachael: I'm not quite done, so expect more edits 16:36:05 ... we've added more structure 16:36:10 ... links to places you need to get to 16:36:18 ... hopefully this will be clearer 16:36:41 ... getting started is the hardest part, pulling the data you have, where to start, and moving forward 16:36:55 ... do recommend grabbing a chair if you have questions 16:37:08 Chuck: Want to highlight this link to the spreadsheet 16:37:17 ... Kevin put together this pathways doc 16:37:32 ... link to the requirements that helps guide the subgroup in defining and clarifying the requirement 16:37:38 ... most common question 16:37:59 ... I will ask for anyone participating in subgroups if they have any other questions you'd like to ask now 16:38:03 ... anything we haven't addressed? 16:38:08 q? 16:38:27 julierawe: One question about pathways, I was looking at this this morning 16:38:34 q+ 16:38:35 ... it was looking like things have moved to different paths? 16:38:56 ... for example, things that were in organization and structure are now in plain language 16:38:57 ack Rach 16:39:11 Rachael: The organization of the pathways is not the organization of the document 16:39:30 ... mix of things like expertise needed, number of guidelines that are interrelated and connected 16:39:38 ... like grouping together COGA-related guidelines 16:39:52 ... trying to keep the same amount of guidelines in the paths 16:39:54 q+ 16:40:03 Chuck: Did that answer your question? 16:40:07 ack Ch 16:40:08 julierawe: Still processing 16:40:26 Chuck: Wanted to add to that, this was an organizational exercise to try and focus our resources and knowledge 16:40:53 ... it does not necessarily represents the organization of the document, but an educated guess on the best groups of guidelines to tackle 16:41:16 ... as a subgroup does the work is free to create content or recommendations to address in other pathways or guidelines 16:41:19 q? 16:41:24 ... our best guess on how to start this task 16:41:32 Chuck: Any other questions? 16:41:52 ... we might be able to start subgroups early! 16:42:07 rrsagent, please make minutes 16:42:09 I have made the request to generate https://www.w3.org/2025/01/28-ag-minutes.html wendyreid8 16:42:15 https://docs.google.com/spreadsheets/d/1HQYuPuhDYJNJ_9RUgW3G3qMntEpFC7iwYvxBrnY4KMw/edit?gid=528192582#gid=528192582 16:42:33 q+ on update from sub-groups 16:42:39 ack ala 16:42:39 alastairc, you wanted to comment on update from sub-groups 16:43:01 alastairc: So groups can prepare, from next week, we'll do a little update from each sub-group as to where you are in terms of status 16:43:06 ... so we can call keep tabs 16:43:10 ... also to check for overlap 16:43:45 q+ to say you can add me to the safety and deception group on that list 16:43:51 wendyreid5 has joined #ag 16:44:19 we had an input meeting last week! 16:44:32 rrsagent, please make minutes 16:44:34 I have made the request to generate https://www.w3.org/2025/01/28-ag-minutes.html wendyreid5 16:44:40 Yes, Keyboard subgroup transitioned to Inputs starting last week 16:44:40 Detlev - in the tuesday meeting 16:44:40 Detlev - in the tuesday meeting? 16:44:45 yes 16:44:49 https://docs.google.com/spreadsheets/d/1HQYuPuhDYJNJ_9RUgW3G3qMntEpFC7iwYvxBrnY4KMw/edit?gid=528192582#gid=528192582 16:45:14 Hmm, I don't have access, that probably isn't in the right folder? 16:46:44 See https://docs.google.com/spreadsheets/d/1Ecg9qFIUVCUQfAPgNSEZ8MmsCSjbAynK8hbGBU8NrzQ/edit?gid=912588073#gid=912588073 16:51:07 chuck - I think your subgroup spreadsheet is an out of date duplicate. If you look at the Group Members tab of the Pathways For WCAG 3 document, you can more up to date info: https://docs.google.com/spreadsheets/d/1Ecg9qFIUVCUQfAPgNSEZ8MmsCSjbAynK8hbGBU8NrzQ/edit?gid=912588073#gid=912588073 18:01:46 RRSAgent, make minutes 18:01:48 I have made the request to generate https://www.w3.org/2025/01/28-ag-minutes.html alastairc 20:10:01 kirkwood_ has joined #AG