W3C

– DRAFT –
WAI Coordination Call Teleconference

10 August 2022

Attendees

Present
GeorgeK_, janina, Judy, Lionel_Wolberger, Matthew_Atkinson, shawn
Regrets
Brent, Tzviya
Chair
Judy
Scribe
Matthew_Atkinson

Meeting minutes

Publication plans, announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts

shawn: Just added WCAG 2.2 CR and WAI-Adapt CR. Both dates uncertain.

Judy: I understand December for WCAG 2.2.

Chuck: *agrees*

shawn: Note: WCAG 2.2 CR is the upcoming one.

Chuck: We are going to address some concerns and re-CfC

Judy: Any questions from the team, e.g. around issues that must be addressed before or after CR?

MichaelC: Discussions continuing, no problems at the moment.

Judy: It's a good idea to plan for ideal dates; this can help ensure we make progress.

shawn: Are we still thinking we may get to CR in August, or after TPAC?

<Zakim> shawn, you wanted to say have been watching... for my timing planning, CR likely when?

Chuck: Likely after TPAC.

Judy: This puts PR by the end of the year at risk.

Judy: *will follow up with others regarding timelines* For now we're aiming for the end of the year for 2.2. Does the site need updating?

shawn: It's up to date in all four places.

Chuck: 2.2 is our priority. No other publications.

Judy: Lots of good work on 2.2; will be good to get it out of the door.

janina: From APA: Maturity Model looks like FPWD late August/early September. CfC currently open.

janina: First draft of the messaging went into the wiki in the past hour.

Judy: re CAUR (~collaborative tools accessible user requirements)... sounds like "cower" when spoken. Could shawn help with this? (ACK that *AUR is a series of documents)

shawn: We refer to the *AURs as *AURs internally, but most of the documents don't even have the acronym in the title. Will think on it, but if we stick with not using the acronym in the title that could be a solution.

Judy: APA and RQTF refer to these documents by acronym

janina: Have lined up some help with the vehicular accessibility document.

shawn: We don't have good findability for the *AURs; setting up a page, and looking for feedback on where it should go.

janina: There's a comprehensive list in the RQTF wiki. Hear the question, though.

<Zakim> shawn, you wanted to mention sidenote

New work? Cross-WAI review requests?

janina: (as above)

GeorgeK_: Accessibility summary is likely to move from a MUST to a SHOULD. The objection was that millions of titles would need to have a human-readable summary created.
… It will be a SHOULD, for use if the publisher has anything additional they wish to add to the existing metadata. E.g. "We have added extended descriptions to the content"

Judy: This sounds like a very significant change that may reduce concerns from any large existing repositories.

GeorgeK_: This will reduce the amount of work needed to meet the European accessibility act. The act requires that information be exposed. We are advocating translating the metadata into human-readable phrases. We have existing maps already (and more to come).

GeorgeK_: Essentially, every retailer is going to have to grab the metadata and convert it to a presentation in their catalogs.

Judy: Is this something that you're relatively confident you'll be reaching consensus on, and something you'd like to be messaging publicly?

GeorgeK_: I see messaging going out about fixed layout; there's a lot more that can be expressed there. I contacted EPUB chairs about it.

Judy: Sounds like this subject is a little premature, but we could be looking at messaging for the future.

GeorgeK_: There's a lot more we can do on messaging.

Judy: If shawn's helping, she'll need clear points as to where to start.

GeorgeK_: The WG hasn't come to consensus on this change yet. Looks likely, from voting so far.

Judy: Could someone update us on the next WAICC?

GeorgeK_: I can't. Tzviya may be able to if she's here.

TPAC questions, travel reminders, joint meeting status/issues

Judy: Want to check that groups that need joint meetings are getting them. Starting with APA, which has I think the most challenging joint meeting planning.

janina: We've still got more work to do, but going well so far. We should have sent all initial requests in the next day or so. We think we're going to get most of the meetings we want to have.

janina: We may be joining more meetings on days that APA is not scheduled, but we should be fine with this.

+1

janina: We have 11 meetings [actually 12 now --Matthew]

Judy: We've had more people register for in-person than we expected; good news.

Lionel_Wolberger: Is there possiblity of more rooms becoming available at the conference rate?

Judy: My latest understanding is there are some rooms available at nearby hotels, but W3C has been unable to negotiate a block rate due to oversubscription of events at this time, and uncertainty on numbers. (I could be wrong.)

Systemetizing SOTD publication sections to maximize usability for commenters and for comment reviewers

Judy: The boilerplate section can in some circumstances even be misleading about the status of the document.

janina: Some of us have been discussing this. Rachael has a Google Doc (I've not read). We're getting to some consensus that we can do something meaningful.
… We can tease out what the needs are at both ends in order to support people who use different tools.
… We can describe the outcomes that are desirable, if we get something we can't work with, we can negotiate with the parties involved.
… Had fruitful conversations with Lisa regarding how things can be delivered to be clear.

Judy: this is good, but for the next agendum. Unless they're the same.

Here's an example of a horizontal review dashboard that APA uses. I showed this to COGA and there was some interest in it - might this be of help? https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review

Matthew_Atkinson: I got the impression it would be helpful. We just agreed to use a COGA label for issues; could we make a trial of a dashboard like this?

MichaelC: Phillipe runs this tool. It may be difficult to do, becuse this is specific to horizontals, and COGA is under APA. However, we could maybe fork the tool and use a version for COGA. I don't know how easy that would be.

Judy: Would you be able to carry this dicussion forward with Phillipe?

MichaelC: If the APA chairs can discuss it further, I can take it to Phillipe.

janina: We have some questions to address.

Judy: Complexity may change if this is to be used for tracking issues from other groups.

Judy: Sounds like APA chairs will discuss further and seek comments from COGA.

janina: Happy to continue the discussion.

+1

Judy: Important to bear in mind that COGA needs to be able to intersect smoothly with all the WAI groups.

<shawn> +1 to EOWG to weigh in before FPWD, thanks, Janina!

janina: E.g. RQTF has just specifically invited COGA to review the CAUR.

Judy: Common ground between COGA and DPUB?

GeorgeK_: With the personalization aspect in particular, yes.

Judy: I sense there may be many other areas, and maybe this system would help evolve those?

GeorgeK_: Yes. Though we don't address modification of language in the specs.

Judy: Do you give voicing options for different words? Plain language? Other accomodations?

GeorgeK_: We're very interested in the Pronunciation work when it's agreed upon, and it may be longer before it's agreed upon.

janina: I think it's gonig to come in pieces.

GeorgeK_: If it comes in the form of specific parts that can be implemented, great. If it's a waterfall that takes a long time to come, that may be challenging.

Judy: A broadly available label is therefore better.

janina: *agrees* [as do others --Matthew]

More public info on legal entity transition, any questions?

Judy: It's progressing. It's complex to turn several international entities into one. Some things may be staggered.

Lionel_Wolberger: Best wishes for the transition. We have an accounting problem and have not been able to get support with it.

Judy: Please loop me in and I will check where it's going and will try to get a response.

GeorgeK_: Are the people who're putting their names forward for the board publicly declared?

Judy: I think it's intended to be. I haven't been watching the entire process.

Judy: Suggest checking with Coralie. Will try to find out.

GeorgeK_: Does the AB see it? I think the composition of the Board is going to be strategically critical.

Judy: There have been extensive discussions about the composition of the Board.

Judy: I'll look into this question for you.

<Chuck> hard stop for me at top of hour. Could use earlier departure.

<shawn> [ to answer George: Nominations and statements for the election for the Board of Directors of W3C, Incorporated https://www.w3.org/2022/08/bod-nominations.html ]

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).

Diagnostics

Succeeded: s/formulate a request/can discuss it further/

Maybe present: Chuck, MichaelC