- From: Matthew Atkinson <matkinson@tpgi.com>
- Date: Wed, 10 May 2023 14:57:12 +0000
- To: Janina Sajka <janina@rednote.net>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Hi all, Minutes from today can be found at https://www.w3.org/2023/05/10-apa-minutes.html and below in text form. Best regards, Matthew – DRAFT – APA Weekly Teleconference 10 May 2023 [2]IRC log. [2] https://www.w3.org/2023/05/10-apa-irc Attendees Present Alisa_Smith, Fredrik, janina, Lionel_Wolberger, matatk, mike_beganyi, niklasegger, Roy Regrets Gottfried, Gottfried_Zimmerman, Paul Chair Janina Scribe Fredrik, Lionel_Wolberger, matatk Contents 1. [3]Agenda Review & Announcements 2. [4]Announcing New Zoom Starting Next Week 3. [5]TPAC 2023 Planning 4. [6]New Charters Review https://github.com/w3c/strategy/ issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+ requested%22 1. [7]Media Interest Group 2. [8]Web of Things Working Group rechartering 5. [9]Explicit Review Requests https://github.com/w3c/ a11y-request/issues 6. [10]A11y Review Comment Tracker https://w3c.github.io/ horizontal-issue-tracker/?repo=w3c/a11y-review 1. [11]WCAG 2.2 1.4.6 Contrast (Enhanced) failure in WCAG 2.2 draft 7. [12]new on TR http://www.w3.org/TR/tr-status-drafts.html 8. [13]CSS Update (Paul) https://github.com/w3c/css-a11y/ issues 9. [14]Actions Checkin (Specs) https://www.w3.org/WAI/APA/ track/actions/open 1. [15]Stock Accessibility Considerations section 2. [16]Compute Pressure API ACs 10. [17]Task Force & Deliverables Updates 11. [18]Other Business 12. [19]be done 13. [20]Summary of action items Meeting minutes <janina> Date 10 May 2023 Agenda Review & Announcements janina: Mostly same agenda as usual. Important second item coming up! janina: Any announcements/agenda? Announcing New Zoom Starting Next Week janina: We're moving away from MIT's Zoom to W3C's. This is happening! … We can have live machine transcription and we can have translation into other languages! … This sort of thing is covered in RTC Accessibility User Requirements, e.g. pinning the ASL feed. I think they're identifying the signer, and hopefully you can pin them. … Two things are changing, and two things are not: the link that's published in all agenda announcements (goes to w3.org/...) is _not_ changing. … The password will remain the same. … What is changing? The meeting ID, and the meeting-joining link URI that is within the W3C page. … Questions/comments? TPAC 2023 Planning Draft page: [21]https://www.w3.org/WAI/APA/wiki/Meetings/ TPAC_2023 [21] https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2023 janina: We filed for a whole series of joint meetings, put a lot of time into thinking about the sequence of them, too. This is because the priorities/goals that come out of some meetings will affect the meetings with others. … We included everything that you (TFs) asked for. Not as long a list as last time, which was our first time IRL for 3 years. However it's still a big list. … We should also have plenty of time to just be APA, and do our own internal work. scribe> Fredrik matatk: Looking very good line-up-wise. Keep an eye on the wiki page, there will be lots going on there shortly. janina: We're looking to the future, and we are excited to plan what we can pull together and work on next! Comments/questions? New Charters Review [22]https://github.com/w3c/strategy/ issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%2 2 [22] https://github.com/w3c/strategy/issues?q=is:issue+is:open+label:"Horizontal+review+requested" Media Interest Group <janina> [23]https://w3c.github.io/media-and-entertainment/ charters/charter-2023.html [23] https://w3c.github.io/media-and-entertainment/charters/charter-2023.html janina: I have a draft PR for this, regarding the topics area. They list a whole series of topics; including accessibility - very good. However, let's get some examples in for accessibility. … E.g. interlinear streams; multiple languages of captions; synchronization of multiple captions/*SLs; rich markup (symbols?) for chapter titles; etc. Lionel_Wolberger: Media predictability janina: Just to note, this is an interest group (IG) which is not a group that produces standards (but might produce notes), it's a group for coordinating cross-industry. Lionel: The ability to inform the user before clicking a link, what the media consists of, if it has multiple BW encodings, captions, ASL, etc janina: (a bit like WAI). janina: We may also like to update the MAUR (2015). janina: +1 to exposure of metadata about the media behind the link, as Lionel_Wolberger mentions. Lionel_Wolberger: Metadata regarding the video, before invoking the link, your user agent can assess if this media has or does not have what you need janina: e.g. YouTube adds a semaphore to a video to indicate the standard/level of captioning that has been done (automated/ASL/human-corrected). … Would we all agree to making a PR to give them a list of examples, but otherwise be happy with the charter? +1 <janina> +1 <Roy> +1 <Alisa_Smith> +1 <mike_beganyi> +1 +1 <niklasegger> +1 janina: I'll work on the PR. Web of Things Working Group rechartering <matatk> Latest update: [24]w3c/strategy#375 (comment) [24] https://github.com/w3c/strategy/issues/375#issuecomment-1536515993 matatk: Quick note: I already did the same thing as what Janina was suggesting with the WOT charter. matatk: They have a charter that we are happy with in general. When they offered to include the accessible onboarding (bringing a thing onto your network: thermostat, smart bulb, printer etc.). They offered accessible onboarding, there's a consideration of the WG and we looked at it, ahd a conversation about it. matatk: It seems that these changes will be in the charter, but they haven't been merged yet. matatk: I've said we're happy with the charter as is because they have included accessibility. The onboarding process is going to be merged, but we haven't heard about it being merged yet. Explicit Review Requests [25]https://github.com/w3c/a11y-request/ issues [25] https://github.com/w3c/a11y-request/issues <matatk> Roy: No new ones A11y Review Comment Tracker [26]https://w3c.github.io/ horizontal-issue-tracker/?repo=w3c/a11y-review [26] https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review WCAG 2.2 1.4.6 Contrast (Enhanced) failure in WCAG 2.2 draft <Roy> - issue: [27]w3c/wcag#3105 [27] https://github.com/w3c/wcag/issues/3105 <matatk> Roy: This looks like an issue with the presentation of the document, for AGWG to resolve. new on TR [28]http://www.w3.org/TR/tr-status-drafts.html [28] http://www.w3.org/TR/tr-status-drafts.html <Roy> Verifiable Credentials Status List v2021 <Roy> - tracker: [29]https://www.w3.org/WAI/APA/wiki/ Verifiable_Credentials_Status_List_v2021 [29] https://www.w3.org/WAI/APA/wiki/Verifiable_Credentials_Status_List_v2021 <Roy> - Spec: [30]https://www.w3.org/TR/vc-status-list/ [30] https://www.w3.org/TR/vc-status-list/ <Roy> [31]https://www.w3.org/TR/ vc-status-list/#accessibility-considerations [31] https://www.w3.org/TR/vc-status-list/#accessibility-considerations ACTION: Lionel_Wolberger: Review Verifiable Credentials Status List v2021 <ghurlbot> Cannot create action. Validation failed. Maybe Lionel_Wolberger is not a valid user for w3c/apa? <matatk> Lionel_Wolberger: I will review. Note that much of this may be low level, but will check the considerations section. <Roy> ghurlbot, Lionel_Wolberger = lwolberg ACTION: Lionel_Wolberger: Review Verifiable Credentials Status List v2021 <ghurlbot> Cannot create action. Validation failed. Maybe lwolberg is not a valid user for w3c/apa? <matatk> matatk: Not 100% sure if ACs section needed, though they have an apparent general VC-related section, which is great to see. There's a note to say that it needs to be written. <matatk> janina: This is reflective of the good relationship we have with VC; good on them for having a stock Accessibility Considerations section. CSS Update (Paul) [32]https://github.com/w3c/css-a11y/issues [32] https://github.com/w3c/css-a11y/issues <matatk> PaulG: [via email] nothing to report. Actions Checkin (Specs) [33]https://www.w3.org/WAI/APA/track/actions/ open [33] https://www.w3.org/WAI/APA/track/actions/open Stock Accessibility Considerations section <matatk> matatk: I am working on this! Compute Pressure API ACs <matatk> [34]w3c/a11y-request#53 (comment) [34] https://github.com/w3c/a11y-request/issues/53#issuecomment-1540076919 <matatk> matatk: The latest in the conversation (per previous discussion). I need to write a proposed section, for us to review. Fredrik or Paul may have input as to anything I missed. <matatk> janina: One example: resource tracking in Linux/GUI. By the time resource pressure is a problem, it can be hard to access a report; having one present and accessilbe can help avoid that. Task Force & Deliverables Updates <matatk> janina: We have a lot of great work going on across the TFs! <matatk> janina: We're expecting Maturity Model's initial work to be complete about this time next year. <matatk> Fredrik: FAST TF update: Working on completing the Work Statement - [35]https://www.w3.org/WAI/APA/wiki/ Fast-work-statement - your input would be much appreciated. [35] https://www.w3.org/WAI/APA/wiki/Fast-work-statement <matatk> Fredrik: It's generally done. <matatk> janina: Let's all review the Work Statement this week - comments on the APA list or otherwise. Other Business be done Summary of action items 1. [36]Lionel_Wolberger: Review Verifiable Credentials Status List v2021 2. [37]Lionel_Wolberger: Review Verifiable Credentials Status List v2021 Minutes manually created (not a transcript), formatted by [38]scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC). [38] https://w3c.github.io/scribe2/scribedoc.html Diagnostics Maybe present: Lionel All speakers: janina, Lionel, Lionel_Wolberger, matatk Active on IRC: Alisa_Smith, Fredrik, janina, Lionel_Wolberger, matatk, mike_beganyi, niklasegger, Roy -- 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, 10 May 2023 14:57:23 UTC