– DRAFT –
Accessible Platform Architectures Working Group Teleconference

Agenda Review & Announcements

<Lionel_Wolberger> agenda: this

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

janina: TPAC planning proceeding well
… discussing with Silver the joint meetings planned
… Recommending COGA do a break-out session on Content Useable
… had a scoping conversation with Automotive
… Concern about mono-culture in the automobile, and coming mono-culture in Browsers with the dominance of Blink
… We should foster conversation around mono-culture, as mono-culture is proven to be less robust, less competetive, etc

<Joshue108> +1 to conversations around mono cultures and implication etc

janina: specifications generally ask for two implementations. How can there be two implementations in a mono-culture?
… APA keeps an eye on the linkage of these technologies with the UI/UX, which impacts a11y.

janina: TPAC invitations on their way out, the old boilerplate templates help it go smoothly

Task Force Updates

janina: Research Questions is almost "there" with XR
… synchronization spec looks on target for Sept.
… COGA is considering a 1 or 2 day meeting at TPAC

Joshue108: COGA is recruiting for a mental health issue paper

FAST Update

Joshue108: FAST rec'd survey results, and is working on functional needs in the Silver TF sub-group
… Rec'd a proposal from Jake on how to work out existing user requirements and gaps, which looks mature and helpful

<JF> a "what" list?

Joshue108: Reviewed the purpose of FAST and how it will be applied to specification gap analysis

janina: Related, W3C is weighing the hosting of a registry, to allow normative reference to non-normative registries (such as schema.org)
… as many W3C groups often find a need reference non-normative registries (e.g., recent discussion in Pronunciation)
… Web accessibility-wide glossary being considered
… to provide consistent definitions and terms

<JF> https://schema.org/docs/howwework.html

JF: John does want us to know, schema.org does have a process and is not just a "wiki"
… it is a bit more tightly locked down than has been suggested today

<janina> https://www.w3.org/Consortium/Process/Drafts/#registries

janina: The above is the registries draft document under consideration

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

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

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

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

MichaelC: DOM review, DOM Review Draft — Published 21 June 2021

paul_grenier: I can take a look.

MichaelC: You can focus on changes, start in the change log

IanPouncey: I can help

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

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

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

<MichaelC> https://www.w3.org/WAI/APA/wiki/Picture-in-Picture

<MichaelC> https://github.com/w3c/picture-in-picture/issues/179

MichaelC: PIP seems very similar to second/multiple screens
… will suggest we meet to discuss issue #179

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

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

MichaelC: We have been meaning to speak with Notifications API
… e.g., important to be able to shut off all notifications (not go item by item)
… Do Not Disturb is an accessibility issue; also a COGA issue (no distractions)