12:39:15 RRSAgent has joined #apa 12:39:19 logging to https://www.w3.org/2026/04/22-apa-irc 12:39:19 RRSAgent, make logs Public 12:39:20 please title this meeting ("meeting: ..."), janina 12:39:30 Meeting: APA Weekly Teleconference 12:39:38 Date: 22 Ap[r 2026 12:39:44 Chair: Matthew 12:39:50 agenda+ Agenda Review & Announcements 12:39:50 agenda+ [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) 12:39:50 agenda+ [Spec review requests](https://github.com/w3c/a11y-request/issues) 12:39:50 agenda+ [Issue tracking](https://github.com/w3c/a11y-tracking/issues) 12:39:51 agenda+ CSS Update (Paul) 12:39:52 agenda+ Other business 12:39:55 agenda+ Be done 12:58:13 /join #rqtf 12:58:19 present+ 12:58:23 agenda? 13:34:32 matatk has joined #apa 13:34:39 agenda? 13:34:46 rrsagent, make minutes 13:34:48 I have made the request to generate https://www.w3.org/2026/04/22-apa-minutes.html matatk 13:53:45 JonCohn has joined #apa 13:56:07 regrets: Jennifer_Strickland, Eric_Hind, Roy_Ruoxi_Ran, Tiffany_Saulter, Gottfried_Zimmerman 13:57:28 present+ 14:00:20 present+ 14:02:32 Fredrik has joined #apa 14:03:04 PaulG has joined #apa 14:03:24 present+ 14:03:54 Neha has joined #apa 14:04:05 present+ 14:04:45 matatk has joined #apa 14:06:02 present+ 14:06:36 scribe: Fredrik 14:06:36 present+ 14:06:39 present+ 14:06:56 zakim, next item 14:06:56 agendum 1 -- Agenda Review & Announcements -- taken up [from janina] 14:07:17 matatk: Nothing particular apart from discussions of old art rock bands. 14:07:30 zakim, close this item 14:07:30 agendum 1 closed 14:07:31 I see 6 items remaining on the agenda; the next one is 14:07:31 2. [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) [from janina] 14:07:34 zakim, next item 14:07:34 agendum 2 -- [TPAC 2026](https://www.w3.org/events/tpac/2026/tpac-2026/) -- taken up [from janina] 14:07:49 janina: Drumpets, trumroll! 14:08:01 stevef has joined #apa 14:08:06 matatk: TPAC 2026! *And yes, the 2027 date and location have been announced as well.) 14:08:10 present+ 14:08:23 matatk: Start thinking about what you will need or might want to do at TPAC. 14:08:28 somebody to love https://en.wikipedia.org/wiki/Somebody_to_Love_(Jefferson_Airplane_song) 14:08:37 matatk: Any and all questions much appreciated and welcome. 14:08:51 matatk: It is very much worh it applying for the Invited Expert Travel Fund. 14:09:09 Dr_Keith has joined #apa 14:09:10 matatk: Unless there isn't one, but that is highly unlikely. 14:09:29 janina: We're Dublin down on Ireland this year. 14:09:29 present+ 14:09:42 janina: Next year Panama City in December due to the rainy season. 14:10:07 matatk: I have many fond memories of Dublin. 14:11:13 matatk: Brilliant stuff coming up, brilliant stuff has gone down before. 14:11:18 q? 14:11:22 matatk: We will keep everyone posted on the IE Travel Fund. 14:11:29 rrsagent, make minutes 14:11:30 I have made the request to generate https://www.w3.org/2026/04/22-apa-minutes.html Fredrik 14:11:39 zakim, next item 14:11:39 agendum 3 -- [Spec review requests](https://github.com/w3c/a11y-request/issues) -- taken up [from janina] 14:11:50 matatk: As ever, we have got lots to get through. 14:12:03 matatk: There are some we need to pay particular attention to. 14:12:11 subtopic: Explainer: Extended Descriptions for Publications and the Web 14:12:11 https://github.com/w3c/publ-a11y-extended-desc/blob/main/README.md 14:12:11 tracking: https://github.com/w3c/a11y-tracking/issues/311 14:13:06 matatk: Reminding people of last week's extended description discussion and the attendant thread and meta thread on that. 14:13:34 subtopic: WebTransport 14:13:34 tracking: https://github.com/w3c/a11y-tracking/issues/310 14:13:52 matatk: We also talked about this last week and I agree with our initial assessment. It is very low level. 14:14:08 matatk: They actually filled out the HTML version of the FAST checklist which is good *woop woop from scribe). 14:14:21 matatk: NOthing for us to do here, I'm convinced. 14:14:29 s/Nothing 14:15:17 matatk: The example was weird though (as noted by Paul which wasn't minuted, again scribe notes). 14:15:49 chiace has joined #apa 14:15:52 matatk: Froman APA perspective we don't have anything to say aobut the spec. The issue of the example is more a personal comment level thingy and I will credit Paul for the discovery of course. 14:16:00 subtopic: Mathematical Markup Language (MathML) Version 4.0 14:16:00 tracking: https://github.com/w3c/a11y-tracking/issues/303 14:16:29 matatk: Neha worked on some examples here and has also commented with others on it. 14:16:56 matatk: There is actually a couple interesting development. 14:17:37 matatk: As for the changes, we aren't concerned. The semantics and the presentational approach are preserved. A11y considerations are substantial. No changes seem negative. The intent attribute seems to semi-semantically explain a structure of an equation. 14:17:50 matatk: In al, there is richer semantics in this than the previous version. 14:17:57 s/all 14:18:43 matatk: One thing that is being worked on is an official acessibility mapping for MathML. People involed include James Nurthern. 14:20:25 q? 14:20:54 subtopic: RDF 1.2 Syntaxes 14:20:54 tracking: https://github.com/w3c/a11y-tracking/issues/309 14:23:05 Fredrik has joined #apa 14:23:10 scribe: Fredrik 14:23:19 rrsagent, make minutes 14:23:20 I have made the request to generate https://www.w3.org/2026/04/22-apa-minutes.html Fredrik 14:23:48 matatk: There are interesting things to note in all the updates to this spec and how they manage it. 14:26:35 matatk: Is it worth adding someone else to this? 14:27:52 matatk: Steve does it on the urging of Fredrik. 14:27:55 subtopic: Accessibility Implementation Guidelines (DVB BlueBook A185) 14:27:55 tracking: https://github.com/w3c/a11y-tracking/issues/266 14:27:56 Fredrik: Thanks Steve! 14:28:06 matatk: This is the DVB thing. 14:28:24 janina: This is the week, this is the week, this is the week... the ICCHP paper is submitted nad now it's go time! 14:28:52 subtopic: CSS Anchor Positioning Level 1 14:28:52 tracking: https://github.com/w3c/a11y-tracking/issues/289 14:29:07 matatk: This is the one where we are still proposign an a11y considerations section. 14:29:37 zakim, next item 14:29:37 agendum 4 -- [Issue tracking](https://github.com/w3c/a11y-tracking/issues) -- taken up [from janina] 14:29:50 subtopic: [css-forms-1] Specify readonly input styles 14:29:50 source: w3c/csswg-drafts#12490 14:29:50 tracking: https://github.com/w3c/a11y-tracking/issues/296 14:29:50 rrsagent, make minutes 14:29:52 I have made the request to generate https://www.w3.org/2026/04/22-apa-minutes.html Fredrik 14:30:36 matatk: Anything we need to do about this right now? 14:31:01 matatk: IF anyone finds themselves surplussing on the bandwidth department, feel free to immerse yourselvves to an appropriate degree. 14:31:08 q+ 14:31:21 ack PaulG 14:32:18 PaulG: This document points out a gap in our collective literature. Someone propbably needs to speak up, maybe APG, to say "this is the test, this is what we need". Basically the consideration, hopefully whoever does that gets feedback from AT users with their experience with read only inputs. 14:32:25 Present+ 14:32:26 ack PaulG 14:32:56 PaulG: Maybe put that in someone's queue to make a note on that? 14:33:20 matatk: From the perspective as an AT vendor, Jon, do you ahve a perspective on read-only form controls that we should consider/ 14:33:30 JonCohn: I haven't seen anything specifically related to that. 14:33:49 matatk: In my experience they seem to cause confusion and maybe not as much as placeholders but they do seem to cause confusion. 14:34:06 matatk: Anyone else with thoughts on read-only input styles? 14:34:25 stevef: I'd like to, but I just don't have time... 14:34:49 matatk: I believe someone mentioned that there was either an idea or now an initiative to deprecate it. 14:34:55 matatk: Does anyone know more about this? 14:35:09 matatk: I will have a look into it because I would like to explore that. 14:35:38 matatk: If I were to prioritise, I would say placeholder is more harmful. NOt to hijack the topic too much, but if anyone is interested at looking at this, let me know. 14:35:48 rrsagent, make minutes 14:35:49 I have made the request to generate https://www.w3.org/2026/04/22-apa-minutes.html Fredrik 14:35:55 subtopic: Other Spec Review: [css-text] `text-fit` property 14:35:55 source: w3ctag/design-reviews#1208 14:35:55 tracking: https://github.com/w3c/a11y-tracking/issues/315 14:37:06 matatk: It seem s to be changing the size of the font so that it fits into containers. Whcih almost certainly will have a11y implications. 14:37:15 matatk: The explainer is quite detailed but not too long. 14:37:36 matatk: I will probably look at it but I would like someone to TAG along. 14:38:05 PaulG: This hasn't come up in CSS but there was quite a long discussion last week about handlign the meta tag they wanted to add for respecting operating system.... 14:38:31 PaulG: In that case, there ws a lot of problems. A lot of author privilege to override user preference. 14:40:22 PaulG: There have to be minmums here that should be respected but even those are targeting variably abled users in different ways. So there would have to be big and broad warning tape aroudn this. You would have to understand how muany issues there are in this if you implement it. 14:43:39 Fredrik: Noting quite interesting discussions here, summarizing with the fact that there is more growth and shrinkage than in your average Alice in Wonderland, also including and referring to pre-call discussions. 14:44:39 For reference, links to the other, meta text-scale proposals: 14:44:41 https://github.com/w3c/a11y-tracking/issues/241 14:44:48 https://github.com/w3c/a11y-tracking/issues/279 14:44:54 https://github.com/w3c/a11y-tracking/issues/300 14:48:11 matatk: This is a potentially really fundamental thing. Once this gets settled one way or the other, this is going to be set in stone. The opportunities and risks are very much worth considering. 14:48:17 https://github.com/w3c/csswg-drafts/issues/13557 I think is the latest 14:48:24 rrsagent, make minutes 14:48:26 I have made the request to generate https://www.w3.org/2026/04/22-apa-minutes.html Fredrik 14:49:37 here is the explainer https://github.com/w3c/csswg-drafts/blob/main/css-env-1/explainers/meta-text-scale.md 14:50:36 Fredrik: There is AI repackaging of websites in accordance with best practices (whatever that i) which may also factor into this discussion. 14:50:41 Thanks Paul, that CSS issue https://github.com/w3c/csswg-drafts/issues/13557 is being tracked in https://github.com/w3c/a11y-tracking/issues/300 linked above (the tracking issue is a good place for APA folk to 'internally' discuss it) 14:51:17 matatk: Our trackign issue 300 ahs been mentioned before. Paul has put a number of comments in there which are rreally interesting. 14:51:41 matatk: The CSS thread is very active of late, have a look at that one too. 14:52:20 matatk: We've smosshed together a couple of related topics there. 14:52:44 PaulG: We have problems with both grow and shrink. 14:54:17 subtopic: [Customizable select] Define UA behavior for interactive content inside