Meeting minutes
Agenda Review & Announcements
Guidance on CR Exit Criteria
janina: going to CR with ADAPT.
MichaelC: I will join the AdaPT call next week to talk about oit.
MichaelC: The MUST is on the process. I don't know exactly what it means for us.
MichaelC: WE might want to say something about user agents with abroader inclusion of plugins and such and what they can do.
MichaelC: Whatever we will test in CR, we will want those statements.
MichaelC: We should talk it through in the TF.
janina: We'll update the WD and put in some MUST statements with respect to user agents.
Lionel_Wolberger: We thought we might have a MAY statement or somesuch, but...
MichaelC: Typically, we only test MUST statements. MAYs are not MUSTs and for good reasons. There are MAYs that should be MUSTs and reasons they got downgraded.
janina: We may or may not. It's workth looking at.
janina: In truth, it's optional to implement this spec. But if you do, it's reasonable to have some MUST requirements in order to guarantee interporerability.
janina: We might all look at the spec until Monday.
Referencing a spread sheet in a FPWD note draft publication
janina: This has to do with an action that RQTF took in in the last hour.
<MichaelC> https://
janina: Short version: we are hopeing to ask your consensus, APA, for permission to publish the Maturity Model draft *a Github link wilbe on the CFC). That document will be accompanied by a Google Sheets spreadsheet. Would it be a problem to refer to a Google Sheet in this document?
MichaelC: We needd to make sure w3c-member has ownership of it so it doesn't disappear later.
janina: This should later be made into HTML formspace tooling. Here's just a quick and dirty way to see it in operation.
janina: We have a recommendation from the group to publish as an Excel instead of a Google Sheet.
Lionel_Wolberger: The MM also relieson macros. The MMTF will have to struggle with it.
Some discussions on the merits of different spreadsheet software.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
CSS Working Group Charter
Roy: One!
<Roy> https://
<Roy> https://
Roy: Besides the horizontal review with us, they want to work on accessible navigation.
<Roy> “work with the Accessible Platform Architectures Working Group to work on accessible navigation which needs to be addressed coherently across multiple modules, address accessibility issues related to the features of individual modules, and develop new CSS modules to address accessibility use cases where appropriate.”
janina: We have a longstanding relationship with them, we wil bbe meeting with them.
Matthew_Atkinson: I'm intrigued with what this navigation work is and I'm looking forward to learning more.
janina: We'll want to discuss that on TPAC. Hierarchical navigation would be an awesome win.
Matthew_Atkinson: I'll add this.
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
[css-color-6] Meta-issue: `color-contrast()` issues
<MichaelC> - issue: https://
<MichaelC> - tracking: https://
MichaelC: CSS is busy. They filed a meta issue on colour contrast.
MichaelC: The issue links to a number of other issues.
MichaelC: We probably only need to acknowledge the issue at the moment.
janina: And ping AGWG that htere is this meta issue. They are deferring at our advice because there has been active development in Silver. And they might want to participate in our conversation with them at TPAC.
[css-color-6] Meta-issue: `color-contrast()` issues
<MichaelC> - issue: https://
<MichaelC> - tracking: https://
MichaelC: The only other issues are related to this issue.
[css-color-6] Behavior of color-contrast() when no level is pecified
<MichaelC> - issue: https://
<MichaelC> - tracking: https://
[css-color-6] Rename color-contrast()?
<MichaelC> - issue: https://
<MichaelC> - tracking: https://
[css-color-6] color-contrast() with automatic continuous lightness adjustment
<MichaelC> - issue: https://
<MichaelC> - tracking: https://
MichaelC: They are getting into it.
janina: They are.
new on TR http://www.w3.org/TR/tr-status-drafts.html
Web Content Accessibility Guidelines (WCAG) 2.2
<MichaelC> - review: https://
<MichaelC> - tracking: https://
MichaelC: There is a wide review request for WCAG 2.2. Plannign to take that into CR as soon as possible.
MichaelC: Does APA want to review it?
janina: 2.2 has more support for more COGA issues than 2.1. It is not the only change, but the major one.
Fazio: Yes, I see it that way to.
Fazio: I got Redundant entry in it, I'm proud to say.
janina: I think we can agree that AG should get to WCAG3 and just get this one out now.
janina: Or at least as soon as possible.
janina: Let's give it a week. The CFC ends on the 11th.
janina: Let's take a look at "sometimes" vs. "increasingly" and see what we can get behind.
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
DAPT Requirements
<MichaelC> - tr: https://
<MichaelC> - tracking: https://
<MichaelC> Need to get review before they start turning it into a spec.
MichaelC: There are a few.
MichaelC: DAPT requirements.
MichaelC: We need to get a review before they start turning it into a spec.
MichaelC: Dubbing and Audio Description Profile of TTML 2.
janina: We should probably add this to our convos with Timed Text.
Geometry Interfaces Module Level 1
<MichaelC> - tr: https://
<MichaelC> - tracking: https://
<MichaelC> Might want an accessibility impact statement.
MichaelC: Geometry Interfaces Level 1.
MichaelC: This was from theree years ago. We said we would write an a11y statement.
MichaelC: It was in CR, but it has been since 2018.
janina: I think this may be let go.
Use Cases and Requirements for Decentralized Identifiers
<MichaelC> - tr: https://
<MichaelC> - tracking: https://
<MichaelC> OBE?
MichaelC: Use Cases and Requirements for Decentralized Identifiers.
MichaelC: May have been overcome by events.
janina: That spec is now a recommendation despite issues from major actors.
janina: They will do a round 2.
janina: We have a wish list and things we think they can help deliver. That includes killing CAPTCHA and perhaps using the credentials that will allow you to avoid passwords entirely to convey your preferred settings for displays and colours and dark modes and so on.
janina: There are other examples of use cases developed in RQTF. There is a wiki of use cases for what ew want out ov Verifiable Credentials.
janina: It's the Reporting API that is on our radar.
janina: This one we#ll close though.
janina: We move on twith them. If some of these are relevant still because they weren#t dealt with, we#ll take that up in the next round.
MichaelC: The number of reviews initiated is lower than the number completed. Maybe we should do a few reassignments?
janina: Maybe start taking them up under dangling specs here as well...?
Task Force & Deliverables Updates
RQTF
janina: It's pretty straightforward.
janina: RATF has provisionally approved, because MMTF is a subgroup of RQTF... RQTF is asking APA to run a CFC on a FPWD on the MM. Hence the spreadsheets conversation earlier.
janina: The CFC is probably coming this afternoon. Running to Friday 13th.
janina: There are two more AURs in development.
janina: One on Natural Language currently on hold.
janina: The other on Collaborative Environments. Literally writing some of those up and trying to be really specific both in terms of wwhere problems exist and how to look at them. It#'s not ready for FPWD yet, but we expect shortly after TPAC, we will porbably be expecting that RQTF wil ask us to do a FPWD.
Spoken Presentation
janina: We know what we need to get done before TPAC. WE are planning to take some of our issues to ARIA, to i18n, to DPUB.
janina: We know what each of us needs to do. We are taking August off and we are all individually responsible for our various action items.
janina: These will be seen shortly in our TPAC planning.
janina: TLDR: SP is on hiatus until September.
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
janina: Maybe we should look for ways to resolve these if we need to. We need to improve this as a group.
TPAC22 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022
Matthew_Atkinson: What we've done is that we have filled 8in a lot of agenda we think we should have on TPA.
Matthew_Atkinson: What we are going to do is actually start responsing to invites from other groups to meetings and also sending out our own invitations to other groups.
Matthew_Atkinson: And of course, this is a wiki. If you notice something that should be there or if you are sitting on resources, please help us by filling in, adding to notes and so on.
janina: +1!
Other Business
Matthew_Atkinson: For wweeks on weeks, I have been saying that I should do my reviews. I have. And posted it to the list. An hour or so before the meeting. But anyway. I finished the review of CSS Color Level 5. I posted the comment and the concerns, particularly from a Front-end Developer wtruggling with color.
Matthew_Atkinson: There is plain text and HTML and I did some poking around about color names and have been playing around with that.
Matthew_Atkinson: I would appreciate your thoughts a lot.
Matthew_Atkinson: There is an option that we could post a comment from APA, smaller in scope, and I'll post my issues personally.
janina: LOet's make this its own agendum next week whether small or big issue from us.
Matthew_Atkinson: Sounds good!
zakim ,open next item
Yes, we are!