17:57:24 RRSAgent has joined #aria 17:57:28 logging to https://www.w3.org/2026/02/19-aria-irc 17:57:28 RRSAgent, make logs Public 17:57:29 Meeting: ARIA WG 17:57:30 agendabot, find agenda 17:57:30 spectranaut_, OK. This may take a minute... 17:57:31 agenda: https://www.w3.org/events/meetings/690d057f-db6d-4169-b13f-68d7f1336b59/20260219T130000/ 17:57:31 clear agenda 17:57:31 agenda+ -> New Issue Triage https://tinyurl.com/3hkcsnym 17:57:31 agenda+ -> New PR Triage https://github.com/search?q=is%3Aopen+is%3Apr+created:%3E=2026-02-12+repo:w3c/aria&type=Issues 17:57:34 agenda+ -> WPT Open PRs https://bit.ly/wpt_a11y 17:57:36 agenda+ -> [css-fonts-5] Text Fitting: Default scaling limit #12886 https://github.com/w3c/csswg-drafts/issues/12886 17:57:39 agenda+ -> CSS/ARIA Issue Triage: [css-display-4] reading-flow/reading-order vs text selection #12014 https://github.com/w3c/csswg-drafts/issues/12014 17:57:43 agenda+ -> CSS/ARIA Issue Triage: Add an ::interest-button pseudo element to interest invokers #12437 https://github.com/w3c/csswg-drafts/issues/12437 17:59:08 filippo-zorzi has joined #aria 18:00:28 Adam_Page has joined #aria 18:04:07 Jacques has joined #aria 18:04:09 giacomo-petri7 has joined #aria 18:04:10 giacomo-petri7 has left #aria 18:04:15 giacomo-petri has joined #aria 18:04:19 present+ 18:04:28 pkra has joined #aria 18:04:37 present+ 18:05:05 present+ 18:05:33 Siri has joined #aria 18:07:17 Francis_Storr has joined #aria 18:08:10 present+ 18:08:10 scribe+ 18:08:12 present+ 18:08:17 present+ 18:08:28 jamesn has joined #aria 18:09:11 zakim, next topic 18:09:11 I don't understand 'next topic', Jacques 18:09:16 zakim, next item 18:09:16 agendum 1 -- -> New Issue Triage https://tinyurl.com/3hkcsnym -- taken up [from agendabot] 18:09:16 I can't comment on that because it doesn't look like a github issue to me. 18:09:33 iank_ has joined #aria 18:10:31 zakim, next item 18:10:31 agendum 2 -- -> New PR Triage https://github.com/search?q=is%3Aopen+is%3Apr+created:%3E=2026-02-12+repo:w3c/aria&type=Issues -- taken up [from agendabot] 18:10:31 I can't comment on that because it doesn't look like a github issue to me. 18:12:29 Stefan has joined #aria 18:12:40 present+ 18:14:29 present+ 18:18:07 zakim, close item 18:18:07 I don't understand 'close item', Jacques 18:18:13 zakim, close this item 18:18:13 agendum 2 closed 18:18:14 I see 4 items remaining on the agenda; the next one is 18:18:14 3. -> WPT Open PRs https://bit.ly/wpt_a11y [from agendabot] 18:18:15 zakim, next item 18:18:15 agendum 3 -- -> WPT Open PRs https://bit.ly/wpt_a11y -- taken up [from agendabot] 18:18:15 I can't comment on that because it doesn't look like a github issue to me. 18:18:35 zakim, close this item 18:18:35 agendum 3 closed 18:18:36 I see 3 items remaining on the agenda; the next one is 18:18:36 4. -> [css-fonts-5] Text Fitting: Default scaling limit #12886 https://github.com/w3c/csswg-drafts/issues/12886 [from agendabot] 18:18:37 zakim, next item 18:18:37 agendum 4 -- -> [css-fonts-5] Text Fitting: Default scaling limit #12886 https://github.com/w3c/csswg-drafts/issues/12886 -- taken up [from agendabot] 18:18:37 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. 18:20:41 scott has joined #aria 18:20:50 present+ 18:20:59 pkra has joined #aria 18:21:09 @Ian: CSS working group is working on a highly requested feature. Given a short paragraph of text, say a heading, and a font size, say 20px, what this does is apply a transform to each individual line such that there is no free space at the end of the container. 2 modes, per line where each line has the same font size, and a paragraph mode that 18:21:09 transforms all lines by the same amount. 18:22:36 Cynthia: Can we see a demo? 18:22:50 s/transforms/… transforms/ 18:23:06 Ian: 18:24:03 Ian: In this example, the second line is stretched to fill the container, and then the first line is stretched to the same amount. 18:24:29 Ian: the next question is, what happens when there is page zoom applied? 18:25:48 Ian: The default implementation would mean that you are only growing the "base" font size, so if you have a 200% browser zoom, we would change the new "base" to double, but that may not actually change the font size. 18:26:15 Ian: on small devices where the container is based on viewport size, a zoom may not actually end up changing the font size. 18:27:38 pkra has joined #aria 18:27:38 Ian: one option considered is that we layout the whole page without browser zoom, record how big the font gets, say 100px and then layout the entire page again and use that first size as the minimum 18:28:03 Ian: this results in a need to render twice, quite expensive, especially on large sites on low-end devices 18:28:37 Siri: Also what happens when text spacing is applied? 18:28:42 cyns has joined #aria 18:28:47 present+ 18:28:51 Ian: That gets boosted as well, but I need to double check that. 18:29:24 present+ 18:29:31 Ian: we change the font size once to get it as close as possible, then apply a transform. 18:29:39 q+ 18:30:15 spectranaut_: In the first situation where we only grow the base font size and the text wraps, is there a transform applied? 18:31:22 Ian: when a line wraps, it will then need to grow to fit the container, meaning that a single line could have smaller text than when it wraps. 18:31:28 ack scott 18:31:59 q+ 18:32:10 Ian: generally we consider text clipping to be worse than small text. 18:32:56 scott: with this feature, when zoom is applied, there is a chance that the text size never actually changes. 18:33:05 Ian: the base size will increase 18:33:16 scott: But to the user, the text won't change though 18:33:35 Ian: the boosted size is often going to be substantially larger than the base size 18:34:50 q- 18:35:00 scott: that is the tricky part, large text, people understand that since its already large, not growing might seem OK. 18:35:33 I was just going to say this should be presented at AGWG. Contact the chairs to ask about agendas: group-ag-chairs@w3.org 18:35:36 q+ 18:35:43 scott: we need to bring this up to WCAG? to get a better idea of where this falls down and what text requirements are. 18:35:50 q+ 18:36:18 scott: not growing could be considered a failure, though in large text scenarios, people might be OK with that. 18:37:16 Ian: its always going to be true that it will render at double the base size, but since its boosted, it may not grow. 18:37:42 q? 18:39:17 Ian: we also apply the minimum font size, in the borwser you can specifiy a minimum font size, default is 9 or 10 by default. The default size is 16. 18:39:34 ack jamesn 18:39:38 ack spectranaut_ 18:40:00 jamesn: I don't think there is any more ARIA can do here, this needs to go to the WCAG wg to see if there is a way of using this that doesn't violate WCAG 18:41:49 jamesn: this happens today with viewports. 18:42:33 scott: I both agree with james and see the need for this. WCAG2 is already here, but WCAG3 is in development, it would be good to bring this there. 18:42:45 zakim, next item 18:42:45 agendum 5 -- -> CSS/ARIA Issue Triage: [css-display-4] reading-flow/reading-order vs text selection #12014 https://github.com/w3c/csswg-drafts/issues/12014 -- taken up [from 18:42:48 ... agendabot] 18:45:08 spectranaut_: is this something that we should talk about more here or have coordination with the CSS working group? 18:46:43 spectranaut_: asking james craig to weigh in. 18:47:36 s/james craig/… jamie teh/ 18:48:37 zakim, next item 18:48:37 agendum 6 -- -> CSS/ARIA Issue Triage: Add an ::interest-button pseudo element to interest invokers #12437 https://github.com/w3c/csswg-drafts/issues/12437 -- taken up [from 18:48:40 ... agendabot] 18:49:28 spectranaut_: The goal of this is to find a solution for touchscreen users and provide and alternative solution for interest invokers 18:50:43 scott: Essentially the interest button psuedo element is being proposed here for when a button is being marked ... so it appears on hover or focus, there is no way for a touch screen user to see. 18:51:10 scott: so this would make a button for touch screen devices, so someone would know they could touch an item and have a popup appear. 18:51:39 scott: we don't need this for mouse/keyboard devices, more important for small touchscreens. 18:52:39 spectranaut_: Maybe we need someone from the css side to come here. 18:52:53 jamesn: Lets do a deep dive rather than in this meeting 18:53:10 q+ 18:53:24 ack giacomo-petri 18:53:48 giacomo-petri: Last week we discussed aria-busy, if we set busy to an element that is improperly using aria attributes 18:55:21 giacomo-petri: say a div with the role list item, is it fine for nested children to have malformed aria content inside? 18:55:43 giacomo-petri: is it an authoring violation or not from an aria point of view? 18:57:01 zakim, close this item 18:57:01 agendum 6 closed 18:57:02 I see nothing remaining on the agenda 18:57:34 scott: we need to do something about the aria-busy problem, will discuss next week. 18:57:54 zakim, end meeting 18:57:54 As of this point the attendees have been giacomo-petri, pkra, Adam_Page, filippo-zorzi, Daniel, Francis_Storr, Stefan, dgrogan, scott, cyns, Siri 18:57:56 RRSAgent, please draft minutes v2 18:57:57 I have made the request to generate https://www.w3.org/2026/02/19-aria-minutes.html Zakim 18:58:04 I am happy to have been of service, Jacques; please remember to excuse RRSAgent. Goodbye 18:58:04 Zakim has left #aria 22:30:47 Adam_Page has joined #aria