15:18:28 RRSAgent has joined #ag 15:18:32 logging to https://www.w3.org/2024/11/05-ag-irc 15:18:32 RRSAgent, make logs Public 15:18:33 Meeting: AGWG Teleconference 15:18:38 chair: AlastairC 15:18:43 present: AlastairC 15:19:39 Regrets: NatT, Makoto, Poornima, SteveF 15:19:51 agenda+ Announcements and Introductions 15:21:24 agenda? 15:21:31 zakim, clear agenda 15:21:31 agenda cleared 15:21:36 agenda+ Announcements and Introductions 15:37:33 regrets+ JenniferS 15:40:01 Chuck has joined #ag 15:50:50 aditya has joined #ag 15:54:12 LauraBMiller has joined #ag 15:54:53 present+ Laura_Carlson 15:55:01 Scribe: Laura_Carlson 15:55:26 present+ 15:56:19 tiffanyburtin has joined #ag 15:56:27 present+ 15:56:48 present+ 15:59:15 zakim, who is on the call? 15:59:15 Present: AlastairC, Laura_Carlson, LauraBMiller, tiffanyburtin, Rachael 15:59:19 present+ 16:00:12 filippo-zorzi has joined #ag 16:00:19 present+ 16:00:29 AC: Welcome. 16:00:30 Tananda has joined #ag 16:00:46 Jennie_Delisi has joined #ag 16:00:51 agenda? 16:00:54 agenda+ Subgroup wrap up briefings 16:01:02 agenda+ Discuss Explainer https://github.com/w3c/wcag3/pull/116#issuecomment-2444491152 16:01:08 ShawnT has joined #ag 16:01:10 agenda+ Discussion of WCAG 3 Guidelines and Requirements https://docs.google.com/document/d/1Hc5fwRKZVdWPoEp-HzrCu4TTsXF36sozE45OfcYUnKU/edit?tab=t.0 16:01:13 present+ 16:01:17 present + 16:01:21 DJ has joined #ag 16:01:23 agenda+ Existing subgroup Work 16:01:25 agenda? 16:01:27 present+ 16:01:57 GN015 has joined #ag 16:01:59 mgarrish has joined #ag 16:02:05 present+ 16:02:06 MJ has joined #ag 16:02:08 giacomo-petri has joined #ag 16:02:12 present+ 16:02:13 present+ 16:02:15 dan_bjorge has joined #ag 16:02:19 present+ 16:02:20 BrianE has joined #ag 16:02:23 nina has joined #ag 16:02:27 present+ 16:02:27 zakim, take up next item 16:02:27 agendum 1 -- Announcements and Introductions -- taken up [from alastairc] 16:02:29 ac: Any announcements? 16:02:36 present+ 16:02:36 Detlev has joined #ag 16:02:37 bruce_bailey has joined #ag 16:02:44 present+ 16:03:12 present+ 16:03:26 Kimberly has joined #ag 16:03:37 present+ 16:03:43 ... mentoring/buddy system. One person was interested so far. If you would like to be one, please contact the Chairs. 16:03:49 mbgower has joined #ag 16:03:53 present+ 16:03:55 julierawe has joined #ag 16:04:01 ashleyfirth has joined #ag 16:04:01 present+ 16:04:07 present+ 16:04:11 sarahhorton has joined #ag 16:04:15 Jen_G has joined #ag 16:04:34 present+ 16:04:36 present+ 16:04:41 agenda? 16:04:56 Glenda has joined #ag 16:05:04 LenB has joined #ag 16:05:07 Present+ 16:05:14 present+ 16:05:41 ... a CFC is out for errata. One -1 so far. Please respond with your +1 , -1 with reasons, etc. 16:05:50 present+ 16:05:50 q? 16:05:59 q+ 16:06:04 ack MJ 16:06:06 Roland3 has joined #ag 16:06:09 jtoles has joined #ag 16:06:27 Mj: For buddy system. Could we announce it to the list? 16:06:30 present+ 16:06:32 q+ 16:06:39 ack kevin 16:06:45 present+ 16:06:56 Keven: minutes go our to the full group. 16:06:57 q+ 16:07:03 ack julierawe 16:07:05 s/Keven/Kevin/ 16:07:32 Julie: dedicated email may be helpful. 16:07:51 ac: Any new members? 16:07:57 scott has joined #ag 16:08:05 Wecome Roldon Brown! 16:08:06 present+ 16:08:15 s/Wecome/Welcome/ 16:08:34 Welcome Roldon ! 16:08:35 RB: I'm Rouldon Brown, joined 2 weeks ago. Happy to join you. 16:08:40 Welcome Roldon! 16:08:52 q+ LauraBMiller 16:09:05 ack LauraBMiller 16:09:27 re-welcome Laura! 16:09:28 We are so happy to have Laura as a Fed! 16:09:33 q+ resources for new members: https://github.com/w3c/wcag3/wiki 16:09:52 LM: I'm Laura Miller. I'm with GSA. Have worked in other capacities too. 16:09:59 Old member, change of affiliation. On the WCAG2ICT working group. 16:10:08 gpellegrino has joined #ag 16:10:10 re-welcome Tiffany! 16:10:23 present+ 16:10:25 q? 16:10:35 ack res 16:10:35 resources, you wanted to discuss new members: https://github.com/w3c/wcag3/wiki 16:10:43 TB: Tiffany Burton I'm now an invited expert. Previous work in other capacities. 16:11:04 RM: we do have intro info in our wiki. 16:11:06 zakim, take up next item 16:11:06 agendum 2 -- Subgroup wrap up briefings -- taken up [from alastairc] 16:11:12 Welcome back Tiffany! 16:12:15 DJ: Haptic Stimulation now calling ourselves Haptic input. 16:12:41 Outcome: 16:12:41 Haptic feedback can be adjusted and/or turned off. 16:13:05 ... goal: Users have the ability to adjust or turn off haptic input and output 16:13:15 q? 16:13:57 ... (reviews Method decision tree) 16:14:43 kirkwood has joined #ag 16:16:18 ... Haptic is not a true alternative 16:16:43 present+ 16:16:49 ... We are focusing on haptic feedback. Haptic input should be a different subgroup 16:17:16 q+ 16:17:31 ack Jennie_Delisi 16:18:16 Jennie: congrats on the sensations of Haptic feedback. 16:18:27 LauraBMiller has joined #ag 16:18:39 q+ to say - great work on this. Love the decision tree. 16:19:20 ... need to differentiate between sales of haptic feedback and for a specific app? 16:19:33 DJ: we did discuss that. 16:19:52 ack LauraBMiller 16:19:52 LauraBMiller, you wanted to say - great work on this. Love the decision tree. 16:19:56 Ac: worth looking into. 16:20:17 GN015 has joined #ag 16:20:19 LM: great work on this. 16:20:46 AC: next week other subgroups will do exist briefings. 16:20:47 zakim, take up next item 16:20:47 agendum 3 -- Discuss Explainer https://github.com/w3c/wcag3/pull/116#issuecomment-2444491152 -- taken up [from alastairc] 16:21:42 Ac: not too many comments. 16:22:40 ... goes over them: https://github.com/w3c/wcag3/pull/116 16:23:15 q+ 16:23:36 ack ra 16:23:36 q- 16:23:42 q+ 16:23:56 RM: quantitative/quantifiable is an editorial change. 16:24:28 +1 to removing somewhat 16:25:06 Kevin: I think quantitative/quantifiable are different. 16:25:42 ...don't think they are interchangeable. 16:25:56 q+ 16:26:04 ack kevin 16:26:06 ack Rachael 16:26:35 RM: Those are the terms we previously agreed on. 16:26:54 ... It is not a small change at this point. 16:26:54 q+ 16:26:59 ack bruce_bailey 16:27:13 seems wishy washy. agree with Bruce 16:27:28 Bruce: I'm okay with it. But it is different 40 lines down. 16:27:52 Ac: could say comparable. 16:28:27 q+ 16:28:42 ack kirkwood 16:28:49 ... but there are a lot of dimensions to it. 16:28:56 q+ 16:28:59 ack Rachael 16:29:14 JK: I'd get rid of "somewhat" 16:29:18 i am all for additional wiggle room 16:29:32 RM: I would like to keep the wiggle room. 16:29:47 q+ 16:29:50 ack Rachael 16:30:23 RM: Want to avoid coming back to this in 6 months 16:30:24 q+ 16:30:39 ack bruce_bailey 16:31:03 Bruce: "somewhat comparable" is fine. 16:31:15 basing on comparable concept ? 16:31:51 julierawe has joined #ag 16:31:58 present+ 16:32:21 r_brown has joined #ag 16:32:30 Suggesting: "An Assertion is another approach to meeting a Guideline. They do not replace Requirements, and not all Guidelines include Assertions." 16:32:38 AC: Detlev thought "Assertions may supplement Requirement to meet a Guideline. Not all Guidelines include Assertions." Was not clear. 16:33:07 Detlev: The sentence feels wobbly. What does "accessibility under guidelines" mean? It's always about accessibility of content? 16:33:20 q+ to say Organizations can make an assertion that they followed a procedure as part of a conformance claim . 16:34:19 ... May open up claim for things that no one can check. 16:34:40 ack Rachael 16:34:40 Rachael, you wanted to say Organizations can make an assertion that they followed a procedure as part of a conformance claim . 16:34:48 ... I don't know what the place of assertions are. 16:35:17 RM: would it help to say: Organizations can make an assertion that they followed a procedure as part of a conformance claim ? 16:35:24 q+ 16:35:53 ack ra 16:35:59 Detlev: is an assertion enough? It seems a wooly way. Not verifiable. Not happy with this. 16:36:57 RM: ambiguity is internal as the group hasn't decided on assertions. 16:37:36 ... need to add an editors note. 16:37:39 +1 to Detlev 16:38:08 also +1 to Detlev's concerns. great points 16:38:19 I had to step away for a doctor call, I agree with what Detlev was raising but missed some of what he stated on call. 16:38:31 s/internal/intentional/ 16:38:32 +1 Detlev 16:38:42 Detlev has joined #ag 16:38:49 LC: +1 to Detlev 16:38:53 present+ 16:39:23 q+ 16:39:41 Ac: An assertion doesn't replace the requirement. Need to explain it better. 16:40:05 ack Detlev 16:40:27 Detlev: we should make it clear from the explainer. 16:41:23 Ac: assertions can' replace the requirements 16:41:43 s/can' replace /can't replace / 16:42:38 Ac: need to flesh out level of maturity. 16:42:58 alastairc the last point (add or refine) was minor, maybe a bit too terse 16:43:24 q+ 16:43:29 Ac: last call for comments on the explainer. 16:43:29 ack sarahhorton 16:43:49 Sarah: I had a comment in the google doc. 16:44:06 ... can we be more explicit? 16:46:21 q+ 16:46:46 ... maybe make it more explicit about ATAG or UAAG and WCAG 3 . 16:46:47 ack ra 16:47:29 RM: Can't commit to writing ATAG or UAAG 16:48:39 q+ 16:48:46 RM: That is fine. But we need to make it clear what we are and aren't doing. How far are we going into that space? 16:48:49 ack Rachael 16:48:59 q+ 16:49:07 RM: We are walking a fine line. 16:49:29 ack kevin 16:50:46 Kevin: How far we can influence. There is information guidance. But not normative standard on UAs. 16:51:00 +1 to alastair's comment 16:52:12 zakim, take up next item 16:52:12 agendum 4 -- Discussion of WCAG 3 Guidelines and Requirements https://docs.google.com/document/d/1Hc5fwRKZVdWPoEp-HzrCu4TTsXF36sozE45OfcYUnKU/edit?tab=t.0 -- taken up [from 16:52:15 ... alastairc] 16:52:15 Ac: Will send out an email with updates and after that do a CFC. 16:52:22 comprable denotes equivalency. comparable is the ability to be compared. that was my earlier point. (sorry for slow comment) 16:54:15 Ac: (Reads comments) 16:54:59 LenB has joined #ag 16:55:32 q+ 16:55:41 ack sarahhorton 16:55:46 Ac: Suggestions to alternative for "Users have" 16:55:50 q+ 16:56:14 Sarah: not a problem across the board. 16:56:46 ... maybe "users can" 16:57:09 scott has joined #ag 16:58:19 q+ to check on the need for a scribe change 16:58:32 ack dan_bjorge 16:58:53 Dan: general complaint about "users have" 16:59:15 +1 to Dan 16:59:30 q+ 16:59:31 ... it is unclear. All users? 2 users? What is the scope? 16:59:42 ack Ch 16:59:42 Chuck, you wanted to check on the need for a scribe change 16:59:49 q- 16:59:52 scribe+ 17:00:30 Dan asks about "user have" versus technical statements 17:00:44 nina has joined #ag 17:01:13 alastairc: Outcomes are at technical level, next level up is about users 17:02:02 q+ 17:02:06 ack sarahhorton 17:02:20 alastairc: statement is to not do the thing or avoid. Why that is a problem? 17:02:57 sarahhorton: seems like two different approaches 17:03:21 rrsagent, make minutes 17:03:22 I have made the request to generate https://www.w3.org/2024/11/05-ag-minutes.html Laura_Carlson 17:03:39 sarahhorton from google doc: These seem like very different things, one is prohibiting content so that users don't experience physical harm and one is allowing users to control content that causes them physical harm. Same comment for each use of this construct. 17:04:06 Letting user control is different than avoiding. 17:04:48 ... harm is okay so long as user has control? 17:05:09 q+ 17:05:09 [alastair word smithing] 17:05:20 ack Rachael 17:05:33 sarahhorton: by combining, takes away option to not include them 17:05:57 q+ on leaving it to the sub-group, as they will be creating trees 17:06:07 s/go our to /go to / 17:06:17 ack me 17:06:17 alastairc, you wanted to comment on leaving it to the sub-group, as they will be creating trees 17:06:19 +1 to Rachael; I think the original already made "don't include it" the first and most obvious option. 17:06:24 Rachael: Chair hat off, if foundational is control versus avoidance at enhanced seems bad 17:07:35 scribe+ 17:07:45 s/comprable/comparable / 17:07:58 bruce_bailey has joined #ag 17:08:04 alastair: As long as these statements include the options, they are going to be broken apart when the subgroups work on them. the question is... 17:08:07 scribe+ 17:08:11 Detlev has joined #ag 17:08:14 alastair: Does this include the direction we are including.... 17:08:20 q+ 17:08:22 present+ 17:08:26 alastair does it include what we are looking for? 17:08:28 q+ 17:08:30 ack sarahhorton 17:08:31 rrsagent, make minutes 17:08:32 I have made the request to generate https://www.w3.org/2024/11/05-ag-minutes.html Laura_Carlson 17:08:38 LenB has joined #ag 17:09:16 sarahhorton: From process perspective, requirements have one expectation, not an "or". 17:09:39 .... will be easier to combine later rather splitting up now. 17:10:15 q+ 17:10:21 bruce_bailey: An editorial comment, there should be more consistent phrasing between them. 17:10:26 Kimberly has joined #ag 17:10:26 alastair: In what way? 17:10:35 ack bruce_bailey 17:10:38 ack dan_bjorge 17:11:12 Bruce: My comment in doc was just editorial -- I feel like they could phrased all the same 17:11:19 tiffanyburtin has joined #ag 17:11:37 these together look good to me, agree with Dan 17:11:44 Dan: Prefers them combined, and see consistent. 17:11:47 They are consistent within the animation/motion category 17:12:26 alastairc: We will keep where we are for now, and pass work along to sub group 17:12:56 “the system” 17:13:08 [alastair continues going through comments] 17:13:15 I queston “the system” wording 17:13:33 alastairc: not sure about better formulation 17:14:33 s/ ourselves Haptic input./ ourselves Haptic Feedback./ 17:14:47 sarahhorton comment in doc of squishy example. 17:14:55 recommend “users are provided” 17:15:10 rrsagent, make minutes 17:15:12 I have made the request to generate https://www.w3.org/2024/11/05-ag-minutes.html Laura_Carlson 17:15:28 alastairc: This gets at why we have settled on Users Have for guidelines. 17:16:48 kirkwood: Users would have the labels. Users would have access to the labels. Features of content are not features of the users. 17:16:52 +1 to Chuck 17:17:14 q+ 17:17:17 ack Ch 17:17:20 Rachael: This the approach which has been the most productive so far. 17:17:21 ack Chuck 17:17:35 sarahhorton has joined #ag 17:18:04 Chuck has joined #ag 17:18:11 present+ 17:18:29 alastairc thanks Sarah for all the feedback on the doc, so that is why attention is on this call 17:18:45 q+ 17:18:53 ack Chuck 17:18:54 ack Ch 17:19:00 alastairc: Chair hat off, we are open to different formulations. 17:19:12 kirkwood: Mechanism? 17:19:34 disagree 17:20:01 Chuck: One goal is for plain language. Mechanism available is not as understandable as Users have.... 17:20:34 +1 to Kirkwood's disagreement, I should have added that my chair hat was off. 17:20:41 Agree that "Users are provided" is system/author focused and we are aiming for user focused statements 17:20:59 i'd want to avoid the use of "focus" in that figure/figcaption guideline 17:21:07 alastairc: Please don't get too stuck on wording, as we have a refreshed version publishing soon, and these pages are in the developmental stage. 17:21:55 [at Interactive Component in doc] 17:22:38 "users can see " is a particularly good example of why I dislike the "users have" sort of language - it makes it clear that we don't always mean "all users", but if we don't mean "all users" consistently, how is someone supposed to interpret where we mean "all" vs "some"? 17:22:43 alastairc: Making more generic, so focus available rather than keyboard focus available. 17:22:51 q+ 17:23:06 ack bruce_bailey 17:23:17 bruce_bailey: This is one of the things that the subgroup is not getting traction on, what is comparable. 17:23:24 bruce_bailey: We have 2 different user needs. 17:24:14 bruce_bailey: Subgroup has worked on number of keystrokes versus time needed via keyboard versus mouse 17:25:19 alastairc: could add note about under discussion, but that is true with all of them 17:27:01 ChrisLoiselle: APG has done work on custom / not custom / standard / non standard. We should take advantage of that work. 17:27:28 s/sales of /styles of / 17:27:34 .... still working through phrasing in subgroup. 17:27:55 rrsagent, make minutes 17:27:57 I have made the request to generate https://www.w3.org/2024/11/05-ag-minutes.html Laura_Carlson 17:28:03 [edit made, subgroup might comeback] 17:28:19 q+ 17:28:35 ack kevin 17:29:03 Rachael: We need to settle on quantifiable versu qualifiable 17:29:15 .... I think it will settle out 17:29:33 s/exist briefings./exit briefings./ 17:29:37 agenda? 17:29:39 kevin: Suggest chairs have off-line conversation 17:29:53 q+ 17:29:56 https://docs.google.com/document/d/1_vWUteDqNAXDYrcwylOoPt0U2hOrbjo1DzsTEs-ScFs/edit?tab=t.0#heading=h.e17kdnrg60xc 17:29:59 ack ChrisLoiselle 17:30:08 [explainer google doc] 17:30:28 q+ to answer Chris 17:31:02 ack Rachael 17:31:02 Rachael, you wanted to answer Chris 17:31:18 ChrisLoiselle: Please see comments via a Word doc, levels is not at all intuitive 17:31:32 zakim, take up next item 17:31:32 agendum 5 -- Existing subgroup Work -- taken up [from alastairc] 17:32:03 Rachael: We got the comment, and will do some wordsmithing, but more in next versions. 17:33:15 julierawe has joined #ag 17:33:18 present+ 17:33:25 q+ 17:33:36 ack julierawe 17:33:51 alastairc: We will not be reconvening. 17:34:47 rrsagent, make minutes 17:34:48 I have made the request to generate https://www.w3.org/2024/11/05-ag-minutes.html Chuck 17:35:05 rrsagent, make minutes 17:35:06 I have made the request to generate https://www.w3.org/2024/11/05-ag-minutes.html Laura_Carlson 17:43:33 Kimberly has joined #ag 17:43:38 present+ 18:13:23 ShawnT has joined #ag 19:04:11 Jem has joined #ag