Meeting minutes
<MichaelC> Publication plans, announcements https://
Publication plans, announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
Judy: for the people who are here, these are the prolific publishers present.
Judy: Any plans or updates for publications?
Judy: Everything accounted for?
MC: Trying to get the transition request sent for Core Accessibility API Mappings
MC: Need to enter CR, then will become a living standard.
<Judy> (Core AAM)
MC: Will try to target publication next week, that may not be realistic. Coming up soon.
Judy: When are the geek week dates?
MC: It would be on "this" side of that. We are working on a WCAG 3 publication. We haven't nailed down what is in and not in.
Chuck: It's pencilled in for January.
MC: We will have taken WCAG 2.2 to proposed rec.
MC: We still need to work out a plan to publish this.
Chuck: Hopeful for a Jan date which is after moritorium.
Chuck: We had a July date.
Judy: This could become an issue when you request charter renewal from AC.
<Judy> WCAG3: Last TR publication 7 December 2021
MC: I'll say we know it's been a while, we keep thinking it's coming soon, but difficulty getting consensus for content. We developed maturity levels to help craft some looser processes for agreeing on draft content.
<Judy> Last Editor's Draft 7 July 2022
Judy: I understand logic from working group concent. Last TR publication was 7 Dec 2021. I'm correct, that is the last time the world would have found world-facing content.
Judy: Sometimes optics matter. That's not the main driving thing.
Chuck: You are right.
Judy: The public facing content should be pretty frequent. The fact that it's more than a year may be challenging.
Judy: Is there any possibility to publish before this year?
MC: Could we publish something on TR? We could publish what we have now, but may have more messaging concerns than the benefit. I do hear you about the concern.
MC: We put in processes in place and I am hopeful that we will have a viable path for more frequent publications. I'm assuming she is considering that as well.
Judy: Great. It would be great that when the chairs next talk about this that you could increase the priority for any possibility of publishing WCAG 3 on TR before - no, by - first week of december.
Judy: We could find a way to help with the messaging. Maybe highlight the changes in processes. And decisions of what's in progress.
Judy: Demonstrate our commitment to business in a public facing way.
Chuck: I am not hopeful that we would be able to get something out rapidly, but MC and I will bring to the chairs.
Judy: Do you want to say more about reservations?
Chuck: There's not a lot of runway.
Judy: I hadn't noticed till recently that TR publication wasn't in this calendar year. I'm sorry I didn't bring to your attention earlier. I was thinking that you were thinking about that too, but I know you have a lot to consider.
Judy: I'm thinking if the most you try to do is publish what was published in July, how much potential grief would that save, or would it cause more.
MC: Consensus in wg is delicate enough that I would trust Rachael's judgement. She has a good handle on the threads. I don't have that nearly as well.
MC: I haven't discussed this with her. I suspect she is trying to make this happen as quickly and reasonably as possible.
Judy: Can you update me when the chairs discuss?
Judy: Whatever messaging we have for the AGWG charter for 3.0 exclusively, we should review the messaging in that. We can't hold up the charter announcement request. You will run out of charter soon. That announcement will buy you an extension.
MC: Will address on Friday.
Judy: It's a tentative. We were going to meet on that day as well. Please chat with Phillipe. I'd like to have an opportunity to be in sync with you.
MC: It's on my priority list to get "ducks" in a row.
Judy: Anything else for AGWG?
Judy: Anything else for APA?
JS: APA, adapt has re-oriented itself. I brought Lisa up to speed. Her reaction was "we will have 12 modules rather than 3".
JS: That is happening hopefully this year. Collaboration tools will hopefully get some content out soon.
JS: We will take Nov and Dec off.
Judy: Remember when you have a break that I need to know to cancel the ASL.
Judy: in this call it doesn't count. I will need email.
JS: I will send email later today.
JS: This is very new. Next major project is with verifiable credentials, digital wallets, we had a good conversation starting on that, we have good next steps.
JS: Has good implications if we can get that to move forward.
Judy: Welcome Brent.
Judy: Can we be clearer that the change of architecture in this is not just because there was a misunderstanding, but rather because this would be better all around. So far I am not certain I'm hearing that.
JS: that's our analysis and intent. We may not be articulating it very well, and it might be getting lost.
JS: There were legitimate complaints, an explanation of why things are put together was legit.
JS: We plan to address and fix issues.
Judy: I wouldn't be hearing months from now that APA was blocked from using preferred architecture.
JS: I don't expect that. Giving the critique we heard, this will only help.
JS: there are some issues, the overall explanation may be a challenge.
JS: We tried to do the overall pic, but that didn't communicate well. We are leaving process concerns with you and work on that which is in our control.
Judy: MC had offered to be a point person. MC understands both sides of the horizontal review, and wants to help with gentle clarifications of process.
Judy: I hope that we improve on communications moving forward, and including experts from APA or ARIA. MC are you comfortable with all of that on your shoulders?
MC: Yes.
JS: Another point, we had a very fruitful meeting. They said to request "Adapt" as the prefix.
Judy: Anything else with APA publications?
Judy: If RQTF is taking a break, please indicate on TF page. Do you need Michael's or someone's help to do that?
JS: Jason is full editor.
Judy: Brent and James, started with asking about any changes in publication plans. Do either of you have anything?
<no from both>
Brent: We are working on final reviews from some specific individuals from hard of hearing community. I'll later give an update on the next round of reviews.
Judy: New docs and heads up for groups. This would be the time to bring that up.
New work? Named what? Cross-WAI review requests?
Judy: Brent, you have the floor.
Brent: Quick background, we've been doing videos on how people with disabilities use the web. Previously we've had reviews of stories of web users video scripts (9), and receiving wonderful feedback.
Brent: Next 9 scripts are ready for review, go with tools and techniques and one more
Brent: Next set is combined, diversabilities and barriers, and tools and techniques. We will put a survey together that opens on the 7th until the 21st.
Brent: I will send an email to this group with survey, to let us know to review. We will also be getting it over to COGA list as well. They want to review that.
Brent: We will also reach out to members of the community. It's a hard deadline we are against. Any questions about the scripts?
Judy: Any commitments for people to review? Sounds like you are recruiting the right reviewers.
Judy: Are you reaching out to individuals, communities? Are we reaching out to the same peoples?
Brent: Mostly individuals, 4 from Shadi, 2 from me. We are looking for "lived experiences". Shawn has sent to a couple of other people.
Brent: Here's link <link provided below>
<Brent> Current Scripts for new EOWG Videos: https://
Brent: This is what we are working on.
Judy: are there any other group working on new things or needs review from other groups?
<no response>
Updated moratoria; what that does and doesn't mean
Judy: Shawn announcing WAI website moratoria, this is different from webrec moratoria. Scope is different from other moratoria.
Judy: I had just mentioned you, and just as it was scribed, you appeared in Zoom with precise timing.
Judy: Shawn had just established wai website moratoria, this is different than web rec moratoria, which is mainly for TR page publications. Because I've been accumulating questions from task forces...
Judy: I wanted to make sure people understood why this is happening, what non-holidays are in play. Another reason is the WAI website is complicated and easily disrupted.
Judy: Individual page stuff is usually ok. Shawn can you give an idea of the scope? I want to make sure chairs and TF facilitators are updated on this.
Shawn: It's basically the things I publish. ACT rules, ARIA APG, doesn't impact anything on wiki, tr, Michael and Roy. They may also have some outages, but I haven't heard from them on that.
Judy: Any q? We have chairs, I was getting from TF, I ask the chairs to pass along to TF leaders.
Shawn: The big thing is WCAG 2.2. What I need to do is schedule some real time off. Could not do that in September. If I have advanced notice, I can accommodate.
Judy: How much advance time is useful for you?
Shawn: Depends. Anything with WCAG needs more attention. If it's just routine stuff, really doesn't matter as much.
Shawn: For PR, we don't need to say much, just need to be careful. For Rec that gets more visibility.
Judy: Earlier in the call, a q came up about WCAG 3 publication. As this won't likely happen until end of year. With charter conversations occuring, I've asked AGWG chairs and Michael to look for possibility of publishing this year.
Judy: MC noted that messaging would be important.
Judy: It's something that the AG chairs need to consider. Nothing to worry about, but could need some attention.
Shawn: I would like to support an extend. The thing we want to point people to is the overview. It's amazing how many people misunderstand the status. Rachael did a pass on the WCAG 3 intro.
Shawn: I suggest we take another pass at the intro.
Shawn: Focus energy on intro, instead of forcing a TR publication.
Judy: The challenge is that there has been more than a year with no publication, and that causes issues with process.
Judy: From a transparency perspective, there's a non-trivial concern.
Judy: Dealing with it by pointing to an overview rather than a frequent publication or an annual publication could cause issues.
Shawn: I think we point heavily to editors draft. We can make sure we point there. I do want to take a pass at strengthening to editors draft.
Judy: That's part of the issue. The group is pointing to the editors draft, that may not be accepted by the AC period, particularly during charter renewal.
Judy: We may not be able to publish an updated version until next year. Increasing on editor's draft doesn't solve process problems. We may need to take conversation offline.
Judy: I appreciate that the chairs and MC will review.
Judy: Happy to have your involvement in messaging. They are running out of runway for charter renewal.
Judy: Anything else on this agenda item?
Judy: For future moratoria, maybe messaging more explicitly on the type of moratoria will reduce confusion.
W3C transitions
Judy: This is a reminder that W3C continues to go through some transitions as it starts from moving from distributed org between 4 hosts to a single legal entity.
Judy: It's been more complicated than expected, but it is happening.
Judy: There is now an appointed board.
Judy: In theory they have now started. They haven't met yet, they are working on logistics.
Judy: Rest of org is getting ready to transition work into their hands.
Judy: That's what's going on. Otherwise it's business as usual.
<no questions offerred>
Judy: I'll keep it here to continually update this audience. I also welcome questions on the side.
Community groups check
Judy: JS, I think we were suppose to check back every so often on whether or not there are community group items that need attention.
Judy: This is "here some things APA is noticing..." where maybe there can be a call for help that APA feels need to pay attention to.
JS: We are aware, my co-chair spent time with open UI, we will file github issue.
JS: We noticed another group take up knowledge domain. We will get back to it. We have been post TPAC, but matrix needs updating.
JS: I think you can expect it soon. Not certain by next meeting, but before Thanksgiving.
Judy: Any q for JS?
Judy: I think that covers us for today.
Judy: any regrets for 2 weeks from now?
Chuck: yes, me
Chuck: Correction, I'm good.
MC: 19th is geek week.
MC: M-enabling is week after.
Judy: Can people keep this on their calendars? timing might be awkward.
+1
Judy: This can be provisional.
Next Meeting
<Judy> [recapturing discussion]
<Judy> JB: Our next meeting date should be October 19th; any regrets?
<Judy> [discussion about which week some events are, including Geek week]
<Judy> JB:I want to ask if people can please hold that meeting available even if during Geek week and a short meeting
<Judy> [no objections]