11:10:18 RRSAgent has joined #apa 11:10:23 logging to https://www.w3.org/2025/03/12-apa-irc 11:10:23 RRSAgent, make logs Public 11:10:24 please title this meeting ("meeting: ..."), janina 11:10:31 Meeting: APA Weekly Teleconference 11:10:37 Date: 12 Mar 2025 11:10:41 Chair: Janina 11:11:03 agenda+ Agenda Review & Announcements 11:11:03 agenda+ [Spec review requests](https://github.com/w3c/a11y-request/issues) 11:11:03 agenda+ [Comment review requests](https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review) 11:11:07 agenda+ [CSS Update (Paul)](https://github.com/w3c/css-a11y/issues) 11:11:09 agenda+ Actions check-in 11:11:12 agenda+ Other business 11:11:14 agenda+ Be done 12:59:01 /me https://rednote.net/scuba250306.mov 13:27:33 matatk has joined #apa 13:27:40 agenda? 13:27:49 zakim, clear the agenda 13:27:49 agenda cleared 13:27:52 zakim, start meeting 13:27:52 RRSAgent, make logs Public 13:27:54 please title this meeting ("meeting: ..."), matatk 13:28:02 meeting: APA Weekly Teleconference 13:28:13 rrsagent, make minutes 13:28:14 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 13:28:40 regrets+ Fredrik Demelza 13:28:41 rrsagent, make minutes 13:28:43 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 13:30:06 agenda+ Agenda Review & Announcements 13:30:06 agenda+ CSS inert review - please check out and review the details emailed to the list so we can ascertain what questions APA should be asking whilst we're on the call. 13:30:06 agenda+ Spec review requests 13:30:06 agenda+ Comment review requests 13:30:09 agenda+ CSS Update (Paul) 13:30:09 agenda+ Actions check-in 13:30:09 agenda+ Other business 13:30:09 agenda+ Be done 13:30:25 zakim, clear the agenda 13:30:25 agenda cleared 13:31:51 agenda+ Agenda Review & Announcements 13:31:51 agenda+ APA re-chartering update 13:31:51 agenda+ CSS inert review 13:31:51 agenda+ Spec review requests 13:31:52 agenda+ Comment review requests 13:31:52 agenda+ CSS Update (Paul) 13:31:52 agenda+ Actions check-in 13:31:53 agenda+ Other business 13:31:53 agenda+ Be done 13:31:58 agenda? 13:32:23 zakim, clear the agenda 13:32:23 agenda cleared 13:32:24 agenda+ Agenda Review & Announcements 13:32:24 agenda+ APA re-chartering 13:32:24 agenda+ CSS inert review 13:32:24 agenda+ Spec review requests 13:32:25 agenda+ Comment review requests 13:32:25 agenda+ CSS Update (Paul) 13:32:25 agenda+ Actions check-in 13:32:26 agenda+ Other business 13:32:26 agenda+ Be done 13:32:31 agenda? 13:32:39 rrsagent, make minutes 13:32:40 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 13:46:43 rrsagent, make minutes 13:46:44 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 13:46:51 regrets Fredrik 13:46:55 regrets+ Demelza 13:46:57 rrsagent, make minutes 13:46:59 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 13:47:32 regrets- Fredrik Demelza 13:47:33 rrsagent, make minutes 13:47:34 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 13:47:51 regrets+ Fredrik 13:47:52 rrsagent, make minutes 13:47:54 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 13:50:46 agenda? 13:54:03 agenda? 14:01:12 PaulG has joined #apa 14:01:21 present+ 14:02:02 matatk has joined #apa 14:02:13 present+ 14:02:46 Gottfried has joined #apa 14:04:27 present+ 14:04:32 present+ 14:04:38 present+ 14:05:05 scribe: Gottfried 14:05:27 scribe+ 14:05:37 rrsagent, make minutes 14:05:38 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 14:05:44 zakim, next item 14:05:44 agendum 1 -- Agenda Review & Announcements -- taken up [from matatk] 14:05:59 zakim, agenda? 14:05:59 I see 9 items remaining on the agenda: 14:06:00 1. Agenda Review & Announcements [from matatk] 14:06:00 2. APA re-chartering [from matatk] 14:06:00 3. CSS inert review [from matatk] 14:06:00 4. Spec review requests [from matatk] 14:06:01 5. Comment review requests [from matatk] 14:06:01 6. CSS Update (Paul) [from matatk] 14:06:01 7. Actions check-in [from matatk] 14:06:01 8. Other business [from matatk] 14:06:01 9. Be done [from matatk] 14:06:15 JonCohn has joined #apa 14:08:19 Gottfried_ has joined #apa 14:08:58 janina1: Community group on XR captioning working on a working draft 14:09:08 https://lists.w3.org/Archives/Public/public-apa-admin/2025Mar/0000.html 14:09:53 janina1: FPWD on accessibility in AI systems. First on content creation, but other topics will be added. 14:10:58 ... In the editor's draft, there is some more information on which topics may be added and requested for more information. 14:12:10 Chiara: Where can we contribute topics? 14:12:36 present+ 14:12:50 chiace7 has joined #APA 14:13:02 present+ 14:13:09 present+ 14:13:45 janina1: In the doc, there are instructions on contributing either by GitHub or be email. 14:14:05 ... Your are also welcome to join the Research Questions Task Force. 14:14:53 present+ 14:15:08 chiace7: Have students working on master degree, may contribute to the topic. 14:15:33 janina1: We will have to add you by hand to the task force calendar and mailing list. 14:15:44 ... Everybody in AOA 14:16:10 ... in APA is welcome to contribute to all 6 task forces 14:16:27 ... explains status of FPWD 14:16:35 s/AOA/APA/ 14:16:36 zakim, next item 14:16:36 agendum 2 -- APA re-chartering -- taken up [from matatk] 14:17:11 janina1: We hoped to make it in March, but will slip to April 14:17:31 regrets+ Dr_Keith 14:17:35 rrsagent, make minutes 14:17:36 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html matatk 14:18:06 ... Specifications in community groups don't show on our radar. We do this for WG specs. 14:18:26 ... So, for community groups, we will need a review process. 14:19:01 ... Upcoming Advisory Committee meeting might empower APA to do this. 14:19:35 ... Hopefully we will add a brief clause about TAG-identified work from certain community groups. 14:20:14 matatk: Good summary. 14:20:20 topic: New Draft Charters 14:20:48 subtopic: Distributed Tracing Working Group Charter 14:20:48 - issue: https://github.com/w3c/strategy/issues/495 14:20:48 - charter: https://w3c.github.io/charter-drafts/2025/distributed-tracing-wg.html 14:21:57 Roy_Ruoxi: Looks relative low-level, related to protocols. I am good with this charter.. 14:22:04 janina1: Anybody objecting? 14:22:09 (no objection) 14:22:23 zakim, next item 14:22:23 agendum 3 -- CSS inert review -- taken up [from matatk] 14:22:55 Background reading (from agenda announcement): https://lists.w3.org/Archives/Public/public-apa/2025Mar/0004.html 14:22:55 For convenience, links from the background reading, in case you need them on the call... 14:22:55 Explainer for CSS carousel features (including inert): https://github.com/w3c/csswg-drafts/blob/main/css-overflow-5/carousel-explainer.md 14:22:55 TAG design review thread (featuring Alice's comment): https://github.com/w3ctag/design-reviews/issues/1055 14:22:57 Background CSS WG discussion (featuring more details on the concerns): https://github.com/w3c/csswg-drafts/issues/10711 14:22:57 Some questions I think we need to answer... 14:22:57 1. What level of concern do we have? 14:22:58 2. Would restricting inert to the top layer be sufficient? 14:22:58 3. What questions do we have? 14:22:58 Any thoughts? 14:23:43 matatk: Everything is in my email, no need to scribe. 14:24:24 The current proposal for interactivity: inert is not tied to visible elements, which could lead to excessive or unintentional use. Has a mechanism been considered to visually indicate the "inert" state to developers (e.g., via DevTools or a specific pseudo-class like :inert)? If so, how could this mitigate implementation risks? 14:27:57 matatk: Alice had this concern as well. Suggested limiting it to the top layer which are usually styled visually. 14:28:20 Is there a plan to provide clear guidelines on when interactivity: inert should (or should not) be used? For example, in carousel design, how can we ensure that developers do not make entire sections of the page inert, compromising accessibility? 14:28:21 q? 14:28:37 ... We would like for APA to have a consensus on this. 14:29:03 matatk: We do not want to make it super easy to make mistakes. 14:29:25 q? 14:29:56 janina1: This seems to be more of a UI concern? 14:30:33 matatk: It may be a bit more. It does not change presentation, but functionality and focusability of things. 14:30:57 ... This is a new thing in CSS. 14:31:12 janina1: So it could be the stocking horse for other things of this kind? 14:31:51 ... So, at some point WCAG 3.0 will need to talk about it. 14:31:57 matatk: Would come in as technique. 14:33:03 ... With other complex features in CSS, the building blocks have been useful. In the context of carousels, scrolling and inertness are addressed as well. 14:34:00 ... My concern: If people start to make things inert that are not visible... What are the other use cases for this, except carousels? 14:34:41 q+ 14:35:02 janina1: I feel we should move forward provisionally. 14:35:05 ack PaulG 14:35:57 PaulG: I don't like carousels. Focus issues, arrow keying. 14:36:18 q+ 14:36:25 ... You could do this with something else. Designers use them too much, developers do a bad job. 14:36:29 q+ 14:36:32 ack chiace7 14:38:16 chiace7: Could work well in CSS. But could be overused by designers, in particular for offscreen elements. 14:38:40 q? 14:39:04 ack chiace 14:39:53 ... We need guidance on when to use it when not, regarding usability and accessibility. 14:40:05 q? 14:40:06 ack 14:40:08 ack me 14:41:12 matatk: There are many ways to do carousels. Trying to fit all carousels in this scheme will not work. 14:41:31 ... We are concerned about the documentation for developers and the potential for misuse by developers. 14:42:03 ... Interested in use cases which requires a CSS property rather than a simple HTML attribute. 14:42:30 ... Are there other types of carousels other than apg? 14:42:48 q? 14:42:49 PaulG: Larger list is on a different computer - will send it by email. 14:45:36 matatk: Propose to make an APA comment on our mailing list, expressing our concerns. Any objections? 14:45:40 (no objections) 14:46:03 janina1: We need to ask them WHY this is needed in CSS rather than HTML? 14:46:15 ack janina 14:46:35 zakim, next item 14:46:35 agendum 4 -- Spec review requests -- taken up [from matatk] 14:46:51 subtopic: webauthn-3 14:46:51 Review request (public-facing thread): https://github.com/w3c/a11y-request/issues/101 14:46:51 Due: 2025-03-31 14:46:51 Changes in this version: https://www.w3.org/TR/2025/WD-webauthn-3-20250127/#changes-since-l2 14:46:52 Accessibility Considerations section: https://www.w3.org/TR/2025/WD-webauthn-3-20250127/#sctn-accessiblility-considerations 14:46:52 Previous APA review, including Fredrik's comments: 14:47:13 matatk: Review in progress on Web authentication 3. 14:48:08 ... To look at: Accessibility considerations sections, are our previous concerns addressed? 14:48:21 zakim, next item 14:48:21 agendum 5 -- Comment review requests -- taken up [from matatk] 14:48:47 subtopic: Comment String Searching 14:48:47 source: (Proposed APA comment, in draft) 14:48:47 tracking: https://github.com/w3c/a11y-review/issues/222 14:48:47 previous minutes: https://www.w3.org/2025/02/05-apa-minutes.html#eed7 14:49:05 ... This is a FPWD. 14:49:50 ... Paul had a good comment on it. We will progress this comment as soon as possible. 14:50:02 janina1: We can always address coga comments later. 14:50:23 subtopic: Email: Comment: WCAG 3.0 accessibility guidelines: Accessing a "virtual" meeting using a teleconferencing application such as Zoom - receipt of streamed text content 14:50:23 source: w3c/silver#476 14:50:23 tracking: https://github.com/w3c/a11y-review/issues/223 14:51:02 matatk: About difficulty of accessing streaming text in a web conference. 14:51:40 ... Braille reading has a "speed limit" - bandwidth is smaller for somebody who is deaf-blind. 14:51:50 ... We need to find ways to summarize the contents of a meeting. 14:52:17 ... It is now in the WCAG3 repository. 14:52:53 ... There is something that could be added to the user reqs. But not sure we should do this. 14:53:03 https://www.w3.org/TR/ctaur/#social 14:53:07 ... For ITTF to consider... 14:53:54 janina1: Now we can reference it with our RTC comments. 14:54:56 matatk: Is there anything objective to say about this? 14:55:28 janina1: Hard to say. Simple solution: "Accommodate the people you have. Be mindful." 14:55:51 zakim, next item 14:55:51 agendum 6 -- CSS Update (Paul) -- taken up [from matatk] 14:56:03 janina1: Any other business? 14:56:07 (none) 14:56:11 s/ITTF/RQTF/ 14:56:13 Meeting is adjourned 14:56:37 zakim, end meeting 14:56:37 As of this point the attendees have been PaulG, matatk, janina, Roy_Ruoxi, Gottfried, chiace, JonCohn 14:56:39 RRSAgent, please draft minutes 14:56:41 I have made the request to generate https://www.w3.org/2025/03/12-apa-minutes.html Zakim 14:56:47 I am happy to have been of service, matatk; please remember to excuse RRSAgent. Goodbye 14:56:47 Zakim has left #apa 15:01:28 rrsagent, bye 15:01:28 I see no action items