Accessible Platform Architectures Working Group Teleconference

09 June 2021


amy_c, becky, COGA, COGA is trying to lock down research methodology for mental health, down, Fazio, for, Fredrik, Gottfried, health, is, janina, JF, joconnor, JonnyJames, Joshue, Joshue108, Lionel_Wolberger, lock, mental, methodology, paul_grenier, research, stevelee, to, trying
Amy, Ian, John

Meeting minutes

Agenda Review & Announcements

Janina: stock agenda, hearing no additions

Gottfried: Accessible input methods for gaming master's thesis candidate is presenting on this on Friday, June 11 - free webinar

<Gottfried> Free webinar on accessible hands-free input methods for a serious VR game on Fri at 3pm CET: https://digitalisierung.hdm-stuttgart.de/barrierefreiheit/2021/06/07/webinar-accessible-hands-free-input-methods-for-a-serious-vr-game/

see details in apa mailing list: https://lists.w3.org/Archives/Public/public-apa/2021Jun/0012.html

Janina: definitely interest from RQTF with respect to XAUR

Gottfried: looking into digital accessibility in learning environments in August in relation to VR

paul_grenier: asks about the video from previous presentation by one of Gottfried's students

Janina: we are making progress on posting the video, just need to get it stored in W3C space

TPAC Planning https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2021

Janina: starting to figuring out other groups we want to meet with at TPAC - we need a specific topic


Janina: please remember that TPAC is a great time to meet with other groups to share information and to get their engagement in promoting our notes and specifications

Fredrik: asks about how meetings work

Janina: before COVID it was Face to face meetings; was virtual last year and will be again this year in October

janina: 2 types of meetings - some with other working groups and also general meetings that W3C sponsors. Can have longer meetings concentrated on a specific subject that needs in-depth discussion (longer than a standard one hour meeting)

janina: usually a 3 year cycle of meetings in europe, north america, asia locations

Task Force Updates

janina: RQTF is going crazy with many topics; making progress, and continue to have wider participation in the group - this is great!

janina: still hoping to close xaur by the end of the month;

janina: Pronunciation is waiting for additional feedback, deadline for feedback is next week; working on conference proposals

janina: personalization making steady progress; Lionel_Wolberger has accepted position as co-facilitator with Sharon Snider, Lisa has stepped down

Fazio: working on position paper and research about anonymized study as some people don't want to give up info

Janina: suggests there is formal guidance on this within the US and folks on RQTF that might be able to help

FAST Progress

Joshue108: There is a survey out for APA and silver participants; Please respond as soon as possible so we can start working on it right away


MichaelC: will be out for next few weeks, back on June 28

Joshue108: survey is open until June 30

Janina: encourages everyone to participate in this survey, it will guide our work as well as silver and how guidelines are tested

janina: it will help drive our horizontal reviews; we will likely follow the same procedure that internationalization uses - have groups complete a form to get started

janina: will help drive getting instructions for groups to include accessibility within specifications

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

<MichaelC> https://w3c.github.io/charter-drafts/2021/svg.html

MichaelC: SVG draft charter

MichaelC: SVG 2 and SVG accessibility api mappings

<Lionel_Wolberger> The last work on these API mappings, https://www.w3.org/TR/svg-aam-1.0/#:~:text=SVG%20Accessibility%20API%20Mappings%20(%20SVG,accessibility%20in%20their%20user%20agent.

Janina: there are some api mappings - some confusion about who owns mapping - ARIA or SVG

MichaelC: has a liaison statement with ARIA and API

Janina: no issues

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

MichaelC: WebGPU - we talked about this last week; Phillippe suggests this is not an apa issue and advises closing

Janina: group agrees to take Philippe's advice - close

<MichaelC> https://github.com/w3c/csswg-drafts/issues/5927

MichaelC: APA is ok with the disposition but wants to see test results demonstrating keyboard accessible collapse / expand.

<MichaelC> Issue closed but APA keeping the mirror one open, we want to see the test results before closing this.

<MichaelC> https://github.com/w3c/miniapp/issues/166

additional horizontal review items

MichaelC: Mini apps wanted review of comment about exposing accessibility tree for mini apps

Joshue108: Roy and I are due to talk about mini apps next week so can take this up then

janina: pronunciation is finding that expressing details of pronunciation may need to be incorporated in accessibility api - not the same issue but elevates the need for a11y api discussions

<MichaelC> https://github.com/w3c/a11y-request/issues/7

MichaelC: wide review requests from performance timeline

MichaelC: we did look at the spec and decided not to review

janina: this is a spec that collects data on how well applications are performing

Fredrik: perhaps should consider that AT can have an impact on performance

Fredrik: as academic would like to see whether or not AT was in use should be part of the data but that brings up data privacy issues

<MichaelC> https://w3c.github.io/performance-timeline/

Action: Fredrik to review the Performance timeline https://w3c.github.io/performance-timeline/

<trackbot> Created ACTION-2293 - Review the performance timeline https://w3c.github.io/performance-timeline/ [on Fredrik Fischer - due 2021-06-16].

<Fredrik> Concernsus, perhaps?

Lionel_Wolberger: is there a worst case example of how info about AT use affects privacy

janina: provides example

<MichaelC> https://github.com/w3c/a11y-request/issues/6

MichaelC: CSS counter styles

<MichaelC> https://drafts.csswg.org/css-counter-styles-3/#changes-2017

<MichaelC> https://www.w3.org/WAI/APA/wiki/CSS_Counter_Styles_Level_3

MichaelC: requesting a review of this draft; we are actively reviewing

janina: suggest assigning to Amy; Lisa Seeman also had interest several years ago

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

<MichaelC> Audio EQ Cookbook

MichaelC: audio EQ cookbook

MichaelC: this is a note that was published without review- is adapted with permission from a published text

janina: this was discussed at RQTF there is a concern about triggering seizures

Janina: need to raise concern that a note was published without APA horizontal review

Janina: there is a concern about visual stroking triggers that may also exist in audio

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

<MichaelC> https://lists.w3.org/Archives/Public/public-apa/2021Apr/0013.html

MichaelC: permission policy is still dangling - believe we had several comments

MichaelC: spec deals with what content features should be allowed within the browsers;

MichaelC: if we have concerns we need to provide a specific accessibility example

MichaelC: I understand that this mostly a security issue

becky: believe that others in this group were also looking into this, perhaps JF?

Janina: believe we have use cases

<Lionel_Wolberger> +1 to making auto-play of audio "defeatable"

Lionel_Wolberger: reviewed media stream content hints; spec offers api to hint to user agent on what to expect from the media track

janina: needs more time

Lionel_Wolberger: please review comment on list


Lionel_Wolberger: choices between video getting blurry or skip frames when "gets behind". there are certainly accessibility concerns

Summary of action items

  1. Fredrik to review the Performance timeline https://w3c.github.io/performance-timeline/
Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).


Maybe present: MichaelC