Accessible Platform Architectures Working Group Teleconference

19 May 2021


becky, Fazio_, Fredrik, IanPouncey, Irfan, janina, JF, Lionel_Wolberger, paul_grenier
Lionel, Lionel_Wolberger

Meeting minutes

<becky> regrets, Gottfried Zimmerman, Amy Carney

Agenda Review & Announcements;

TPAC Planning https://www.w3.org/wiki/TPAC/2021/GroupMeetings

<Fazio_> COGA?

Lionel: APA may want to consider reminding Personalization, pronunciation, etc to clarify TPAC plans

janina: The earlier the TPAC meetings are set, the better
… APA tends to have the most cross org meetings

Lionel_Wolberger: Any other TFs/WGs to remind and coax?

becky: ZAUR, RAUR, Research questions

JF: Web Payments group, Automotive interest group. Many groups may need reminders that we are here to help

janina: True. There is a draft from Fredrik

janina: Reminding everyone, automotive asked APA what does APA want in the not-quite-fully-automated automobile

JF: Rephrasing: is there any proactive reachout that we can do?

janina: We could go from A-Z on groups that are attending TPAC. For each group we need to announce the agenda that we wish to promote with that group.
… this is why it is easier to start with TFs
… Media Groups have some follow-ups
… likely drafting a note on acceptable tolerances on audio/video synchronization, based on evidence-based research
… the above has implications for WCAG 3.0 and perhaps 2.3
… Research questions is expected to revert this answer

Lionel_Wolberger: OGC is also interesting (geospatial) though maps are quite challenging

Task Force Updates;

Irfan: pronunciation TF, the draft has been published
… now creating the proposal to submit to varioua conferences

<JF> Converences: https://github.com/w3c/pronunciation/wiki/Socialization

<janina> https://www.w3.org/blog/news/archives/9062

Irfan: also receiving feedback from COGA and others

janina: We are very interested in getting wide review of this
… text-to-speech engines do not currently have any way to assure correct pronunciation
… this work is needed

becky: Personalization continued discussion of the need for three attributes (action, destination, purpose) and the discussion is converging

janina: In Research Questions Task Force (RQTF) discussion of captions
… there were captions and live sign language on the meeting

Joshue108: Was great to have collaboration across such a broad and diverse group

David_F: A11y impact statement begun

FAST Progress

Joshue108: Next step, looking towards a survey that will go to Silver and APA

New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22

janina: postpone review until Michael is attending.

Horizontal Review Issues Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review

janina: postpone review until Michael is attending.

new on TR http://www.w3.org/TR/tr-status-drafts.html

janina: postpone review until Michael is attending.

CSS Update (Amy) https://github.com/w3c/css-a11y/issues

janina: postpone review until Amy can attend this meeting

Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned

<becky> this is the start of the payments policy thread, there were several replies: https://lists.w3.org/Archives/Public/public-apa/2021May/0028.html

janina: Discussing Payment Request API
… Fredrik's work is a good template

JF: Giving feedback: instead of 'guarantee' privilege terms like 'ensure'

<janina> https://www.w3.org/WAI/APA/wiki/Payment_Request_API

Discussion on payment methods API

<JF> https://www.w3.org/Payments/

<JF> Explainer (of sorts): https://www.w3.org/blog/2020/05/payments-and-authentication-driving-toward-a-whole-greater-than-parts/

becky: There is an a11y statement
… "For the user-facing aspects of Payment Request API, implementations integrate with platform accessibility APIs via form controls and other input modalities. Furthermore, to increase the intelligibility of total, shipping addresses, and contact information, implementations format data according to system conventions."


<becky> https://www.w3.org/TR/payment-request/#examples-of-usage

Discussion of payment, e.g., reading " Some kind of user interface will be presented to the user to facilitate the payment request after the show() method returns."

janina: APA states that you cannot duck a11y just be saying, we do not specify the UI/UX
… "in some jurisdictions you will be legally required to..."

becky: We state that our response still makes sense

janina: We need more time on this, let's continue discussion next time

becky: Looking at https://www.w3.org/WAI/APA/wiki/Permissions_Policy
… This could have a11y impacts, like disabling javascript when someone is relying on that
… they also discuss sensors: some people rely on adjusting sensors to make a personalized experience
… USB changes could affect AT users, who may be running their AT off a USB
… from web app security working group
… security has an interest in turning things off

Lionel_Wolberger: Can we make a statement like, "disabling capabiliteiies and/or devices such as sensors, interfaces, autoplay and other features may affect users relying on personalization or assistive technology. A screen reader working off a USB device could be stopped; on the other hand, a user of AT could enable their AT by auto play."

becky: To be discussed further

Minutes manually created (not a transcript), formatted by scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).


Maybe present: David_F, Joshue108, Lionel