Meeting minutes
Agenda Review & Announcements
Fazio: updates on a conference. asking for any contribution or sharing any research and submitting the papers. ICCHP
will share the link with the team to submit the papers once he gets it.
<matatk> https://
matatk: COGA does lots of things in this area.
janina: Eric is setup as an invited expert now.
COGA Research Papers
matatk: we close to call for consensus in COGA issue papers. We talked in TPAC. Lisa and JUlie and COGA team and us have been working on this. IT might go out this week. There are small procedural issues to address and then we are good to go.
matatk: watch out for a call. It will probably will run after the meeting next week.
janina: we will publish it this year.
matatk: COGA would like to publish FWD and get feedback
TPAC 2025 Recap
matatk: I havent finished reporting on this. but there are things that want to mention.
one of the things, the horizontal review.
APA is providing use cases helping people with disabilities and helping COGA
proposed new HTML element 'amount' and great discussion about this.
<Fazio> I think I missed this session :(
there are several use cases that COGA can contribute to
<janina> Related item in Edge Capabilities: https://
Janina and I will get some use cases of COGA and we will be touch with COGA through Lisa, Julie, and Eric. We will use the standard process to raising issues.
Eric can then help coordinating
we talked about how to make guthub process more accessible. there are a few ideas that we can agree to make cooridnation process more accessible. perhaps commandline tool can help us
some people in COGA might find it useful
other option is google sheet
there are more thing from TPAC.
We also talked on improving horizontal review here at APA.
we talked about changing the process
making it faster, better
management is happy to make those changes to make ti simpler
New on TR
tsaulter: TPAC wrapup and issue tracking.
CSS Backgrounds Module Level 4
<Roy_Ruoxi> w3c/
<Roy_Ruoxi> URL: https://
PaulG: havent attended any group meeting and have no idea if it has been discussed recently.
PaulG: just a syntax change and not worth to discussing
Spec review requests
<tsaulter> w3c/
matatk: it was discussed at TPAC
it was more of a limitation of certain AT. if thats the case then they are adopting the right case.
tsaulter: browser is not exposing it in a certain way which is documented in TPAC notes.
matatk: will check those minutes
and will send an email to summarize that. anything concerning will be flagged
matatk: we have a few different specs that are related to each other
rdf12-semantics
<matatk> w3c/
rdf12-n-triples
<matatk> w3c/
rdf12-concepts
<matatk> w3c/
anyone wants to have a look to ensure that we are not missing anything?
it has a deadline e.g. 23rd December. looks like a transition request
janina: its been a while since it was done.
<Eric_hind> I can ask Lisa as well?
matatk: there are three specs. the purpose of review to ensure there is no concern. there is a list of review request. we want to come back to it in next couple of weeks before the 23rd Dec.
Fredrik will get some issues assigned in gitHub
matatk: Lisa is expert but she might be busy
Issue tracking
WG New Spec: scroll-triggered aminations
<matatk> w3c/
<matatk> (this is an addition to the agenda - recently opened)
matatk: this is a tracking issue
we can review and give some feedback if we need to
explainer and specs are linked to design review
<matatk> Explainer: https://
<matatk> Specification: https://
PaulG: this is closely align to give a carousel use case.
they have been doing it with JS long time
animated view where you scroll to see the story
we want to make it Tab but dont call a tab.
it gets into so many trouble and dark spot
I can review
but when you try to put it together with other parts, it seems complicated
matatk: when you see it on high level, this is how it is going to be used which could be concerning in terms of a11y point of view
<Glenda> are we considering the importance of respecting reduce motion?
matatk: the mechanism is there and it should be checked.
<Fazio> huge cognitive implications
<Fazio> the jumping impairs attention focus and cognition
matatk: we are trying to improve the process of Horizontal review. any thought on this will be very much appreciated.
janina: as an organization we need to think of this. this thing is bubbling up and we do not want to stop creativity. all the work that epople want to do but the questions is governance and guiding people appropriately. figuring out where is the landing point for these kind of development.
working groups needs to be mindful of these kind of things
matatk: I am doing some background research about how similar risk and potential solutions
Fazio: talking about a few usecases
matatk: if we add David to the review, could he write some stuff that APA can raise with them.
Fazio: I can find some links
matatk: we need to address it very quickly and if we are able to get some stuff together then we can forward this and talk about our concerns. we have limited window of opportunity