Meeting minutes
Agenda Review & Announcements
matatk: Registration for AC is on
<Roy_Ruoxi> https://
Meeting of AC board meeting 2026 in China, link is shared above
<Roy_Ruoxi> https://
Roy: Workshop announcement, link shared
janina: It is virtual, can be of interest of lot of people
<Roy_Ruoxi> homepage
matatk: check for registration details
Fredrik: Zero project conference in Vienna https://
Spec review requests
<mpaiva> Present
CSS Anchor Positioning
<matatk> w3c/
<matatk> w3c/
mpaive: has reviewed it, noted down understanding, added a usecase, details - anchoring a tooltip or popover to a control,
increasing zoom to 200–400%,
and triggering the anchored content near the viewport edge, where the visual relationship between the anchor and anchored element becomes difficult or impossible to perceive.
mpaive: you want me to review your guidelines only or something else?
matatk: let me see if they want to cover us somthing
matatk: Accessibility section should be improved and some references should be added
matatk: overall yes it helps for above questions
matatk: Paul had mentioned about pop over examples and Neha has added that
matatk: APA needs to say if spec improves the situation, but yes we have some concerns , as a group we can add accessibiliy section to this spec
matatk: we can start with google docs
matatk: We can mention and inform that we are working on it and will be ready in a couple of weeks
PaulG: Positioning can be controlled with Javascript but can be skipped, do we need last sentence where we mention do not add many things
PaulG, mpaiva - happy to help in editing
<matatk> PaulG: doing the work in JS - you have to manipulate the attributes already and may as well do the positioning there, and have a resize observer to address Marcelo's use case
<matatk> this means they can get through QA faster w/o doing the proper accessibility work
<matatk> ... like that first thing is a giant warning that says you can't rely on visual positioning to express the semantic info
<matatk> aria-details doesn't work yet - should remove
<matatk> if you're building it yourself and not using popover api, you need aria-expanded
<matatk> last sentence - about 'difficult to comprehend' - do we need that? why is this needed. Just make the semantic bindings
<matatk> point to existing docs like APG for the patterns (which will update at some point)
janina: I agree with Paul
<matatk> s/this means they this means they/... this means they/
<Fazio> +1
janina: Operative term is overuse - it should be illustrative what is mean by operative
DVB Implementation Guidelines
<matatk> w3c/
matatk: couple of things will pop up one janina and matatk go through it
matatk: Tiffiany has already added comments but still anyone want to have a look by next week
janina: noone has experty on captioning but they have done a good job in adding details
matatk: for this one we can start with another google docs and then we can share it with them, and start getting feedback to them
janina: I will be better prepared by next week, if anyone want to help in this
janina: It is a big read and not a simple document
janina: instead of going through whole document, go through TOC and pick a topic to go through
Dr_Keith: I am not getting rmeinders from bot, can someone send me reminder for this
Issue tracking
Scroll-triggered animations
<matatk> w3c/
matatk: google docs summarize all the discussion we had on all the threads
matatk: if someone wants to start working, follow the link for issue and google doc
Web platform gap: motion
<matatk> w3c/
matatk: we talked about this last week
matatk: I wanted to log an issue on TACS regarding this gap
matatk: I have added a long comment regarding motion
JenStrickland: Carousels are not applied to animations, but it should be enforced
matatk: I am adding videos and user may need to pause the motin, I have updated the comment
<JenStrickland> I'd like to see a suggestion that being able to stop animations at a user request.
matatk: User agents know the content is animated
<Zakim> janina, you wanted to ask about any TAG process guidance in documenting gaps
<JenStrickland> In CSS animations it is possible to set it to stop after a set number, or anything.
janina: I am proposing to write an issue about viewing and selecting content in lists - the back button doesn't work after you've selected an item
matatk: Please add it as an issue
janina: Years ago we have user agents, but now this is the path from where we can start again, so this is very important
<mike_beganyi> Nice work, Neha!
<JenStrickland> Yes, please, publish it!
<mike_beganyi> +1
<Neha> +1
<Eric_hind> +1
<tsaulter> +1
<marcelo> +1