14:29:39 RRSAgent has joined #ag 14:29:43 logging to https://www.w3.org/2025/04/15-ag-irc 14:29:43 RRSAgent, make logs Public 14:29:44 Meeting: AGWG Teleconference 14:29:48 chair: Chuck 14:29:56 meeting: AGWG-2025-04-15 14:30:06 rrsagent, generate minutes 14:30:07 I have made the request to generate https://www.w3.org/2025/04/15-ag-minutes.html Chuck 14:30:17 regrets: Poornima Subramanian, Rachael Montgomery, Christopher Loiselle, Frankie Wolf 14:30:46 agenda+ UI-context (ex-views) definition https://github.com/w3c/wcag3/discussions/286#discussioncomment-12480952 14:30:51 agenda+ WCAG 2.2 issues https://lists.w3.org/Archives/Public/w3c-wai-gl/2025AprJun/0000.html 14:31:05 agenda+ Review template https://docs.google.com/document/d/1MHJwOWJhGZS4zZYiF9ufNfxTmqFf6bf07vNHAAgfylE/edit?tab=t.0#heading=h.jwan2ys80z90 14:31:15 agenda+ Subgroup work 14:47:51 present+ 14:52:36 ljoakley has joined #ag 14:59:18 todd has joined #ag 14:59:21 GreggVan has joined #ag 15:00:12 bruce_bailey has joined #ag 15:00:39 filippo-zorzi has joined #ag 15:01:05 present+ 15:01:15 present+ 15:01:16 Jennie_Delisi has joined #ag 15:01:21 present+ 15:01:35 present+ 15:01:49 present+ 15:01:52 present+ 15:01:57 present+ 15:01:59 Deltev has joined #ag 15:02:08 mbgower has joined #ag 15:02:11 BrianE has joined #ag 15:02:18 present+ 15:02:27 present+ 15:02:27 scribe: Detlev 15:02:32 Laura_Carlson has joined #ag 15:02:37 kenneth has joined #ag 15:02:54 GN015 has joined #ag 15:02:54 present+ Laura_Carlson 15:03:19 tiffanyburtin has joined #ag 15:03:22 Any introductions? 15:03:23 julierawe has joined #ag 15:03:27 present+ 15:03:53 No announcements.... 15:03:55 jtoles has joined #ag 15:04:01 present+ 15:04:04 present+ 15:04:06 Makoto has joined #ag 15:04:13 present+ 15:04:13 present+ 15:04:13 Chuck: Any items from group? 15:04:18 Azlan has joined #ag 15:04:19 ...nnone... 15:04:20 zakim, take up item 2 15:04:20 agendum 2 -- WCAG 2.2 issues https://lists.w3.org/Archives/Public/w3c-wai-gl/2025AprJun/0000.html -- taken up [from Chuck] 15:04:25 maryjom has joined #ag 15:04:35 present+ 15:04:40 q+ 15:04:42 present+ 15:04:52 ack bru 15:04:58 present+ 15:05:19 mbgower: (walking though the email with WCAG 2.X reviews 15:05:29 sarahhorton has joined #ag 15:05:35 present+ 15:05:38 Kimberly has joined #ag 15:05:46 present+ 15:05:51 mbgower: Due date extended to 22 April 15:05:52 present+ 15:06:11 ...first section on proposed changes 15:07:01 mbgower (runs through content structure of regular email proposing changes and bug fixes and ways to contribute) 15:07:53 https://github.com/orgs/w3c/projects/56 15:07:54 http://github.com/orgs/w3c/projects/56/views/1 15:08:12 board requires log in 15:08:14 mbgower: four discussion areas in the Default board (a kanban board of issues) 15:08:21 AlinaV has joined #ag 15:08:33 present+ 15:09:03 https://github.com/w3c/wcag/pull/4256 15:09:03 mbgower : explains changes in #4256 (alphabetical listing) 15:10:20 giacomo-petri has joined #ag 15:10:20 mbgower: as a normative change this has to gone through CFC process 15:10:27 CHall has joined #ag 15:10:38 present+ 15:10:39 present+ 15:11:13 mbgower: more substantive changes are planned for future version changes 15:11:33 https://github.com/w3c/wcag/pull/4122 15:11:45 looking at #4122 now (user inactivity) 15:12:15 ....want to get feedback on this 15:12:18 q+ 15:12:38 ack Gregg 15:13:38 GreggVan: :sentence broken out as note would have to be art of the definition - it can't be a note, notes cannot alter a definition, just explain it 15:14:00 q+ to ask Mike how he wants to receive the feedback. 15:14:13 ...better leave it as part of the definition 15:14:50 ack Ch 15:14:50 Chuck, you wanted to ask Mike how he wants to receive the feedback. 15:14:52 mbgower: purpose is not to solve it but gather feedback, Gregg please add this info 15:15:17 Chuck: Mike how do you want to receive feedback? 15:15:27 mbgower: best in WCAG issue 15:15:58 ...if there is discussion, the TF will look at how to move forward 15:16:13 listserv email is public-wcag2-issues@w3.org 15:16:39 mbgower: the two are normative changes - the next are substantive, but not normative - Understanding, Techniques, clarify info 15:17:00 https://github.com/w3c/wcag/pull/4212 15:17:37 mbgower: looking at #4212 (labels descriptions) - please comment or give thumbs up or down 15:18:20 q? 15:18:23 mbgower: there seven altogether - you have time till next tuesday 15:18:32 zakim, take up item 1 15:18:32 agendum 1 -- UI-context (ex-views) definition https://github.com/w3c/wcag3/discussions/286#discussioncomment-12480952 -- taken up [from Chuck] 15:19:07 UI-context / view definition discussion 15:19:46 alastairc: lots of discussion already (showing loaf of bread) 15:20:27 alastairc: working in parallel on term for "smallest possible unit" and "conformance unit" 15:21:03 alastairc: explaining that components have units (like drop-down menu where items have focus) 15:21:28 ...main focus has been User Interface Context / Conformance unit 15:21:50 ...we need something to define whether some issue falls within a conformance unit or not 15:22:57 ...it matter where there are alternative ways to achieve functionality (other target on page) - conforming alternate view 15:23:17 ...process / task will probably a set of conformance units 15:23:42 ...one definition is Content (reading WCAG definition) 15:24:33 ...another is "closely available", e.g. "in current interface or after one control activation" 15:24:47 could you share the presentation link? 15:24:53 https://docs.google.com/document/d/1pN6zc0YjxY2TmhmrSii0Y5ghzjdNOqMV5F4a_Dfqsyo/edit?tab=t.yyfjn0xes91s#heading=h.9fwyp0lk034n 15:24:56 ...last iteration was (reads latest definition) 15:24:57 https://docs.google.com/presentation/d/15FRc6dstrCV6brDfA-zL5xH_FRZo6Dr068Cet24TI4U/edit#slide=id.g34c0dee94c2_0_31 15:25:27 ...reading page (URL above) 15:25:52 alastairc: showing example email app with different views 15:26:10 q+ 15:26:15 ...moe difficult would be eBay - same header but content is changing) 15:26:43 ...extra navigation on some pages - item page with dedicated controls 15:27:17 q+ 15:27:26 Thin / Thick slicing slide is https://docs.google.com/presentation/d/15FRc6dstrCV6brDfA-zL5xH_FRZo6Dr068Cet24TI4U/edit#slide=id.g34c0dee94c2_0_37 15:27:32 ...exercise show you can thick-slice or thin-slice it (like treating all pages with same navi as one UI context) 15:27:54 ...thin-slicing interface with specific layout 15:28:40 ...any change where some element comes up this would count as new - probably too extreme because the number gets very high soon 15:28:44 q+ 15:28:47 ack Gregg 15:28:48 .. we need a happy medium 15:29:25 GreggVan: Ebay examples are clearly three units (despite sharing the same header) 15:29:28 q+ on how to define something without comparing to the other pages/units? 15:29:39 I think the location of components which are maintained also belong to the context. 15:30:09 Graham has joined #ag 15:30:13 present+ 15:30:13 GreggVan: suggest Conformance unit changes view if 50% or more of the page changes 15:31:02 not to measured quantitively when looking at the after state (e.g .when an expansion opens tone of content) 15:31:35 ...tabs may have different content - maybe 50% isn't going to work 15:32:02 MJ has joined #ag 15:32:11 GreggVan: if the whole structure changes. in would be a new view - not if something is expanded 15:32:12 present+ 15:32:17 ack hdv 15:32:19 q+ to point out wcag 2 term is a bit circular 15:32:48 hdv: I struggle to map the definition to the practice of audits 15:32:55 present+ 15:33:25 ...the report in the Netherlands shows a thick-slice approach would be difficult - thin-slice would be too many 15:33:37 present+ 15:34:08 q+ to answer hidde, being from a company that creates a large number of conformance reports 15:34:23 ...you look at it more practically to define a sample that makes sense of the content under test that will be useful for recipients of a report - we can't be too prescriptive, need to keep it flexible 15:34:38 ack kirk 15:35:32 ack ala 15:35:32 alastairc, you wanted to comment on how to define something without comparing to the other pages/units? 15:35:41 kirkwood: question is could you respond to design if a page completely changes design e.g. to a smaller screen - how does it relate to the slicing issue? 15:36:41 alastairc: we would need a concept like the existing one on page variation the viewport with probably shouldn't play into Conformance units as this would get messy 15:37:10 ack kirk 15:37:11 A percentage might not meet user needs, though, as counting does not take into account which elements are in te mental focus of the user. 15:37:27 +1 to alastairc's point: easy to 'see' which pages are different, hard to 'define' why it is different 15:37:33 ...its easy to click through a website and define this is really different - the difficulty is defining *why* it is different 15:37:50 q+ 15:38:11 ...like "I know what it is when I see it" - you can only do it when comparing pages within a set 15:38:33 ...equivalent issue is important - element needs to be available 15:38:57 ...the second one is a conformance statement - can people declare one for a part of their site? 15:39:03 ack bru 15:39:03 bruce_bailey, you wanted to point out wcag 2 term is a bit circular 15:39:29 https://www.w3.org/TR/WCAG22/#dfn-change-of-context 15:39:30 ack Ch 15:39:30 Chuck, you wanted to answer hidde, being from a company that creates a large number of conformance reports 15:39:30 major changes that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously 15:39:31 bruce_bailey: WCAG defines changes of context in terms that they are problematic 15:40:23 Chuck: speaking as member of Oracle (1000s of conformance reports): finds large slice definition appealing 15:40:32 Bruce - this did start out with "change of context" as the basis, but were trying to make it more objective 15:40:36 ack GN 15:40:47 q+ to say I remember! The 50% suggestion 15:41:43 ack Ch 15:41:43 Chuck, you wanted to say I remember! The 50% suggestion 15:41:51 alastairc -- i agree the direction we are working *is* making it more objective 15:41:55 GN015: i a user is on a page - is dependent on what is above and below, what comes before and after... like pieces above should not change while pieces below can change 15:42:01 q+ on 50% 15:42:03 q+ 15:42:29 ack ala 15:42:29 alastairc, you wanted to comment on 50% 15:42:38 Chuck: finding 50% change intriguing - it would pertain to changes the meaning for the user - Gregg was talking about changes before and after 15:43:14 ack Gregg 15:43:15 alastairc: 50% of content could change very easily - leaning toward "50% of controls" 15:43:31 +1 to Alastair 15:44:58 GreggVan: changed min on 50% line in the sand - because content changes may be substantial without changing much of the rest - control might be a better idea - should be very clear - and then run against a set of pages to see whether it works - should be roughly equivalent to page definition in WCAG 2 - the key about "view" is whether or not the 15:44:58 structure has changed 15:45:08 q? 15:45:18 ...like for a blind user experience 15:45:23 Among the 50% or less there might be a change above the scrolling area, for example. 15:45:23 On the other side, the page might be large showing many search results, so even a change of 90% might not be a change of context. 15:45:27 https://github.com/w3c/wcag3/discussions/286#discussioncomment-12670208 15:45:28 q+ 15:45:41 Chuck: Alastair where do we go here? 15:45:46 https://docs.google.com/document/d/1pN6zc0YjxY2TmhmrSii0Y5ghzjdNOqMV5F4a_Dfqsyo/edit?tab=t.yyfjn0xes91s#heading=h.9fwyp0lk034n 15:45:48 q- 15:46:43 q+ 15:46:45 q+ to ask about github diff 15:46:49 ack hdv 15:46:52 Alastair :we had a new idea here that's fine - any idea on pinning down this definition to make it more objective - when is a page different enough to become its own conformance unit - not so worried about sampling - can be separate 15:47:17 hdv: would we need a different word fr that too, since now it is based on pages? 15:48:01 ack Ch 15:48:01 Chuck, you wanted to ask about github diff 15:48:07 alastairc: Inn practice it is more separated in terms of components - it there is a methodology based on components, the idea of sampling might change 15:48:55 q? 15:49:14 Chuck: referring to layout flows differences and similarities - could that be a mechanism to determine units because it is isolated from viewport width issues 15:49:52 zakim, take up item 3 15:49:52 agendum 3 -- Review template https://docs.google.com/document/d/1MHJwOWJhGZS4zZYiF9ufNfxTmqFf6bf07vNHAAgfylE/edit?tab=t.0#heading=h.jwan2ys80z90 -- taken up [from Chuck] 15:49:53 alastairc: Look at examples (45 mins past) 15:50:43 Chuck: Makoto wondered what the template to be used should be - different groups were tweaking and alternating templates 15:51:09 alastairc: still living doc currently until it settles... 15:51:37 q+ to ask alastair to paste the text appearance link into irc 15:51:53 q+ 15:52:28 ...Guideline, Requirements from draft; goal what to do, User needs, Foundational Applicability Tree (with some flexibility in the tree) 15:52:46 ...the key work is creating a list of requirements 15:52:51 https://docs.google.com/document/d/1EGEgRebgj8XfvwU-Fx2kAtd-3Ifl-UkEgyOxT1Xc5UY/edit?tab=t.0 15:53:11 DJ has joined #ag 15:53:12 ack ch 15:53:12 Chuck, you wanted to ask alastair to paste the text appearance link into irc 15:53:18 regrets+ 15:53:25 alastairc: Text appearance applicability tree (explains) 15:54:00 ...table of requirements: foundational, supplementary 15:54:27 ...each requirement needs a tech-agnostic but testable statement 15:54:28 ack Gregg 15:54:57 GreggVan: Is the new one the yellow one? 15:55:08 Alastair: yes 15:55:26 GreggVan: what's the difference between guideline and goal? 15:55:52 alastairc: started with previous draft guideline... 15:57:01 GreggVan: (discussion on semantic differences of"goal" and "guideline"with alastairc 15:57:16 +1 no objections 15:57:21 GreggVan: put user needs at the top, then guideline and goal... 15:57:50 ...goal is going into understanding doc 15:58:16 ...difference between guideline and requirements 15:58:34 if gov’t we often used “Purpose”, if useful. 15:58:49 alastairc: was useful for this guideline 15:59:05 Francis_Storr has joined #ag 15:59:10 present+ 15:59:11 GreggVan: what comes first, requirement and test? 15:59:11 q+ to ask about our short term goal 15:59:20 ack Ch 15:59:20 Chuck, you wanted to ask about our short term goal 15:59:43 Guidelines and a purpose statement seems poss missing? 15:59:58 Chuck : Should we alter goals regarding template based on Gregg's feedback? 16:00:05 q+ to ask about "out comes" 16:00:13 Keep a smaller group here to discuss template? 16:00:22 q+ 16:00:27 qq+ 16:01:05 GreggVan: no more comments on template - applicability should come after requirement - requirement have to be split into author and UA 16:01:12 input stays here please 16:01:18 new scribe for template?? 16:01:29 ack Ch 16:01:29 Chuck, you wanted to react to Chuck 16:01:34 scribe+ Chuck 16:01:37 ack bruce 16:01:37 bruce_bailey, you wanted to ask about "out comes" 16:02:08 bruce: What is closest to the outcome? 16:02:35 bruce: You have guideline, goal... we've got this set for most of our requirements, we have a good first draft. 16:02:46 https://docs.google.com/document/d/1y5r2ubojyx4kHOu01HqyC1WLkIPhJibwJigAHwLNwrI/edit?tab=t.345nehok2mye#heading=h.8s3hqqb76mwp 16:02:47 bruce: I'd like to go back to the decision tree refinement document. 16:02:59 alastair: Should I join your breakout room? 16:03:08 will you handle the creation of minutes later on? 16:03:14 bruce: Yes, but to highlight. The decision tree template was very helpful. 16:03:23 q+ 16:03:36 q+ 16:03:47 bruce: this doesn't follow the template. I'm not sure which should be our focus at this point. There is the guideline but its not in the editors draft. The goal is not there, but not sure where they would go in this. 16:04:15 alastair: The doc you linked to was the decision tree refinement. This I put together is focused on how I translated what I saw in the input document. It's more of a trunk. 16:04:37 alastair: It's a trunk, that's not a problem. The question is where does the other stuff go. 16:05:01 alastair: I only included the guideline because it helps understanding. The key thing at this stage is defining foundational and supplimental requirements. 16:05:06 ack kirk 16:05:44 kirkwood: What is missing, maybe it is goal. I've had this in the court room, what is the purpose statement? That was often the way that people could disentangle what was meant. by having a quick definition. 16:05:55 kirkwood: goal sounds unachievable. 16:06:04 alastair: This was intended to be the informative portion. 16:06:07 ack julie. 16:06:25 julierawe: Can one of the ag chairs join the breakout, we have some questions from the template. 16:06:32 alastair: I think I can. 16:06:41 ack julierawe 16:06:52 ack Gregg 16:07:31 Gregg: The decision tree won't fly in any other standards group. It's ok for people to use them. When we are all done I will take a task to do a demonstration to show how it can be done without the tree. I will prove to myself if it can or can't, as an alternative. 16:07:57 Alastair: We are holding that out as a fallback. 16:08:14 Gregg: Tree or no tree, that is something we are going to work out, and I volunteer. 16:08:26 Alastair: I went through that before, it looked similar. 16:08:27 q? 16:09:35 present+ 16:09:56 zakim, make minutess 16:09:56 I don't understand 'make minutess', Chuck 16:10:01 rrsagent, make minutes 16:10:02 I have made the request to generate https://www.w3.org/2025/04/15-ag-minutes.html Chuck 17:58:13 Jem has joined #ag 18:02:26 Adam_Page has joined #ag 19:30:36 ljoakley1 has joined #ag