W3C

– DRAFT –
Accessible Platform Architectures Working Group Teleconference

08 February 2023

Attendees

Present
Fredrik, janina, matatk, mike_beganyi, niklasegger, PaulG, Roy
Regrets
-
Chair
Matthew
Scribe
Fredrik

Meeting minutes

<Gottfried> +present

Agenda Review & Announcements

<matatk> https://www.tpgi.com/webinar-february-14-at-12pm-et-exploring-new-accessibility-frontiers-with-tpgi-and-the-w3c/

matatk: A general announcement that Matthew is giving a webinar next week for TPGI called Exploring New A11y Frontiers, which is going to be about some of the stuff we've been working on since TPAC.

matatk: Let people know of it.

matatk: It's stuff people haven't heard of usually, W3C deep cuts.

matatk: Symbols, CTAUR, WoT, and so forth.

janina: We have withdrawn the CFC on the charter. There was a technical glitch. There were substantive misses in the CFC, so we'll have to restart that process, probably by this time next week.

janina: We have a new TF! Maturity Model is now its new TF! Join if you would, one and all.

APA Rechartering

Moving from Tracker to GitHub

matatk: A reminder: We're moving from Tracker to Github and Tracker will be frozen at some point forever. At that point, your remaining acitons will be there forever until the end of entropy. Close things, do things, whatever. Just take care of them.

matatk: If you have a11y concerns about Github and trackingthings, just let us know or ask around in your TFs.

matatk: We are aware on some concerns we're working on in the background. Several wAI groups have already made the switch, so hopefully we will be able to, too, without too much ado.

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

Roy: One new charter!

Rechartering Web Machine Learning Working Group

<Roy> - charter: https://w3c.github.io/machine-learning-charter/charter.html

Roy: Web ML learnign working grou.

Roy: Any interest in liaising with them?

matatk: This should porobably be run by RQTF, but there is the issue of ethical considerations which we want to be represented in.

matatk: We'd want to be a bit cautious with this group.

Roy: It's the Web Machine Learnign Working Group.

janina: There are multiple ways already identified that ML can get things wrong if it has an inadequate data set. Harms can result.

matatk: I wil just mention the Code of Ethics and Professional Conduct is referenced, but that ethics work we were in volved in is not.

janina: We may want to break out some a11y considerations, too. There are too many gap opportunities.

matatk: We may want to find things out to point them to between out.Unless someone in the group has some excellent resources to point to in this topic.

janina: Jutta Treveranus and Jason White are both authorities in this space.

Roy: That's all for this week.

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

Compute Pressure API

<Roy> - issue: w3c/a11y-request#53

<Roy> - spec: https://www.w3.org/TR/compute-pressure/

<Roy> - tracked: https://www.w3.org/WAI/APA/wiki/Compute_Pressure_Level_1

Roy: There is one issue from Compute Pressure API which we already looked at

Fredrik: Working on that score.

Fredrik> My Github name is fredrika11y

matatk: Right, So there is one issue with the issue tracking. People should be able to assign issues to other people in order to be able to track issues, so to speak. We'll look into it.

Fredrik: Making a note of the issue at hand.

Roy: WCAG 2.2 due 24th this month

matatk: Already on it. I'll continue.

zkaim, next item

zakim , next item

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

Roy: Nothing new here.

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

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

Roy: There are some CSS issues, from last year. Could you, Paul, look at those?

<matatk> w3c/a11y-request#29 is completed

matatk: Would you, Paul, tell us which needs looking at and we can get back to this?

Roy: My questiosn are answered.

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

PaulG: Last week's meeting didn't have any new news.

Task Force & Deliverables Updates

Maturity Model

Maturity Model

<matatk> https://www.w3.org/WAI/APA/task-forces/maturity-model/

matatk: MM is a TF!

matatk: Very exciting work, still early stages, possible for people to get in and shape the work from the ground floor as they say.

Pronunciation

PaulG: We've setled on language for our communication to AT vendors. There will be communication forthcoming to solicit the AT vendor's preferences on our options for whether or not we're trying to promote SSML or an attribute model where we are injecting SSML information into HTML with attributes.

PaulG: It makes a difference to AT vendors whether we ask browser vendors to parse SSML and move it into the AX tree. Depending on the AT vendors\ answer, we\ll either have more questions or just move along with our spec.

<PaulG> https://github.com/w3c/pronunciation/wiki/Re:-AT-Vendors

janina: The stuff that came from ARIA, probably just a digression, but perhaps even another contexutalising question for the above: would you even implement anythi8ng, or do you even feel you don't want to go to this level?

janina: We need to fish or cut bait here.

PaulG: If AT vendors came back and said that they only want to deal with pronunciation info in the AX tree, we need to work on mapping and with WhatWG.

PaulG: There still could be decisions to be made pertaining to authoring.

PaulG: The paths are very different at this point.

janina: SSML is now generally accepted by the PDA's?

PaulG: THat's par to fothe APIs for the digital systems, I believe they all use some flavour of SSML.

PaulG: It's more ubiquitous than it used to be.

janina: It's different form platform to platform, but at least there seem sto be consensus on the authoring side.

PaulG: Yes. It's still new. An AT vendor, say, NVDA, that parses the HTML or XML, they hmay have a chocie where they won't do that. Some may want ti to be part lf the cor functionality and so on.

janina: No AT left behind is good, but no author left behind is sort of also very very important.

matatk: There seems to be a lot left do sicuss.

matatk: Let's hope we can get some sort of consenssus from the community.

matatk: Anyhone who wants to can join the TF and help out.

RQTF

janina: We have good progress generally. Progress on process.

janina: The notes from today's presentation on AI, ML and that whole complex, once they're available, may be of great interest..

Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open

matatk: PSA: get your actions closed before everything is frozen!

matatk: Quite a lot fo actions open at this point, but there's still time.

Other Business

Be done

matatk: Thanks everyone! Keep up the e

matatk: All the best for all the TFs and associated work!

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

Succeeded: s/WCAG 2.2?/WCAG 2.2 due 24th this month

Succeeded: s/Las tw/Last w/

Succeeded: s/didn\t/didn't/

All speakers: Fredrik, janina, matatk, PaulG, Roy

Active on IRC: Fredrik, Gottfried, janina, matatk, mike_beganyi, niklasegger, PaulG, Roy