Meeting minutes
Updates: publication plans, announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
JB: Hi Janina
JB: Have you seen Shawns response to agendum 2?
JS: Back to back meeting since 9am
JB: Are there any changes to Updates: publication plans, announcements
JS: Awaiting CFC - we are going to do a few more edits
JS: As a note onSynchronized a11yREquirements
JS: It applies to so many groups
JB: you think it is crisp enough
JS: We will add a few edits to heading etc
JB: WAs Shawn able to help
JS: Yes
JB: I think she keeps a complete archive on findig all of the previous examples
JS: We will need a good BLOG posting in additional to announcements
JB: Tzviya, Do you have a collection of your blogs?
JB: please put in a link or an email back to this list
Checking: New work under development? Cross-WAI review requests?
JB: Updates New work under development?
tzviya: ePub went to CR. Did it make it to Shawn?
JB: Shawn has been slammed with work
JB: She might have missed something.
tzviya: I have to check with WEndy
GK: I know it is out
JB: I see a thing from Wendy
<Judy> https://
JB: I am going to drop in...
JB: I am checking the link in the previous agenda item
Tzviya: I think Wendy adding something on ePub in what WAI is up to
GK: Isee a webinar on TechForum
<Judy> [JB: Thinks that the EPUB 3.3 needs follow-up through regular WAI messaging channels]
Tzviya: Jusy I will follow up
JB: Is there a way to get WEndy and Shawn connected?
Tzviya: I thought they were already connected
<janina> https://
JS: APA is poking into some corners, such as...
JS: Web Performance WG. Look at what the user actually got, not just what they are sending? How robust is this?
JS: Is that too heavy weight?
JB: There is a very large point is sustainability. Refresh burden, a cpst that some orgs have begun to quantify
JB: In April w3C I lead some things on sustainability, TrustWorthy canadian
JB: WE might get synergy there
JB: Can we brainstorm on this?
Performacne and Delivery aspect as RTF is working on that
JS: We expect i18n by TPAC
JB: What they have is looking at a screen, and has nothing to do with aural UIs
JS: We have exceeded what SMIL can give us
JB: Thanks
Recommended materials from TPAC sessions on working with COGA (note re-framing/generalizing topic)
JB: at last call an agenda request from Rain for COGATF
JB: It looked like it was one WG, it might be a big topic
JB: Rain has kindly added some stuff that was pre-recorded. For todays- call, please tell us Rain about what this is
Rain: n the emmail thread following this adgenda - there are two documents
Rain: We have this working doc
<Rain> Working document for inclusive working groups: https://
Rain: COGA started in a messy google doc, and transformed it into, started as a clloab ofTF members
Rain: we have alot of unique blockers to collab. A lot of the tools dont wrk with the members of our group. We need options
Rain: What are the barriars?
<Rain> TPAC 2021 recording of How to work with COGA: https://
<Rain> Slide deck: https://
Rain: The google doc translated into the other docs - which is what we did for TPAC - that turned into a recording 2021 -how to work with COGA. Slide deck
<Rain> Meeting minutes: https://
Rain: What we dont have yet but we heard people want to be helpful for WAI is a cheat sheet
Rain: We haven't produced that yet - I woul dneed a huge amount of time
Rain: The other peice to the puzzle - the reason EO was included in the original request - these collabs are two ways
Rain: EO is trying to prioritize and manage - EO is trying to mitigate of what we are asking - COGA drosnt have the resources
Rain: Even when we try our best is to have a clear process and understanding how these interaction will work
RAin: a list of challaneges
Rain: I am worried EO is frustrated
Rain: We recognize that
Rain: WE want to make sure tht this is smooth - we are not handling it right. How can we better support EO and other groups?
Rain: How can we support structures, in my month I hope to be able to set that foundation
Rain: This is what is Hard for COGA. Ans how can it go both ways?
JB: I am hearing a clear intent in in reciprocity. I think that great
JB: Off the links is most of it is redundancies?
JB: Any thoughts?
RAin: Enjoys content through audio then the recordings is best - if you are going to do just one- the slides are closest to the cheat sheet.
Rain: Recording is about 40 minutes
Judy: any questions right now?
Ryladog: good idea and understand the difficulties
GeorgeK: improving communications is essential
GeorgeK: are there technologies getting in the way?
Rain: at a high level - github itself is challenging - not from a technical standpoint. Putting in a comment or editing is fine
Rain: email comms in general - everything is deeply threaded and very hard to find contextual threads leading to cognitive overload
Rain: when notifications enabled some of us are too overwhelmed by email. Can't get to what are meant to be reaching
GeorgeK: I think we all struggle with that. Present in my life too. Can symaphize with difficulty this presents
janina: I like that emphasis on the struggle with threading. pretty common for many people with or withour disabilities
janina: kind of amazed that mail user agents haven't looked into this. reminds me of a user agent where it said don't have those deep deep quotes
janina: a python script
janina: some things that ADAPT could give us ways to build simplification
janina: want to make sure RQTF is looking at this too
janina: not just google docs and github which people find difficult for different reasons
tzviya: everyone agreeing that threading can be an issue. wondering whether documenting best practices would be useful.
tzviya: find replying at bottom is almost impossible
<Zakim> tzviya, you wanted to ask about offering best practices
Judy: want to talk about repricocity - we have so many microcultures even in WAI - and every group and even TF has a different expectation
GeorgeK: hear comments about threading etc. just because the software has the capability. Learning how to use things can be difficult. Folks helped me get going with github. Think there needs to be ways to provide help and training.
GeorgeK: github and email threading are 2 things that could be helpful for everybody
Judy: Tooling and interpersonal part are 2 buckets
Rain: Learning disabilities are a disability. I know how to use threading. Have 3000 unread emails.
Rain: I shut down and cannot function. Don't realize how huge this is as a struggle
<Ryladog> You are a highly competent individual
Rain: some folks written communications are not possible
<GeorgeK> Thank you for that.