Meeting minutes
Group Updates
matatk: we don't have anything new on apg
matatk: matt king would like us to review it
matatk: we are working on highlighting the issues to discuss
matatk: respect to maturity, we have some ideas that are probably good for everyone. we will discuss with maturity faciliators tomorrow, we will have stuff to propose after that
shawn: what are the considerations or draft proposal is
matatk: the issue we want to address is that from the outside it might look like two similar things are being done... we are looking at how to harmonize and present in a unified way
shawn: welcome opportiunity to develop approach together
matatk: we are working to come to agreement on what to propose to you/the team,
matatk: we are not at the point of having a formal proposal, just a proposal for feedback
matatk: we think we understand what your concerns are, but if you wanted to email a list of concerns, we can make sure to use that as the template for tomorrow
kevin: good to know
matatk: one thing I might add -- we have at least some share membership between accessibility maturity model and the equity one, so they have had been talking to each other for a while. sherry is in the equity one
matatk: I don't mean to be drama and suspense, I just haven't run anything by facilitators
shawn: first get w3c out of the title, after that I don't have strong feelings
shawn: any other group updates?
Infoshare
<shawn> Infoshare - Anything else in the accessibility world, W3C world, or other to share with WAI-CC?
<shawn> WAI-CooP
matatk: I'd mention -- the WAI coop symposium was last week, it was really interesting, it stands for "web accessibility initiative communities of practice"
matatk: about research and getting it out to the public
<shawn> https://
matatk: it was very well run, and it taught me quite a bit
shawn: we will do recordings and transcripts and get them out
<shawn> fyi, here is report and recording from the previous one https://
shawn: what did you learn matatk ?
matatk: I learned about the research that Yeliz Yesilada is doing on sampling for accessibility auditing... I happen to review their paper already, but it would have been new
matatk: there was a discussion around the appropriate time of use for machine learning/appropriate scope
matatk: I think it wasn't controversial, stuck to things we know, very interesting
matatk: the mobile best practices one was cool
matatk: it was really all great
kevin: the colleague of Jan was doing the mobile stuff, get moving on the mobile task force
kevin: making best practices is something they are interested in
Meetings in Nov & Dec, then in 2024 https://www.w3.org/WAI/cc/wiki/Main_Page#Telecons
shawn: lets not meet next week
shawn: any other overall thoughts on december? 4th, 11th, 18th?
<matatk> I can make all of those.
I can make decemeber and january meetings
shawn: no meeting on 25 dec and 1 jan, the rest of dec we will meet
Managing issues and public comments
shawn: mary-jo had shared guidance on managing issues and public comments
shawn: does anyone else have tips or tricks to share? the EO needs to make a better system for managing all the comments on their many resources
jamesn: we have had good luck triaging issues at the beginning of the meeting, it gets the first step, first comments -- we assign people and put milestones
jamesn: we try to close them quickly if we think that is possible
shawn: you assign and milestone in github so it's public?
jamesn: yes everything is in github in the public
shawn: so the commenter gets feedback right away, they know it gets seen
jamesn: and we link the minutes if there is a discussion
shawn: with my comm hat on, giving people feedback that we are working on things is really great, and some groups in the past (like my own groups) have had trouble doing that
jamesn: goal is to make clear someone has at least read it
shawn: how many comments come through github?
jamesn: everything comes through github
<shawn> Mary Jo https://
jamesn: if something came in a different way, I would file an issue
matatk: this is really interesting, because we struggle to keep up with comments. I agree with giving people feedback early on even if they have to wait a bit after that. just quickly to say, I am working on a tool to help make the process of tracking horizontal review requests and actions easier for chairs, not ready for production, it works for APA and could be tweaked for other groups
matatk: I'll email about it
shawn: one of EOs issue is that we have many repositories....
shawn: the solutions you come up with will hopefully help with EO
shawn: Any other closing comments?
kevin: just to add, we created a WAI-CC repo, in case we need to track issues as a group, everyone here should be write members for it
<kevin> w3c/
shawn: I'll add that to the wiki page
shawn: Thank you for scribing, Valerie!