- From: Matthew Atkinson <matkinson@tpgi.com>
- Date: Wed, 7 Dec 2022 15:47:23 +0000
- To: Janina Sajka <janina@rednote.net>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Hello all, Please find today's minutes at https://www.w3.org/2022/12/07-apa-minutes.html and below, in text form, for convenience. Best regards, Matthew – DRAFT – APA Weekly Teleconference 07 Dec 2022 [2]IRC log. [2] https://www.w3.org/2022/12/07-apa-irc Attendees Present Alisa_Smith, janina, matatk, mike_beganyi, niklasegger, PaulG, Roy Regrets Becky_Gibson, Fredrik_Fischer, Lionel Chair Janina Scribe matatk Contents 1. [3]Agenda Review & Announcements 2. [4]Advancing Adapt Symbols to CR 3. [5]New Charters Review https://github.com/w3c/strategy/ issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+ requested%22 4. [6]Dangling Spec Review Cleanup: https://www.w3.org/WAI/ APA/wiki/Category:Spec_Review_Assigned 1. [7]Autoplay Policy Detection 2. [8]Verifiable Credential Data Integrity 1.0 5. [9]CSS Update (Paul) https://github.com/w3c/css-a11y/issues 1. [10]no-motion 2. [11]fragment url() 3. [12]animate display:none 4. [13]ruby spacing 6. [14]Task Force & Deliverables Updates 1. [15]Pronunciation 2. [16]Adapt 3. [17]Maturity Model (?) 7. [18]Actions Checkin (Specs) https://www.w3.org/WAI/APA/ track/actions/open 1. [19]Web of Things 8. [20]Other Business 9. [21]be done 10. [22]Summary of resolutions Meeting minutes Agenda Review & Announcements janina: Matthew, Lionel and I participated in the W3C Workshop on Permissions (virtually). We learnt quite a bit, and have work to follow up on. We'll let you know when the workshop report is out. … We've made connections for some of the work, particularly edge-related, that we started in TPAC (e.g. verifiable credentials). matatk: I got insights from the workshop into ways the UA is acting on behalf of the user. janina: Note: APA _is_ meeting next week. Advancing Adapt Symbols to CR janina: We have a resolution from our Adapt TF. <janina> [23]https://www.w3.org/2022/12/ 05-adapt-minutes.html#r01 [23] https://www.w3.org/2022/12/05-adapt-minutes.html#r01 janina: Adapt TF has asked us to move the Symbols Module forward to CR. We do not believe we need a new CfC, because this module is the result of removing (for now) the non-symbol attributes. janina: We met with TAG during TPAC and they agreed, as do we, that symbols is the best-architected part. So we have removed the rest for now, and are investigating the other work separately. <janina> [24]https://www.w3.org/2022/12/ 05-adapt-minutes.html#r015 [24] https://www.w3.org/2022/12/05-adapt-minutes.html#r015 janina: The Symbols Module depends on our new AAC Registry, the FPWD of which was just approved overnight. janina: Does anyone object, and believe that another CfC is required? We do not believe so, but if you have concerns, questions, please raise them here. <janina> DRAFT RESOLUTION: APA confirms support for advancing Adapt Symbol Module to CR based on our previous consensus which included symbols logged at [25]https://lists.w3.org/Archives/ Public/public-apa-admin/2022Aug/0058.html [25] https://lists.w3.org/Archives/Public/public-apa-admin/2022Aug/0058.html janina: Any concerns about this resolution? RESOLUTION: APA confirms support for advancing Adapt Symbol Module to CR based on our previous consensus which included symbols logged at [26]https://lists.w3.org/Archives/Public/ public-apa-admin/2022Aug/0058.html [26] https://lists.w3.org/Archives/Public/public-apa-admin/2022Aug/0058.html janina: This truly is groundbreaking work. +1 New Charters Review [27]https://github.com/w3c/strategy/ issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%2 2 [27] https://github.com/w3c/strategy/issues?q=is:issue+is:open+label:"Horizontal+review+requested" Roy: No new charters, no new issues, and nothing new on TR this week. Dangling Spec Review Cleanup: [28]https://www.w3.org/WAI/APA/wiki/ Category:Spec_Review_Assigned [28] https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned Autoplay Policy Detection <Roy> - TR: [29]https://www.w3.org/TR/autoplay-detection/ [29] https://www.w3.org/TR/autoplay-detection/ <Roy> - tracking: [30]https://www.w3.org/WAI/APA/wiki/ Autoplay_Policy_Detection [30] https://www.w3.org/WAI/APA/wiki/Autoplay_Policy_Detection Verifiable Credential Data Integrity 1.0 <Roy> - TR: [31]https://www.w3.org/TR/vc-data-integrity [31] https://www.w3.org/TR/vc-data-integrity <Roy> - tracking: [32]https://www.w3.org/WAI/APA/wiki/ Verifiable_Credential_Data_Integrity_1.0 [32] https://www.w3.org/WAI/APA/wiki/Verifiable_Credential_Data_Integrity_1.0 <Roy> - review by Lionel: [33]https://lists.w3.org/Archives/ Public/public-apa/2022Nov/0045.html [33] https://lists.w3.org/Archives/Public/public-apa/2022Nov/0045.html <Roy> [34]https://www.w3.org/WAI/APA/wiki/ UI_Events_KeyboardEvent_code_Values [34] https://www.w3.org/WAI/APA/wiki/UI_Events_KeyboardEvent_code_Values <Roy> [35]https://www.w3.org/WAI/APA/wiki/ UI_Events_KeyboardEvent_key_Values [35] https://www.w3.org/WAI/APA/wiki/UI_Events_KeyboardEvent_key_Values CSS Update (Paul) [36]https://github.com/w3c/css-a11y/issues [36] https://github.com/w3c/css-a11y/issues no-motion <PaulG> [37]https://github.com/w3c/csswg-drafts/issues/7440 [37] https://github.com/w3c/csswg-drafts/issues/7440 PaulG: One option suggested was an "important" directive to override motion. I think the UA should control this ultimately. A general path forward, involving adding some ability to continue to reduce motion, was agreed. fragment url() <PaulG> [38]https://github.com/w3c/csswg-drafts/issues/3320 [38] https://github.com/w3c/csswg-drafts/issues/3320 PaulG: this is about clarifying expectations about how the URL is resolved. … This is only for IDs. PaulG: This one didn't seem a11y-related animate display:none <PaulG> [39]https://github.com/w3c/csswg-drafts/issues/6429 [39] https://github.com/w3c/csswg-drafts/issues/6429 PaulG: This one is about how some properties can't be animated. … Trying to make it more intuitive for developers. … Shouldn't affect animations or anything like that; just a technique for how the animation is executed. ruby spacing <PaulG> [40]https://github.com/w3c/csswg-drafts/issues/5995 [40] https://github.com/w3c/csswg-drafts/issues/5995 janina: Are we piggybacking on this with Symbols? PaulG: This is more about how whitespace is stripped or not, in different cases. i18n is being consulted on it. PaulG: I mentioned the work on AAC symbols, but in current prototypes e.g. from matatk the symbols have their own spacing, margins. … Spacing is a little more important with Ruby because the rubies need to line up precisely wiht the charactrs. For Symbols, it is a bit more coarse and the text will need to be re-laid out to accommodate the symbols. Task Force & Deliverables Updates Pronunciation janina: PaulG: Does the new proposed time work for you? PaulG: Yes; that time looks generally good. janina: Will check up on having a call next week. … I have an action to re-write the draft response to WHATWG. We may need to work with the WICG, too. Adapt janina: As above - some key work finished, and AAC Registry FPWD will be published next Tuesday we hope. … Also, we hope, the Symbols Module CR, before the moratorium. … The Explainer has been, and will be, updated, so we should publish an updated draft of that too. Maturity Model (?) janina: We're going to propose making MM a TF, probably in January. We'll run a CfC on this. … They've started working on a Work Statement, which will be reviewed shortly. … In the new year, APA is re-chartering, so we'll be asking you about making MM a TF then. Actions Checkin (Specs) [41]https://www.w3.org/WAI/APA/track/actions/ open [41] https://www.w3.org/WAI/APA/track/actions/open matatk: Suggest everyone reads and comments, if needed, on Lionel's review, posted to the list: Action item: Review Verifiable Credential Data Integrity: [42]https://lists.w3.org/ Archives/Public/public-apa/2022Nov/0045.html [42] https://lists.w3.org/Archives/Public/public-apa/2022Nov/0045.html Web of Things niklasegger: Have been looking at the spec; have a few questions. … Gottfried planning to review between Christmas and New Year, and deliver report in the new year. Is that too late? janina: No, that's fine. We didn't block their CR, but we can put in any comments before the CR closes. niklasegger: The original question posted by WoT was if the Architecture doc should have an accessibility section. I talked with Gottfried and he had some more ideas, which relate to WoT in general, e.g. including more semantic info in the ThingDescription, (e.g. type of the device; it's location). Should we consider these things too, or is it too late? janina: No it's not too late. Do you recall they have profiles, and they created an accessibility considerations section for the profiles. I think it needs a little more than what they have. We should decide on those together. Whether it goes into the Architecture spec, or Profiles, I'm not sure. … Also I want to capture what we called "middleware" accessibilty issues, which we raised with the group earlier, and the importance of making consumers aware of those issues/requirements in advance. niklasegger: Thanks; we'll keep you updated. Other Business be done janina: Thank you very much everyone for your time and good work, of which there is quite a bit being done! janina: See you next week! Summary of resolutions 1. [43]APA confirms support for advancing Adapt Symbol Module to CR based on our previous consensus which included symbols logged at https://lists.w3.org/Archives/Public/ public-apa-admin/2022Aug/0058.html Minutes manually created (not a transcript), formatted by [44]scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC). [44] 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, 7 December 2022 15:47:41 UTC