Meeting minutes
Agenda Review & Announcements
Hearing nothing… Zakim, take up next
<janina> http://
For the new folks: http://
Call for consensus is open through midnight tonight.
There are two negatives, that the chairs will review
TPAC 2025
TPAC is just a few weeks away.
Calendar is coming together. Breakouts were to be proposed by yesterday.
60 breakouts proposed, 9 are accessibility related.
<Fredrik> TF breakout disclosure!
<Zakim> matatk, you wanted to talk about breakouts and HR updates
Fredrik - is there a disclosure we need to discuss?
<Fredrik> JenStrickland - no, it was just me piping up in my capacity as FAST fastilitator.
matatk is discussing improvements to the horizontal review process, the FAST checklist, the framework for accessibility. And improvements to where APA sits in the process (currently too late).
matatk The feedback received as we've embraced GitHub is very helpful. We are working with the W3C technical teams to implement the ideas within the process and improve the documentation.
matatk Thank you very much for the helpful feedback.
New on TR
CSS Environment Variables Module Level 1
<Roy_Ruoxi> URL: https://
Roy_Ruoxi There is one document the CSS Environment Variable Module, Level 1.
Roy_Ruoxi It's about CSS variable module… first public working draft from two weeks ago.
PaulG I don't know anything about it directly, but will take a look.
janina Anyone else want to take a look?
Spec review requests
<Roy_Ruoxi> w3c/
Still discussing the new on TR, planning to create a new tracking issue. There is a longitudinal tracking issue that Roy_Ruoxi created.
matatk I think this is a good place for me to mention, the purpose of the different repositories: request, tracking, and longitudinal tracking. The horizontal review page in the wiki explains the purpose. What it doesn't currently add, is where to put things like issues or questions. The documentation will be updated to include this shortly.
matatk if you have questions in the interim, please email group-APA-chairs or the list for the public list.
<Roy_Ruoxi> also a assignees list in project view: https://
matatk to walk through the open issues.
Accessibility Implementation Guidelines (DVB BlueBook A185)
<Roy_Ruoxi> tracked at: w3c/
Roy_Ruoxi Another org called DVB asked for a review about their documented called Accessibility Implementation Guidelines.
matatk This is an unusual thing because it comes from an external org.
matatk janina and I need to do research to understand how this came to us, if there is a liaison agreement between DVB and W3C. It's not a web standard, doesn't entirely relate to web hosted content. You mentioned something important it went to Media and Entertainment Interest Group, Accessibility Guidelines Working Group, and us. We are going to
ask WAI leadership if they are aware of it and include the AGWG chairs.
matatk I'm not yet proposing we ask anyone to look at this yet, but we're not really sure how appropriate it is for this group to review.
janina We have process questions to answer that will scope what we say / don't. Also, there is some history about a year or so ago, about EU regulations in digital broadcasting… want to see if this is related. Meanwhile, it's logged and on our agenda, and we should know more by next week.
<Roy_Ruoxi> Comments from Kevin: Ideally this should not deviate from what is in WCAG 2 and ideally should align with the direction that WCAG 3 is going so that when that is published we don’t end up with conflicting standards in this topic area.
Roy_Ruoxi By the way, we got some feedback from Kevin White.
janina I'm not sure who knows the answers to what they want us to come up with here, etc.
2025-10-31: css-color-adjust-1
<matatk> w3c/
matatk This is a relatively small change.
<matatk> TAG review for reference w3ctag/
PaulG I don't have any detail. I think it was discussed a while ago. It looks kind of complicated, so if anyone else wants to look at it…
matatk It's a candidate recommendation snapshot, which they wish to republish soon, likely to discuss at TPAC. I'll look at it with you, PaulG. I'll make a shared meta issue for us to discuss.
Issue tracking
Scoped Focusgroup
<matatk> Incubation: Scoped Focusgroup
<matatk> w3c/
matatk: we have discussed this before but we did not conclude, it appeared in the list because a11y label was added. But comments are added
matatk: I will go through previous minutes to get what we had discussed
PaulG: I am not sure why orientation is not being covered, ARIA roles,is it too hard ? Is the structure tree and may be it might be difficult to work with it? There are some questions about its completeness.
matatk: I will add these points from PaulG to comments section
janina: what is the status of this particular proposal?
matatk: Why do they behavior as well as role I can think of , but not sure about ARIA role
matatk: link is shared for OpenUI in zoom which is already shared on irc
[css-anchor-position] Enable scroll position change for focused elements within anchored content
<matatk> w3c/
matatk: This will be added in TPAC agenda list. matatk reading description from issue
<matatk> example from OP: https://
matatk: PaulG have you come across this one?
PaulG: It has been a while, trying to recall
matatk: I may need to read into it when not on-the-fly
matatk: We can take a look at offline
Tiffany: I will take a look and I could reproduce the error
Tiffany showed issue by sharing screen
matatk: It is saying it is a bug specs but can it be bug in the browser?
janina: If it is not spec bug it is out of scope
PaulG: If broswers are using similar algorithm I think Fredik is right this is just with Blink
matatk: I wouldn't want to have to use an attribute to get the behavior that ought to be the default (and I'm not sure that we'd ever want the current behavior anyway?)