15:18:27 RRSAgent has joined #ag 15:18:31 logging to https://www.w3.org/2024/11/26-ag-irc 15:18:31 RRSAgent, make logs Public 15:18:32 Meeting: AGWG Teleconference 15:18:38 chair: Chuck 15:18:47 meeting: AGWG-2024-11-25 15:18:54 rrsagent, generate minutes 15:18:55 I have made the request to generate https://www.w3.org/2024/11/26-ag-minutes.html Chuck 15:19:03 regrets: Mary Jo Mueller, Bruce Bailey 15:19:13 agenda+ Introduction to FPWD Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)(JJ) 15:19:21 agenda? 15:19:30 zakim, clear agenda 15:19:30 agenda cleared 15:19:34 agenda+ Introduction to FPWD Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)(JJ) 15:19:45 agenda+ Discussions of issues with publication 15:19:54 agenda+ Communications 15:20:06 agenda+ Content Related Definitions (text, image, content, interactive component, etc.) 15:20:19 agenda+ Subgroup working sessions 15:22:53 regrets+ Tiffany Burtin 15:54:14 GreggVan has joined #ag 15:54:41 filippo-zorzi has joined #ag 15:58:18 zakim, who is here? 15:58:18 Present: alastairc, Rachael, ToddL, ShawnT, ChrisLoiselle, Jennie_Delisi, filippo-zorzi, bruce_bailey, Ben_Tillyer, wendyreid, Azlan, Francis_Storr, mbgower, tiffanyburtin, 15:58:22 ... ljoakley, Makoto, mgarrish, nina, julierawe, GreggVan, Gez, kirkwood, Graham, dan_bjorge, MJ, jon_avila, Laura_Carlson, Glenda, scott, LenB, Kimberly 15:58:22 On IRC I see filippo-zorzi, GreggVan, RRSAgent, Chuck, Jem, kirkwood, Zakim, dmontalvo, jedi, elguerrero, hdv, ZoeBijl, alastairc, jeroen, bwang, alice, cwilso, Rachael, tink, 15:58:22 ... ChrisLoiselle, kevin, jcraig 15:58:26 present+ 15:58:34 Present: Kevin, ChrisLoiselle 15:58:46 apologies, can 15:58:48 present+ 15:58:53 apologies can't scribe today. 15:59:12 present+ 15:59:29 thanks! 16:00:07 JJ has joined #ag 16:00:10 present+ 16:00:35 giacomo-petri has joined #ag 16:00:50 Jennie_Delisi has joined #ag 16:00:55 present+ 16:00:58 scribe+ 16:01:08 present+ 16:01:13 Laura_Carlson has joined #ag 16:01:16 present+ 16:01:23 present+ 16:01:33 Tananda has joined #ag 16:01:40 present+ 16:01:48 present + 16:01:52 present+ Laura_Carlson 16:01:56 Chuck: Scribes get positive attention for their efforts 16:02:17 (trophy?) 16:02:24 Chuck: I also try to give out scribe trophies 16:02:41 mbgower has joined #ag 16:02:41 Makoto has joined #ag 16:02:41 GN015 has joined #ag 16:03:03 present+ 16:03:12 present+ 16:03:15 Chuck: Thank you for joining. 16:03:17 ShawnT has joined #ag 16:03:20 present+ 16:03:31 present+ 16:03:31 ...Is there anyone on the call who is new, or has a new role they would like to announce? 16:03:33 julierawe has joined #ag 16:03:36 present+ 16:03:56 ...Announcement: holiday break. 16:04:06 ...December 10th is the last meeting of the year. 16:04:14 ...Next 3 weeks have no meeting 16:04:14 Frankie has joined #ag 16:04:23 ...Subgroups: figure out availability over the holidays 16:04:31 Present+ 16:04:34 ...Our group resumes January 7th 16:04:44 ljoakley has joined #ag 16:04:50 presnet+ 16:04:56 ...Any new topics to add to the new topics list? 16:05:00 present+ 16:05:06 agenda, take up item 1 16:05:16 zakim, take up item 1 16:05:16 agendum 1 -- Introduction to FPWD Guidance on Applying WCAG 2.2 to Mobile (WCAG2Mobile)(JJ) -- taken up [from Chuck] 16:05:30 ToddL has joined #ag 16:05:34 sarahhorton has joined #ag 16:05:37 present+ 16:05:41 present+ 16:05:42 Chuck: This is applying WCAG 2.2 to mobile. 16:05:57 DJ has joined #ag 16:06:00 present+ 16:06:06 ...Jan Jaap will be presenting 16:06:43 JJ: I am the new facilitator of the mobile accessibility task force 16:07:01 ...Android, iOS, but also addressing the larger mobile space including hybrid apps 16:07:01 LenB has joined #ag 16:07:07 present+ 16:07:09 ...On Github: matf 16:07:18 ...Similar set up to WCAG2ICT 16:07:30 ...WCAG2Mobile will be our working name 16:07:44 Azlan has joined #ag 16:07:54 present+ 16:07:59 /me oops, no, it's fine https://github.com/w3c/matf/ 16:08:03 ...(displayed the github information) 16:08:07 BrianE has joined #ag 16:08:21 ...There are files for each success criteria 16:08:26 ...Then we add out guidance 16:08:27 present+ 16:08:39 ...There is a document on the github domain 16:08:46 https://w3c.github.io/matf/ 16:08:54 r_brown has joined #ag 16:09:01 JJ: this is the guidance 16:09:10 ...We are getting ready for our first group draft ntoe 16:09:22 ...We are still working on our abstract, introduction 16:09:30 ...We have comments about our success criteria 16:09:39 ...We have reached consensus for some of them 16:09:59 ...We are taking the text as written from WCAG2ICT, and when needed adding our own changes and notes 16:10:11 ...We are planning to have an expand and collapse 16:10:18 ...1 for WCAG, 1 for WCAT2ICT 16:10:24 ...Underneath you have our guidance 16:10:46 ...This helps people review the sections of interest to them 16:11:00 ...For our draft we have about 17 success criteria with something written. 16:11:06 ...We are looking for feedback. 16:11:22 ...We are interested in hearing what is missing. 16:11:24 q? 16:11:28 q+ 16:11:45 q+ to ask where the controversial ones might be? 16:11:45 Chuck: Your ask is for group members to review and provide feedback - correct 16:11:48 q+ 16:12:02 ack kikr 16:12:03 JJ: Yes. Especially the alignment to WCAG and WCAG2ICT. And if there are issues we should address. 16:12:05 ack kirk 16:12:10 Detlev has joined #ag 16:12:22 kirkwood: You characterized this as non-web. Is that the terminology? 16:12:30 JJ: No, not in our current workstatement. 16:12:31 great work on this. Thanks for your presentation ! I like the alignment where it is applicable. 16:12:44 ...I did try to focus on native, but we are considering other types. 16:12:58 kirkwood: Thank you for clarifying. 16:13:11 ...This will be a focus from a regulatory perspective. 16:13:16 Jen_G has joined #ag 16:13:17 From Work Statement: The objective of the Task Force is to produce informative resources for applying WCAG to Mobile Applications, including but not limited to native mobile apps, mobile web apps, mobile web content, and hybrid apps using web components inside native mobile apps. 16:13:18 JJ: I will put the work statement in chat 16:13:23 ack ala 16:13:23 alastairc, you wanted to ask where the controversial ones might be? 16:13:41 Present+ 16:13:48 https://github.com/w3c/matf/issues?q=is%3Aissue+is%3Aopen+label%3Alarge-variation 16:13:48 alastairc: From the draft - most of the conversation is happening around the ones which need to vary more. 16:13:59 ...There is a tag for large variation. For me - that is where I will start. 16:14:09 JJ: The draft only contains the ones we have reached consensus on. 16:14:23 jj: Yes, most of the description is happening in the medium and large variation ones. 16:14:27 ack kevin 16:14:48 s/most of the description/most of the discussion 16:14:48 mbgower has joined #ag 16:14:53 Kevin: I think it would be good to have an element of consensus from the group to publish 16:14:57 q? 16:14:57 ...because it is the first time 16:15:05 q+ 16:15:07 Chuck: Any other questions? 16:15:09 ack Ch 16:15:19 Chuck: JJ - what is your preferred engagement? 16:15:28 ...How would you like them to share with the group? 16:15:40 JJ: Ideally in a github issue so we can assign it to someone. 16:15:47 q+ 16:15:51 ...Or if there is an existing issues, continue with those. 16:15:52 nina has joined #ag 16:15:56 ...Otherwise the public email 16:16:11 ...Also possible is to use Slack, though this is not preferred. 16:16:13 There is a "feedback" section at the top of the draft: https://w3c.github.io/matf/ 16:16:17 could you add the exploratory tag to the SCs in conversation that vary and point to the GitHub in the section? 16:16:19 ack Chris 16:16:47 ChrisLoiselle: In the W3 document .io - there is a reference to github 16:16:55 ...and possibly tag exploratory? 16:17:00 ...That's a suggestion 16:17:05 JJ: Yes, that is something we can do. 16:17:17 ...Normally you would not link to an external website. 16:17:32 ...We could place a link to the issue for people to join the discussion if we are allowed to do. 16:17:36 q? 16:17:38 ...I think that would help. 16:17:47 Chuck: Any other questions or thoughts? 16:17:49 zakim, take up next item 16:17:49 agendum 2 -- Discussions of issues with publication -- taken up [from Chuck] 16:18:10 Chuck: Publication: we are working with maximum effort on the next draft of WCAG 3 16:18:19 ...We have been making changes on the side. 16:18:22 The most recent version: https://w3c.github.io/wcag3/guidelines/ 16:18:33 Alastairc: I will share screen 16:18:55 ...This latest version - I will highlight areas of interest 16:19:08 ...At the top: there are a set of questions we are asking the public for feedback on 16:19:16 ...(reads those questions) 16:19:39 ...Most of this we asked for review a few weeks ago, so there have been minor changes 16:19:44 ...To images alternatives 16:19:57 ...This has the outcome, and the provisions 16:20:01 ...The decision tree. 16:20:04 Detlev has joined #ag 16:20:10 present+ 16:20:21 ...Most of these direct links should work. They are on the right. 16:20:29 ...Some of the definitions have content. 16:20:40 q+ to suggest that "Avoid cognitive tasks" and should perhaps still be changed 16:20:51 ...There are links to the appropriate method. 16:20:55 ...Clear meaning is the new one. 16:21:07 ...We have a decision tree which works slightly differently than the others. 16:21:08 q? 16:21:10 Q+ 16:21:13 ...If you have a preference, please comment. 16:21:20 ack Detlev 16:21:20 Detlev, you wanted to suggest that "Avoid cognitive tasks" and should perhaps still be changed 16:21:48 Detlev: I hope that this one guideline sounds odd where it says "Avoid cognitive tasks" 16:21:53 q+ 16:21:56 ...Can it still be changed? 16:21:58 ack Chris 16:22:07 ChrisLoiselle: To keep up with terminology 16:22:18 ...Are we now using foundational provision instead of requirements? 16:22:30 q+ 16:22:31 Alastair: yes. Foundational, supplemental, and assertions. 16:22:33 ack Rach 16:22:46 q+ 16:22:53 Rachael: Re name change: most are exploratory, and just placeholders. 16:23:04 makes sense, thanks! 16:23:05 ...If there are ones like Detlev called out - we can change those now. 16:23:17 ack julie 16:23:18 ...Pretty easy to change as long as nobody objects. 16:23:31 Julierawe: Looking at the image alternatives section - there is a style guide 16:23:42 q+ on style guide 16:23:42 ...Is that one there as a foundational requirement? 16:23:48 ...How is that part of the image alternatives. 16:23:51 ack Gregg 16:23:58 GreggVan: We changes from requirements to revisions 16:23:59 agree “avoid cognitive tasks” doesn’t sound right…. “avoid undue cognitive pressure… or something like that (needs work) 16:24:05 sarahhorton has joined #ag 16:24:11 ...We need a way to tell the requirements from the conditions. 16:24:16 ...We don't have a shall vs should 16:24:38 q+ to answer gregg 16:24:38 ack ala 16:24:39 alastairc, you wanted to comment on style guide 16:24:46 ...If not to include recommendations - how will we tell the difference between requirements and recommendations 16:24:57 Alastairc: Regarding the style guide - we have assertion next ot it 16:25:08 ...Everything under image alternatives 16:25:18 q+ 16:25:19 Detlev has joined #ag 16:25:23 ...We have foundational ones, supplemental ones (above the base level of conformance) 16:25:27 ...and we have assertions. 16:25:37 ...There is also a note saying we are considering recommendations 16:25:45 ack Rach 16:25:45 Rachael, you wanted to answer gregg 16:25:50 ...Not all guidelines will have all of those, but they are the ones we discussed so far. 16:25:54 "2.9.1 Reduce cognitive load" might be an option 16:26:00 Rachael: right now we only use provision in a few places. 16:26:08 ...We could replace the first one. 16:26:13 ack Gregg 16:26:15 ...To address the concern. 16:26:21 GreggVan: That would be great. 16:26:25 q+ 16:26:25 +1 to changing provisions to requirements 16:26:43 ...Requirements and recommendation...and avoid ambiguity 16:26:44 q+ on including non-requirements in decision tree. 16:26:45 q+ to mention Detlev's suggestion Reduce Cognitive Load 16:26:58 present+ 16:27:00 ...In the keyboard group we have mixed requirements and recommendations 16:27:05 q+ 16:27:07 +1 for a non technical non W3 member to understand this from non technical plain language standpoint 16:27:17 ack julie 16:27:24 Chris, sorry, +1 to which bit? 16:27:42 Julierawe: Having assertions listed - I just noticed another set of guidelines with an assertion with a styleguide listed 16:27:47 ...Clear meaning will have one as well. 16:27:57 q+ to answer Julie 16:27:59 ...Will the longterm plan be to have one at the end of every section? 16:28:02 ack ala 16:28:02 alastairc, you wanted to comment on including non-requirements in decision tree. 16:28:08 +1 to the use of terms being used appropriately and defined. 16:28:13 Alastair: to answer Julie's question 16:28:15 q- 16:28:31 ...We need to get through a few more examples so we can work out if we can have a standardized style guide 16:28:41 ...And then will have to discuss how this impacts conformance. 16:28:59 ...For now we are including it because it is part of our intended scope 16:29:19 ...Gregg was talking about adding the recommendations into the decision tree - I found that hard to do 16:29:23 q+ 16:29:28 ...if you are trying to use it to get to a pass or fail. 16:29:45 ...You would have to stack some of them at the beginning or end, when you already have your pass or fail. 16:29:55 ...The tree helps with the pass/fail. 16:30:08 ...But if the things that are not foundational - if they are used for scoring. 16:30:14 ...They don't work in a tree as such. 16:30:21 ...I would be interested to see the keyboard one. 16:30:24 q? 16:30:26 ack Ch 16:30:26 Chuck, you wanted to mention Detlev's suggestion Reduce Cognitive Load 16:30:31 ...But for the ones reviewed so far, I cannot see a way to do that. 16:30:44 Chuck: Detlev made a suggestion of reduce cognitive load 16:30:49 ...To update the name of that one. 16:30:49 ack Gregg 16:31:00 GreggVan: We cannot really use a direction item 16:31:06 ...You can never satisfy that 16:31:16 ...You have to have something which is a target. 16:31:20 minimize 16:31:22 ...A minimum conformance level. 16:31:28 ...Unless it is a recommendation. 16:31:33 q? 16:31:35 "Avoid complex cognitive tasks"? 16:31:39 ...Then you can reduce, because you don't test a recommendation. 16:31:57 ...Re Alastair's comment - there are some recommendations which would come alongside the requirement. 16:31:58 agree ‘reduce’ is a comparative action 16:32:04 ...But many are attached to a requirement. 16:32:16 ...You must do this, best practice to do that... 16:32:21 ...Makes sense to put them there. 16:32:39 ...They do not contribute to scoring, but then they are located along with the other information. 16:32:43 q+ on listing together 16:32:47 q+ 16:32:56 ...I think they should be together. 16:33:01 ...It could be in 2 columns. 16:33:03 q+ to say Users can complete tasks without needing to memorize nor complete advanced cognitive tasks 16:33:07 “minimize cognitive load” (?) 16:33:10 My main point was that "Avoid Cognitive Tasks" sounds weird. I am not partial t any there particular name - so if reduce does not work it could be "Low cognitive load" 16:33:17 ...Then if there are points for the recommendations, but this might be hard to do. 16:33:28 ack ala 16:33:28 alastairc, you wanted to comment on listing together 16:33:33 ...This would help get more of the untestable stuff in there. 16:33:44 Alastairc: Onscreen are the list of provisions. 16:33:52 ...It is in the listing. 16:33:53 q+ to say if and how we want to incorporate recommendations is a future conversation, post this publication 16:34:11 ack julie 16:34:15 ...I think it will be useful once we review the keyboard one to see if there can be alignment. 16:34:34 Julierawe: Will there be a link between the WCAG 3 guidelines and the how-to information living under WAI? 16:34:39 q? 16:34:42 ...Will there be an easy way to get between them? 16:34:54 ack Rach 16:34:54 Rachael, you wanted to say if and how we want to incorporate recommendations is a future conversation, post this publication 16:34:57 Alastairc: Yes. It is in the "i" area that says "how to meet" 16:35:03 dan_bjorge has joined #ag 16:35:05 present+ 16:35:10 q+ 16:35:18 ack Ch 16:35:18 Chuck, you wanted to say Users can complete tasks without needing to memorize nor complete advanced cognitive tasks 16:35:19 Rachael: Re incorporating recommendations - we had decided to postpone it and we will come back to it. 16:35:33 Chuck: There have been conversation around the naming of one of the guidelines 16:35:42 ...I want to see if we can decide what that should be. 16:35:53 ...Users can complete tasks (continues reading) 16:35:59 No memorization 16:36:08 ...that is one possible title suggested. 16:36:17 ack Dan 16:36:33 DB: I see the yellow and red 4s at the top of the document. 16:36:34 q+ 16:36:37 qq+ 16:36:39 ...Are these already being addressed? 16:36:49 ack kevin 16:36:49 kevin, you wanted to react to dan_bjorge 16:36:57 Kevin: They are not programmatic errors. 16:37:04 ...They are missing defintions 16:37:13 ack Rach 16:37:30 Rachael: some of those are missing links, and I have been doing some of those fixes while we have been meeting. 16:37:37 Chuck: Back to the title 16:37:41 minimize cognitive load 16:37:45 ...of the one success critieria 16:37:53 No memorization 16:37:58 Detlev also suggested Low Cognitive Load 16:38:14 Chuck: 3 suggestions 16:38:21 q+ 16:38:26 q+ 16:38:28 Any other suggestions? 16:38:29 ack Gregg 16:38:36 GreggVan: I think low works. 16:38:37 avoid high cognitive load 16:38:40 r_brown has joined #ag 16:38:40 q+ 16:39:01 DB: I think low cognitive load is an improvement. 16:39:15 ...But no memorization - 2.9.5 is fairly close. 16:39:18 q+ 16:39:22 draft poll: 1) Minimize Cognitive Load, 2) Low Cognitive Load, 3) No Memorization 16:39:26 ack dan 16:39:28 ack lj 16:39:46 ljoakley: If we say complete advance cognitive tasks - will that cover the new types of people challenges with puzzle pieces needing to go in the correct place to access the site? 16:39:47 ack Rach 16:40:02 Rachael: This section of guidance has not had a subgroup work on it - it is exploratory 16:40:18 ...Conversations around what it will cover does not need to happen or be decided. 16:40:26 ...Please watch for when the subgroup happens. 16:40:57 scribe+ 16:40:58 scribe: Rachael 16:41:09 Jennie_Delisi has joined #ag 16:41:11 scribe: alastairc 16:41:13 present+ 16:41:17 "Avoid cognitive tests"? 16:41:17 poll: 1) Minimize Cognitive Load, 2) Low Cognitive Load, 3) No Memorization 16:41:18 scribe+ 16:41:26 * I am back - thank you 16:41:42 poll: 1) Minimize Cognitive Load, 2) Low Cognitive Load, 3) No Memorization, 4) Avoid cognitive tests 16:41:55 GN015 has joined #ag 16:42:11 q+ 16:42:12 4 16:42:18 ack kevin 16:42:30 Kevin: I sense there are a few definitions required for any of these 16:42:31 ToddL has joined #ag 16:42:31 4 16:42:35 4, but does that address Detlev's understanding? 16:42:40 1/4 16:42:44 4 16:42:44 ...this should be considered what best suits your thoughts. 16:42:46 1 16:42:47 4 > 2 > 1 16:42:47 There is a subentry "No cognitive tests" already... 16:42:56 1 (4 is too close to another that it will likely be merged into in the future) 16:43:00 kirkwood: Does "no memorization" cover it? 16:43:02 q 16:43:07 q+ 16:43:13 ack Det 16:43:16 Chuck: I did not think no memorization covered it. 16:43:16 2 or 4 16:43:23 Frankie has joined #ag 16:43:30 2.) Low Cognitive Load 16:43:35 Detlev: I think avoid cognitive tests which would cover it, but there is an item beneath which covers this. 16:43:39 q+ 16:43:43 q+ 16:43:48 q+ to suggest this needs to be tackled by the sub-group 16:43:51 ...Minimize cognitive load is more general - maybe it covers the spread better. 16:43:58 ack gia 16:44:04 ...I don't have a preference, but the original one is more difficult to understand. 16:44:17 Can someone reshare the options for voting? IRC keeps disconnecting. 16:44:21 Giacomo: The current is very restrictive. 16:44:28 ...There is a difference between test and task. 16:44:31 ack Rach 16:44:38 1, 4 16:44:41 Rachael: I agree changing from tasks to tests reduces the scope. 16:44:52 q+ to report on the results of the poll 16:44:53 1 16:44:55 ...Originally there was one agreed upon in 2.2 - no tests, no puzzles. 16:45:04 ...This one has a broader scope. 16:45:15 1 16:45:18 ...I think there is a different gist to this that the subgroup will need to review. 16:45:19 1 16:45:23 ack ala 16:45:23 alastairc, you wanted to suggest this needs to be tackled by the sub-group 16:45:24 ...I hesitate to remove it 16:45:38 Alastairc: I wonder if we can let it go for the moment, and let the subgroup work on it. 16:45:39 so I correct myself to: 1, alternatively keep the original 16:45:44 OliverH has joined #ag 16:45:49 ...There is something similar coming which may overlap. 16:45:58 ack ch 16:45:58 Chuck, you wanted to report on the results of the poll 16:45:58 1 16:46:00 Chuck: That wasn't a poll option 16:46:09 1 16:46:18 Chuck: At this point, 1 is the highest response 16:46:24 Minimize Cognitive Load 16:46:29 q+ 16:46:29 Frankie has joined #ag 16:46:46 ack Gregg 16:46:46 Chuck: Let's change the name to Minimize Cognitive Load, knowing it needs to go to a subgroup 16:46:58 I think 1 had a stronger objection than the current option. 16:47:10 GreggVan: That is impossible - I could never meet it 16:47:24 ...If this is a requirement, we cannot use that type of vocabulary 16:47:26 q+ 16:47:34 ...The requirement underneath will be to meet some level. 16:47:36 "Avoid cognitive tests & memorization" 16:47:37 q+ to ask if there are any objections to Avoid cognitive tests 16:47:43 ...If it is a recommendation, that is fine. 16:47:57 Jamie has joined #ag 16:48:11 Chuck: Those who supported 1 - do you have objections to the 4th option? 16:48:14 (chair hat off) I object to the 4th option 16:48:20 ...1 was minimize cognitive load 16:48:23 q+ 16:48:25 ...4 was avoid cognitive tests 16:48:26 present+ 16:48:29 ack Ch 16:48:29 Chuck, you wanted to ask if there are any objections to Avoid cognitive tests 16:48:35 q+ 16:48:37 GreggVan: cognitive test means you are testing the person. 16:48:39 ack Greg 16:48:40 Alastair's option is better 16:48:43 Q+ 16:48:50 ...These are tests for whether it is a human. 16:48:51 q+ 16:48:57 LenB has joined #ag 16:49:09 I'd like to also propose in the poll to keep it as is for now, waiting for subgroup feedback 16:49:11 ack Rach 16:49:12 I prefer the original over Option 4, as 'tasks' is wider than 'tests' 16:49:21 Rachael: I object to changing tests to tasks. 16:49:26 ...that is chair hat off. 16:49:34 ack Chris 16:49:35 ...This is talking about tasks. 16:49:35 +1 to Rachael 16:49:56 ChrisLoiselle: I feel it is more a subgroup thing 16:49:57 +1 to subgroup work needed. 16:50:02 ...as opposed to word smithing here. 16:50:07 +1 16:50:09 q- 16:50:12 +1 subgroup 16:50:13 ...There is a lot related to instructions and detailed instructions 16:50:23 +1, leave as is 16:50:26 “CAPTCHA can test users’ cognitive ability” 16:50:28 +1 to leave as is 16:50:29 +1 16:50:31 +1 to leave as is 16:50:31 Chuck: Then we are talking about leaving it here, knowing the subgroup needs to address it 16:50:35 +1 16:50:44 Chuck: We will leave it as is 16:50:45 +1 16:51:08 Chuck: We will send this out to the group for review 16:51:19 Rachael: I think we are asking people to look at it today and tomorrow. 16:51:29 ...If you know of an objection for going to CFC, please raise it. 16:51:37 ...Then we will send the CFC tomorrow. 16:51:52 Chuck: Because Thursday is a U.S. holiday. 16:51:59 ...Be expecting it to go out. 16:52:08 zakim, take up next item 16:52:08 agendum 3 -- Communications -- taken up [from Chuck] 16:52:51 Chuck: There are a lot of people on the call who get questions about what is happening with WCAG 3 16:52:59 ...We also know people will put out social media posts. 16:53:09 ...We appreciate the work to keep the spotlight on the group. 16:53:20 ...We have some communications suggestions 16:53:32 ...These are things which might be helpful. 16:53:39 ...We are moving towards publishing soon. 16:53:58 ...Anyone who wants to create an article - start thinking about what you might want to say. 16:54:02 q? 16:54:07 ...The W3C will have its own communications as well. 16:54:14 ...When considering your communications, 16:54:21 ...Please share that it is a draft. 16:54:34 ...Point out the maturity levels - that most of the content is still exploratory. 16:54:47 ...Include the key questions we want feedback on. 16:55:01 ...Consider adding that WCAG 2 remains the standard of record, and will be so for a while. 16:55:18 ...We would like you to avoid saying that WCAG 3 is around the corner. 16:55:28 ...Also avoid suggesting that people start adopting it. 16:55:59 ...Technical point: if images are used in communications to make key points, consider that the alt text doesn't always get moved forward to the next platform. 16:56:16 q? 16:56:26 Alastairc: images also sometimes do not get pulled through. 16:56:32 Chuck: Any questions? 16:56:43 zakim, take up next item 16:56:43 agendum 4 -- Content Related Definitions (text, image, content, interactive component, etc.) -- taken up [from Chuck] 16:56:59 Chuck: This will be discussed in the future. 16:57:05 https://github.com/w3c/wcag3/discussions/140 16:57:22 Alastairc: I have introduced the topic - thank you to Gundula for responding. 16:57:29 ...We need a few more reactions and comments. 16:57:46 ...There are a few key ones that tend to get referred to a lot. 16:58:06 ...I have suggested a couple of updates to the text one. 16:58:20 ...I suggested an update. 16:58:36 ...There are a couple of questions like: have you come across issues with the WCAG 2 versions we could solve? 16:58:46 ...Would it help if we separated controls from content further? 16:59:00 q+ to either ask for a scribe change or end scribing 16:59:09 ...Now would be a good time to point out solutions. 16:59:15 ...It would be great to have more people review. 16:59:22 ack Ch 16:59:22 Chuck, you wanted to either ask for a scribe change or end scribing 16:59:24 ...We could work on getting these into the next draft. 16:59:37 zakim, take up next item 16:59:37 agendum 5 -- Subgroup working sessions -- taken up [from Chuck] 17:00:53 scribe:alastairc 17:01:04 mbgower has joined #ag 17:01:07 TOPIC: Keyboard feedback 17:01:40 OliK has joined #ag 17:01:48 GreggVan: Originally had 5 provisions, went through them and kept repeating ourselves. E.g. user needs and testing. 17:01:57 ... looked at putting together into 1. 17:02:37 ... came to 9 user-needs / topics, and collapsed them down. 17:02:43 q+ to ask if we could schedule this for next week? 17:03:18 ... in the outcome we added a pre-condition, so you can jump out quickly if it doesn't apply 17:03:28 ... added a list of requirements underneath. 17:03:56 ... the last one is a bit tricky, comparing to other inputs. 17:04:10 q+ to say have you considered "comparable time on task"? 17:05:02 ... then, in the 'foundational requirements' section, it works through the various requirements [see doc, 2nd tab] 17:05:19 ... it incorporates the best practices. 17:05:32 ... they are like recommendations, just a different term. 17:05:52 ... it means you only have to navigate the page once, rather than going through 5 times. 17:05:53 q+ to say that "all elements viewable" is at least awkwardly phrased. Do you mean discoverable? 17:06:04 ... any time there is a recommendation, can be slotted into the tree. 17:06:24 ... sometimes there's best practice that doesn't slot in, went underneath. 17:06:44 ack ch 17:06:44 Chuck, you wanted to ask if we could schedule this for next week? 17:06:52 ... so what used to be a bunch of long, repeated things, it collapsed down into one. 17:07:06 q+ to ask what is the input, and can we treat this as an intro to a conversation next week? 17:07:24 q+ to say it looks like you also have not specified a need for indication of the current item with focus 17:07:29 ... Dan thought it was harder to parse than when separate. 17:07:34 ack mb 17:07:34 mbgower, you wanted to say have you considered "comparable time on task"? and to say that "all elements viewable" is at least awkwardly phrased. Do you mean discoverable? and to 17:07:37 ... say it looks like you also have not specified a need for indication of the current item with focus 17:07:48 mbgower: This seems like a new topic, but three things I noted. 17:08:17 q+ 17:08:19 ... for the final bullet, the comparison, have you considered a time comparable task. 17:08:53 GreggVan: yes, but also impossible. If there are 700 clickable items, there's no way to make that the same as zipping down with a mouse. 17:09:17 mbgower: "comparable time on task" 17:09:54 ... and further down, "all elements viewable", does that mean discoverable? 17:10:23 ... finally, in "h", focus not obscured, doesn't have the core requirement of visible focus indicator? 17:11:02 GreggVan: There's no interface that doesn't do that. 17:11:25 Alastairc: We have a separate guideline for focus-appearance. 17:11:40 GreggVan: Does the group support the overall approach 17:11:44 q+ on approach 17:11:50 ack detlev 17:12:17 Detlev: I like avoiding the duplication of testing, but some of these items seem to fit elsewhere. 17:12:27 qq+ alastairc 17:12:43 ... not sure about one big decision tree. 17:12:45 ack ala 17:12:45 alastairc, you wanted to comment on approach 17:12:48 ack ala 17:12:48 alastairc, you wanted to react to Detlev 17:13:25 ack Ch 17:13:25 Chuck, you wanted to ask what is the input, and can we treat this as an intro to a conversation next week? 17:13:46 giacomo-petri has joined #ag 17:13:48 alastair: If the requiremnets and testing work together, that's a good sign that it is working as a single outcome. 17:13:58 alastair: We have something that covers the visual appearance. 17:15:02 Noting that text contrast is now called "Text appearance" https://docs.google.com/document/d/1EGEgRebgj8XfvwU-Fx2kAtd-3Ifl-UkEgyOxT1Xc5UY/edit?tab=t.0 18:05:14 ShawnT has joined #ag 18:35:05 rrsagent, make minutes 18:35:06 I have made the request to generate https://www.w3.org/2024/11/26-ag-minutes.html Laura_Carlson 19:00:18 Adam_Page has joined #ag 19:20:13 ShawnT has joined #ag 22:02:49 ShawnT has joined #ag 22:40:51 ShawnT has joined #ag