13:24:12 RRSAgent has joined #apa 13:24:16 logging to https://www.w3.org/2024/02/07-apa-irc 13:24:16 RRSAgent, make logs Public 13:24:17 please title this meeting ("meeting: ..."), janina 13:24:33 zakim, who's here? 13:24:33 Present: (no one) 13:24:35 On IRC I see RRSAgent, Zakim, roy__, janina, gb, imlostlmao, AnthonySpencer, M2cshkpcgrp, SintayewGashaw, matrix638, joraboi445, gonzu_15, sonicscrewdriver, slightlyoff, Rachael, 13:24:35 ... cwilso, tink, ada, jcraig, agendabot 13:25:48 Meeting: APA Weekly Teleconference 13:25:57 Date: 07 Feb 2024 13:32:28 Chair: Janina 13:32:28 agenda+ Agenda Review & Announcements 13:32:28 agenda+ New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22 13:32:31 agenda+ A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review 13:32:34 agenda+ Explicit Review Requests https://github.com/w3c/a11y-request/issues 13:32:36 agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html 13:32:39 agenda+ CSS Update (Paul) https://github.com/w3c/css-a11y/issues 13:32:41 agenda+ Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open 13:32:44 agenda+ Task Force & Deliverables Updates 13:32:46 agenda+ Other Business 13:32:49 agenda+ be done 13:33:28 kirkwood has joined #APA 14:04:35 wendyreid has joined #apa 14:52:26 kirkwood has joined #APA 14:55:07 PaulG has joined #apa 14:57:40 present+ 14:59:22 Lionel_Wolberger has joined #APA 15:00:50 present+ 15:00:50 present+ 15:01:30 Fredrik has joined #apa 15:01:33 present+ 15:02:20 matatk has joined #apa 15:02:31 present+ 15:02:34 agenda? 15:04:28 scribe+ 15:04:35 zakim, next item 15:04:35 agendum 1 -- Agenda Review & Announcements -- taken up [from janina] 15:06:45 scribe+ 15:06:52 matatk: Something we should be part of 15:06:56 subtopic: W3C Breakouts day 15:06:57 https://www.w3.org/2024/03/breakouts-day-2024/ 15:07:21 matatk: At TPAC, Wednesdays include breakouts 15:07:36 matatk: W3C is doing a Breakouts Day in March; Proposals welcome 15:08:12 matatk: Possible APA activities that might be appropriate include Adapt, Tooling under dev; etc 15:08:22 matatk: Worth submitting; worth raising on this call 15:08:39 nehaj has joined #apa 15:08:54 present+ 15:09:09 Nichole_ has joined #apa 15:09:16 present+ 15:09:29 matatk: Deadline for proposal is Feb 29th 15:10:08 Lionel_Wolberger: This is virtual TPAC? 15:10:11 matatk: Yes 15:10:21 Lionel_Wolberger: Would like to do an Adapt breakout 15:10:32 matatk: Suggesting WK 15:10:41 s/WK/Weell Known/ 15:11:27 q? 15:11:30 Nehaj_ has joined #apa 15:12:34 janina: TPAC is in late September: https://www.w3.org/news-events/w3c-tpac/ 15:12:38 zakim, next item 15:12:38 agendum 2 -- New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22 -- taken up [from janina] 15:13:05 zakim, close this item 15:13:05 agendum 2 closed 15:13:06 I see 8 items remaining on the agenda; the next one is 15:13:06 3. A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review [from janina] 15:13:08 zakim, next item 15:13:08 agendum 3 -- A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review -- taken up [from janina] 15:13:33 subtopic: Accessible Rich Internet Applications 1.3 15:13:47 issue: https://github.com/w3c/a11y-request/issues/72 15:13:59 spec: https://www.w3.org/TR/wai-aria-1.3/ 15:15:20 What's changed since 1.2: https://www.w3.org/TR/wai-aria-1.3/#changelog 15:17:36 janina: This is an FPWD; we're not holding up CR. 15:17:49 ... Best thing we can do is look at the areas that have changed, and give some early feedback 15:18:19 ... along the lines of scope - is it too much? is there something that we think they should look into? 15:18:41 ... There's a lot of work to do on it, and we will be asked for a final review when they go to CR. 15:18:47 ... So: scoping concerns are most important now. 15:18:54 rrsagent, make minutes 15:18:55 I have made the request to generate https://www.w3.org/2024/02/07-apa-minutes.html matatk 15:19:03 q? 15:19:43 Fredrik: How does ARIA WG respond to feedback? 15:19:59 janina: We have a good relationship; they'll ACK our feedback, and often take things up. 15:20:32 janina: They also keep a list of things that they are holding for 2.0, which they may add some of our suggestions to; either way we'll find out from them - and we should look at those lists first. 15:21:14 mike_beganyi has joined #apa 15:21:17 present+ 15:21:33 ARIA 1.3 issues: https://github.com/w3c/aria/issues?q=is%3Aopen+is%3Aissue+label%3A%22ARIA+1.3%22 15:21:38 q? 15:22:19 ARIA 2.0 issues: https://github.com/w3c/aria/issues?q=is%3Aopen+is%3Aissue+label%3A%22ARIA+2.0%22+ 15:23:04 janina: If you think something missing from scope, be sure to check the 2.0 list 15:23:16 zakim, next item 15:23:16 agendum 4 -- Explicit Review Requests https://github.com/w3c/a11y-request/issues -- taken up [from janina] 15:23:32 subtopic: Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel 15:23:34 q+ 15:23:39 - issue: https://github.com/w3c/webrtc-pc/issues/2931 15:23:55 scribe+ 15:23:55 scribe+ mike_beganyi 15:24:04 ack mike_beganyi 15:25:09 subtopic: RQTF 15:25:33 janina: bespoke for RQTF to look at this topic. very much covered by previous discussion. most discussion should be captured by RAUR which are now an APA note 15:26:13 Digital Accessibility User Requirements: https://www.w3.org/WAI/research/user-requirements/ 15:26:40 janina: approached Media Accessibilty User Requirements many years ago. This was very successful in HTML5 and have since taken on other areas in this fashion 15:27:13 q+ 15:27:35 janina: flagged this issue and read far enough to recognize what it was about (the issue at the outset of this discussion). support in comms protocols that tries to capture communication at the character level 15:28:39 ...this is about capturing all the text coming through and what are the accessibility concerns with that 15:29:08 subtopic: [css-scrollbars] Upgrade to Recommendation? 15:29:11 ...this should be brought into RQTF, which happened today and it is in the notes 15:29:14 - issue: https://github.com/w3c/csswg-drafts/issues/9508 15:29:57 q? 15:30:01 ack ma 15:30:07 matatk: moving css scrollbar to recommendation. what if scrollbars are styled and are confusing to some. is the task to come up with accessibility considerations specific to scrollbars? 15:30:08 https://drafts.csswg.org/css-scrollbars/#accessibility-considerations 15:30:10 subtopic+ CSS Scrollbars 15:30:17 janina: Begins above ... Sorry! 15:30:32 PaulG: they have an accessibility considerations section. maybe we won't find anything new but worth a look. 15:30:52 q? 15:31:41 tracking issue: https://github.com/w3c/a11y-review/issues/184 15:32:03 PaulG: other considerations here which we can discuss 15:32:07 rssagent, make minutes 15:32:18 rrsagent, make minutes 15:32:19 I have made the request to generate https://www.w3.org/2024/02/07-apa-minutes.html janina 15:33:53 PaulG: size of the thumb, colour, contrast, making it thin, etc. Potential for lots of affordance loss 15:33:57 PaulG: Transparency also 15:34:56 PaulG: My overall caveat is to just say: if you touch these properties, you are required to meet WCAG guidelines for the scrollbar. Since you took over control, you own the scrollbar and its accessibility considerations. 15:35:18 janina: would like to +1 that. It's an important comment that we can use as a template 15:35:44 rrsagent, make minutes 15:35:45 I have made the request to generate https://www.w3.org/2024/02/07-apa-minutes.html matatk 15:35:51 ...another example is a Submit button which is customized by the author. form can be completed but not submitted 15:35:52 q+ 15:36:01 ...would you rather accept boring or take on the accessibility requirements for it? 15:36:38 janina: you own it, you are responsible 15:37:32 PaulG: Don't need to fix focus in Chrome if you haven't touched it, as another example 15:37:51 janina: to a greater or lesser degree, the big players have paid attention to this and have done a pretty good job of it 15:38:16 q? 15:38:18 ack me 15:38:22 q? 15:39:02 matatk: put link to tracking issue on GitHub. I have put a comment on the issue to note areas that were not mentioned in the Accessibility Considerations section 15:39:26 ...already got something approaching an accessibility considerations note with the number of points we've made collectively 15:41:17 bkardell_ has joined #apa 15:41:49 subtopic: [css-zoom?] Zoom and CSSOM 15:42:03 - issue: https://github.com/w3c/csswg-drafts/issues/9398 15:42:17 rrsagent, make minutes 15:42:18 I have made the request to generate https://www.w3.org/2024/02/07-apa-minutes.html janina 15:43:35 - our tracking issue: https://github.com/w3c/a11y-review/issues/183 15:43:36 PaulG: about how resize is reported while under css zoom. Argument was that some platforms tried to recalculate and some didn't and so it would be less taxing on authors and engines to return the original size and shape through the original APIs 15:43:47 q? 15:44:00 ...if used a 2x on something then it's the original but literally bigger, but where it sits is incumbent on the author if that calculation was needed 15:45:07 PaulG: focus not obscured didn't change, it's that the API is just setting a baseline across platforms. You still need to follow Focus Not Obscured and there's a tool to help achieve that. Intention is to make things more consistent. 15:46:01 janina: Trying to figure out how to close these issues. I'm inclined to work offline on this one with Mat and Paul 15:46:26 matatk: Maybe just close this 15:46:42 zakim, next item 15:46:42 agendum 5 -- new on TR http://www.w3.org/TR/tr-status-drafts.html -- taken up [from janina] 15:47:02 janina: ARIA 1.3 FPWD published. See above. The link is above in the minutes. 15:48:01 matatk: We should look at this as a group. Maybe I'll look at it and bring back any comments. 15:48:08 q+ 15:48:17 Fredrik: I have a relaxed Friday so can take a look also 15:48:47 ack mi 15:48:47 mike_beganyi: Happy to take a look at ARIA 1.3 15:49:01 I read through the changes last week and didn't see anything that jumped out. 15:49:23 matatk: will assign the three of us to that tracking issue and point to minutes. 15:49:41 q? 15:49:53 zakim, next item 15:49:53 agendum 6 -- CSS Update (Paul) https://github.com/w3c/css-a11y/issues -- taken up [from janina] 15:50:05 zakim, close this item 15:50:05 agendum 6 closed 15:50:06 I see 4 items remaining on the agenda; the next one is 15:50:06 7. Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open [from janina] 15:50:07 zakim, next item 15:50:07 agendum 7 -- Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open -- taken up [from janina] 15:50:26 janina: anything to report on? 15:50:48 Fredrik: haven't looked at Device Orientation spec but will shortly 15:51:58 janina: expect in a few weeks or a bit longer a presentation on approach that will help us out, care of of Mat 15:52:18 zakim, next item 15:52:18 agendum 8 -- Task Force & Deliverables Updates -- taken up [from janina] 15:52:48 isubtopic: RQTF 15:52:56 subtopic: RQTF 15:53:38 in COGA call, we did revisit current method between COGA and APA and that we think the process is working. Our process gave us a way to address concerns raised during process and double-check them. We're happy with our current process. This is an achievement. 15:54:06 zakim, close this item 15:54:06 agendum 8 closed 15:54:07 I see 2 items remaining on the agenda; the next one is 15:54:07 9. Other Business [from janina] 15:54:08 zakim, next item 15:54:08 agendum 9 -- Other Business -- taken up [from janina] 15:54:18 q+ 15:54:57 mike_beganyi: Going back to template wording on accessibility considerations: I'm happy to help, alongside someone else. 15:55:13 janina: A 'standard warranty paragraph' - happy to have your help; we can work on it. 15:56:01 janina: It may become a short general APA note we can publish. 15:56:15 zakim, next item 15:56:15 I see a speaker queue remaining and respectfully decline to close this agendum, mike_beganyi 15:56:21 ack mi 15:56:22 ack mike_beganyi 15:56:24 zakim, next item 15:56:24 agendum 10 -- be done -- taken up [from janina] 15:56:39 janina: Thanks everyone! Thanks mike_beganyi for scribing. 15:56:46 janina: thanks to all for all your contributions. Looking forward to all future endeavours with this group. 15:56:49 janina: We appreciate you all, and your input! 15:57:10 rrsagent, make minutes 15:57:11 I have made the request to generate https://www.w3.org/2024/02/07-apa-minutes.html mike_beganyi 15:57:33 zakim, bye 15:57:33 leaving. As of this point the attendees have been janina, Lionel_Wolberger, PaulG, Fredrik, matatk, nehaj, Nichole_, mike_beganyi 15:57:33 Zakim has left #apa 16:00:12 action mike_beganyi: Wording for general Accessibility Considerations section 16:00:59 gb, status 16:00:59 matatk, the delay is 15, issues are off, names are off, full issues are printed 10 at a time; and the repository is https://github.com/w3c/apa 16:01:24 gb, on 16:01:24 matatk, OK. 16:02:55 action mike_beganyi: Wording for general Accessibility Considerations section 16:02:56 Cannot create action. Validation failed. Maybe mike_beganyi is not a valid user for w3c/apa? 16:12:41 Nichole_ has left #apa 16:25:51 zakim, who's here? 16:25:56 rrsagent, bye 16:25:56 I see 2 open action items saved in https://www.w3.org/2024/02/07-apa-actions.rdf : 16:25:56 ACTION: mike_beganyi to Wording for general Accessibility Considerations section [1] 16:25:56 recorded in https://www.w3.org/2024/02/07-apa-irc#T16-00-12 16:25:56 ACTION: mike_beganyi to Wording for general Accessibility Considerations section [2] 16:25:56 recorded in https://www.w3.org/2024/02/07-apa-irc#T16-02-55 16:25:59 Cannot create action. Validation failed. Maybe mike_beganyi is not a valid user for w3c/apa? 16:26:02 Cannot create action. Validation failed. Maybe mike_beganyi is not a valid user for w3c/apa?