- From: Janina Sajka <janina@rednote.net>
- Date: Wed, 9 Dec 2020 13:00:55 -0500
- To: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Minutes from the APA teleconference of 9 December are provided here as text. They're available in hypertext at: https://www.w3.org/2020/12/09-apa-minutes.html W3C - DRAFT - Accessible Platform Architectures Working Group Teleconference 09 Dec 2020 Attendees Present janina, Matthew_Atkinson, \, JF, paul_grenier, IrfanA, joconnor Regrets Gottfried_Zimmerman, Amy_Carney Chair becky Scribe janina Contents * Topics 1. Agenda Review & Announcements 2. APA Rechartering Begins -https://raw.githack.com/w3c/apa/charter-2021/charter.html 3. Task Force Updates 4. New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22%22 5. new on TR http://www.w3.org/TR/tr-status-drafts.html 6. Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open 7. Horizontal Review Issues Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review 8. Other Business 9. be done * Summary of Action Items * Summary of Resolutions ___________________________________________________________________________________________________________________________________________________________________________________________________________________ <scribe> scribe: janina Agenda Review & Announcements bg: Notes John Foliot is back, and we're welcoming him back ... Reminder, we meet the 16th, and then take two weeks off--23rd and 30th. ... Any other? ma: Q: Are we reviewing ARIA 1.2 js: Recalls APA passed on review, but if Matthew has issues, please advise. ma: Will check bg: Notes we feel fairly comfortablee with ARIA being OK. ... And they should have addressed open issues on way to releasxe APA Rechartering Begins -https://raw.githack.com/w3c/apa/charter-2021/charter.html bg: Need to get on this because we want to finish in January ... We need TFs with rec track deliverables to specify what those are mc: For us this is Pronunciation and Personalization -- and I'm not up to speed ... So, if others could update those, it would help very much. ... There is a specific template for deliverables: <MichaelC> https://raw.githack.com/w3c/apa/charter-2021/charter.html mc: Scroll to Normative Deliverables ... template at the end with the required items ... Can do PR on this branch bg: will be on Personalization call Monday pg: Will add to agenda notes for Pronunciation bg: Anything the group should work on together? mc: Please look at other deliverables, eg. note track docs, etc ... Also bullets in Success Criteria section jf: Sees old dates -- Reauthored, yes? mc: Yes ... RAUR and XAUR should be added to other deliverables jf: Suggests we call out our RQTF, because it's worth advertising it mc: That's for our Home Page, more than for our Charter jf: Seems our TFs should get mentioned mc: You're welcome to create a PR ... I'll help with tidying up, but don't want to be the bottleneck Task Force Updates ia: Only Pronunciation update is we're trying to setup with Epub for examples to include in our docs ... Paul and Mark both working on the two approaches we're publishing with our FPWD bg: Personalization still plugging away at issues on Module 1 ... ... Also important to note we need more people in the TF ... Especially from potential implementers jo: We were working through github issues against the RAUR ... A very productive meeting ... Esp deaf and hearing; and multiple atomic display options ... Some exciting items coming for next rev ... There's new updted RAUR on TR page ... We need a sign off from XR if OK; otherwise we move to NOte New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22%22 mc: A new charter for Math on web pages ---- ... Some people we know involved --- <MichaelC> https://w3c.github.io/charter-drafts/math-2020.html mc: as 1st class citizen ... Liaison statement to APA [Agreement to sign off] new on TR http://www.w3.org/TR/tr-status-drafts.html <MichaelC> CSS Conditional Rules Module Level 3 mc: Last updated 2013 -- now CR snapshot ... We don't know whether or not there are issues, but need a check ... MQ support, if a11y values included could be positive mjs: Suggests Amy! <MichaelC> ACTION: carney to review CSS Conditional Rules Module Levels 3 and 4 <trackbot> Created ACTION-2272 - Review css conditional rules module levels 3 and 4 [on Amy Carney - due 2020-12-16]. <MichaelC> action-2272: https://www.w3.org/TR/css-conditional-3/ <trackbot> Notes added to action-2272 Review css conditional rules module levels 3 and 4. <MichaelC> action-2272: https://www.w3.org/TR/css-conditional-4/ <trackbot> Notes added to action-2272 Review css conditional rules module levels 3 and 4. jf: Notes Priv/Security section in the doc ... Had we not asked for standard a11y section mc: It's an ongoing conversation; no resolution <MichaelC> action-2272: https://www.w3.org/WAI/APA/wiki/CSS_Conditional_Rules_Module_Level_3 <trackbot> Notes added to action-2272 Review css conditional rules module levels 3 and 4. mc: We can ask, if we think it's relevant <MichaelC> action-2272: https://www.w3.org/WAI/APA/wiki/CSS_Conditional_Rules_Module_Level_4 <trackbot> Notes added to action-2272 Review css conditional rules module levels 3 and 4. jf: We could say, concern, or no concern -- and that's valuable <MichaelC> close action-2241 <trackbot> Closed action-2241. <MichaelC> CSS Custom Highlight API Module Level 1 bg: Amy already noted this one <MichaelC> ACTION: carney to review CSS Custom Highlight API Module Level 1 https://www.w3.org/TR/css-highlight-api-1/ <trackbot> Created ACTION-2273 - Review css custom highlight api module level 1 https://www.w3.org/tr/css-highlight-api-1/ [on Amy Carney - due 2020-12-16]. <MichaelC> RTC Accessibility User Requirements js: We'll review as our pub process <MichaelC> The MerchantValidationEvent interface js: lowlevel -- no review <MichaelC> WebXR Layers API Level 1 bg: Might it be important for pwd to say: "I need X"? <MichaelC> action-2273: https://www.w3.org/WAI/APA/wiki/CSS_Custom_Highlight_API_Module_Level_1 <trackbot> Notes added to action-2273 Review css custom highlight api module level 1 https://www.w3.org/tr/css-highlight-api-1/. js: Suggesting auto limiting to the essentials could be an a11y feature bg: Lots of rendering options ... But is this low level, or higher UI layer? pg: This sounds like the A11y Considerations Note <MichaelC> ACTION: joshue to review WebXR Layers API Level 1 <trackbot> Created ACTION-2274 - Review webxr layers api level 1 [on Joshue O Connor - due 2020-12-16]. <MichaelC> action-2274: https://www.w3.org/TR/webxrlayers-1/ <trackbot> Notes added to action-2274 Review webxr layers api level 1. Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open pg: Have update ... 2270 action-2270? <trackbot> action-2270 -- Paul Grenier to Review webauthn 2 https://www.w3.org/tr/webauthn-2/ -- due 2020-12-09 -- OPEN <trackbot> https://www.w3.org/WAI/APA/track/actions/2270 <MichaelC> action-2274: https://www.w3.org/WAI/APA/wiki/WebXR_Layers_API_Level_1 <trackbot> Notes added to action-2274 Review webxr layers api level 1. pg: some concerns and some questions, not all a11y ... notes again a priv/sec, but no a11y ... we might recommend not forcing a particular interface, eg. biometric ... some sort of thing that helps authenticate ... affordances for different pwds, but also timing ... they mention timing -- but wording is problematic ... q on phrase "special needs" ... allowing revocation of keys should be an RFC2119 MUST, not just SHOULD <Zakim> JF, you wanted to note that this spec currently doesn't reference RFC 2109 (MUST, SHOULD, MAY) jf: Good catch on must vs should pg: Fido Alliance points to 2119 <paul_grenier> https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-security-ref-v2.0-id-20180227.html jf: Suggest bringing the must concern to this doc and getting the group to elevate theto 2119 must bg: XRlayers should specify should recommend elevating ma: appreciate the thorough review ... <Zakim> MichaelC, you wanted to separate individual comments from APA comments ma: A bit confused ... back to XR layersmc: Noting possibly a11y comments and non a11y comments mc: Suggest identify which are which; reviewer can respond on non a11y; and apa on a11y ma: Back to XRlayers ... ... looks like layer is chosen is a direct result of the output device being used ... ... They have an explainer <Matthew_Atkinson> https://github.com/immersive-web/layers/blob/master/explainer.md Horizontal Review Issues Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review mc: Nothing Other Business be done Summary of Action Items [NEW] ACTION: carney to review CSS Conditional Rules Module Levels 3 and 4 [NEW] ACTION: carney to review CSS Custom Highlight API Module Level 1 https://www.w3.org/TR/css-highlight-api-1/ [NEW] ACTION: joshue to review WebXR Layers API Level 1 Summary of Resolutions [End of minutes] ___________________________________________________________________________________________________________________________________________________________________________________________________________________ Present: janina Matthew_Atkinson \ JF paul_grenier IrfanA joconnor Regrets: Gottfried_Zimmerman Amy_Carney Found Scribe: janina Found Date: 09 Dec 2020 People with action items: carney joshue -- Janina Sajka https://linkedin.com/in/jsajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Received on Wednesday, 9 December 2020 18:01:12 UTC