00:02:29 RRSAgent has joined #aria 00:02:33 logging to https://www.w3.org/2025/11/10-aria-irc 00:02:33 RRSAgent, make logs Public 00:02:34 Meeting: ARIA WG 00:02:45 zakim, stay 00:02:46 I don't understand 'stay', daniel-mac 00:03:04 Jacques has joined #aria 00:03:42 scribe: ZoeBijl 00:03:58 VY: we’ll start with introductions 00:04:06 Jamie has joined #aria 00:04:09 vmpstr has joined #aria 00:04:14 ... please mention your name, pronouns, where you work, and what you’ve been passionate about lately 00:04:58 Valerie Young (Val), she/her 00:05:07 James Nurthen, he/him 00:05:26 Lucal, he/him 00:06:13 Giacomo, he/him 00:06:28 rrsagent, stay 00:06:28 Rémi Bétin, he/him 00:06:35 siri has joined #aria 00:06:56 Shirisha Gubba (Siri), she/her 00:07:17 Present+ 00:07:19 sarah has joined #aria 00:07:29 sarah has joined #aria 00:07:29 siri has joined #aria 00:07:29 Jacques has joined #aria 00:07:29 github-bot has joined #aria 00:07:29 keithamus has joined #aria 00:07:29 smockle has joined #aria 00:07:29 jcraig has joined #aria 00:07:31 Zoë Bijl, she/her 00:07:53 James Teh (Jamie), he/him 00:08:21 James Craig, he/him 00:08:39 jamesn has joined #aria 00:08:39 sarah has joined #aria 00:08:39 siri has joined #aria 00:08:39 Jacques has joined #aria 00:08:39 github-bot has joined #aria 00:08:39 keithamus has joined #aria 00:08:39 smockle has joined #aria 00:08:39 jcraig has joined #aria 00:09:05 cabanier has joined #aria 00:09:11 ??, he/him 00:09:24 present+ 00:09:33 present+ 00:09:43 ?? Rogers, he/him 00:09:58 jamesn has joined #aria 00:09:58 sarah has joined #aria 00:09:58 siri has joined #aria 00:09:58 Jacques has joined #aria 00:09:58 github-bot has joined #aria 00:09:58 keithamus has joined #aria 00:09:58 smockle has joined #aria 00:09:58 jcraig has joined #aria 00:10:02 Yamaha? 00:10:16 ???, he/him 00:10:27 Arielle Gilmore (Ari), she/her 00:11:02 xxx, she/her 00:11:08 jamesn has joined #aria 00:11:08 sarah has joined #aria 00:11:08 siri has joined #aria 00:11:08 Jacques has joined #aria 00:11:08 github-bot has joined #aria 00:11:08 keithamus has joined #aria 00:11:08 smockle has joined #aria 00:11:08 jcraig has joined #aria 00:11:25 Daniel, he/him 00:11:32 Alan Page, he/him 00:11:43 Matt King, he/him 00:12:09 Sarah Higley, she/her 00:12:11 jamesn has joined #aria 00:12:11 sarah has joined #aria 00:12:11 siri has joined #aria 00:12:11 Jacques has joined #aria 00:12:11 github-bot has joined #aria 00:12:11 keithamus has joined #aria 00:12:11 smockle has joined #aria 00:12:11 jcraig has joined #aria 00:13:32 jamesn has joined #aria 00:13:32 sarah has joined #aria 00:13:32 siri has joined #aria 00:13:32 Jacques has joined #aria 00:13:32 github-bot has joined #aria 00:13:32 keithamus has joined #aria 00:13:32 smockle has joined #aria 00:13:32 jcraig has joined #aria 00:13:47 *fixing meeting settings* 00:14:40 front-endian-jane has joined #aria 00:14:40 masonf has joined #aria 00:14:40 giacomo-petri has joined #aria 00:14:40 arigilmore has joined #aria 00:14:40 jamesn has joined #aria 00:14:40 sarah has joined #aria 00:14:40 siri has joined #aria 00:14:40 Jacques has joined #aria 00:14:40 github-bot has joined #aria 00:14:40 keithamus has joined #aria 00:14:40 smockle has joined #aria 00:14:40 jcraig has joined #aria 00:15:39 Chris ??, he/him 00:15:44 Mike ??, he/him 00:15:54 LeoL has joined #aria 00:15:54 front-endian-jane has joined #aria 00:15:54 masonf has joined #aria 00:15:54 giacomo-petri has joined #aria 00:15:54 arigilmore has joined #aria 00:15:54 jamesn has joined #aria 00:15:54 sarah has joined #aria 00:15:54 siri has joined #aria 00:15:54 Jacques has joined #aria 00:15:54 github-bot has joined #aria 00:15:54 keithamus has joined #aria 00:15:54 smockle has joined #aria 00:15:54 jcraig has joined #aria 00:16:05 Jqcques Newman, he/him 00:16:15 s/Jqcques/Jacques/ 00:16:54 Rahim, he/him 00:17:22 LeoL has joined #aria 00:17:22 front-endian-jane has joined #aria 00:17:22 masonf has joined #aria 00:17:22 giacomo-petri has joined #aria 00:17:22 arigilmore has joined #aria 00:17:22 jamesn has joined #aria 00:17:22 sarah has joined #aria 00:17:22 siri has joined #aria 00:17:22 Jacques has joined #aria 00:17:22 github-bot has joined #aria 00:17:22 keithamus has joined #aria 00:17:22 smockle has joined #aria 00:17:22 jcraig has joined #aria 00:17:44 Joey Artner 00:17:52 Vladimir Levin (Vlad), he/him 00:18:04 OK, let’s go through the details for the week 00:18:13 at 9:30 we have our first session 00:18:27 ChrisCuellar has joined #aria 00:18:42 Adam_Page has joined #aria 00:19:04 mehm8128 has joined #aria 00:19:04 LeoL has joined #aria 00:19:04 front-endian-jane has joined #aria 00:19:04 masonf has joined #aria 00:19:04 giacomo-petri has joined #aria 00:19:04 arigilmore has joined #aria 00:19:04 jamesn has joined #aria 00:19:04 sarah has joined #aria 00:19:04 siri has joined #aria 00:19:04 Jacques has joined #aria 00:19:04 github-bot has joined #aria 00:19:04 keithamus has joined #aria 00:19:04 smockle has joined #aria 00:19:04 jcraig has joined #aria 00:19:22 Remi has joined #aria 00:19:24 present+ 00:19:28 present+ 00:19:34 present+ 00:19:35 present+ 00:19:38 present+ 00:19:46 masonf_ has joined #aria 00:19:53 present+ 00:20:20 present+ 00:20:25 masonf_ has joined #aria 00:21:27 present+ 00:21:42 Back to the day… 00:21:54 agenda is on a wikipage:https://github.com/w3c/aria/wiki/TPAC-2025-Kobe,-Japan-Agenda#monday-nov-10-2025 00:21:59 https://github.com/w3c/aria/wiki/TPAC-2025-Kobe,-Japan-Agenda 00:22:04 s/wikipage:/wikipage: / 00:22:08 we have a full agenda today 00:22:10 https://github.com/w3c/aria/wiki/TPAC-2025-Kobe,-Japan-Agenda 00:22:25 we haev an open half hour tomorrow 00:22:33 masonf has joined #aria 00:22:50 if there are breakout sessions that could be interesting for ARIA to join, feel free to edit the wiki 00:22:52 s/haev/have/ 00:23:01 thursday tehre’s ??? 00:23:08 and on friday ?? 00:23:31 s/friday ??/friday there’s a Joint meeting with AGWG/ 00:23:50 s/???/Joint meeting with APA for cross-spec review/ 00:23:57 s/tehre’s/there’s a Joint meeting with APA/ 00:24:39 s/with AGWG/with AGWG about how the automation projects may help with testing WCAG techniques/ 00:24:51 RRSAgent, make minutes 00:24:53 I have made the request to generate https://www.w3.org/2025/11/10-aria-minutes.html ZoeBijl 00:25:36 chair: spectranaut_ jamesn 00:26:31 VY: the enter aria-at is a general session 00:26:45 SH: on wednesday at 5:30 there’s ??? 00:27:02 s/???/a session about IDRef\/CSS selectors/ 00:27:31 JT: they put all the accessibility ones in the same time slots 00:27:47 JN: there’s a whole list of sessions that day 00:27:55 VY: i’ll keep adding links to the wiki 00:27:59 ... feel free to add more 00:28:40 JN: mo-tu, th-fr are usually working group meetings and then wednesday are breakout sessions 00:29:14 link to breakout agenda: https://www.w3.org/2025/11/TPAC/schedule.html#monday 00:29:43 TODAY AT 5 https://www.w3.org/events/meetings/af242c02-5463-4aea-9203-7b2616111a6e/ 00:30:35 topic: AccName vs Content 00:30:53 mark has joined #aria 00:30:57 JN: we’ll try and talk about label precedent and all sort of stuff 00:31:00 ... we have two main issues 00:31:12 ... first is whether `label` should override and set precedent 00:31:36 ... second clarify whether should split ?? 00:31:42 jugglinmike has joined #aria 00:31:54 s/??/name from content/ 00:32:16 present+ 00:32:45 ... i think we probably want to come up with some presedence rules 00:32:57 ... the current algorithm doesn’t really work for anybody 00:33:14 ... we have a whole bunch of things where authors think they’re doing the right thing but they’re not 00:33:24 ... we should look what we can do to clarify this 00:33:35 present+ jugglinmike 00:33:37 ... Steve Faulkner and some other folks at ?? came up with a ??? 00:33:39 https://html5accessibility.com/stuff/2025/06/12/accname-unclarified/ 00:33:40 present+ 00:33:50 s/???/content model/ 00:33:55 ... that’s probably worth a read 00:34:01 ... there are three different ways forward 00:34:03 ... 1. do nothing 00:34:21 ... 2. create some sort of presedence table 00:34:31 ... 3. some sort of content model table 00:34:54 ... we’ve talked about coming up with those tables at various times 00:34:58 ... it could be v useful 00:35:02 ... but would be a huge lift 00:35:13 ... certainly something worth doing 00:35:27 ... for content models, Steve’s blog is probably the easiest way to look at this 00:35:49 ... those different kind of content models fall into different ??? 00:36:04 q? 00:36:18 SH: it looks like it’s focused on elements that make the element not be empty 00:36:27 JC: ?? 00:36:29 Jemma has joined #ARIA 00:36:46 ... i’ll try to look it up before tomorrow’s meeting 00:36:52 JN: that’s the problem 00:37:01 ... looking at these different thins 00:37:05 s/thins/things/ 00:37:21 MK: you were saying about different browsers and AT 00:37:28 ... do we have any info about what they are doing? 00:37:38 ... in the APG we have a table that lists every role 00:37:45 ... this is what happens for every role 00:37:49 JN: it might be 00:38:03 ... to take an example that i think we all agree shouldn’t be named, a paragraph 00:38:14 ... but you still can 00:38:22 VY: the browser won’t complain 00:38:23 q+ to clarify that name and content are not necessarily mutually exclusive, are fundamentally different and can have different requirements depending on type 00:38:37 JN: but then a list item can be named and that could be useful 00:38:43 ... but it generally makes things worse 00:39:06 MK: do we have any instances where some SR+browser combo is overwriting content and others are not 00:39:10 JT: i believe so 00:39:14 s/JC: ??/jcraig: also certain types of content (SVG, USD via ) can have their accessibility defined in the remotely loaded "embedded" content... e.g. SVG title element in a remote file's sub-DOM 00:39:15 ack Jamie 00:39:15 Jamie, you wanted to clarify that name and content are not necessarily mutually exclusive, are fundamentally different and can have different requirements depending on type 00:39:22 ... but don’t have an example top of mind 00:39:27 q? 00:39:32 JT: name is basically a flat string 00:39:36 ... as it’s currently defined 00:39:41 ... but content can contain semantics 00:39:44 ... and other objects 00:39:54 ... so if you flatten it you get just text 00:40:05 ... the second part is that they’re not mutually exclusive 00:40:12 ... an example is landmarks 00:40:15 ... the name is important 00:40:22 ... but you don’t want to overwrite the content 00:40:28 ... AT already know about these 00:40:41 ... with headings you can argue that the name should overwrite the content 00:41:13 ZB: ?? 00:41:30 JT: but in those situations people wouldn’t put a label on the heading 00:41:33 ZB: right 00:41:53 q? 00:42:00 ack me 00:42:08 s/??/for the heading example, a common pattern is links in headings, to create a permalink/ 00:42:14 q+ 00:42:15 MK: we need to figure out the end goal 00:42:20 ... before we jump into solving 00:42:29 ... there’s either intentional masking 00:42:40 ... or unintential masking 00:42:44 ... because of how browsers and at work 00:42:51 ... i wonder if there’s agreement in the room 00:43:01 ... about intentional overriding 00:43:10 ... is encessary in cases and something we don’t want to break 00:43:23 JN: you’re saying there are use cases for that overriding? 00:43:31 MK: yes, and they’re supported by the spec 00:43:56 ... yea, so the ones where the spec currently allows it, and is being used… is there agreement that we don’t want to break that? 00:44:00 s/JN: you/JT: you/ 00:44:06 JT: i would agree with caviats 00:44:13 q+ to discuss the follow-on problem... it's not just the agreement of the browser engine... there re different expectations from users of different downstream AT 00:44:17 ack siri 00:44:26 MK: it’ll be important to know about caviats 00:44:36 siri: for accordians ?? 00:44:47 ... i don’t feel like heading with label didn’t break accessibility 00:44:56 ... for a paragraph i can understand 00:45:21 ack jcraig 00:45:21 jcraig, you wanted to discuss the follow-on problem... it's not just the agreement of the browser engine... there re different expectations from users of different downstream AT 00:45:27 JC: clarifying question 00:45:27 Matt_King has joined #aria 00:45:36 q+ 00:45:37 ... if i recall correctly paragraph label is now prohibited 00:45:38 siri: yes 00:46:04 JC: what did you mean with the heading? 00:46:04 so we have the heading, then the button inside 00:46:10 s/so/siri: so/ 00:46:13 q+ to note that the spec doesn't actually specify whether names should or shouldn't override at all, plus answer the screen reader question 00:46:18 JC: this could be specific AAM problems 00:46:33 ... but the follow on, there are different user expectations based on which AT you use 00:46:51 ... VoiceOver on Mac might say “Accordian heading with two buttons” 00:46:56 ... then the user knows where to go from there 00:47:08 ... go into the heading to find the buttons for example 00:47:12 q? 00:47:21 q+ 00:47:25 ack giacomo-petri 00:47:31 ... but the accname spec right now says the name should include the button labels 00:47:42 siri: ??? 00:47:52 giacomo-petri: when we ?? the generic roles 00:47:57 ... at the time we also broke some of the ?? 00:48:04 ... to provide visual presentation 00:48:23 ... we had normal price vs promotional price 00:48:27 ... we would use aria-label to indicate the different prices 00:48:51 JC: can you clarify the example? 00:49:08 Jemma has joined #ARIA 00:49:15 GP: there was a strike through price and a discount price 00:49:18 present+ 00:49:21 ... and the aria-label was placed ??? 00:49:42 s/???/on the `div`/ 00:49:47 q? 00:49:51 JN: we’re not too worried about things that never really worked 00:50:07 MK: for most AT label information just disappears in those situations 00:50:09 s/there was a strike through price and a discount price/there was a strike through price and a discount price so the SRs were not adequately conveying the old content was stricken/ 00:50:12 ack Jamie 00:50:12 Jamie, you wanted to note that the spec doesn't actually specify whether names should or shouldn't override at all, plus answer the screen reader question 00:50:16 siri: i think it worked in JAWS at some point 00:50:23 JT: if the div was empty maybe 00:50:31 q? 00:50:44 ... with the exception of ?? 00:50:53 ... what ATs are having to do is make assumptions 00:51:05 ... the spec doesn’t say anything about whether label should overwrite content 00:51:24 s/exception of ??/exception of name prohibited/ 00:51:28 ... the answer to the heading questions 00:51:47 ... currently because headings are generally pretty straight forward in their content 00:51:52 ... if there’s an explicit label 00:51:55 ... aria-label for example 00:51:59 qq+ to mention the logistics of queueing with a prompt 00:52:04 ... then the label overrides the content complely 00:52:22 ... if the heading contains an itneractive element it doesn’t do that 00:52:30 ... that kind of solves the problem 00:52:33 ... but it’s not defined 00:52:36 ... which is scary 00:52:45 ack me 00:52:46 jcraig, you wanted to react to Jamie to mention the logistics of queueing with a prompt 00:52:51 ack jcraig 00:52:52 ... with the content model ??? 00:53:18 ... ????? 00:53:18 ack me 00:53:24 ack me 00:53:27 JN: drag this bag to problems and solutions 00:53:45 ... sounds to me that Jamie made it clear that label and content are different concepts 00:53:58 ... we should be clearer in the spec that these are different things 00:54:09 ... are there cases where label should overwrite content? 00:54:12 JT: yes 00:54:37 q+ 00:54:46 JN: do we have use cases for overriding where label overwrites content with focusable children? 00:54:50 JC: yes 00:54:58 q+ to answer use cases for nodes with child accessible nodes 00:55:01 ... there was ?? 00:55:13 daniel-mac_ has joined #aria 00:55:22 ack front-endian-jane 00:55:36 front-endian-jane: there are some data-viz examples 00:55:44 ... things that make visual sense and have some semantics 00:55:54 ... with trying to make it sr compatible 00:55:55 q+ 00:56:10 ... it would be a lot less code to be able to override content explicitly 00:56:11 q+ to respond to the charts/dataviz scenario 00:56:29 ... we usually have to write it multiple times and hack with css 00:56:31 ack sarah 00:56:31 sarah, you wanted to answer use cases for nodes with child accessible nodes 00:56:35 JN: could you not use role=img on it? 00:56:45 front-endian-jane: we don’t necessarily want it to be treated as an image 00:56:51 SH: ??? 00:56:58 ... so you overwrite that wiht an aria-label 00:57:00 q? 00:57:04 ... another is ?? 00:57:09 ... another is with an AI bot 00:57:13 ... if you’re arrowing through messages 00:57:30 ... it would be nice if you could hide the repeat commands (??) 00:57:32 q+ to note that these are not override cases 00:57:44 ack jcraig 00:57:44 jcraig, you wanted to respond to the charts/dataviz scenario 00:57:56 JC: to respont to the dataviz scenarios 00:58:00 q+ 00:58:05 ... which are kinda leading into aria actions… 00:58:18 ... there’s a session tomorrow where i talk about the ?? 00:58:22 ... what are we doing with SVG 00:58:30 ... interactive SVG 00:58:35 ... relevant to this situation 00:58:44 ... do we want something like a leafnote 00:58:54 ... VO on the desktop has this ?? 00:59:02 ... on iOS you can do it via the actions rotor 00:59:08 s/leafnote/leaf node/ 00:59:17 ... and it kinda sounds like that’s part of what we’re talking about 00:59:29 ... but you wouldn’t want that for the main content for a user 00:59:44 ack Jamie 00:59:44 Jamie, you wanted to note that these are not override cases 01:00:04 JT: the examples are, as i understand, where you don}t want the label to override? 01:00:11 SH: no i do want the override 01:00:35 JT: when you cursor through the content you don’t want the child nodes to be read 01:00:44 ... but you want to be able to navigate into it and still read them 01:01:00 ... so that’s where the definition of override is important 01:01:04 ... same with list item 01:01:18 q+ lucas 01:01:28 ... do you know how this works with the heading and link role? 01:01:35 various: no 01:01:41 q+ 01:01:46 ack Matt_King 01:02:05 JT: to answer your questions JN, are there any situations where we do want this 01:02:12 MK: the link naming one is a good example 01:02:20 ... you see a lot of links with an image inside of it 01:02:27 ... and then an aria-label on the link 01:02:46 ... that image is like it’s not there 01:02:54 ... so that’s what i meat with override 01:02:57 ack lucas 01:03:04 ... sounds like that’s what you meant too JT 01:03:08 JT: correct 01:03:28 Lucas: i had to rewrite parts of the accname stuff for chrome 01:03:38 ... when you have this list of things that override eachother 01:03:49 ... it feels like… as a human i’m trying to get it all in my head 01:03:56 ... it was complicated to get it to work 01:04:09 ... would the spec say you have a button, and a label 01:04:23 ... in the chrome implementation the label would override the content of the button 01:04:34 ... as a SR user you would only get the label 01:04:41 ... does it make sense to override here and there 01:04:45 ... if we do this 01:04:52 ... this list would grow to be unmangable 01:05:00 VY: too many categories… 01:05:00 ack sarah 01:05:25 SH: it’s not fully overriding, but not not fully overriding 01:05:30 q+ 01:05:31 q+ 01:05:46 ... with instances, with JAWS, it will duplicate the label and then the content (??) 01:06:07 ... moving through cells with arrow keys, you don’t want that duplication 01:06:25 JT: i genuinly thought grid and table cells were consistent 01:06:42 SH: with a feed list (articles in a feed) 01:06:45 ... ??? 01:07:05 ... the list should specifiy overrides in certain situations 01:07:09 ... semi-overridden? 01:07:22 MK: we kinda already have this 01:07:28 ... it’s not spelled out 01:07:33 JC: what are you thinking of? 01:07:42 MK: well if you look at regions and articles 01:07:51 ... you have name from content and name from author 01:08:14 ... this is more a matter of actually specifying of what SR behaviour is in sitations 01:08:28 ack me 01:08:28 ... we don’t want the content to be hidden 01:08:32 ... but we don’t want it to be read 01:08:51 q+ 01:08:55 JN: the content is never the name for a region 01:08:58 MK: no correct 01:09:03 ... we have name from content 01:09:06 ... name from author 01:09:08 ... name from either 01:09:12 ... or name prohibited 01:09:12 ack front-endian-jane 01:09:31 front-endian-jane: what SH said, having more control/specificity of what happens would be good 01:09:45 ... the authors are going to want to do different things 01:10:00 ... having a list of what should happen unless otherwise specified would be good 01:10:04 q+ 01:10:08 ack j 01:10:09 q+ 01:10:11 ... but having more control would be great 01:10:19 q+ to note that this is an AT spec, the models, how it currently works 01:10:19 JN: so where do we move from here 01:10:25 q? 01:10:37 q- 01:10:42 ack sarah 01:10:54 q+ 01:10:55 SH: interactive controls that are also containers 01:10:58 ... like articles in a feed 01:11:03 ... and things that are neither of those things 01:11:15 ack Jamie 01:11:15 Jamie, you wanted to note that this is an AT spec, the models, how it currently works 01:11:15 ... a region or a non-interactive list item 01:11:22 JT: i get this is kinda implicit 01:11:34 ... but explicitly, we are defining an AT spec 01:11:40 ... we are getting into AT speccing here 01:11:49 ... i don’t have a problem with that, just want to be clear about 01:11:57 ... browsers don’t like removing things 01:12:15 ... that way AT gets more ways to interpret/use the thing 01:12:21 ... and then how we define it 01:12:25 ... we have the name 01:12:31 ... i don’t want to talk about naming… 01:12:36 ... but we have: 01:12:42 ... - naming always overrides 01:12:46 ... - naming from ??? 01:13:07 q+ to discuss the pitfalls of "spec-ing" AT behavior, accidental hiding of content, and the VO web navigation changes about 8 or 10 years ago, 01:13:12 ... - use name when focused 01:13:16 ... is there a fourth list? 01:13:19 s/from ???/for container/ 01:15:00 q? 01:15:23 ... fourth category is: name prohibited 01:16:54 the four categories: 01:16:54 1. name always overrides 01:16:55 2. name of container (append) 01:16:55 3. use name when focused 01:16:55 4. name prohibited 01:17:52 examples 01:17:52 1. button and link 01:17:52 2. landmarks 01:17:52 3. grid cell, list item, focusable article in feed 01:17:52 4. paragraph and generic 01:18:02 JN: ten minutes till break 01:18:02 ack m 01:18:03 ack jcraig 01:18:04 jcraig, you wanted to discuss the pitfalls of "spec-ing" AT behavior, accidental hiding of content, and the VO web navigation changes about 8 or 10 years ago, 01:18:29 q+ 01:18:31 JC: there are some potential pitfalls what people are interpreting speccing AT behaviour 01:18:36 ... that’s broader than the W3C 01:18:43 ... ?? to avoid accidental masking 01:18:57 ... this group as it should be is heavily represented by authors 01:19:14 ... i hinted we probably shouldn’t get into the changes we made to VO 01:19:21 ... but i think it’s apllicable here 01:19:34 ... VO on mac was developed for mac apps specifically 01:19:42 ... WebApps weren’t a big deal when it started 01:19:57 ... basically container elements had a label 01:20:06 ... so any container, in say mail, would have a lebl 01:20:15 ... and it would force the user to interact with the element 01:20:24 ... that particular behaviour… 01:20:42 ... the way people were developing applications at the time 01:20:45 ... this behaviour became problematic 01:20:51 s/lebl/label/ 01:20:57 ... it could be three quearts of the content on the apge 01:21:15 ... you’d hear the name “group” and be like “oh this could be a massive thing” 01:21:19 s/quearts/quarters/ 01:21:25 ... we sat down to talk about this at the time 01:21:27 s/apge/page/ 01:21:39 ... people kinda liked the navigation 01:21:54 ... the major shift we made was that VO would auto step in and out of things 01:22:25 ... people know VO+Shift+Up Arrow|Down Arrow to go out and in of containers 01:22:38 q? 01:22:43 q- 01:22:52 ... you can also do VO+Shift+Left|Right Arrow to skip around the tree 01:23:05 ... so what i’m hearing is not specifying AT behaviour 01:23:10 ... it’s ?? 01:23:29 ... i’m always weary of speccing interaction behaviour 01:23:38 ... but there may be ?? for an aria flag 01:23:52 ... but maybe there’s a scenario like chart 01:24:16 ... where as long as it’s clear to users you can interact with it 01:24:31 ... you can have a override label and then still have the internals? 01:24:56 ... maybe a switch user wants the content exposed but an AT user doesn’t(??) 01:25:01 zakim, close the queue 01:25:01 ok, jamesn, the speaker queue is closed 01:25:18 Lucas: one of the ideas that it was going into 01:25:21 s/have the internals/access (or interact with) the content inside/ 01:25:22 ... if it’s a leaf node 01:25:25 ... the idea i had 01:25:36 ... leaf node overrides, known leaf node appends 01:25:51 ... and a flag to override, append, or prohibit 01:26:05 JT: this isn’t really relative to browser ?? 01:26:26 ... I’d argue the browser is, mostly, already doing what the spec requires 01:26:29 Lucas: i agree 01:26:39 ... i’m talking about the AT process 01:26:39 JT: ah, yes, understood 01:26:44 q? 01:26:47 JN: not sure where we’re going with this 01:27:02 ... but it seems we agree this is something to work towards 01:27:21 ??: were you suggesting a new feature? 01:27:24 q+ 01:27:29 JC: i think there’s an apportunity for it 01:27:41 ... what i’m weary about , it doesn’t matter how easy a feature is 01:27:57 ... some authors are going to missuse or overuse this 01:28:09 ... it’ll only affect their pages luckily 01:28:18 ... if everything’s a heading, nothing is 01:28:32 ... so i don’t know, but i think there’s an opportunity for it 01:28:40 s/apportunity/opportunity/ 01:28:57 VY: suggestion for next steps: 01:29:09 ... to start, i think it would be nice to have an explainer to the problem 01:29:23 ... i think we made great strides towards articulating that in this meeting 01:31:25 JT: how often have you heard this be a problem for users? 01:31:31 JN & VY: all the time 01:31:36 JT: ah 01:31:50 ... it’s like maybe, i’m not clear on where the lack of interop is 01:31:57 ... and where does it cause the most pain 01:31:59 MK: yea 01:32:05 s/& VY/&SH/ 01:32:10 ... certain places where browsers do overrides… 01:32:21 ... authors wanting to get a good experience 01:32:27 ... but not knowing how to get there 01:34:02 RESOLUTION: Jamie, Sarah, and Zoë will meet to discuss 01:34:11 *break time* 01:34:16 zakim, open the queue 01:34:16 ok, jamesn, the speaker queue is open 01:34:36 RRSAgent, make minutes 01:34:38 I have made the request to generate https://www.w3.org/2025/11/10-aria-minutes.html ZoeBijl 01:42:06 front-endian-jane has joined #aria 01:46:42 mehm8128 has joined #aria 01:51:18 daniel-mac has joined #aria 01:58:49 lucasradaelli has joined #aria 02:02:49 present_ 02:02:53 present+ 02:03:31 sarah has joined #aria 02:04:24 topic: Update on Open UI 02:04:56 reminder that the room is muted 02:05:35 Penny has joined #aria 02:06:43 Adam_Page has joined #aria 02:06:48 s/Lucal, /Lucas Radaelli, / 02:07:35 arigilmore has joined #aria 02:07:35 s/xxx, /Jane Fulton, / 02:07:38 jugglinmike has joined #aria 02:07:49 JN: anyone new in the room? 02:07:57 siri has joined #aria 02:08:08 hello world. first message to IRC. 02:08:11 Keith Cirkel, he/him or they/them 02:08:45 ??, he/him 02:08:55 Lola, she/her 02:08:58 present+ 02:09:16 https://github.com/w3c/aria/wiki/TPAC-2025-Kobe,-Japan-Agenda 02:09:23 Penelope, ?? 02:09:35 Jan Jaeschke, he/him 02:09:57 JN: Keith, you want to take it over? 02:10:00 KC: I would love to 02:10:04 ... still doing some login stuff 02:10:14 *elevator music* 02:10:16 Penelope (Penny), she/her, PM @ Google for UI Capabilities (drawing pixels!), passionate about cats! 🐈 02:10:23 LeoL has joined #aria 02:10:46 s/Penelope, ??/Penelope (Penny), she\/her/ 02:11:52 Adam_Page arigilmore re the new WebDriver locator strategy for "accessible name": https://github.com/w3c/webdriver/pull/1440 02:12:08 KC: we’re talking about a variety of Open UI features 02:12:16 ... wanted to give some details on popovers as a feature 02:12:27 ... `popover` is an attribute that can be added to any element 02:12:37 ... it adds elements to the top layer 02:12:41 ... which is a visiual thing 02:12:50 ... other elements on the top layer are full screen 02:12:54 ... an example is dialogs 02:12:59 ... ?? ui 02:13:02 s/dialogs/modal dialogs/ 02:13:08 ... such as menus and ?? 02:13:10 s/??/floating/ 02:13:16 ... and usually that’s click 02:13:23 ... but there’s these different modes of popover 02:13:36 ... because we want to be able to dictate how to layer these UIs 02:13:49 ... when you use escap or a gesture, it will dismiss the popover 02:13:53 ... you can nest popovers 02:13:59 ... there’s also popoverhint 02:14:03 ... which is like a tooltip 02:14:08 ... but can also be a hover card 02:14:15 s/popoverhint/popover=hint/ 02:14:16 ... like issues on github or users on social media 02:14:30 ... popover=manual doesn’t have this light dismiss behaviour 02:14:36 q? 02:14:39 ... it’s possible to make it work the same though 02:14:50 ... so the intent is that most of these modes are going to be auto 02:14:58 ... but they can used interchangably 02:15:00 jarhar has joined #aria 02:15:05 ... popover’s have a source 02:15:10 ... this is usually a button 02:15:21 ... the popovertarget action ?? 02:15:31 ... and the `commandfor` ?? 02:15:39 ... `interestfor` uses a different model 02:15:50 ... `interestfor` is a dive independent way 02:15:55 s/dive/device/ 02:16:09 s/action ??/attribute/ 02:16:12 ... the short answer is hover on mouse, focus on keyboard, and context menu for touch 02:16:49 ... the ppoint of the source is that it allows us to do interesting things with focus 02:16:56 ... like restore it to the source on clos 02:16:59 s/clos/close/ 02:17:03 s/ppoint/point/ 02:17:10 ... when the button is focused ?? 02:17:19 ... rather than looking at the next focuxsable thing in the dom 02:17:22 ... it will look at the ?? 02:17:31 ... it skips the ??? 02:17:46 ... in this way it creates this relationship where it skips focus into the popover 02:17:50 ... relationships 02:17:59 ... there are ways to open a popover 02:19:02 ... there are four actions 02:19:26 ... `popovertarget`, `commandfor`, `interestfor`, and imperative API 02:19:29 ... anchors 02:19:32 ... what’s an anchor? 02:19:34 q? 02:19:40 ... CSS has created this new way to position elements 02:19:55 ... traditionalyl you would use `postition` and the inset properties 02:20:03 ... (top, right, bottom, etc) 02:20:19 ... this new way uses `anchor-name` 02:21:06 ... example: `heading { anchor-name: --foo }` `a { position-anchor: --foo }` 02:21:35 https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/position-area 02:21:38 Also there's this cool tool: https://anchor-tool.com/ 02:22:09 ... the intent of anchors is that they present a ?? for visual design 02:22:14 ... but they can be decorative 02:22:20 ... they can just be for decoration 02:22:23 ... example: a tooltip 02:22:49 ... ??? 02:23:00 KC: elements can have implicit anchors 02:23:06 ... there are three things specified 02:23:14 ... - popovers with a source 02:23:25 ... - a `