Meeting minutes
Agenda Review & Announcements
TPAC planning: we need your input
<MichaelC> https://
<MichaelC> https://
Matthew_Atkinson: The APA chairs will work to understand and coordinate meetings that the TFs want to have with other groups
… TFs to provide feedback by the 18th
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
<MichaelC> https://
<MichaelC> https://
Matthew_Atkinson: We agree to do the pull request.
… MichaelC will do it. Perhaps wait for them to merge it before close and sign off.
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://
MichaelC: There are implications for Chinese, may want to wait for Roy.
Matthew_Atkinson: Agree.
<MichaelC> https://
<MichaelC> https://
becky: This looks really low level to me.
<Fredrik> Does a new spec, which, due to it's not having been picked up yet, doesn't dangle, slither?
<Fredrik> Fredrik
<Fredrik> scribe> Lionel_Wolberger
janina: This reminds us about concerns regarding headings. We are interested in 'transforms downstream'
… accessibility often depends on transformations downstream, and this is an old issue that we have planned to have out with HTTP for a long time
Matthew_Atkinson: That seems a larger issue than this baggage header spec
Lionel_Wolberger: Agree it's out of scope
… would add that JS is transformations downstream
janina: And activity at the edge
janina: This conceern with HTTP header development may require a conversation with IETF
… W3C has a formal relationship with IETF, and we often meet at TPAC. There is coordination
Matthew_Atkinson: Propose we pursue this 'HTTP transformations' issue
MichaelC: So we agree no review on 'baggage'
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
<Joshue108__> Here is my WebXR layers API comment/question https://
FAST and Maturity Model Deliverables Update
<MichaelC> https://
MichaelC: PR to incorporate functional needs developed in the Silver group (now being moved into APA) to icorporate into the FAST
… this removes the list of user needs that was there before
<Matthew_Atkinson> Note for new members: FAST === Framework for Accessible Specification of Technologies (more info at the other end of the link MichaelC put in above)
janina: Maturity Model is actively meeting, trying to cleanup the Google doc, driving for FPWD for review
… for those interested in Maturity Model, send a request to public-apa-chairs@apa.org
… This will add you to RQTF, which is the umbrella TF for this Maturity Model work
Task Force & Deliverables Updates
RQTF update
janina: Remote meetings guidelines has rec'd great comments and is being shared
RQTF update
janina: Remote meetings guidelines has rec'd great comments and is being shared
pronunciation
janina: Problem statement being written regarding outreach to i18n and IETF
… regarding pronunciations need for a specification regarding TTS
… seeking the ability to specify characteristic of the spoken: juvenile v adult, gender, time-based language specifity, example Chaucerian English v conntemporary english
… the existing specs are orthographic, and lack ways to specify these characteristics
Personalization (aka Adapt)
Lionel_Wolberger: We are anticipating adopting the new name of Adapt [CfC still open! -scribe]
Lionel_Wolberger: We closed issue #144 which occupied us for a long time; discussed with i18n.
Lionel_Wolberger: We have taken on some additional actions around clarifying the symbol attribute (having only one symbol attribute value, for simplicity).
janina: I'll tell the team to expect CR by end of May
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
Lionel_Wolberger: I was able to get back to i18n about the glossary. You have to understand why the words that are there are there.
Lionel_Wolberger: They have a focus on time, calendar, reading and writing.
Lionel_Wolberger: Emphasis on orthography and typography—on sight-based reading. The glossary misses languages such as sign and symbol languages. Can't blame them for not putting things in the glossary that aren't often discussed in the specs.
Lionel_Wolberger: Close to completing my review. In line with what we do in personalization, it'd be great if oral-/aural-based reading be included.
janina: I can help write up a note on that; can add to conversation at TPAC. Can give them time to work on it.
Lionel_Wolberger: I'll add terms we'd like to see (and would be great to refer to them).
janina: +1; we'll need to chat at TPAC.
Lionel_Wolberger: Was looking at ways to go beyond, to cognitive concerns; this may be over-reaching.
janina: ASL/*SL is gestural; there is an ISO spec for *SLs.