Meeting minutes
Agenda Review & Announcements
janina: Standard agenda today. NOthing special from me.
New charters review
janina: WE may have a couple.
Accessibility Guidelines Group Charter
<Roy_Ruoxi> - charter: https://
<Roy_Ruoxi> - issue: w3c/
janina: I don't think that tAPA were asked to take a resolution.
matatk: We had a question whcih I linked to.
matatk: I asked a question at the state of WCAG3 in 2027. They said it would be completed in Q4 2027. Kevin said it would be aworking draft by then.
janina: I expect they will go throuugh CR more than once.
matatk: Well, that's the answer to the question we had.
janina: Any questions?
janina: No objections heard.
matatk: I will sign off on it.
Math Group Charter
<Roy_Ruoxi> - charter: https://
<Roy_Ruoxi> - issue: w3c/
janina: Any questions here?
janina: I don't have any concenrs here either. NO reaosn for not approving from where I sit.
janina: Any objections tothe Math charter?
Web of Things Working Group rechartering
<Roy_Ruoxi> - charter: https://
<Roy_Ruoxi> - issue: w3c/
Roy_Ruoxi: Signing off [on Math WG charter]
Roy_Ruoxi: Looks like no big changes here.
janina: We have good relations with this g group just s with the MathML group.
Roy_Ruoxi: That's a diff link.
janina: So nothing new really.
janina: Any questions? In that case, without objection, we'll sign off.
Roy_Ruoxi: Certainly.
Accessibility Guidelines Group Charter
<Roy_Ruoxi> - charter: https://
<Roy_Ruoxi> - issue: w3c/
WebAssembly WG rechartering
<Roy_Ruoxi> - charter: https://
<Roy_Ruoxi> - issue: w3c/
Roy_Ruoxi: That's low level stuff going on right here.
janina: We have never had need to comment on their specs other than wondering if we were missing something.
New on TR
Roy_Ruoxi: We#ve got two items here.
CSS Image Animation Module Level 1
<Roy_Ruoxi> - spec: https://
PaulG: There is some discussion on GitHub on this. There is some poking about play/stop and how the interaction and how to programmatically determine whether things are running.
matatk: We definitely want to make a tracking issue for this. I'll make one. It seems like we want to be on top of this along withthe others who already are (crowded top here).
PaulG: I'd happily have a look.
matatk: It looks like it may be addressing some of the thigns we raised int eh gap issues concerning motion. Thi sis just me skimming.
PaulG: It's the autoplay of gifs and so on. Not a centralized control for things. Exposing that and making it something that CSS is aware of means that we are starting to get tot he point where the UA isn't just shoving this in your eyeholes but where you as an author can take some control.
janina: Any further comments?
Verifiable Credentials Data Model v2.1
<Roy_Ruoxi> - spec: https://
<Roy_Ruoxi> - issue: w3c/
Roy_Ruoxi: That's another VC data models thingy. It sounds more related to Data Level things. Also it's just a FPWD. But a Version 2 spec.
janina: Is there a dif here? Hope, and such.
matatk: I would sggest we don't need to od an early review with it. I would go for the CSS and other stuff since we have good relatiosn with VC and their data models.
s/suggest
janina; And they have a11y considerations which are more than half good.
Spec review requests
matatk: We've got quite a few thigns, no guarantees we'll get to all of them.
Explainer: Extended Descriptions for Publications and the Web
<matatk> https://
<matatk> tracking: w3c/
matatk: We had the request for reviewing extended descripiton and publications for the Web.
matatk: Please see last week's excellent minutes for a recap of what this is.
PaulG: aria?describedby isn't even mentioned here. Why? They are using aria?details as state of the art but it isn't well supported. I don't understand the problem the way they are framign it.
matatk: Paul has very eloquently deescribed this on the tracking thread and here.
matatk: I will pass it on.
janina: I think it may be a question of clarity here. The problem is that you might want to have some text to point to using aria_describedby... you need something there already to associate to.
PaulG: I would say there is probably an RDF rel-type for description where they might find what they are looking for. I'm pretty sure image description has a schema.
janina: Nobody wants longdesc but we ned longdesc although it has myriad problems.
PaulG: They are placing a link to the extended description. BUt they don't say what they want AT to do with the information here. What would be the ideal scneario here?
PaulG: I'm almost thiking aria_controls would be appropriate since it links programmatic elements. aria_controls on the extended descriptoipn then ponting to the image.
matatk: We want a clearer descripoin of the use cases they are after, and whether they just want to do things for AT (harrumph!) or for everyone.
WebTransport
<matatk> tracking: w3c/
matatk: This is quite low level I think.
PaulG: Is it talking about streaming content? Because I know there are things happening with streaming HTML.
matatk: It seems very low level, as I said.
MathML 4.0
<matatk> request: w3c/
<matatk> tracking: w3c/
matatk: MathML VErsion 4: Neha added an example to CodePen and a recording of it as well.
matatk: I haven't looked into this yet, though.
matatk: I looked at the a11y tree I received. Last time I looked at it, I didnt receive anything. The plugin I used though added aria_hidden on the whole thing.
matatk: We can always ask for a little extension of time since this is due rather soon.
matatk: In an effort to combine OpenMath and MathML I thoguht that MathML was supported in the rowser. If it is, you wound't need any plugins unless they provided any non-default expploration tools. I got stuck because of the aria_hidden thing.
Neha: I'm in for joint exploration.
janina: You might want to loop in a question to Jason White.
<matatk> Fredrik: I think Blink has at least rudimentary native support for MathML
matatk: I will look at what@s in the spec itself of course, first. Separately I will test it on some other browsers and willlet Neha know what I find. I'll be in touch after this meeting.
matatk: This may or may not be sufficient.
<Neha> sounds good
RDF 1.2 Syntaxes
tracking: w3c/
matatk: RDF 1.2: There are three different syntaxes here that are proposed or have been updated for chagnes to the RDF 1.2 language.
matatk: We are looking at those.
matatk: The big changes with RDF 1.2 not really a11y-related but architectural. There are differences in 12., the xtent of which is under debate right now, which may cause forward compatibility issues for the 1.1 docuemnts parsed by 1.2 parsers and vice versa. There may be different non-error outcomes.
matatk: Soem have suggested there should e a different MIME-type because of the diferences.
matatk: We might be concerned with ti if there were a particular syntax that suits being authored by people with disabilities and if you can losslessly roundtrip here.
Fredrik: I wil look at this tomorrow and pign as needed.
Issue tracking
CSS - Expansion of validity pseudo-classes
tracking: w3c/
matatk: We have had some nudging on a couple of these from our side thus far, but let's go for the ones which are purely relevant here.
matatk: I amcjust going to check if the CSSWG issue is still open.
PaulG: It looks like.. I was acknolwdged a month ago and then not again. I still think there's... They are asking how this isn't solved by standard linking. And it's not.
PaulG: I am watching this here.
PaulG: Steve's comment mainly adds support.
matatk: Keep it open, keep watching.
CSS Forms - Switch input might need a state indicator
matatk: This is about proposing aswitch control in its default rendering. It's really hard to tell the differece between the two states in its default rendering.
matatk: Now it looks a little differen.
matatk: The concerns remain, though. So I'll write the daft commetn anyway.
CSS Forms - Specify readonly input styles
matatk: If its read-only inputs it's just text on the page. If you come from the world of analogue forms there would be a box. There is a big inertia about wanting to match up and be symmetrical. But what is best for the user in the end?
janina: You could actually stop with what's thepoint?
matatk: They have asked "close?".
matatk: That's all for now. Thanks everyone for everything.
matatk: More on this next time.