Meeting minutes
Judy: Next meeting will be February 9
Updates: publication plans, announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
matthew: we're expecting this to be ready for pub in Feb
… just checking for any blocking issues
… want timed text coordination
… probably want w3c statement
jb: is apa prepared to do a w3c statement carefully
jb: michael can you say more about preparing for a w3c statement
Judy: This will be one of the first Statements we'll be publishing.
tzviya: It will be the first
MichaelC: There's no Statement track, so we'll publish as a Note first and then ask for that to become a Statement.
<tzviya> https://
MichaelC: Process dictates we'll prepare as a Note and ask to move to Statement.
Checking: New work under development? And status on cross-WAI review requests.
Sharron: Got good feedback on How people with disabilities use the web, including from COGA. The process of cross-WAI reviews has been helpful.
Sharron: We had some resources we wanted to bring along after the last redesign, and have both new and outdated resources now. We are receiving comments via GitHub, but the comments aren't getting feedback. We have outdated tools listed on the site.
Sharron: Were and how do we find the resources we need in order to keep things current?
Sharron: This is a reputational issue. Need a process to cover this.
Judy: Some of the comments have been surfaced to me. Most policy content has been updated, and we need to publish it (expected soon).
Judy: Course lists are part of commitments with partners.
Judy: Open to info from EO about the priorities; checking that we have the resources to address them.
Sharron: It's important that we ensure that advice and resources are up to date.
Judy: We are working on being able to publish updates with the expectation that this will be addressed soon.
Judy: With respect to tutorials, we're working to understand EO's priorities; suggest a more detailed separate discussion.
Judy: Other issues under publications? Feedback from Sharron and all is welcome.
<tzviya> https://
tzviya: Found out about this summit today. Some sessions are being opend up to the public. Need to register in advance.
<Zakim> tzviya, you wanted to mention Accessible Publishing Summit
Carried over: Further discussion on WAI CC meeting frequency, focus, timing
Judy: Several proposals; one was to reduce the frequency, but that didn't seem too popular. Others include focused sessions. Training opportunities for working with d/Deaf colleagues, etc.
Kim_patch: It's helpful to learn about the work and interests of other groups. E.g. recent useful meetings with Low Vision and COGA.
<tzviya> +1 to Kim_patch
<Sharron> +1 to Kim
brent: EO tries to help other groups with outreach, so if there are things EO can do to help other groups with accessibility outreach that would be good to know and pursue.
brent: This meeting has a fairly standard make-up; several people over email can't make it due to other priorities. Have we asked over email for people's priorities?
Judy: We could run a survey, with some suggestions included.
Judy: What are we aiming for in terms of participation from each group?
Judy: Are there particular things (e.g. updates from COGA) that all of WAI would like to know?
brent: Could be helpful to have a section on understanding what other groups are working on, at least in a nutshell.
brent: Would be good to raise awareness and interest, which can be followed up outside of the meeting.
Judy: Would a round robin approach meet this need? Either different groups per call, or round robin on a given call?
brent: Something like a stand-up style meeting, where each group has a minute.
brent: Time monitoring would be needed. Suggest questions be asked outside of the call.
Matthew: I really like this idea, helpful to know what other groups are working on.
stevelee: +1
Kim_patch: +1
Kim_patch: I like the idea of limiiting the time and taking questions separately.
<Sharron> +1
stevelee: questions could be put on the agenda, or done separately, but agree should not be done as part of the round robin
Judy: There are at least two groups that have a cross-WAI purpose: EO and APA. Maybe in addition to round robin, we rotate and have an "EO corner" where sometimes we talk about what EO is doing, and sometimes what EO can help others with (likewise for APA).
brent: +1
brent: We often find others in the accessibiilty community and raise awareness of WAI with them.
brent: We may also help others such as Low Vision with outreach.
brent: We're looking for someone to lead outreach efforts; savvy with social media; can make an outreach plan.
brent: That plan can include more than just EO.
brent: Important to give a purpose for the round robin when announcing it on the call.
brent: I.e. connecting to further support/engagement for both projects.
Judy: ACK generally. In favour of an updated messaging plan for WAI
tzviya: The timing of this is good for me, but may be difficult for others, e.g. EU and Asia. Worth considering again.
tzviya: +1 to brent but it's important to learn about the work of the rest of the W3C.
tzviya: This is a big opportunity we have here.
<Zakim> tzviya, you wanted to ask about timing and about interaction with rest of W3C
Judy: We've tried to reschedule before; it's challenging but could be tried again.
Judy: The dilemma with what to bring in from other W3C groups is guaging the right threshold for interest. This can even be the case within WAI. However something like a process change that affects all would be suitable (e.g. Statements).
Judy: Are there particular kinds of things that we would all be intersted in hearing from other parts of W3C?
Judy: tzviya: You've got a good view on the whole organization; any thoughts?
tzviya: We should pay attention to HTML, WHATWG, HTML-related specs around W3C (e.g. ARIA); privacy (incumbent on WAI to pay attention, as not much overlap between privacy and accessibility).
Judy: hearing core specs, and key intersections
stevelee: also CSS (fits under core specs). Are security and privacy considered separate?
Judy: WAI is working on the intersections, and will be doing more.
Judy: Thanks for the input!
Judy: Will see what we can adjust in future agendas, and calendar.
Hybrid TPAC planning: What's coming for options and what does your group need
Judy: Updates from other parts of W3C. The pandemic is ongoing and significant. Some people are missing the 'meeting in the hall' type meetings. Virtual TPAC attendance has gone up and is being recieved well, particularly by people who could not have attended a physical event.
Judy: W3C is looking into running a hybrid event. Therefore there needs to be a great deal of coordination regarding accessibility of both physical, virtual, and joining the two, as well as preparations around Covid.
Judy: Looking into joining some existing IRL events with e.g. a small staff, and piping in other people virtually.
Sharron: Keen for the return of in-person events. AccessU coming up in May. Recorded sessions will be available the week before. During the in-person week, there will be live Q&A with the presenters for the pre-recorded talks. We are in the process of planning at the moment.
Sharron: Our hosts have a lot of infrastructure for webcasting.
Judy: TPAC for the past two years has relied heavily on pre-recording, which helps us optimize our real-time interactive time.
MichaelC: I find the pre-recorded sessions run more smoothly.
tzviya: Some people prefer to present in person, and others prefer video. Frankfurt book fair was hybrid. I was not involved, but one of the ways to run this was using very large screens for pepole to present from.
Judy: Equipment budget seems to be very important for successful hybrid events.
tzviya: The AC meeting is/was [scribe: wasn't sure which; apologies] hybrid; with pre-recorded sessions.
Judy: A survey will be coming out soon to get a feel for what people are thinking about in relation to TPAC.
brent: Survey for chairs?
Judy: Current survey draft is for chairs to get a feel from the groups. E.g. what might be the threshold for in-person travel. We need to consider things quite far in advance.