Meeting minutes
Agenda Review & Announcements
Remembering Judy Heumann
matatk: Judy Heumann passed away at the weekend. A memorial service for her, hopefully recorded for posterity, is actually ongoing right now.
matatk: Heumann was a pioneering disability rights advocate who really moved not only the needle but the whole world of disability rights.
<matatk> More on Judy's achievements: https://
Daylight Saving Time
Daylight Savings Time
matatk: The US changes clocks this Sunday. The time of this meeting may change next week and we will have to update the stock agenda then.
matatk: There may be reminderes in the next agenda to let you know of the time changes.
WG and TF meetings next (CSUN) week
matatk: If anyone is going, have a great time. We do plan to meet in terms of APA next week because we don't think that many epople on the call are going.
matatk: Some TFs are not meeting n3ext week: MM and RQTF for instance.
TPAC 2023 - https://www.w3.org/wiki/TPAC/2023
matatk: This is already a thing! It#'ll be in Seville, Spain. We want to know what you want to do - who do you/we need to talk to at TPAC.
matatk: Please in your TF meetings, both there and here, tell us who you need to talk to. Thsi will become a standing agendum as is usujally the case.
matatk: We wil have to provide our summary of whom we want to talk to by the 7th of May at the latest.
janina: A quick addendum: Don't just tell us who you want to talk to but also why you want the call or meeting and what you expect to get ou to fit, the outcomes if you will. Those are really useful things to bring to the table.
Reporting calendar issues - https://github.com/w3c/calendar/issues
matatk: There are sitll some homegrown tools we use and are engouraged to use for good reasons. We know that sometimes there may be AX/UX issues with them.
matatk: In case you ahve been using the calendar tool and having probelms with it, you are encouraged to file issues on their Github repo. The link is in the subtopic.
matatk: This helps us also being able to reference thse thigns and move them up the cahin of command should it be necessary.
janina: An addendum: The calendar tool, yes, but that mostly applies to the TF organizers. However...
Beta new W3C web site (for internal review; not wide sharing) - https://beta.w3.org/
matatk: There is a publicly accessible, beta version of the revised w3.org website. We are really keen for you to have a look at that.
matatk: There is a link at the top of everyone of these pages to provide feedback, linking to the Github repo. Please file issues if you have issues.
matatk: Any a11y changes most appreciated.
janina: Soem people have noted that there seem to be differences whether you're logged in or not. If you do look at the beta, try to check it both ways if you can.
New Charters Review - https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
MiniApps Working Group Charter
<Roy> - charter: https://
Roy: There is one new charter: Mini Apps WG charter.
Roy: Idon't think there is much to comment on here. We have already viewed their documents.
janina: You're a MiniApps expert, Roy, so we've ben relying on you a lot here.
matatk: I agree that there is not much to add here. We#ll work with them as we have done before.
Explicit Review Requests - https://github.com/w3c/a11y-request/issues
Roy: No new review requests.
<Roy> w3c/
Roy: Web of Things Profiles have asked to have their documents reviewed by the 20th of March, I think.
A11y Review Comment Tracker - https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Roy: No new comments.
New on TR - http://www.w3.org/TR/tr-status-drafts.html
Roy: CSS Animation Level 2.
CSS Animations Level 2
<Roy> - spec: https://
<Roy> - tracker: https://
Roy: We reviewed Web Animation last week.
Roy: CSS Animation is logically enough from CSSWG.
Roy: I'm not an expert here.
matatk: There is no a11y considerations section, but there is a privacy and security considerations section.
matatk: Janinaq and I have an action outstaqndign to create a biolerplate a11y section which we might then run by Paul for this.
janina: This one would be a good example. We#d have our stock one but also point to Media Queries 5 to relate to it.
PaulG: I agree it's missign some ovious pointers. Nothing about MQ in here, for instance.
matatk: This is FPWD so not an urgent one, but we want to get it done anyway of course.
CSS Update (Paul) - https://github.com/w3c/css-a11y/issues
<PaulG> w3c/
PaulG: The only thing to bring up is the issue linked here. It ha s a resolution.
PaulG: We can probably close it or change it or however we move on from this kind of thing.
PaulG: I can neither close it nor change its labels.
Roy: I could close it. And I did.
Actions Checkin (Specs) - https://www.w3.org/WAI/APA/track/actions/open
Web of Things
janina: Do we want any cahnge in th text of their charter?
janina: I think I should go ahead and send my response to Michael McCool of the WOT group and say "if it's useful to change yoru language according to our wishes (middlewqare, fault tolerance, and set up as well as the Matter question); does that need to go into the charter?". That's their most urgent idssue at the moment.
janina: RQTF has always felt comfortable raising issues with them, we've always gotten a good hearing there.
matatk: I agree it doesn't needd to go into the charter, since it seems to be out of scope, and we already have a good working relationship with them, as well as a lot ot talk about with them. I don't have any concerns with the charter.
Fredrik: +1
matatk: Thank yous and kudos to Niklas and Gottfried for your great work on this.
<janina> w3c/
matatk: It sounds like we can follow up on this as discussed.
ACTION-2328: Multi-Screen Placement Spec Review - https://lists.w3.org/Archives/Public/public-apa/2023Mar/0006.html
<matatk> Thanks to Mike and Fredrik for your comments thus far.
matatk: We do have time to create an APA comment on this. That might be the right way to go on this.
matatk: Perhaps we can, on list, we can arrive on a suggestion for language could be and then solicit a CFC form the group.
matatk: I was also wondering a bit abotu come content-wise things, one about visual impairments. I also wonder if any of the AURs could be of use here.
matatk: I have a feeling there might be useful use cases across the AURs that we can point to.
matatk: We need to come up with some suggestiosn for the language. This also relates to a stock a11y section thing that Janian and I are working on.
matatk: I haven't yet heard any objectiosn to following sa8id course.
Dangling Spec Review Cleanup - https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
matatk: Nothign to report.
Task Force & Deliverables Updates
Other Business
WCAG to ICT Note
<janina> https://
janina: What happened 10 years ago was that the US Access Board came to wAI and asked if they could tell everyone in ICT to follow WCAG.
janina: How htoroughly could WCAG be applied to ICT?
janina: This was work that fed into the refresh of 508 and the emergence of 301549.
janina: The WCAG to ICT is being updated. If anyone has any particular interest in that, Mary/Jo Mueller is leading that TF in AGWG.
janina: As to how WCAG2 SCs might impact command-line tools, for instance.
janina: Anyone who wants to get involved here should.
janina: The big enhancement in CLI tools is that they have become context sensitive. You can work your way through whatever you are about. Starting with Microsoft's PowerShell, CLI tools have become interactive and context-sensitive. The gh client for GitHub does it and so forth. That's the exciting news if you are in a CL environment.
mike_beganyi: How can I get involved?
matatk: The opportunity should come up through our regular APA work.
janina: It's a publication we wil end up reviewing, but we canstart withthe FPWD.
janina: For those interested in console, CLI, terminal stuff, we may get int touch with the TF specifically on that.
matatk: Thanks to all of you for your excellent work wherever you are and whtaever you do!