14:59:07 RRSAgent has joined #apa 14:59:11 logging to https://www.w3.org/2024/01/31-apa-irc 14:59:11 RRSAgent, make logs Public 14:59:12 please title this meeting ("meeting: ..."), matatk 14:59:17 agenda? 14:59:41 PaulG has joined #apa 14:59:45 present+ 14:59:50 Chair: Matthew 14:59:52 present+ 14:59:53 niklasegger has joined #apa 14:59:58 present+ 15:00:01 present+ 15:00:01 meeting: APA Weekly Teleconf 15:00:18 agenda+ Agenda Review & Announcements 15:00:48 kirkwood has joined #APA 15:00:50 agenda+ New Charters Review 15:01:01 agenda+ Explicit Review Requests 15:01:11 agenda+ A11y Review Comment Tracker 15:01:14 Fredrik has joined #apa 15:01:17 present+ 15:01:23 agenda+ New on TR - http://www.w3.org/TR/tr-status-drafts.html 15:01:32 agenda+ CSS Update (Paul) - https://github.com/w3c/css-a11y/issues 15:01:46 agenda+ Actions Checkin (Specs) - https://github.com/w3c/apa/labels/action 15:01:59 agenda+ Dangling Spec Review Cleanup 15:02:10 agenda+ Task Force & Deliverables Updates 15:02:19 agenda+ Other Business 15:02:29 agenda+ Be done 15:02:33 agenda? 15:02:54 present+ 15:03:18 present+ 15:03:22 nehaj has joined #apa 15:03:23 scribe: Fredrik 15:04:31 rrsagent, make minutes 15:04:32 I have made the request to generate https://www.w3.org/2024/01/31-apa-minutes.html matatk 15:04:39 present+ 15:04:41 Nichole has joined #apa 15:04:47 present+ 15:04:52 zakim, next item 15:04:52 agendum 1 -- Agenda Review & Announcements -- taken up [from matatk] 15:05:09 present+ Irfan 15:05:33 Irfan: I sent out an email about CSS Speech - there was recent discussion of it; there is still not widespread support. 15:06:31 mike_beganyi has joined #apa 15:07:04 present+ 15:07:14 matatk: This is more of an announcmemt for us. 15:08:18 Lionel_Wolberger has joined #apa 15:08:20 present+ 15:08:23 matatk: We have been learning abou thte Github bot (GB). When we go through the horizaontal review section, it gets a little chatty when it thinks we are talking about our issues when we are actually talking of issues of others. 15:08:41 matatk: I will shut GB up temporarily when we do horizontal review for this reason. 15:09:24 zakim, open next item 15:09:24 agendum 2 -- New Charters Review -- taken up [from matatk] 15:10:55 gb, off 15:10:55 matatk, OK. 15:11:13 Roy: Nothing new here. 15:11:21 zakim, next item 15:11:21 agendum 3 -- Explicit Review Requests -- taken up [from matatk] 15:11:31 subtopic: DeviceOrientation Event Specification 15:11:31 - issue: https://github.com/w3c/a11y-request/issues/71 15:11:31 - spec: https://www.w3.org/TR/orientation-event/ 15:11:31 - self-review: https://github.com/w3c/deviceorientation/issues/131 15:11:35 Roy: Yes. There is one. 15:12:21 Roy: They have created an a11y request and have done a self review as well, both through comment review and a11y/request. 15:12:33 Roy: It provides new physical orientation DOM events. 15:13:15 Roy: They have marked some a11y issues in their self review. 15:13:54 matatk: The Devices and Sensors WG, weve worked witht them before. They maintain the Compute Pressure API spec and others such as the Device Posture spec. They are receptive to a11y considerations. 15:14:12 q+ 15:14:24 matatk: I'm not hugely familiar with this spec. It's porbably worth thinking about it for a while to see if there may be a11y considerations. 15:14:52 janina: We wanted the ability to lock a particular orientation. For a screen reader user, in particular, you may want to keep things in a certain mode even though you turn your device over. 15:15:45 cognitive considerations as well 15:16:22 zakim, who is here? 15:16:22 Present: PaulG, Fazio, Roy, niklasegger, Fredrik, matatk, janina, nehaj, Nichole, Irfan, mike_beganyi, Lionel_Wolberger 15:16:24 On IRC I see Lionel_Wolberger, mike_beganyi, Nichole, nehaj, Fredrik, niklasegger, PaulG, RRSAgent, Fazio, Zakim, matatk, wendyreid, Roy, janina, M2cshkpcgrp, matrix638, 15:16:24 ... AnthonySpencer, sonicscrewdriver, gonzu_15, SintayewGashaw, imlostlmao, joraboi445, gb, slightlyoff, Rachael, cwilso, tink, ada, jcraig, agendabot 15:16:31 matatk: It does talk about rotation. I've kind of skipped over that. WE have an expecation fo what we will find there. 15:16:51 janina: That is an old comment form us. 15:16:57 matatk: There is device orientation and then there is device motion: accelerometer stuff. 15:17:34 q? 15:17:35 matatk: There's permissions for gyroscope and magnetometer and so on. 15:17:59 q+ 15:18:50 Fredrik: I'll look at it, happily. 15:19:18 niklasegger: I just wanted to add: I had a look at the documetn before the meeting. There is a section for Use Cases and Requirements. They give axamples. 15:19:54 q+ 15:19:57 ack niklasegger 15:20:01 ack PaulG 15:20:03 niklasegger: There are issues such as shaking to clear a web form where I thought of persons with uncontrolled movement. I'll also happily look at it, perhaps in tandem? 15:20:06 Fredrik: Gladly. 15:20:10 niklasegger: Done! 15:20:21 PaulG: Fixed devices would also be a problem here. 15:20:43 PaulG: What they are uilding up to is a bunch of permissions. Tehre will be opting ins and by default these things should be off. I hope that's where they are going with this. 15:21:18 PaulG: How do we fall on fingerprintable permissions in this? Is that somethign we are worreid about because the persons we are talking about can be fringerprinted for disabilities and so on? 15:21:24 matatk: Excellent point and question. 15:21:42 matatk: First off, this group is really hot on things like fingerprinting and stuff like that. If we discuss it with them, I'm sure the discussion will be productive. 15:22:24 Design Principles: https://w3ctag.github.io/design-principles/ 15:22:26 https://www.w3.org/TR/fingerprinting-guidance/ 15:22:31 this? 15:22:37 matatk: There is guidance on issues around privacy and fingerprinting in the Design Principe doc which the TAG maintains.janSecurity and privacy are horizontal review things that every spec should get from W3C itself, so iot isn't just up to us or on us. 15:26:31 matatk: Short discussion on what fingerprinting is. 15:27:01 matatk: As to Paul#s question: I don't think that htere is any specific fingerprinting guidance around a11y. Maybe that is somethign we want to add as a note in the Design Principles. 15:27:10 s/Pincipe/Principle 15:27:32 q? 15:27:56 s/worreid/worried 15:28:02 rrsagent,make minutes 15:28:03 I have made the request to generate https://www.w3.org/2024/01/31-apa-minutes.html Lionel_Wolberger 15:28:41 rrsagent, make minutes 15:29:12 I have made the request to generate https://www.w3.org/2024/01/31-apa-minutes.html Lionel_Wolberger 15:29:17 APA tracking issue for this spec: https://github.com/w3c/a11y-review/issues/182 15:29:19 matatk: When you, Niklas and Fredrik, are looking at this, we need to go thorugh the review process. For reporting your results there is a trackign issue that has been created. You're welcome to put thoughts on teh mailing list as you go as well as putting them in teh Github issue. Whichever works. 15:29:19 s/Principe/Principle 15:29:19 matatk: My plan is to comment on this issue and link back to the minutes so we don't miss them. 15:29:22 s/somethign/something 15:29:27 zakim, next item 15:29:27 I see a speaker queue remaining and respectfully decline to close this agendum, matatk 15:29:30 q? 15:29:31 ack me 15:29:33 zakim, next item 15:29:33 agendum 4 -- A11y Review Comment Tracker -- taken up [from matatk] 15:30:05 Roy: Nothing new on the comment tracker. 15:30:13 https://github.com/w3c/a11y-review/issues 15:30:51 matatk: This is he repo where we receive tracking issues from someone asking for our input. It can be anywhere on Github: if someone, whoever, asks for our input on any a11y issue, it will be created as an issue here. 15:33:52 zakim, open next item 15:33:52 agendum 5 -- New on TR - http://www.w3.org/TR/tr-status-drafts.html -- taken up [from matatk] 15:34:04 subtopic: CSS Viewport Module Level 1 15:34:04 - tracker: https://www.w3.org/WAI/APA/wiki/CSS_Viewport_Module_Level_1 15:34:04 - spec: https://www.w3.org/TR/css-viewport-1/ 15:34:10 Roy: There is one. 15:35:00 matatk: Github issues come form a specific publication whereas Wiki tracking gives us more context. 15:35:45 kirkwood has joined #APA 15:37:03 PaulG: I think I'm fine with this one. 15:37:13 matatk: I think this is just viewport bounds and zoom. 15:37:35 PaulG: When zoomed, do you keep the same coordinates or do you change them and report that? Something along those lines. 15:38:06 matatk: This is an FPWD so we haven't een officially requested to review this. 15:38:14 kirkwood has joined #APA 15:38:28 matatk: We are brought on usually when a documetn is to transition between stages. 15:39:27 https://www.w3.org/TR/css-viewport-1/#interaction-with-virtualkeyboard-overlayscontent 15:39:30 matatk: I don't think this needs following as of now. It will come back to us. Plus, we're familiar with it thorugh Paul's input. 15:42:31 PaulG: Often a virtual keyboard is covering things and I need to tap away to see what it is covered. 15:43:12 q+ 15:44:37 PaulG: It would be interesitng to know if anyone working in AT could tell us how their calculations worked when the viewport is changed, for instance through zoom. 15:45:10 PaulG: Can any AT developer weigh in: hwo do you calculate your virtual cursor placement or do you hand that over to the UA? For instance. 15:45:18 matatk: That might be an ARIA/WG thing. 15:45:35 matatk: The virtual cursor isn't rendered as such. It is more like a place in the DOM. 15:45:45 PaulG: Is it in the DOM, in teh bitmap, on top in another layer? 15:46:37 matatk: We should defiinitely ask about this, and I can think of no one better to ask than the ARIA WG. 15:46:57 matatk: If there is an appropriate issue to link to and ask them ato chime in, maybe that's the thing to do. 15:47:07 Fazio: We could make a new issue...? 15:47:12 https://github.com/w3c/csswg-drafts/issues/9442 15:47:19 PaulG: I had ot things in my notes concerningzoom. 15:47:30 PaulG: This one is the one I wanted to talk about. 15:48:37 nehaj: I have a little doubt here. Are we talking about the virtual keybards on mobile devices or do we also include the ones on bank websites where they don't want to know keystrokes really? 15:49:32 q? 15:49:41 ack nehaj 15:49:51 PaulG: I would assme that if someones implementing HTML virtual keybaords, you know you are using CSS zoom The problem I see comes with the author using zoom on a web page or an application thhat then the AT doesn#t know is being zoomed. When it gets viewport information without zoom appliedd, then does that still work or does the irtual ursor appear in the wrong place? Or is it delegeated to teh borwser? I dont know. 15:50:51 I think this is it https://github.com/w3c/csswg-drafts/issues/9398 15:51:19 matatk: Let#s move on. We need to figure out where to report this. If I could think of how to succinclty create that as an action, I would do that now. 15:51:34 PaulG: Put a stamp on the link I posted, perhaps? 15:52:01 zakim, open next item 15:52:01 agendum 6 -- CSS Update (Paul) - https://github.com/w3c/css-a11y/issues -- taken up [from matatk] 15:52:18 https://github.com/w3c/csswg-drafts/issues/9508 15:52:20 PaulG: Scrollbars! 15:53:16 PaulG: What about making scrollbars completely stylable and resizable? Thats not standard compliant. There should be considerations for this. Or at least warnings. 15:53:36 matatk: Brilliant summary. I'e put a11y tracker on it as well. 15:53:50 zakim, next item 15:53:50 agendum 7 -- Actions Checkin (Specs) - https://github.com/w3c/apa/labels/action -- taken up [from matatk] 15:54:00 zakim, close this item 15:54:01 agendum 7 closed 15:54:01 I see 4 items remaining on the agenda; the next one is 15:54:02 8. Dangling Spec Review Cleanup [from matatk] 15:54:03 zakim, next item 15:54:03 agendum 8 -- Dangling Spec Review Cleanup -- taken up [from matatk] 15:54:07 zakim, close this item 15:54:07 agendum 8 closed 15:54:08 I see 3 items remaining on the agenda; the next one is 15:54:08 9. Task Force & Deliverables Updates [from matatk] 15:54:21 zakim, close this item 15:54:21 I do not know what agendum had been taken up, matatk 15:54:26 zakim, next item 15:54:27 agendum 9 -- Task Force & Deliverables Updates -- taken up [from matatk] 15:54:30 zakim, close this item 15:54:30 agendum 9 closed 15:54:31 I see 2 items remaining on the agenda; the next one is 15:54:31 10. Other Business [from matatk] 15:54:32 zakim, next item 15:54:33 agendum 10 -- Other Business -- taken up [from matatk] 15:55:04 matatk: There is a lot left for next week. 15:55:15 Fazio: I'll be at CSUN. 15:55:56 zakim, end meeting 15:55:56 As of this point the attendees have been PaulG, Fazio, Roy, niklasegger, Fredrik, matatk, janina, nehaj, Nichole, Irfan, mike_beganyi, Lionel_Wolberger 15:55:59 RRSAgent, please draft minutes 15:56:01 I have made the request to generate https://www.w3.org/2024/01/31-apa-minutes.html Zakim 15:56:07 I am happy to have been of service, Fredrik; please remember to excuse RRSAgent. Goodbye 15:56:14 Zakim has left #apa 16:57:47 PaulG has left #apa 17:16:33 bkardell_ has joined #apa 18:04:39 duga has joined #apa 19:16:52 duga has joined #apa 20:50:19 duga has joined #apa 21:22:13 kirkwood has joined #APA 22:20:26 duga has joined #apa