- From: Matthew Atkinson <matkinson@tpgi.com>
- Date: Wed, 12 Apr 2023 15:09:11 +0000
- To: Janina Sajka <janina@rednote.net>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Hi all, Today's minutes can be found at https://www.w3.org/2023/04/12-apa-minutes.html and below in plain text for convenience. Best regards, Matthew – DRAFT – 12 April 2023 [2]IRC log. [2] https://www.w3.org/2023/04/12-apa-irc Attendees Present Fredrik, matatk, mike_beganyi, PaulG, Roy Regrets Gottfried_Zimmerman, Lionel_Wolberger, Niklas_Egger, Susana_Pallero Chair Janina Scribe matatk Contents 1. [3]Agenda Review & Announcements 1. [4]GitHub Actions tracking 2. [5]TPAC 2023 Planning 3. [6]The Metaverse Collection 4. [7]New Charters Review https://github.com/w3c/strategy/ issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+ requested%22 5. [8]A11y Review Comment Tracker https://w3c.github.io/ horizontal-issue-tracker/?repo=w3c/a11y-review 1. [9]Consider allowing <hr>within list elements (ol, ul, menu) 6. [10]CSS Update (Paul) https://github.com/w3c/css-a11y/ issues 7. [11]Actions Checkin (Specs) https://www.w3.org/WAI/APA/ track/actions/open 8. [12]Task Force & Deliverables Updates 1. [13]Adapt 2. [14]Other groups 9. [15]Other Business 10. [16]be done 11. [17]Summary of action items Meeting minutes <janina> /join #rqtf <janina> /join #rqtf/join #rqtf Agenda Review & Announcements GitHub Actions tracking matatk: There's a bot for that: [18]https://w3c.github.io/ GHURLBot/manual.html - looks promising; we plan to try it out in APA calls first. [18] https://w3c.github.io/GHURLBot/manual.html TPAC 2023 Planning janina: Please let us know agenda items for TPAC, so we can arrange meetings with other groups. … Thanks Pronunciation for the agenda you gave already. We also expect to want to talk with EPUB and others about blue sky work (some started up in RQTF, e.g. transcripts). … We'd like to synchronize music scores with performances, for example. … Please think about these cross-group conversations, and we can start developing agenda. <Roy> [19]https://www.w3.org/2023/09/TPAC/ [19] https://www.w3.org/2023/09/TPAC/ Roy: The TPAC home page now exists. janina: We will soon have our own APA planning page. janina: TF co-ordinators: please add this as a standing agenda from now. matatk: Our ultimate deadline is the 7th of May, so we need broad strokes on who to meet, and topics, well before then. The Metaverse Collection Minutes from last APA call on this: [20]https://www.w3.org/ 2023/04/05-apa-minutes#t04 [20] https://www.w3.org/2023/04/05-apa-minutes#t04 janina: RQTF just discussed this, too: [21]https://www.w3.org/ 2023/04/12-rqtf-minutes#t02 [21] https://www.w3.org/2023/04/12-rqtf-minutes#t02 janina: Previous week's RQTF minutes on it: [22]https:// www.w3.org/2023/04/05-rqtf-minutes#t05 [22] https://www.w3.org/2023/04/05-rqtf-minutes#t05 janina: XAUR, SAUR (has a specific section Jason highlighted), MAUR, NAUR, and Content Usable (we should send the Note version). <janina> [23]https://www.w3.org/TR/coga-usable/ [23] https://www.w3.org/TR/coga-usable/ Fredrik: I know it's at an early stage, but CTAUR also has relevant stuff. janina: CTAUR is at least FPWD. janina: Good idea Fredrik, if you think it's relevant. <janina> SAUR especially: [24]https://www.w3.org/TR/ saur/■https://www.w3.org/TR/ saur/#xr-environment-synchronization [24] https://www.w3.org/TR/saur/■https://www.w3.org/TR/saur/#xr-environment-synchronization Fredrik: One of the big points of metaverse is collaboration, so many relevant situations will come up. matatk: RAUR too? I can imagine having a Skype [or similar] call inside of a virtual environment. Fredrik: +1 matatk: Accessibility of Remote Meetings? Because if people are sharing content, they need to know how to make it accessible. Fredrik: Yes, in the sense of how people use the tech, rather than the related CTUAR, which is more about the technical aspects. ACTION: matatk: Post Metaverse-related standards reply - due 2023-04-14 <ghurlbot> Created [25]action #321 [25] https://github.com/w3c/apa/issues/321 <Fredrik> Hooray! But what does RRSAgent need to recognize it for? New Charters Review [26]https://github.com/w3c/strategy/ issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%2 2 [26] https://github.com/w3c/strategy/issues?q=is:issue+is:open+label:"Horizontal+review+requested" Roy: No new Charters, nor TR, nor review requests, this week. zakim close this item A11y Review Comment Tracker [27]https://w3c.github.io/ horizontal-issue-tracker/?repo=w3c/a11y-review [27] https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review Consider allowing <hr>within list elements (ol, ul, menu) <Roy> - issue: [28]whatwg/html#9126 [28] https://github.com/whatwg/html/issues/9126 janina: Should we ask the Low Vision TF? Fredrik: Yes matatk: Can mike_beganyi have a look too? mike_beganyi: Yes Fredrik: Could this be a COGA issue? janina: Not sure, but a lot of things could be. janina: Is anyone confused by having these divisions; does it clutter things up? janina: I can bring it up in the COGA planning call. CSS Update (Paul) [29]https://github.com/w3c/css-a11y/issues [29] https://github.com/w3c/css-a11y/issues PaulG: One issue that was interesting; already resolved and I think they had the right resolution. PaulG: [css-pseudo] Safari’s ::selection “wash” and UA tweaks to highlight colors [30]#6853 - [31]w3c/csswg-drafts#6853 [30] https://github.com/w3c/css-a11y/issues/6853 [31] https://github.com/w3c/csswg-drafts/issues/6853 <ghurlbot> [32]Issue 6853 [not found] [32] https://github.com/w3c/apa/issues/6853 PaulG: The resolution was to not follow Safari's differing approach on this, and to clarify the spec. Actions Checkin (Specs) [33]https://www.w3.org/WAI/APA/track/actions/ open [33] https://www.w3.org/WAI/APA/track/actions/open janina: I guess we still call them actions, though this URI is incorrect :-) <Roy> [34]https://github.com/w3c/apa/labels/action [34] https://github.com/w3c/apa/labels/action matatk: We signed off on DID's charter, and asked about CAPTCHA. matatk: I will post (and cross-post to RQTF) for any new WoT issues. Existing issues were already posted to the lists. <Roy> [35]w3c/strategy#376 [35] https://github.com/w3c/strategy/issues/376 Roy: ^ there's the DID recharter link Task Force & Deliverables Updates Adapt janina: We have a guest presentation about an ontology/taxononmy based on a multi-year NSF-funded project about how children learn. This may inform some of our next steps with Adapt, … and the adapt-* prefix we requested from WHATWG. Info that the project co-ordinator provided for us about the ontology work: [36]https://bob-dlc.github.io/clipps/ [36] https://bob-dlc.github.io/clipps/ janina: If you'd like to be part of the presentation, let us know before Monday so we can add you to the call. It'll be at 10am Boston (same time as APA). Other groups janina: Nothing specific that is new, but wanted to note that a lot of good work is going on. Adapt teleconf info link (Roy says you should already have access; thanks for checking, Roy): [37]https://www.w3.org/2017/ 08/telecon-info_adapt [37] https://www.w3.org/2017/08/telecon-info_adapt Other Business be done (Relvant to discussion about language: [38]https://www.w3.org/ International/articles/language-tags/ HT Adapt issue [39]https://github.com/w3c/adapt/issues/240) [38] https://www.w3.org/International/articles/language-tags/ [39] https://github.com/w3c/adapt/issues/240) Summary of action items 1. [40]matatk: Post Metaverse-related standards reply - due 2023-04-14 Minutes manually created (not a transcript), formatted by [41]scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC). [41] https://w3c.github.io/scribe2/scribedoc.html -- Matthew Tylee Atkinson (he/him) -- Principal Accessibility Engineer TPG Interactive https://www.tpgi.com A Vispero Company https://www.vispero.com -- This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
Received on Wednesday, 12 April 2023 15:09:20 UTC