14:48:39 RRSAgent has joined #ag 14:48:43 logging to https://www.w3.org/2024/10/22-ag-irc 14:48:43 RRSAgent, make logs Public 14:48:44 Meeting: AGWG Teleconference 14:49:40 agenda+ Announcements 14:49:50 agenda+ Requirements Publication https://github.com/w3c/wcag3/pull/117 14:50:07 agenda+ WCAG 2.x issues https://lists.w3.org/Archives/Public/public-wcag2-issues/2024Oct/0002.html 14:50:30 Agenda+ Breakouts for technical-statement refinements & notes 14:54:27 Chuck has joined #ag 14:54:34 present+ 14:56:02 chair:alastairc 14:56:04 present+ 14:56:10 agenda? 14:58:39 GreggVan has joined #ag 14:59:09 giacomo-petri has joined #ag 14:59:31 Francis_Storr has joined #ag 14:59:31 dj has joined #ag 14:59:36 present+ 15:00:34 Kimberly has joined #ag 15:00:37 Laura_Carlson has joined #ag 15:00:47 Laura_Carlson has left #ag 15:00:52 Laura_Carlson has joined #ag 15:00:58 present+ 15:01:01 present+ 15:01:19 Azlan has joined #ag 15:01:26 jeanne has joined #ag 15:01:35 present+ 15:01:46 ashleyfirth has joined #ag 15:02:07 Laura_Carlson has joined #ag 15:02:12 filippo-zorzi has joined #ag 15:02:37 present+ 15:02:37 bruce_bailey has joined #ag 15:02:39 present+ 15:02:45 https://www.w3.org/WAI/GL/wiki/Scribe_List 15:02:57 Jennie_Delisi has joined #ag 15:03:03 present+ 15:03:16 ShawnT has joined #ag 15:03:19 present+ 15:03:19 jeanne2 has joined #ag 15:03:44 present+ 15:03:50 zakim, pick a scribe 15:03:50 Not knowing who is chairing or who scribed recently, I propose Jennie_Delisi 15:03:50 * I can scribe if needed 15:03:53 present+ 15:03:54 GN015 has joined #ag 15:03:54 present+ 15:04:07 scribe: Jennie 15:04:16 Kimberly has joined #ag 15:04:25 aditya has joined #ag 15:04:28 julierawe has joined #ag 15:04:29 zakim, take up next item 15:04:29 agendum 1 -- Announcements -- taken up [from alastairc] 15:04:32 jtoles has joined #ag 15:04:35 present+ 15:04:36 present+ 15:04:48 nina has joined #ag 15:04:48 Makoto has joined #ag 15:04:52 sarahhorton has joined #ag 15:04:55 Alastairc: Chairs discussed item from TPAC: starting a mentoring or buddy system 15:04:58 present+ 15:04:59 present+ 15:05:04 ...someone with more experience. 15:05:05 Tananda has joined #ag 15:05:14 ...There is a video for new people starting. 15:05:17 present+ 15:05:32 MJ has joined #ag 15:05:39 ...Is there anyone interested in helping set up a spreadsheet and matching people? 15:06:01 Justine has joined #ag 15:06:04 present+ 15:06:09 ...If you are interested in becoming a mentor or buddy, please email the chairs. 15:06:24 present + 15:06:41 steveF has joined #ag 15:06:43 Gez has joined #AG 15:06:53 present+ 15:06:55 https://www.w3.org/2002/09/wbs/35422/AGWGSubgroupParticipation_Oct_24/ 15:07:07 present+ 15:07:10 Chuck: Announcement 2 - need volunteers for these subgroups 15:07:24 ...This survey is open until end of day today, Boston time. 15:07:33 AlinaV has joined #ag 15:07:35 ...When they start: it will be working sessions in this call. 15:07:42 present+ 15:07:50 ...Then there will be times outside of this call. 15:07:59 q+ 15:08:02 Graham has joined #ag 15:08:13 present+ 15:08:15 q? 15:08:19 ack DJ 15:08:23 DJ: The subgroup form time? 15:08:55 Chuck: Consider it daylight savings time 15:09:10 Alastairc: Boston time is the way our times are set. 15:09:29 ...Anyone new who would like to introduce themselves? 15:09:41 zakim, take up next item 15:09:41 agendum 2 -- Requirements Publication https://github.com/w3c/wcag3/pull/117 -- taken up [from alastairc] 15:10:07 present+ 15:10:23 Alastairc: Background: Requirements for WCAG 3 turns into a document to assess how successful WCAG 3 is 15:10:26 ...We iterated. 15:10:50 ...Earlier in the year: issues available on Github related to this document 15:11:07 ...Small group reviewed, and made changes to the document. We are in the final stages getting ready for publication. 15:11:10 Frankie7 has joined #ag 15:11:16 present+ 15:11:21 ...People have been reviewing, asking questions. 15:11:49 ...Changes include editorial information towards the beginning... 15:12:04 ...In the requirements section are the pieces which will be used to assess success 15:12:27 ...We tried to make them more testable - that WCAG 3 satisfies these requirements. 15:12:39 ...Comments have been resolved, merged in. 15:13:03 present+ 15:13:06 ...A few things were left from a thread on the readability section. 15:13:27 ...(reads the edits made) 15:13:50 ...There is a last minute suggestion 15:13:52 "WCAG 3 is written using the plain language guidance from WCAG 3. The goal is for the widest possible audience to understand WCAG 3 15:14:25 ...1 other change made recently is to add the self-validation section, which overlaps 15:14:35 ...(reads from the document) 15:14:51 ...Should we keep the readability requirement as a separate thing? 15:15:17 ...Or should we remove it because it is taken care of by the self-validation section? 15:15:20 dan_bjorge has joined #ag 15:15:21 ...Questions or comments? 15:15:32 Gregg: This is a requirement and listed separately? 15:15:33 q+ 15:15:59 Alastairc: To me, the self-validation section is the umbrella one, which encompasses the other. 15:16:00 ack julierawe 15:16:10 Julie: One of the design principles, #5, is plain language. 15:16:32 ...Connecting plain language requirements to what makes it into WCAG 3 about plain language. 15:16:42 ...What if the plain language things are not ready yet? 15:16:59 q+ to speak to the use of plain language before final publication 15:17:06 ...Is it essential to tie the section about readability to things specifically in WCAG 3 vs general plain language principles? 15:17:07 ack alastairc 15:17:07 alastairc, you wanted to speak to the use of plain language before final publication 15:17:07 q+ 15:17:14 q+ 15:17:24 present+ 15:17:34 Alastairc: I don't think we have to formally meet the requirements until we get close to the final publication. 15:17:46 ...Also the requirements document will primarily be applied to the normative text. 15:17:55 q+ 15:18:04 +1 15:18:05 ack GreggVan 15:18:09 +1 15:18:19 Gregg: Readability is more than plain language. It has to do with structure, order, organization. 15:18:32 +1 to Gregg 15:18:41 ...I think I would add some of that and leave it in for now. 15:18:53 ack Makoto 15:19:05 Makoto: I think we should keep the readability section. 15:19:13 +1 to keeping plain language 15:19:23 ...It would help ensure it is more readable and understandable. 15:19:30 ack Graham 15:19:32 ...This will help emphasize this. 15:19:53 Graham: Does it still need to be in the design principles section? 15:20:02 q+ to answer 15:20:05 Alastairc: I don't think there is a problem to have it in both places. 15:20:13 ack Rachael 15:20:13 Rachael, you wanted to answer 15:20:24 Rachael: I think the reason it was set up this way is the design principles are aspirational 15:20:32 ...But the requirements are what we use to check. 15:20:44 q+ 15:20:45 q+ 15:20:53 ...Testable ones are the ones we hold ourselves to, and is the reason they are divided up this way 15:21:18 Graham: Is this an overview because we need to define what plain language looks like? 15:21:44 Alastairc: This is "out in the world" - this is an update to it 15:21:53 ...But we are iterating as we go through the process. 15:22:12 Jeanne: Measurability and testability is the difference between the design principles and the requirements 15:22:23 ...More difficult to measure aspects went into the design principles. 15:22:24 current regs in US: “The Plain Writing Act of 2010 requires federal agencies to use plain language when communicating with the public.” 15:22:25 “ 15:22:44 ...Readability is critical, and came out in all input about WCAG 3 15:22:46 q/ 15:22:47 q? 15:22:50 ...That's why it is in the requirements section. 15:22:51 ack Graham 15:22:53 ack jeanne2 15:22:55 ack jeanne 15:22:59 "WCAG 3 is written using the plain language guidance from WCAG 3. The goal is for the widest possible audience to understand WCAG 3." 15:23:06 Alastairc: The proposal is to update that language. 15:23:25 ...(reads from the document) 15:23:34 ...Any objections? 15:23:53 +1 15:23:57 ...OK I can make that update, then it goes to CFC 15:24:00 q+ 15:24:04 Kirkwood: Does that language make sense? 15:24:28 Diff document: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FTR%2Fwcag-3.0-requirements%2F&doc2=https%3A%2F%2Fdeploy-preview-117--wcag3.netlify.app%2Frequirements%2F 15:24:30 Chris: Design principles - "based on requirements of WCAG 2.x and build upon those requirements" 15:24:37 scott has joined #ag 15:24:41 ...Then in the requirements we say "should" 15:24:43 present+ 15:24:56 q+ 15:25:00 ...Seems like we are mentioning a couple of different terms that are conflated when someone is reading it through 15:25:05 ack ChrisLoiselle 15:25:25 present+ Laura_Carlson 15:25:33 Alastairc: Regarding scope: if there are any new things people want to suggest - these can be added into Github 15:25:37 ack Graham 15:25:38 ...Today we are reviewing these changes. 15:25:47 giacomo-petri has joined #ag 15:26:04 Graham: Can we add a caveat about adding to WCAG 3? 15:26:31 Alastairc: In terms of all of them - the requirements are written in present tense 15:26:39 ...and that was a deliberate choice 15:26:51 ...I think that is a quirk about how this document works. 15:27:02 ...Otherwise we would have to make minor edits. 15:27:13 ...Rachael mentions we can add an editor's note to address this. 15:27:14 +1 to editors note then, far better idea! 15:27:34 Alastairc: I did not see any issues with the proposed language. 15:27:40 ljoakley has joined #ag 15:27:43 ...The other topic on this: adding something about mental health. 15:27:46 present+ 15:28:06 ...There is a section in the broad disability support section (reads from the document) 15:28:08 tiffanyburtin has joined #ag 15:28:29 q+ 15:28:34 ...The proposal is to add 15:28:34 "This approach includes particular attention to people whose needs may better be met with a broad testing strategy, such as people with low vision, limited vision, cognitive and learning disabilities, or mental health disabilities." 15:28:55 ...Are we happy to add mental health disabilities to this list? 15:29:02 present+ 15:29:05 ...This is being worked on in the Cognitive and Learning Disabilities Task Force 15:29:10 q+ 15:29:14 ack ljoakley 15:29:18 q+ I had one other question. 15:29:22 q+ 15:29:26 Laurie: There is nothing in here about people with restricted mobility. 15:29:33 ...Why wouldn't we add that in? 15:29:44 Alastairc: Because it was perceived to be well-covered in WCAG 2. 15:29:59 ...Those included were felt to be more difficult to cover in a WCAG 2 structure. 15:29:59 q+ to ask about voice control? 15:30:06 ...Otherwise we have to list all disabilities. 15:30:09 ack GN 15:30:31 GN: Are there consequences for adding mental health because it is a complex topic? 15:30:43 ...How could we cover it from an accessibility perspective? 15:30:48 ack ChrisLoiselle 15:30:53 q+ to speak to mental health 15:31:19 q+ to say that we discussed mental health when writing the original document and chose not to because of the lack of research at that time 15:31:24 Chris: Design principles: in the heading, #4 - is that the same topic that Gregg was asking about? It seems circular to me. 15:31:33 +1 to Chris 15:31:39 ...Should I raise an issue about this or is it covered by this conversation? 15:31:48 Alastairc: WCAG 2 is supposed to conform to WCAG 3. 15:31:55 ...Yes, the guidelines document should conform 15:32:02 q? 15:32:05 ack Rachael 15:32:05 Rachael, you wanted to ask about voice control? and to speak to mental health 15:32:06 Chris: OK. Thank you 15:32:25 Rachael: re mobility - we may want to call out voice control. But I am not sure it fits there. 15:32:41 ...Regarding mental health: it is hard, and it is something COGA is working on - what can be included. 15:32:46 ...It is an important area. 15:32:58 ...There is enough research to make improvements. 15:33:05 ...It is a conversation we will be having. 15:33:20 ...It will only include what we can work in based on research, but this is true of all disabilities. 15:33:21 ack jeanne 15:33:21 jeanne, you wanted to say that we discussed mental health when writing the original document and chose not to because of the lack of research at that time 15:33:34 q+ on the reason for the section 15:33:56 Jeanne: History - we wanted to include mental health. When we looked at it in 2018 - we didn't want to tie ourselves to something without sufficient research. 15:34:03 ack alastairc 15:34:03 alastairc, you wanted to comment on the reason for the section 15:34:15 Alastairc: The reason for the section - it used to be called multiple ways to measure 15:34:25 ...We are trying to go beyond true false statements. 15:34:37 q+ 15:34:45 q+ 15:34:51 ...The different structure and provisions we are including, like assertions - these are the reasons to include something in this section 15:34:57 mental health disabilities should be the language used, no? 15:35:16 ...Along with COGA - it does seem like an area that would benefit from assertions 15:35:16 ack Graham 15:35:34 Graham: We don't we move the whole section into the design principles section? 15:35:34 q+ 15:35:45 ...Then it could grow or shrink without it being a requirement? 15:35:51 q+ on keeping it as a requirement 15:35:55 ack GreggVan 15:36:17 Gregg: 1: Broad disability support is a wonderful section. I think it focuses too much on measuring. 15:36:34 ...It mentions other ways of measuring, but in the end you need to pass or not pass. 15:36:46 +1 to Gregg 15:36:49 ...Even if a sliding scale you need to say where on the scale it passes. 15:37:07 ...We are not mentioning all the things we are doing, or not doing. 15:37:22 ...We are making a broader range of guidance. 15:37:27 ...Measuring is measuring. 15:38:10 ...2: We have limited and low vision as people not included. I am not sure why we have particular attention to low vision 15:38:21 ...I would suggest removing them. 15:38:22 ack Rachael 15:38:37 Rachael: I strongly think we need the broad disability support section. (Chair hat off) 15:38:48 ...The 1st sentence - this is a strong start. 15:38:57 ...I agree with Gregg's comments related to measurement. 15:39:14 ...I like cognitive being called out because getting additional support will be a good test. 15:39:25 ack alastairc 15:39:25 alastairc, you wanted to comment on keeping it as a requirement 15:39:27 ...I think we can simplify it and meet the needs to keep it in this section. 15:39:41 Alastairc: (chair hat off) we should keep something like this in. 15:39:51 ...It needs to be a requirement, not just a design goal. 15:40:16 ...The main thing - we are trying to create something with more flexibility - that is the point. 15:40:28 ...Regarding mental health: maybe it is premature to include it here at the moment. 15:40:47 ...I don't know that there are different mechanisms needed for mental health that isn't in COGA in general. 15:40:55 ...I can poll on this. 15:41:12 ...If people think we need to reframe the whole section... 15:41:29 q+ 15:41:56 Bruce: regarding dropping low vision (missed what he said) 15:42:04 julierawe has joined #ag 15:42:15 Alastairc: I think people in the low vision task force were frustrated that some requests they had re WCAG 2 did not go in 15:42:30 ...That a slightly different approach would enable them to include more provisions 15:42:33 ack bruce_bailey 15:42:53 Bruce: I agree with Gregg that WCAG 2 does a decent job for low vision, in comparison with the needs of COGA 15:42:58 q+ 15:43:06 q+ about LVTF not even trying to be included in 2.2 15:43:07 ack GreggVan 15:43:09 Alastairc: I think we would get an objection if we removed that, from people who are not on the call. 15:43:16 q+ 15:43:53 Gregg: There are people who think low vision / limited vision is something that is an area requiring special attention? 15:44:20 Alastairc: Not special attention, but had certain requirements which could not fit into the true / false 15:44:30 ...There were frustrations around things they could not get into WCAG 2 15:44:47 Gregg: There is so much focus on vision, this could draw concerns from other areas 15:44:56 ...I would remove "limited vision" 15:44:57 +1 to Gregg on removing one of the mentions of vision 15:44:59 perhaps intersectional needs and disabilities and remove the "classes and categories " of disabilities 15:45:09 ...There were things for all areas which could not be fit in 15:45:30 Alastairc: I will take that as an editorial comment. 15:45:31 ack jeanne 15:45:38 q+ 15:45:45 Jeanne: When we first wrote this - there were task forces being formed for different disability groups 15:45:47 +1 to Gregg, acuity versus the visual field. low/limited. i would keep limited rather than low 15:46:00 ...who felt their needs were not getting added into WCAG 2.1 15:46:24 ...Low vision had a number of proposals which did not get added into 2.1 because they did not meet the true / false requirements 15:46:54 ...I was informed by one of the chairs of the low vision task force that they disbanded because they did not feel it was worth their time to continue trying, and would wait for WCAG 3 15:47:06 ...I think it is important to keep it there. 15:47:10 +1 to Alastair I remember the low vision situation the same. But Wayne and JonA are not here to speak to it. 15:47:17 q? 15:47:20 ...If we want to change the order so cognitive goes first in the list, I am fine with that. 15:47:23 q+ 15:47:33 +1 to Jeanne 15:47:36 Chris: In IRC I added a possible suggestion 15:47:48 agree putting with Jeanne 15:48:02 +1 to Jeanne 15:48:05 ...I can echo Jeanne's point to a degree, and I feel we are trying to include rather than exclude 15:48:15 ack ChrisLoiselle 15:48:17 ack Rachael 15:48:18 Rachael: I put a suggested alternative in (chair point on) 15:48:21 +1 to Jeanne 15:48:33 Rachael suggested alternative: WCAG 3 guidance will have a structure, tests, and/or approach that allows for requirements that are not available in WCAG 2.x, such as additional needs of people with cognitive and learning disabilities, intersectional disabilities, and limited vision. 15:48:35 ...Possibly (reads from her comment) 15:48:59 ...This gives us more flexibility, doesn't focus just on the measurement, and uses these as exemplars 15:49:01 WCAG 3 guidance will have a structure, tests, and/or approach that allows for requirements that are not available in WCAG 2.x, such as the additional needs of people with cognitive and learning disabilities, intersectional disabilities, and limited vision. 15:49:04 +1 to Rachael suggestion 15:49:13 +1 15:49:19 +1 15:49:20 q+ 15:49:24 simpler suggestion is just adding "such as (but not limited to) ..." in the current setence? 15:49:40 q- 15:49:58 +1 to Rachael 15:50:05 Alastairc: Should we update the broad disability support to the proposal above? 15:50:12 ...Any suggestions, objections, or comments? 15:50:14 +1 15:50:24 Will we be covering intersectionality? 15:50:28 Rachael: I added the suggested revision 15:50:28 +1 15:50:33 +1 15:50:54 ...(not limited to) 15:50:55 +1 15:50:55 +1 to Rachale #2 15:50:58 +1 15:51:00 +1 15:51:01 +1 15:51:06 Draftr RESOLUTION: Accept the suggestion to replace the current "Broad disability support" 15:51:06 +1 15:51:09 +1 15:51:17 +1 15:51:20 +1 15:51:20 +1 15:51:22 +1 15:51:22 +1 15:51:23 I can't see the suggested text. 15:51:24 +1 15:51:31 WCAG 3 guidance will have a structure, tests, and/or approach that allows for requirements that are not available in 15:51:31 WCAG 2.x, such as (but not limited to) additional needs of people with cognitive and learning disabilities, intersectional disabilities, and limited vision. 15:51:34 +1 15:51:39 +1 15:51:40 +1 15:51:51 +1 15:51:58 RESOLUTION: Accept the suggestion to replace the current "Broad disability support" 15:52:10 Frankie has joined #ag 15:52:30 Alastairc: moving to the WCAG 2 issues 15:52:33 zakim, take up next item 15:52:33 agendum 3 -- WCAG 2.x issues https://lists.w3.org/Archives/Public/public-wcag2-issues/2024Oct/0002.html -- taken up [from alastairc] 15:52:58 Alastairc: We are building to a republication 15:53:08 ...These are large but minor - lots of editorial things 15:53:26 ...Lots of style-guide type things. 15:53:52 ...I am highlighting things which are minor but part of the normative text. 15:53:59 ...They will be added to the CFC 15:54:26 ...The other one, not normative: there was a proposal with discussion about automatic 15:54:35 ...there was some back and forth 15:54:46 ...If you looked at it 2 weeks ago there have been minor updates. 15:54:56 ...If you are concerned about this, please review in the next few days. 15:55:04 ...It has received several thumbs ups 15:55:19 R_Brown8 has joined #ag 15:55:24 ...We will have a CFC soon. 15:55:36 ...Any questions or comments? 15:55:38 Kimberly has joined #ag 15:55:41 nina has joined #ag 15:55:49 zakim, take up next item 15:55:49 agendum 4 -- Breakouts for technical-statement refinements & notes -- taken up [from alastairc] 15:56:03 Alastairc: This is a continuation of our work from last week. 15:56:13 https://docs.google.com/spreadsheets/d/1JgjDonZEvJMc3_k_R6r3siNexeBjigQsqVxvQRhLEN8/edit?gid=0#gid=0 15:56:18 present+ 15:56:19 ...Outcomes are now called technical statements. 15:56:26 ...Are there refinements we can make? 15:56:38 ...It is fine not to know what it means or the intent behind it. 15:56:44 ...We are usability testing it. 15:57:00 ...Notes are given to the subgroups as feedback. 15:57:08 ...There might be things that are easy to update. 15:57:33 q+ 15:58:05 do we have those two links related to the exercise? 15:58:20 ack Jennie_Delisi 15:59:21 my group was 151-180 15:59:44 Have to drop, thank you all! 16:06:16 ljoakley1 has joined #ag 16:15:44 LenB has joined #ag 16:15:49 present+ 16:33:31 giacomo-petri has joined #ag 16:40:53 scott has joined #ag 16:42:39 group 61-90 is "complete". 16:47:05 2 left for us 16:54:33 dj has joined #ag 16:56:07 jtoles has joined #ag 16:56:32 bruce_bailey has joined #ag 16:56:46 q+ 16:57:01 ack bruce_bailey 16:57:26 Need to check 160, 174 etc. 16:58:03 present+ 16:58:09 ljoakley has joined #ag 16:58:38 RRSAgent, make minutes 16:58:40 I have made the request to generate https://www.w3.org/2024/10/22-ag-minutes.html alastairc 18:01:14 Adam_Page has joined #ag 18:48:20 Laura_Carlson has joined #ag 18:48:32 Laura_Carlson has joined #ag