– DRAFT –
Accessible Platform Architectures Working Group Teleconference

<Fredrik> +present

Agenda Review & Announcements

<matatk> https://lists.w3.org/Archives/Public/public-apa-admin/2023Jan/0000.html

janina: Reminder on the CfC Establish the Maturity Model Task Force. Deadline 23:59 Boston Time, 3. February

Accessibility for Children & Adapt call https://www.w3.org/2017/08/telecon-info_adapt

matatk: Intereseting call happen next week in the adapt time slot. 10am Boston time, monday. Main thing is about learning what the a11y for Children group is doing

matatk: ... there as similarities within this work and the work of the coga group

<matatk> https://www.w3.org/2017/08/telecon-info_adapt

<matatk> Here's some background, from the last Adapt call, about the sorts of things that the Accessibilty for Children CG is working on (with a skew at the moment towards symbols, Adapt's main work right now): https://www.w3.org/2023/01/23-adapt-minutes.html

janina: : ... we don't really know the agenda right now, however some topics are probably user scenarios for adapt-dash

matatk: ... definitely relevant work and probably a new perspective for some of us

Moving from Tracker to GitHub

matatk: We are going to move away from this self hosted w3c tools to more commodity tools

matatk: ... we are going to move to Github like the other groups

matatk: : ... to move to github to track the actions. Probably in the next 2 months

matatk: If we want to, we can move our issues from tracker to github

janina: We don't want to fall in the pit where we review something and then six months later we can't find it

<matatk> In case it's of interest, GitHub's command-line client is very cool, and with respect to issue management is very full-featured: https://cli.github.com/manual/gh_extension

<matatk> * https://cli.github.com/manual/

matatk: We have two systems right now (Wiki and Tracker) and will have two in the future (Wiki and Github). So there is no big change in this context. It will surely work out

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

Lionel_Wolberger: I still have to do secure payment confirmation spec

<Lionel_Wolberger> https://w3c.github.io/secure-payment-confirmation/

<matatk> w3c/a11y-request#50

matatk: Due date 1st of February, it has a section about a11y. So we will have to look at it

<Lionel_Wolberger> https://www.w3.org/TR/vc-data-integrity/

<janina> https://www.w3.org/WAI/APA/track/actions/2332

(Now about Verifiable Credential Data Integrity 1.0)

janina: Lionel do we see potential a11y problems here?

Lionel_Wolberger: They really want to push UI out of the scope. However it might be appropriate that the explanation of credentials are accessible

Lionel_Wolberger: Will look at it after my vacation

janina: Yeah, i think we can postpone it

(Now about again about the secure payment confirmation)

matatk: We will look at it because of the due date

Moving from Tracker to GitHub

Task Force & Deliverables Updates

janina: RQTF is starting back up

<matatk> https://www.w3.org/TR/ctaur/

janina: About the Collaboration Tools Accessibility User Requirements spec. We want to find out what requirements need to be fulfilled so that these collaborative tools are accessible

Fredrik: Are the developers of those tools involved?

janina: Unfortunately no

janina: The spec is still a bit abstract. A few specific examples would be great without naming any products

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

Other Business

<matatk> https://raw.githack.com/w3c/apa/charter-2023/charter.html

janina: I propose that we start a CfC next week about the group charter. At least we plan to

Be done