Meeting minutes
agenda check
Judy: Any additional announcements? Agenda request COGA and EO coordination.
Judy: Invite people to comment on our agenda choices for today – I welcome any kind of agenda requests. Also good to make sure we are doing coordination between groups.
Judy: Pushing back Coordination request two weeks – any quick questions about
Rain: several thoughts on that – reason why it came here is that we been trying to get a meeting for quite a long time for text conversation. The challenge we have is our group is not the best with email threads and github. We understand where EO is coming from but a group has its own needs in order for communication to be successful.
I think this is important to raise here – full group meeting rather than small group meeting – same challenges with most of groups we work with. So finding a way that the COGA group can engage successfully without it being an undue burden on others is important.
Rain: Second thing – at the end of June I'm going to step down as Cofacilitator of the COGA task force. I think it would be good to iron this out while I am still cofacilitator. I'm happy to help beyond that but my not being a facilitator might make people feel awkward.
Judy: thanks for explaining why you want to have that discussion in this coordination call.
Judy: this might be relevant for other groups as well
Judy: I propose that what we do for today's to say that we will defer this discussion in light of several of the relevant folks from EO not being able to join us for the discussion today. I will follow up with them to have just a bit of discussion on why I think the agenda item is relevant for all of the WAI groups.
Judy: I think we might want to frame the request more broadly So it's not just a request between two groups. This is exactly the thing the coordination group is designed to address.
Judy: anyone else has any comments on this?
Judy: or quick questions
Kim: quick summary that might give us something to think about for next time?
Judy: Rain – minute or two synopsis for now and then maybe sending us reminder link about the TPAC presentations on this topic so we all would be more prepared for next time, with an understanding that this is more generally about interactions with other WAI groups in general, not just one group (EOWG)
Rain: I can do a very high level– At TPAC we did a very high level deck some of the communication challenges and barriers that we experience, Barriers of process, then we presented some ways to get around these – working with COGA
Rain: that was kind of one-directional – what we need. In reality a little more messy – there are times when the needs are different
Rain: So at a very high level finding the right way for the people who are taking leadership of very coordinated efforts, To ensure it goes smoothly
Rain: the way COGA and mobile has interacted has been smooth and might be a good model, but again that gets messy and is not necessarily the model that you can follow by all groups because the mobile task force has been very specific – Others more nuanced expanded or longer-term
Rain: how do we take what we put out one directionally and figure out how to craft in the specific relationships a successful two directional exchange that works for both parties when there may be conflicting needs
Judy: I'm hoping that was helpful for people who haven't heard this line of discussion before.
<Rain> yes, I can hang out
Judy: We can refer to the minutes.
Updates: publication plans, announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
Judy: what you think you'll be publishing next and announcements – link in the agenda item that you can check if you're not certain – any updates that anybody has as they look at that?
Janina: We have cleared our long-standing issue with internationalization
Janina: we are in the process of doing that and I think we are going CR at the end of the month and yes I know we have to work on messaging and we have started on that
Judy: Anyone else have publications coming up in the next three or four weeks?
Janina: if you look out that far I think Media Synchronization accessibility user requirements will move to notes status. We will try to see if the ACA will accept it
Janina: synchronization is first because it's the least controversial, will benefit across other tracks And beyond accessibility
Judy: not the same visibility as a recommendation, but it has to go through the same consensus processes in W3C
Checking: New work under development? Cross-WAI review requests? Pre-GAAD fyi's to share?
Judy: any New Work announcements? Critical global accessibility awareness day?
Janina: we just published for wide review everything we learned about how to hold as assessable meeting as we can. It's Our second wide review draft. We That good comments and incorporated a lot of them I want to make sure we didn't miss anything.
Judy: there is so much going on in hybrid meetings – I know that is something wanted to do as a follow-up
Judy: is there follow-up on the hybrid part of that as well?
Janina: the current document does address that – some feeling is that it should address that more deeply
Judy: Action item to myself – my next meeting is with the hybrid team and I'm going to ask that we share our document. You're trying to figure out how to do hybrid conferences on behalf of W3C's upcoming plans for TPAC in Vancouver
Judy: anything else for work announcements – new work or just heads up?
COGA and EO coordination of how people with cognitive disabilities use the web
Updates, and reminder of 2nd survey about Hybrid TPAC https://www.w3.org/2002/09/wbs/1/LogisticsTPAC2022/
<janina> https://
Judy: this is a reminder at the working group level – every working group cochairs and team contacts should have received – and the taskforces may have received this directly as well. On the chairs list on April 29 you should've received a note about another survey about the TPAC is planned in Vancouver September 2022
<janina> Above URI is Remote Meetings review announcement
Judy: more information in the email, the link is to the survey itself. We are trying to figure out the best we can do to accommodate people who are coming with all kinds of different risks and hopes to see each other again and are worried about being in public again. And were also trying to create a situation that's equitable for people who can only participate remotely.
Judy: so there's a lot of Context in the email and a bunch of questions That will help us try to plan as best we can.
Judy: have people fill out the survey or have questions about it or have you not noticed it yet?
Judy: at a working group level have you made sure that your task force facilitators are aware of the survey? Have task force facilitators seen this directly and are you prepared to respond?
Janina: I believe so
Chuck: I've not been tracking the survey – Another trip conflict
Chuck: we are tracking it I don't have an anticipation of when we're going to answer it
Rain: we know about the survey. The difficulty that we are having I'm imagining is not unique to our group. Very few people are willing to commit one way or the other right now. So were finding it impossible to give Janina and RachelleThe information that they are asking for
Judy: that's her bottom-line assumption that nobody can guarantee the responses because the world is not giving us that option
Judy: W3C is in the position of needing to have an approximation of what people want and what people think they want to do
Judy: that data is still helpful to us. One other thing about the survey – we have started to have more discussions about it in open office hours meetings and what we are finding is when people start to answer they start having Really detailed questions about – I think I want to, can you assure me that everybody else is going to be tested or requiring N95 masks– That kind of info is really helpful for us to hear. We would much rather h[CUT]
Judy: that's another reason I'm asking people to indulge in the uncertainties
Janina: daily testing, some people might need assistance
Judy: yes, and confidence in Testing
Judy: anything else about the survey?
Judy: a quick minute for go rounds
Judy: name and what your WAI relationship is
Valerie: Valerie Young I work at A__ and I just joined the chairs of the aria working group – cochair with James
Steve: Steve Lee
George Kircher: I work for Daisy Consortium in Benetech
Rain: Rain Michaels, part of the cognitive accessibility task force and an interaction designer at Google
James: the other chair of the aria working group and an accessibility engineer at Adobe
Chuck: cochair , Oracle
Janina: cochair of accessible architectures
Kim: facilitator mobile working group journalist turned developer, speech input and mixed input
Updates & q&a on legal entity transition, as needed
Judy: Deferred the agenda item to the next meeting, but Rain gave some background– It's an agenda item that relates to most of WAI groups. We want to get to it pretty quickly so were going to do that in two weeks
Judy: updates and legal entity transition
Judy: Reminder – W3C is going through significant transition – international entity multiple hosts to single legal entity. Agenda item in case anyone has any questions or recent concerns, Because we don't want people to feel like they are in the dark about what is happening.
Judy: I can say discussions are coming along well and their significant progress, coming to a consensus with advisory board. There's plenty left to figure out for the most part discussions are going in a positive direction.
Judy: questions how this relates to a stable foundation for WAI?
Meeting length suggestion
Kim: how long is the transition to legal entityoexpected to take
Judy: We have a timeline we are working against – each of hosts in slightly different situation, might spin out at different times but the majority of the activity a think will be in the coming half-year
Judy: In some team side discussions in surviving life and videoconferences we've noticed that particularly with people who are in back-to-back meetings the entire day – if you are doing that virtually there's no transition – sometimes people are tied up every single minute of the day. Some organizations have started to build in a break. Within an hour if you are scheduling a meeting for an hour for only 50 minutes, ar 55 minutes as a def[CUT]
Judy: W3C was looking at that for team side to start trying to do – build a break at the end of the meeting.
Judy: curious about if people are doing that anyway in organizations
Janina: noting that is going to be a challenge for APA
George: it's a good idea to design your meetings like this
James: I think it's a good idea – realistically you start a meeting at the top of the hour and people drift in for the first five minutes anyway – realistically I fear it's going to take another five minutes
Judy: the suggestion that will be coming up for W3C will be saying suggesting starting at the top of the hour and ending 10 minutes before because of exactly that concern
James: I think it's a great idea but we tried doing that and finishing 50 past the hour and inevitably we ended up dragging it to the hour – people want to talk about things a little bit more and say can you say a little longer and people do because I've got 10 minutes to my next meeting
Judy: I know we've got some groups here that manage every second of their meetings – this is not intended to try to make anything more difficult
Janina: advanced regrets – usually in the hour ahead of this call I have a meeting in a totally different ecosystem that will frequently run over a few minutes – I'm likely to be late here. Sorry in advance
Judy: encourage people to look at the links Rain will share – really excellent plenary