14:30:02 RRSAgent has joined #ag 14:30:07 logging to https://www.w3.org/2024/10/01-ag-irc 14:30:07 RRSAgent, make logs Public 14:30:08 Meeting: AGWG Teleconference 14:30:10 chair: Chuck 14:30:16 meeting: AGWG-2024-09-30 14:30:23 rrsagent, generate minutes 14:30:25 I have made the request to generate https://www.w3.org/2024/10/01-ag-minutes.html Chuck 14:31:31 agenda+ TPAC Review 14:31:39 agenda+ Review Conformance Model Options 14:31:47 agenda+ Deciding on outcome formatting 14:31:53 agenda+ Outcome Breakouts 14:32:01 regrets: Bruce Bailey. Mary Jo Mueller, Makoto Ueki 14:54:06 Glenda has joined #ag 14:58:02 present+ Laura_Carlson 14:58:14 Scribe: Laura_Carlson 14:58:31 Francis_Storr has joined #ag 14:58:35 GreggVan has joined #ag 14:58:36 kirkwood has joined #ag 14:58:38 rscano has joined #ag 15:00:19 present+ 15:00:24 present+ 15:00:48 present+ 15:01:15 MJ has joined #ag 15:01:18 filippo-zorzi has joined #ag 15:01:26 present+ 15:01:29 present+ 15:01:36 present+ 15:01:57 giacomo-petri has joined #ag 15:01:59 present+ 15:02:25 Azlan has joined #ag 15:02:34 present+ 15:02:36 Jennie_Delisi has joined #ag 15:02:39 present+ 15:02:40 present+ 15:02:48 mbgower has joined #ag 15:02:49 jtoles has joined #ag 15:02:51 present+ 15:02:52 present+ 15:03:00 present+ 15:03:12 Chuck: Welcome. 15:03:49 Chuck: Any new members? None. 15:03:56 dan_bjorge has joined #ag 15:04:01 present+ 15:04:01 julierawe has joined #ag 15:04:05 present+ 15:04:08 Chuck: Announcements? None 15:04:13 Chuck: Any new topics? 15:04:20 zakim, take up item 1 15:04:20 agendum 1 -- TPAC Review -- taken up [from Chuck] 15:04:20 ... None. 15:04:41 ... will share screen. 15:04:52 https://docs.google.com/presentation/d/17VJvnm5UQW4WUzIoo9QNPVGfePgaZa8ifZWs-wtmv7E/edit#slide=id.g306477bedd2_0_0 15:05:04 nina has joined #ag 15:05:06 ShawnT has joined #ag 15:05:12 present+ 15:05:20 ... Slide Deck from TPAC and Minutes. 15:05:43 ... next steps. Individual Activity: Participants try out testing WCAG 3 15:06:03 ... Chairs: Try flipping % passes and fails 15:06:30 Group activity explained on slide. 15:06:39 zakim, take up next item 15:06:39 agendum 2 -- Review Conformance Model Options -- taken up [from Chuck] 15:06:43 ... questions? 15:06:53 sarahhorton has joined #ag 15:07:00 present+ 15:07:03 ... Conformance models to explore 15:07:23 ... first one is Required plus %: 15:07:33 present+ 15:07:37 ... Level 1: Required outcomes; 15:07:40 Detlev has joined #ag 15:07:42 Graham has joined #AG 15:07:47 ...All levels above level 1 are based on % 15:07:50 present+ 15:07:51 present+ 15:08:25 ... Second model is Levels: Each of 4-5 level is clearly defined; Each level has a required set of outcomes (preselected to balance functional needs) 15:08:30 Jen_G has joined #ag 15:08:50 ... third model is Hybrid: Level 1: Required outcomes; All levels above level 1 include % AND a subset of required outcomes for that level 15:08:54 Present+ 15:09:03 Kimberly has joined #ag 15:09:15 present+ 15:09:26 ... fourth model is Required plus functional need %: Level 1: Required outcomes; All levels above level 1 include % AND a minimum % requirement for each functional need 15:09:55 q+ 15:10:00 Rain has joined #ag 15:10:02 present+ 15:10:10 ... AC put together doc with pros & cons. 15:10:22 AC: work in progress. 15:10:56 ... https://docs.google.com/document/d/17J4lkSBGBlDDLTtqJ2YcI687uNuDn_-4aeDNdnOloP4/edit#heading=h.pzyudbi3bzk1 15:10:57 ack Gregg 15:11:11 q+ on NAs 15:11:24 ack ala 15:11:24 alastairc, you wanted to comment on NAs 15:11:26 Gregg: id something is N/A does it pass 15:11:57 q+ 15:12:07 AC: N/A count as pass is 15:12:08 Kimberly has joined #ag 15:12:17 ack Kevin 15:12:58 Kevin: with counting failures N/A don't count as much. 15:12:59 q+ 15:13:12 ack Gregg 15:13:24 counting fails turns the numbers around, but it doesn't affect NAs as such. You either have to count them as part of the whole, or not. 15:13:24 Is that occurrences of a fail, or number of requirements not met? 15:13:29 Gregg: are failures non-passing of an outcome? 15:13:29 q+ 15:13:32 present+ 15:13:34 Not instances, outcomes 15:13:34 Chuck: yes. 15:13:41 ack Grah 15:14:02 q+ on option 2 15:14:09 ack ala 15:14:09 alastairc, you wanted to comment on option 2 15:14:11 Graham: How would counting failures work with number 2? 15:14:54 q+ 15:14:55 Ac: this isn't instances. It is whether an outcome is met or not. 15:14:59 ack Grah 15:15:01 q+ 15:15:37 question on this slide vs. https://github.com/w3c/wcag3/pull/112#issuecomment-2377452956 and my comment there. 15:15:38 Kimberly has joined #ag 15:15:40 ack Chris 15:16:54 q+ on how it relates to A/AA etc and pre-req / baseline 15:16:56 Chris: Slide 49. How does it relate to AA, AAA and A? 15:17:36 ... terminology mapping question. 15:17:39 ack ala 15:17:39 alastairc, you wanted to comment on how it relates to A/AA etc and pre-req / baseline 15:18:04 AC: we are trying to settle terminology. 15:18:14 Kimberly has joined #ag 15:18:57 ... Required is what we had like combo of pre requests and baseline. 15:19:14 ... Somewhat different than A. AA, AAA. 15:19:22 q+ 15:19:26 ack Graham 15:19:38 has bronze / silver / gold been dumped for good? 15:19:58 Detlev - no, we're just not naming that yet. 15:20:10 Graham: #2 puts us back into the situation that we are in now. 15:20:20 q+ on option 2 15:20:28 ... where people get discouraged. 15:20:33 ack ala 15:20:33 alastairc, you wanted to comment on option 2 15:20:47 scott has joined #ag 15:20:48 present+ 15:20:53 present+ 15:20:57 q+ 15:20:59 AC: it is an obvious con on option 2. 15:21:02 ack Grah 15:21:26 Kimberly has joined #ag 15:21:43 Graham: could have a subset of things. 15:21:58 q? 15:22:08 ... hybrid of 3&4. 15:22:11 zakim, take up next item 15:22:11 agendum 3 -- Deciding on outcome formatting -- taken up [from Chuck] 15:22:11 scott0 has joined #ag 15:22:45 Chuck: GitHub Discussion 15:23:45 AC: we went thru various options. 15:23:52 ... Revising existing structure 15:24:07 ...Finding a need to organize content by a higher grouping 15:24:20 ... We have been referring to those as outcomes but we suggest better aligning the language since the technical format we decided on isn’t an “outcome” 15:24:33 ... Suggested way forward: 15:24:43 ...Outcomes: Plain language, user-oriented statements of the desired outcome; grouping the guidelines 15:24:49 ...Guidelines: Technical statements to meet each outcome 15:25:11 ... example: Outcome: Users can see which element has keyboard focus. 15:25:11 Guidelines: 15:25:26 ... Present 15:25:32 q+ 15:25:38 ...Not obscured: The focus indicator is not obscured or partially obscured (more than 50%, TBC) 15:25:45 ...Persistent: The focus indicator persists while the element has focus, but does not persist after the element loses focus. 15:25:47 q+ 15:25:52 ... Distinctive: The keyboard focus indicator uses a style that is distinct from the style of other controls, so that the item in focus can be distinguished without reference to the non-focused state. 15:25:53 q+ 15:25:54 ack Detlev 15:25:59 ... Sufficiently visible: According to the specific method (below), the indicator must be visually discernible whilst navigating. 15:26:12 q- 15:26:20 +1 to detlev 15:26:25 100% - that was my recommendatiuon - requirement! 15:26:38 Detlev: don't understand why guideline is better that requirements. 15:26:48 Frankie has joined #ag 15:26:50 ack julie 15:26:51 Q+ 15:26:54 q+ 15:26:57 AC: they are not phrased as outcomes. 15:27:02 Present+ 15:27:04 Requirements that produce the outcome 15:27:11 +1 they are written as requirements, and requirements is nice and clear 15:27:17 Julie: outcome is a little confusing. 15:27:22 ack Rach 15:27:42 "Guidelines" is confusing 15:27:46 q? 15:27:48 ack Gregg 15:27:53 AC one concern with it, 15:28:25 GreggVan: I'd like to speak for using guidelines. 15:29:22 Silver had guidelines > outcomes > methods/requirements 15:29:27 did we lose me? 15:29:30 ... guidelines allows some things to be required or and somethings that are not testable. 15:30:04 q+ 15:30:16 q+ on examples not include assertions - so it's a good piont 15:30:32 present+ 15:30:51 ... could have minimums are required and other are things that you can do. 15:30:59 +1 to minimum - I like this slightly better than "prerequisite" although I do get that "prerequisite" is trying to say something slightly different 15:31:01 q+ to ask if we must stick with one "word" as a description? 15:31:06 Required, recommended - simple and straight forward language. Required are for a pass, recommended could (not necessarily) then be used for further scoring if we use one of those models. 15:31:12 present+ 15:31:13 ack Detlev 15:31:32 q+ 15:32:02 Detlev is bang on with terms that work in my mind, literally just said the same! 15:32:06 Poornima has joined #ag 15:32:08 q+ 15:32:10 q+ 15:32:11 ack ala 15:32:13 alastairc, you wanted to comment on examples not include assertions - so it's a good piont 15:32:16 Detlev: seems counter intuitive. Could use requirements, recommendations, and assertions. 15:32:20 q- later 15:32:50 q+ 15:33:17 ack Ch 15:33:17 Chuck, you wanted to ask if we must stick with one "word" as a description? 15:33:21 Ac: Somewhat baffled . guidelines has been used for many, many, years. 15:33:43 Chuck: does it have to be a one word? 15:33:49 ack dan 15:33:51 Q+ 15:33:54 -1 to multiple words 15:34:01 @AC yes sure but for a higher level 15:34:20 ack Gregg 15:34:24 Dan :has different meaning in WCAG 2 15:35:10 +1 to GreggVan 15:35:11 Gregg: like outcomes, guidelines , requirements, recommendations, and assertions. 15:35:13 In WCAG 2 the "guidelines" are the groupings for sets of SC. 15:35:45 ack kevin 15:35:57 ... 3 kinds of guidelines: requirements, recommendations, and assertions. 15:35:57 ack ljo 15:35:58 q+ to suggest we don't title the list of things on the face of the spec. 15:36:40 qq+ 15:37:00 q+ to say if we name it for ourselves and just ourselves, I'm ok with any options mentioned, favorable to requirements 15:37:40 LO: Guidelines may not be the best term. Some people don't think that they are definitive. 15:37:42 ack Rach 15:37:50 I think this points to putting more than word, per Chuck's option, if possible. 15:38:11 ack ala 15:38:11 alastairc, you wanted to suggest we don't title the list of things on the face of the spec. 15:38:12 RM: ice if we had a term for the differences. Liked Gregg's comment. 15:38:15 +1 to ljoakley 15:38:38 q+ 15:38:55 ack kevin 15:38:55 kevin, you wanted to react to ljoakley 15:38:55 Ac: suggest not putting a name on the face of the spec for this. 15:39:36 q+ 15:39:44 ack Ch 15:39:44 Chuck, you wanted to say if we name it for ourselves and just ourselves, I'm ok with any options mentioned, favorable to requirements 15:39:56 q- 15:40:18 Kevin: we are aware that legislators will sue. Challenge against w3c rec. but recognition that they are standards. 15:40:44 AC: maybe we can work on this without giving this a name. 15:40:52 ack Rain 15:41:10 another word to consider “Standard” 15:41:26 Rain: Maybe use use a simple header. 15:42:39 q+ 15:43:26 +1 to Rain 15:43:35 ... experiences with people in the wild are direct experiences. Need to explain things on a basic level. General population perspective is valuable. 15:43:36 +1 to proposed resolution, which I will test after queue 15:44:02 ack Grah 15:44:03 ... put this on our list of topics. 15:44:35 We do have a glossary in development. 15:44:38 Graham: let's create a glossary for the time being. 15:45:12 Chuck: need to have some level of consensus. 15:45:13 q? 15:45:15 q+ 15:45:17 Q+ 15:45:19 ack Julie 15:45:34 ack Rach 15:46:04 +1 to structure of sentence and technical statement below it 15:46:09 +1 15:46:09 Rachael 1+ 15:46:10 +1 15:46:14 =1 15:46:14 RM: what of you think of the structure of the sentence. 15:46:16 +1 15:46:17 q+ 15:46:21 ack Gregg 15:46:55 the hundred plus outcomes so far collected are fairly fine-grained - so will they move up in granularity? 15:47:09 draft RESOLUTION: For the next publication, we will use "Outcome" (user-focused outcomes) to group the requirements and assertions. We will explore terminology for the requirement/assertion level in future. 15:47:10 Gregg: Guidelines is in the name of our document 15:47:41 +1 15:47:43 +1 (but we must link to a glossary of terms) 15:47:44 +1 15:47:44 +1 15:47:45 +1 15:47:45 +1 15:47:48 +1 15:47:48 +1 15:47:49 +1 15:47:50 +1! 15:47:51 0 only because outcome often equals results 15:47:52 +1 15:47:52 +1 (and agree with Graham) 15:47:53 +1 15:47:57 MJ has joined #ag 15:47:59 +1 15:48:00 Laura: +1 15:48:01 +1 15:48:01 Frankie has joined #ag 15:48:03 +1 15:48:08 0 15:48:09 0 15:48:15 +1 15:48:31 RESOLUTION: For the next publication, we will use "Outcome" (user-focused outcomes) to group the requirements and assertions. We will explore terminology for the requirement/assertion level in future. 15:48:33 =1 15:48:48 +1 15:49:04 s/=1// 15:49:10 q+ 15:49:11 q+ on PR, we'll need to overhaul that 15:49:21 q- later 15:49:22 ack Kevin 15:49:30 Julie: pull request for outcomes. 15:49:39 +1 to that statement Julie made. 15:49:55 ack ala 15:49:56 alastairc, you wanted to comment on PR, we'll need to overhaul that 15:50:10 Kevin: I'm looking at it now. We can make changes going forward. 15:50:23 zakim, take up next item 15:50:23 agendum 4 -- Outcome Breakouts -- taken up [from Chuck] 15:51:24 Chuck: 3 separate groups. 15:51:34 MelanieP has joined #ag 15:51:34 q+ 15:51:47 .... Group 1: Refine outcome and guideline organization 15:51:59 ... Group 2: Refine outcomes statements to match agreed upon format 15:52:08 ... Group 3: Categorize as Required and Enhanced to help with testing conformance and forming subgroups 15:52:10 q+ 15:52:19 ... We are still at exploratory for this exercise 15:52:27 ... We need clarity and consistency but not perfection 15:52:30 ack Gregg 15:52:33 ... Editors will combine the results 15:52:53 Gregg: Group 3 doesn't make any sense. 15:53:35 ack Melanie 15:53:54 Chuck: we are deciding at the if the "thingy" is required or not. 15:54:02 q+ on bronze / pre-req / required 15:54:13 ack ala 15:54:13 alastairc, you wanted to comment on bronze / pre-req / required 15:54:40 Melanie: How does this relate to bronze, silver, gold? 15:55:08 ... (explains history) 15:56:58 ... Kind of dropped them.. Not trying to recreate a, aa aaa. 15:56:59 bronze, silver, gold, a, aa, aaa , pre req, baseline, enhanced - is there a mapping reference that compare of all these? I know this is iterative. 15:57:40 ... we are so far away from WCAG 2. 15:57:51 Q+ 15:58:01 https://github.com/w3c/wcag3/pull/112#issuecomment-2377452956 has a list of questions that relate to Melanie's questions , I look forward to those answers to understand this more fully. 15:58:06 ... way more in baseline for WCAG 3 15:58:08 ack Rach 15:58:42 I have to drop for a work meeting. Have a good week, everybody! 15:58:45 RM: A future activity would be a mapping. 15:59:42 scribe+ 15:59:50 scribe- 16:00:14 I have to drop off for a meeting but will rejoin in 30 minutes. 16:00:23 MJ has left #ag 16:00:33 q+ to answer Chris's questions, briefly. 16:00:40 Chuck: 1 & 3 are self explanatory. 16:00:44 q? 16:00:48 ack ala 16:00:48 alastairc, you wanted to answer Chris's questions, briefly. 16:01:03 https://github.com/w3c/wcag3/pull/112 16:01:08 ... correction: 2 & 3 are self explanatory 16:01:55 AC: we have grouped prerequisite an baseline together. 16:02:10 ... they are in required/ 16:02:19 thanks. 16:03:04 ... any questions? 16:03:23 https://docs.google.com/presentation/d/17VJvnm5UQW4WUzIoo9QNPVGfePgaZa8ifZWs-wtmv7E/edit#slide=id.g306477bedd2_0_10 16:03:24 Group 1: https://docs.google.com/document/d/1ZAC75CJPRXaplQh3ekxIYrfaZ2jkyTsDSJroxR5F5xM/edit 16:03:33 Group 2: https://docs.google.com/spreadsheets/d/1JgjDonZEvJMc3_k_R6r3siNexeBjigQsqVxvQRhLEN8/edit?gid=0#gid=0 16:03:44 Group 3: https://docs.google.com/spreadsheets/d/1QwSUxRm96Ez7RWbyqJEtiUa0j0ZbkfvvTpdK8x9Ww1c/edit?gid=0#gid=0 16:04:25 JenStrickland has joined #ag 16:04:28 present+ 16:04:48 rrsagent, make minutes 16:04:49 I have made the request to generate https://www.w3.org/2024/10/01-ag-minutes.html Laura_Carlson 16:05:23 I need to leave, now. Bye all. Thanks. 16:17:53 Kimberly has joined #ag 16:18:08 Azlan has joined #ag 16:21:05 Kimberly has joined #ag 16:27:59 Kimberly has joined #ag 16:28:07 present+ 16:40:54 MJ has joined #ag 16:48:06 Kimberly has joined #ag 18:19:43 Azlan has joined #ag 18:50:53 Azlan has joined #ag 19:15:22 Azlan has joined #ag 19:43:29 Azlan has joined #ag 19:48:38 ShawnT has joined #ag 19:58:05 kirkwood has joined #ag 19:59:45 Azlan has joined #ag 20:13:56 kirkwood has joined #ag 20:19:13 Azlan has joined #ag 20:42:58 Azlan has joined #ag 21:00:31 Azlan has joined #ag 21:13:52 ShawnT has joined #ag 21:21:15 Azlan has joined #ag 21:43:01 Azlan has joined #ag 22:06:50 Azlan has joined #ag 22:26:06 Azlan has joined #ag 22:49:28 Azlan has joined #ag 23:07:14 Azlan has joined #ag 23:24:38 Azlan has joined #ag 23:44:08 Azlan has joined #ag 23:45:38 ShawnT has joined #ag