Meeting minutes
<janina> Date: 22 Ap[r 2026
<janina> /join #rqtf
Agenda Review & Announcements
matatk: Nothing particular apart from discussions of old art rock bands.
TPAC 2026
janina: Drumpets, trumroll!
matatk: TPAC 2026! *And yes, the 2027 date and location have been announced as well.)
matatk: Start thinking about what you will need or might want to do at TPAC.
<stevef> somebody to love https://
matatk: Any and all questions much appreciated and welcome.
matatk: It is very much worh it applying for the Invited Expert Travel Fund.
matatk: Unless there isn't one, but that is highly unlikely.
janina: We're Dublin down on Ireland this year.
janina: Next year Panama City in December due to the rainy season.
matatk: I have many fond memories of Dublin.
matatk: Brilliant stuff coming up, brilliant stuff has gone down before.
matatk: We will keep everyone posted on the IE Travel Fund.
Spec review requests
matatk: As ever, we have got lots to get through.
matatk: There are some we need to pay particular attention to.
Explainer: Extended Descriptions for Publications and the Web
<matatk> https://
<matatk> tracking: w3c/
matatk: Reminding people of last week's extended description discussion and the attendant thread and meta thread on that.
WebTransport
<matatk> tracking: w3c/
matatk: We also talked about this last week and I agree with our initial assessment. It is very low level.
matatk: They actually filled out the HTML version of the FAST checklist which is good *woop woop from scribe).
matatk: NOthing for us to do here, I'm convinced.
s/Nothing
matatk: The example was weird though (as noted by Paul which wasn't minuted, again scribe notes).
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.
Mathematical Markup Language (MathML) Version 4.0
<matatk> tracking: w3c/
matatk: Neha worked on some examples here and has also commented with others on it.
matatk: There is actually a couple interesting development.
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.
matatk: In al, there is richer semantics in this than the previous version.
s/all
matatk: One thing that is being worked on is an official acessibility mapping for MathML. People involed include James Nurthern.
RDF 1.2 Syntaxes
<matatk> tracking: w3c/
matatk: There are interesting things to note in all the updates to this spec and how they manage it.
matatk: Is it worth adding someone else to this?
matatk: Steve does it on the urging of Fredrik.
Accessibility Implementation Guidelines (DVB BlueBook A185)
<matatk> tracking: w3c/
Fredrik: Thanks Steve!
matatk: This is the DVB thing.
janina: This is the week, this is the week, this is the week... the ICCHP paper is submitted nad now it's go time!
CSS Anchor Positioning Level 1
<matatk> tracking: w3c/
matatk: This is the one where we are still proposign an a11y considerations section.
Issue tracking
[css-forms-1] Specify readonly input styles
<matatk> source: w3c/csswg-drafts#12490
<matatk> tracking: w3c/
matatk: Anything we need to do about this right now?
matatk: IF anyone finds themselves surplussing on the bandwidth department, feel free to immerse yourselvves to an appropriate degree.
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.
PaulG: Maybe put that in someone's queue to make a note on that?
matatk: From the perspective as an AT vendor, Jon, do you ahve a perspective on read-only form controls that we should consider/
JonCohn: I haven't seen anything specifically related to that.
matatk: In my experience they seem to cause confusion and maybe not as much as placeholders but they do seem to cause confusion.
matatk: Anyone else with thoughts on read-only input styles?
stevef: I'd like to, but I just don't have time...
matatk: I believe someone mentioned that there was either an idea or now an initiative to deprecate it.
matatk: Does anyone know more about this?
matatk: I will have a look into it because I would like to explore that.
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.
Other Spec Review: [css-text] `text-fit` property
<matatk> source: w3ctag/design-reviews#1208
<matatk> tracking: w3c/
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.
matatk: The explainer is quite detailed but not too long.
matatk: I will probably look at it but I would like someone to TAG along.
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....
PaulG: In that case, there ws a lot of problems. A lot of author privilege to override user preference.
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.
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.
<matatk> For reference, links to the other, meta text-scale proposals:
<matatk> w3c/
<matatk> w3c/
<matatk> w3c/
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.
<PaulG> w3c/
<PaulG> here is the explainer https://
Fredrik: There is AI repackaging of websites in accordance with best practices (whatever that i) which may also factor into this discussion.
<matatk> Thanks Paul, that CSS issue w3c/
matatk: Our trackign issue 300 ahs been mentioned before. Paul has put a number of comments in there which are rreally interesting.
matatk: The CSS thread is very active of late, have a look at that one too.
matatk: We've smosshed together a couple of related topics there.
PaulG: We have problems with both grow and shrink.
[Customizable select] Define UA behavior for interactive content inside <option>
<matatk> source: whatwg/html#12328
<matatk> tracking: w3c/
matatk: If you want APA backup on a personal comment, comment in the APA discussion thread and ask for some amplification.
matatk: We'll get back to this next week.
PaulG: There is a lot of activity with HTML and canvas now. I can't get a good handle on the a11y in their demos and that is worrisome. They are moving exceedingly fast.
matatk: I will make sure to put this on the agenda next week.
stevef: I've loked into it a little.
stevef: I will go on looking at it.
mat: We'll put it on the agenda and if there is somethign particularly interesting, I would very mych like your opinion on it.
stevef: I got in contact with someone from Freedom to ask them to have a look at the canvas related stuff form the point of view of screen magnification.
matatk: We'll flag this up wwell ahead of the next meeting so people can look at it as early as possible.
matatk: Thansk everyone for the contributions and the discussion.