16:59:27 RRSAgent has joined #aria 16:59:31 logging to https://www.w3.org/2026/04/16-aria-irc 16:59:31 RRSAgent, make logs Public 16:59:32 Meeting: ARIA WG 16:59:35 chair: ValerieYoung 16:59:39 agendabot, find agenda 16:59:39 spectranaut_, OK. This may take a minute... 16:59:40 agenda: https://www.w3.org/events/meetings/690d057f-db6d-4169-b13f-68d7f1336b59/20260416T130000/ 16:59:40 clear agenda 16:59:40 agenda+ -> New Issue Triage https://tinyurl.com/mse38et2 16:59:40 agenda+ -> New PR Triage https://github.com/search?q=is%3Aopen+is%3Apr+created:%3E=2026-04-09+repo:w3c/aria&type=Issues 16:59:43 agenda+ -> WPT Open PRs https://bit.ly/wpt_a11y 16:59:45 agenda+ -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates 16:59:48 agenda+ ARIA in HTML for revised recommendation, please have your AC reps vote 16:59:51 agenda+ -> CSS scroll-marker-group modes && WAI-ARIA patterns https://github.com/w3c/css-aam/issues/18 16:59:54 agenda+ -> Updates to aside element https://github.com/w3c/html-aria/issues/411 17:00:09 sakhapov has joined #aria 17:00:14 giacomo-petri has joined #aria 17:01:40 aardrian has joined #aria 17:01:52 present+ 17:01:54 present+ 17:02:08 Francis_Storr has joined #aria 17:02:13 present+ 17:02:19 present+ 17:02:23 pkra has joined #aria 17:02:35 present+ 17:02:42 present+ 17:02:42 present+ 17:03:09 scribe+ 17:03:17 zakim, next item 17:03:17 agendum 1 -- -> New Issue Triage https://tinyurl.com/mse38et2 -- taken up [from agendabot] 17:03:17 I can't comment on that because it doesn't look like a github issue to me. 17:03:21 Siri has joined #aria 17:04:02 spectranaut_: html-aam 604. li outside list 17:04:36 pkra: it would be great if implementors could implement this change 17:04:51 spectranaut_: right. looks like we have a bunch of these. 17:05:15 q+ 17:05:34 scotto: was wondering about this. Conversation with chrome engineer, that they do look at WPTs and track failing ones to deal with. 17:05:42 ... but of course the WPT has not been merged either. 17:05:50 ... still, it would be good if we only need one. 17:05:55 ... WPT or browser bugs. 17:06:14 ack keithamus 17:06:22 cyns has joined #aria 17:06:30 katez has joined #aria 17:06:35 present+ 17:06:37 keithamus: just to say: there's a lot of WPTs and a lot of failure and thus a lot of noise for teams, at least for us. 17:06:52 ... so it's worth filing a separate issue to make sure it's surfaced with the right team 17:06:53 melsumner has joined #aria 17:07:18 scotto: thanks for clarifying! 17:07:21 present+ 17:08:04 spectranaut_: if you're interested, we could set up a deep dive for people who want to learn filing browser bugs. 17:08:31 ... though I wonder why the WPT test isn't merged. 17:08:49 cyns: maybe we should have separate processes for different browsers. 17:09:10 keithamus: I suspect they're similar though. 17:09:42 dgrogan: we have the same firehose problem as firefox. If you can find the automated WPT bugs and ping it, that would be sufficient. 17:09:52 Stefan has joined #aria 17:09:55 spectranaut_: I'll look into landing the WPT PR. 17:10:34 keithamus: I think WebKit doesn't have automatic bugs for WPT failures. 17:10:51 spectranaut_: aria 2767. listbox and accname 17:11:40 q+ 17:11:56 scotto: listboxes as popups often don't have accessible names. I haven't seen anyone being impacted by this. I don't think testing flags it since combobox names cover it. Conversations with other developers made me wonder if this requirement should be more nuanced. 17:12:14 ack giacomo-petri 17:12:16 ack giacomo-petri 17:12:21 Stefan has joined #aria 17:12:28 present+ 17:12:58 CurtBellew has joined #aria 17:13:05 giacomo-petri: to echo what scotto said. Our tool triggers an error for this kind of scenario and I agree with Scott that this change would negatively impact users. 17:13:06 present+ 17:13:37 q+ 17:13:50 scotto: I'm not sure how this works from the automatic table generation code in the spec. so maybe not a great first issue. 17:15:19 pkra: there's a wider issue on handling more nuanced requirements in the automation. I think it's a good first issue in that we editors should work out the automation. 17:15:26 ... I'll tag the issue that reflects this. 17:15:27 ack giacomo-petri 17:15:50 giacomo-petri: just fyi, I think the suggestion role and separator are cases. 17:17:25 mattking: I'm wondering if this kind of situation should also look into accname, i.e., whether this should affect calculation. 17:17:33 melsumner: I can take it on. 17:17:42 scott has joined #aria 17:17:52 present+ 17:17:56 bryan: me too. 17:18:06 spectranaut_: next up css-aam 17. 17:18:24 aardrian: I just wanted to flag it quickly so it's not lost. 17:18:34 spectranaut_: should we agenda it? 17:18:48 aardrian: I'm not sure anymore. 17:18:58 ... but I assigned myself to update. 17:19:01 spectranaut_: great. 17:19:18 ... next graphics-aria 14 17:21:40 pkra: I just wanted to put this down. inspired by recent svg-aam text discussions and longtime on my mind. 17:21:48 cyns: assign to me so we can track as well. 17:22:02 spectranaut_: next aria 2762 17:23:46 pkra: it's a bit of a mismatch. Definition doesn't suggest any specific way to connect to term. Term suggest something. We should clarify, probably a good first issue. 17:25:04 zakim, next item 17:25:04 agendum 2 -- -> New PR Triage https://github.com/search?q=is%3Aopen+is%3Apr+created:%3E=2026-04-09+repo:w3c/aria&type=Issues -- taken up [from agendabot] 17:25:04 I can't comment on that because it doesn't look like a github issue to me. 17:25:11 spectranaut_: just one from peter 17:25:18 pkra: still a draft. I'm working on it. 17:25:28 zakim, close this item 17:25:28 agendum 2 closed 17:25:29 I see 5 items remaining on the agenda; the next one is 17:25:29 3. -> WPT Open PRs https://bit.ly/wpt_a11y [from agendabot] 17:25:36 zakim, take up item 4 17:25:36 agendum 4 -- -> Deep Dive planning https://bit.ly/aria-meaty-topic-candidates -- taken up [from agendabot] 17:25:36 I can't comment on that because it doesn't look like a github issue to me. 17:25:47 spectranaut_: nothing new. 17:25:52 zakim, close this item. 17:25:52 agendum 4 closed 17:25:53 I see 4 items remaining on the agenda; the next one is 17:25:53 3. -> WPT Open PRs https://bit.ly/wpt_a11y [from agendabot] 17:25:59 zakim, next item 17:25:59 agendum 3 -- -> WPT Open PRs https://bit.ly/wpt_a11y -- taken up [from agendabot] 17:25:59 I can't comment on that because it doesn't look like a github issue to me. 17:26:12 zakim, close this item. 17:26:12 agendum 3 closed 17:26:13 I see 3 items remaining on the agenda; the next one is 17:26:13 5. ARIA in HTML for revised recommendation, please have your AC reps vote [from agendabot] 17:26:14 zakim, next item 17:26:15 agendum 5 -- ARIA in HTML for revised recommendation, please have your AC reps vote -- taken up [from agendabot] 17:26:28 spectranaut_: just a reminder to please ask your AC rep to vote. 17:26:40 zakim, close this item. 17:26:40 agendum 5 closed 17:26:41 I see 2 items remaining on the agenda; the next one is 17:26:41 6. -> CSS scroll-marker-group modes && WAI-ARIA patterns https://github.com/w3c/css-aam/issues/18 [from agendabot] 17:26:42 zakim, next item 17:26:42 agendum 6 -- -> CSS scroll-marker-group modes && WAI-ARIA patterns https://github.com/w3c/css-aam/issues/18 -- taken up [from agendabot] 17:26:42 I can't comment on that github issue because it's not in a repository I'm allowed to comment on, which are: w3c/aria w3c/aria-common w3c/core-aam w3c/accname w3c/html-aam. 17:27:29 daniil: to recap, CSS scroll-markers were introduced, in particular for native carousels. 17:27:41 ... this is our update after feedback from the ARIA WG 17:27:59 ... in my explainer I compared the two modes for scroll-marker-groups. 17:28:11 ... the first one is tab mode. the second links mode. 17:28:49 ... I would suggest to go through the explainer a bit. 17:29:22 ... or wait until people have read it? 17:29:34 dgrogan: could you live share some demos perhaps? 17:30:20 daniil: yes. First one is tabs mode. 17:30:42 ... one page of the carousel is one tab. Only the active tab is present in the acc tree. 17:30:58 ... this was one change - browsers should now auto-hide it. 17:31:08 ... here's a codepen demo 17:31:37 ... I can tab to get to the first marker. then left/right arrows moves through the tabs. 17:31:58 ... in the a11y tree you can see that only the active tab is in the tree. 17:32:12 ... when we're at the marker, we go from the marker to content. 17:32:40 ... but another tab won't take you to the next tab but out of the group. 17:32:53 ... the second one is links mode 17:33:13 ... in this mode, every scroll marker is a tab stop. They act like a focusgroup. 17:33:28 ... another codepen demo 17:33:47 ... we go to the first link. Tab moves me through the links. 17:33:58 ... activation moves me to the content. 17:34:43 ... just to recap, we discussed aria-current a while back and it's out of scope for this explainer. 17:34:47 spectranaut_: thank you. 17:34:47 q? 17:35:10 q+ 17:35:36 mattking: I will need to read the explainer but it sounds like the first case is very similar to tabpanel behavior so I hope we can align there. 17:35:41 +1 to Matt 17:36:05 daniil: we followed the tabbed carousel pattern. 17:36:10 mattking: great. 17:36:17 ack cyn 17:36:22 daniil: the links case is from the landmark navigation pattern. 17:36:38 q+ 17:36:42 cyns: there was a proposal a few years back from Google on a customized tab panel. 17:36:52 ... is this a continuation of that? 17:37:09 daniil: I don't know but don't think so. This sounds like HTML but here we are talking about CSS 17:37:10 ack scott 17:37:17 scotto: I think it's definitely different. 17:38:30 ... it sounds like a lot of the feedback Sarah H, Sara S, myself and others provided is being considered. 17:38:35 ... I would suggest to please update the codepen to include focusable content. Otherwise it's not as clear what the keyboard behavior would be. 17:38:42 q? 17:38:44 ... it will take me a while to take a look. 17:39:04 mattking: I'd second that. Also something before and after to make it easier for AT users. 17:39:14 daniil: thanks, will do. 17:39:39 Rob's examples - https://flackr.github.io/web-demos/css-overflow/scroll-marker-type/ 17:39:43 spectranaut_: it would be great if many people could take a look. 17:39:58 I think this is the proposal I was talking about https://css.oddbird.net/toggles/explainer/ 17:40:07 ... do people know how to take a look? E.g. get chrome canary and activate experimental features. 17:40:08 chrome:://flags 17:40:16 oops. chrome://flags 17:40:33 chrome://flags/#enable-experimental-web-platform-features 17:41:12 mattking: yes more details for testing would be great. Also in the issue itsef. 17:41:41 spectranaut_: right. that would be good. 17:43:12 siri: regarding link mode. tab mode makes sense. But also in the linked mode arrow keys is the expected way? 17:43:43 daniil: for links you just tab through them. 17:43:51 siri: but in the example I thought I had to 17:44:01 daniil: for me arrow navigation doesn't work. 17:44:15 siri: curious, it's different for me. I'll look into it. 17:44:35 zakim, next item 17:44:35 agendum 7 -- -> Updates to aside element https://github.com/w3c/html-aria/issues/411 -- taken up [from agendabot] 17:44:35 I can't comment on that github issue because it's not in a repository I'm allowed to comment on, which are: w3c/aria w3c/aria-common w3c/core-aam w3c/accname w3c/html-aam. 17:45:31 q+ 17:45:42 spectranaut_: there was a recent comment from APG putting it on the agenda. 17:46:14 Daniel: from APG user research, chrome and firefox mark aside as complimentary in header and footer. But spec says only main and body, unless named. 17:46:37 ... we should either match implementations or file bugs. 17:46:50 spectranaut_: this is testable already, right? 17:46:56 scotto: there are tests from 2023. 17:47:09 mattking: I don't think we need to re-discuss. Browsers are just not doing it. 17:47:36 scotto: looking through the tests from 2021. In 2023 James Craig commented on updated tests. 17:47:52 ... there's a lingering PR of mine that just wasn't merged. 17:47:57 ... due to the implementation mismatch. 17:48:17 spectranaut_: I'll look at WPT tests and follow up - unless someone else wants to. 17:48:37 mattking: sounds good. Daniel? 17:48:57 Daniel: yes. It sounds good to update tests to get things moving. 17:49:24 mattking: we have a PR in APG to say the same thing that html-aam says. But then we noticed the discrepancies and thus wanted to clarify. 17:49:41 ... which brings us back to the start of the meeting. 17:49:45 spectranaut_: agreed. 17:49:48 zakim, end meeting 17:49:48 As of this point the attendees have been Adam, aardrian, Daniel, Francis_Storr, pkra, giacomo-petri, filippo-zorzi, katez, melsumner, Stefan, CurtBellew, scott 17:49:51 RRSAgent, please draft minutes v2 17:49:52 I have made the request to generate https://www.w3.org/2026/04/16-aria-minutes.html Zakim 17:49:59 I am happy to have been of service, pkra; please remember to excuse RRSAgent. Goodbye 17:49:59 Zakim has left #aria 17:50:10 melsumner has left #aria 18:04:03 github-bot has joined #aria