14:58:17 RRSAgent has joined #apa 14:58:21 logging to https://www.w3.org/2023/01/18-apa-irc 14:58:21 RRSAgent, make logs Public 14:58:22 please title this meeting ("meeting: ..."), janina 14:58:44 Meeting: Accessible Platform Architectures (APA) Weekly Teleconference 14:58:50 date: 18 jan 2023 14:58:56 chair: Janina 14:58:59 present+ 14:59:01 agenda? 15:00:22 zakim, who's here? 15:00:22 Present: PaulG, matatk, Roy, janina, Fredrik, Lionel_Wolberger, Gottfried 15:00:25 On IRC I see RRSAgent, matatk, PaulG, janina, MichaelC, agendabot, cwilso, Rachael, Joshue108, jcraig, ZoeBijl, slightlyoff, tink, adarose, Github, Zakim, trackbot 15:00:38 regrets: Gottfried 15:00:44 present+ 15:00:48 present+ 15:02:50 regrets+ Nadine 15:04:24 scribe: matatk 15:05:09 Fredrik has joined #apa 15:05:09 niklasegger has joined #apa 15:05:09 present+ 15:05:09 zakim, next item 15:05:09 agendum 1 -- Agenda Review & Announcements -- taken up [from janina] 15:05:09 present+ 15:05:51 zakim, close this item 15:05:51 agendum 1 closed 15:05:52 zakim, next item 15:05:53 I see 10 items remaining on the agenda; the next one is 15:05:53 2. CfC Elevating Maturity Model to Task Force httpS://www.w3.org/WAI/APA/task-forces/maturity-model/work-statementtatus [from janina] 15:05:53 agendum 2 -- CfC Elevating Maturity Model to Task Force httpS://www.w3.org/WAI/APA/task-forces/maturity-model/work-statementtatus -- taken up [from janina] 15:06:35 https://lists.w3.org/Archives/Public/public-rqtf/2023Jan/0015.html 15:07:11 janina: The above is an email from one of the co-facilitators, explaining why W3C is doing this work. Does this allay your concerns? 15:07:58 https://lists.w3.org/Archives/Public/public-rqtf/2023Jan/0015.html 15:08:42 Lionel_Wolberger has joined #apa 15:08:47 present+ 15:08:58 Lionel_Wolberger: I'm involved in this work. I support the proposed CfC. 15:09:31 https://lists.w3.org/Archives/Public/public-rqtf/2023Jan/0015.html 15:10:13 janina: Asking differently: anyone opposed to the CfC? 15:10:19 Fredrik: I'd like the CfC. 15:11:45 matatk: I wasn't clear on point 7 in the email; is there another example? (Not opposed to CfC.) 15:11:57 +1 15:12:15 (support removal of #7) 15:12:35 Fredrik: Maybe best to leave that point out (seems confused, and technologies change rapidly anyway). 15:12:50 janina: We should ask the MM group to clarify or drop that one. 15:12:58 rrsagent, make minutes 15:12:59 I have made the request to generate https://www.w3.org/2023/01/18-apa-minutes.html matatk 15:13:23 janina: Others OK with that approach? 15:13:33 +1 (others already +1'd) 15:13:36 zakim, next item 15:13:36 agendum 3 -- APA Rechartering https://github.com/w3c/apa/blob/charter-2023/charter.html -- taken up [from janina] 15:14:34 janina: Nothing changed since last week; still seeking comments and questions. 15:14:38 zakim, close this item 15:14:38 agendum 3 closed 15:14:39 I see 8 items remaining on the agenda; the next one is 15:14:39 4. Payments Security IG Rechartering https://github.com/w3c/strategy/issues/365#issuecomment-1379515981 [from janina] 15:14:40 zakim, next item 15:14:40 agendum 4 -- Payments Security IG Rechartering https://github.com/w3c/strategy/issues/365#issuecomment-1379515981 -- taken up [from janina] 15:15:21 zakim, take up item 3 15:15:21 agendum 3 -- APA Rechartering https://github.com/w3c/apa/blob/charter-2023/charter.html -- taken up [from janina] 15:15:28 Here's the pretty link: https://raw.githack.com/w3c/apa/charter-2023/charter.html 15:16:09 zakim, take up item 4 15:16:09 agendum 4 -- Payments Security IG Rechartering https://github.com/w3c/strategy/issues/365#issuecomment-1379515981 -- taken up [from janina] 15:16:33 janina: Lionel_Wolberger had a look at this, and raised some issues about UI, and what was included. 15:17:00 ... We were invited by WPSIG leadership to join their management call, which matatk and I did yesterday. 15:17:42 ... It was an aha! moment, as they're fully supportive of accessibility, but are currently working on lower-level things. There are some things coming up that may need our input, and they're happy to liaise with us then. 15:18:06 ... They are not working on the same things (e.g. wallet UIs) as Verifiable Credentials. The focus is narrower, specifically on payments. 15:18:35 ... The VC work is less tied to browsers. 15:19:01 ... We laid out what we're looking for in the short-term future, and longer-term aspirations (as per last TPAC). 15:19:47 ... Their focus remains on registration-free secure payments, though there was no objection to our work/aims. There was FIDO representation there, and they're looking into what process may be used to liaise with us (membership and IP considerations ongoing). 15:19:53 rrsagent, make minutes 15:19:55 I have made the request to generate https://www.w3.org/2023/01/18-apa-minutes.html matatk 15:20:11 ... We expect to hear back from them, as there was the desire to work jointly. 15:20:50 rrsagent, make minutes 15:20:51 I have made the request to generate https://www.w3.org/2023/01/18-apa-minutes.html matatk 15:21:29 janina: Any considerations/concerns (specifically related to the charter)? 15:21:46 janina: They said let's get together at TPAC, which reminds me... 15:22:06 ... TPAC will be the 11th to 15th of September, in Seville :-). 15:23:07 janina: Lionel_Wolberger: does this allay any concerns? 15:23:25 Lionel_Wolberger: sounds great; let's make the meetings happen. 15:23:31 agenda? 15:23:52 zakim, next item 15:23:52 agendum 5 -- PROPOSED Private Advertising Technology Working Group https://www.w3.org/2022/08/PROPOSED-PATWG-charter.html -- taken up [from janina] 15:24:48 janina: New group being proposed to find a way to allow the advertisting industry to add adverts to web content, and collect data from the user without disclosing who they are (and, one assumes, without disclosing they have a disability - though that is not explicitly stated). 15:25:23 ... We signed off on this group back last May, but I now have some additional concerns, partly due to the work we did in Adapt. IIRC we signed off with a caveat, but not sure if that has been reflected in the draft charter. 15:25:56 ... I also have concerns about how we preserve people's anonymity, or the masking of their disability, or their ability to read the ads (COGA implications; maybe distracting). 15:26:18 ... Some users with disabilities may want to read the ads, but need an accessible way to do so. 15:27:27 ... My list of things that I'd add, if we were looking at this with perhaps a little more forethought than we did last May, 15:28:01 ... would include demarcating where the ad starts and ends. Also, adding an ad into a page should not do anything to break its accessibility. 15:28:03 q+ 15:28:06 ... Do you share these concerns? 15:28:18 q? 15:28:22 ack Lionel_Wolberger 15:29:15 Lionel_Wolberger: Sites tend to offer slots in which to place ads, so the chance of an ad changing the page outside of itself is unlikely. 15:29:26 ... The tendency for ads to slide in/out seems to have stopped. 15:29:57 ... However there is something powerful in what you said, which is that given a page has a certain level of accessibility, we don't wnat an ad to come in and lower the accessibility. 15:30:42 Lionel_Wolberger: I think this is a concern we could raise fruitfully. 15:30:46 q+ 15:30:49 janina: Could this include a keyboard trap? 15:31:09 Lionel_Wolberger: Actually yes, on reflection, though ads don't tend to have a lot of keyboard interactivity. 15:31:18 ... Today the bane of the web is autoplaying video. 15:31:31 q+ 15:31:37 q? 15:31:57 ack pa 15:32:50 q+ 15:33:10 PaulG: Reminds me of the Reporting API conversation at TPAC. I think this'd be a fantastic use case becuase the brokering is on-demand. People who have a UA/plugin that reports accessibility issues within ads, that ad could get downgraded within the brokering conglomerate. You could have an agreement with them that you (as a site provider) 15:33:25 +1 to Paul's idea of Reporting API could report back to the RTB ad-provisioning system 15:33:42 ... only want ads that meet a certain level of accessibility. Some consideration would be needed wrt anti-competitive behavior, but this could empower users (especially e.g. with distracting content). 15:33:42 +1 to "Accessibility Reporting API" 15:33:54 +1 to Paul's ideas! 15:33:59 ack ni 15:34:24 niklasegger: +1 to all of the above. Just to add something about videos: it is theoretical possible that the video displays some flickering content, which is a huge risk to some people. 15:34:30 janina: Another excellent point. 15:34:31 +1 15:35:19 janina: When we signed off, they went to AC vote, which failed. They're trying again. 15:35:22 q+ 15:36:02 janina: Seems like there are still some votes against the new charter. We need people who can vote, i.e. AC reps, to make a formal objection. 15:36:09 janina: I think there are others here who are formal members. 15:36:21 s/others here/several here/g 15:36:30 janina: We can then work with this group to close them. 15:36:58 ack Lionel_Wolberger 15:37:00 ack matatk 15:37:52 scribe: Fredrik 15:38:09 matatk: Privacy concerns: Are we more concerned if people are for instance using the ADAPT plugin? 15:38:31 janina: We brought it up perhaps in May last year. I'll find it and post it to list. 15:39:12 matatk: +1 again to PaulG's ideas; it's a really positive way to approach ads. 15:39:30 janina: Ads can be fun, and we should have access to them. 15:39:41 janina: Are the bounding boxes for ads semantically identifiable? Yes? 15:39:52 PaulG: They should be marked with a landmark or something. 15:42:42 Q? 15:42:47 matatk: Something about marking content, and privacy: need user to be able to opt out of some types of content, for health reasons, without giving away PII. 15:42:56 q+ 15:43:06 janina: The vote is open to February 10. When I find our previous comment, I'll post that to the list, along with this date. 15:43:06 kirkwood has joined #APA 15:43:17 ... Please reach out to your AC rep to express these accessibility concerns. 15:43:52 matatk: Suggest we work on a comment to give to AC reps about this. 15:43:59 janina: +1; please comment on list 15:44:00 Fredrik: +1 15:44:56 Lionel_Wolberger: There can be malware in advertising, with commercial solutions having been devised. This proposed approach is similar to that. We do have a tall hill to climb. 15:45:54 ... There was an article about prior efforts in this area. 15:47:16 q? 15:47:23 ack li 15:47:25 ack q 15:48:16 FYI https://en.wikipedia.org/wiki/Evil_bit 15:48:36 zakim, next item 15:48:36 agendum 6 -- Review Requests https://github.com/w3c/a11y-request/issues -- taken up [from janina] 15:49:00 janina: This will become a stock agenda item. It is not the dashboard, but it's like the dashboard. 15:49:08 rrsagent, make minutes 15:49:10 I have made the request to generate https://www.w3.org/2023/01/18-apa-minutes.html matatk 15:50:08 janina: Whe groups ask for an APA review, that starts the clock ticking. These requests are formal (and we also receive via email) and we only have 30 days to respond. 15:50:52 janina: The latest one: https://github.com/w3c/a11y-request/issues/50 15:51:06 ... Secure Payment Confirmation 2023-01-11 > 2023-02-01 15:52:12 PaulG: They have an accessibility considerations section. 15:54:08 agenda? 15:54:30 zakim, next item 15:54:31 agendum 7 -- CSS Update (Paul) https://github.com/w3c/css-a11y/issues -- taken up [from janina] 15:55:00 PaulG: I reviewed Web Locks; it's very low-level; fine to pass on it. 15:57:11 niklasegger has joined #apa 16:00:14 tzviya has joined #apa 16:02:38 s/Evil_bit/Evil_bit HT matatk/ 16:02:42 rrsagent, make minutes 16:02:43 I have made the request to generate https://www.w3.org/2023/01/18-apa-minutes.html matatk 16:03:21 rrsagent, make minutes 16:03:52 I have made the request to generate https://www.w3.org/2023/01/18-apa-minutes.html matatk 17:02:49 kirkwood has joined #APA 18:17:58 kirkwood has joined #APA 19:41:39 janina has changed the topic to: APA Weekly Teleconference; Wednesday 25 January at 1500Z 22:09:14 kirkwood has joined #APA