Meeting minutes
<janina> Meeting Accessible Platform Architectures (APA) Weekly Teleconference
Agenda Review & Announcements
janina: Paul is now formal liason to CSS, we have added CSS status onto our regular agenda.
Janina: group leaders Noted that we need to review standard tooling and how we track horizontal reviews
Janina: no additions from others for agenda
janina: reminding folks about changing of the clocks - Europe first and then US; not sure about other areas of the globe. See dateandtime.com to see magnitude of changes across time zones. Have trouble accommodating all of the time zones.
janina: for one week we are out of sync for europe and UK with US by one hour
CfC Reminder https://lists.w3.org/Archives/Public/public-apa-admin/2022Oct/0008.html
<Fazio> COGA wants to object until our comments are in
<Fazio> Lisa remembers us being given till end of October
janina: reminds folks about cfc for collaboration tools usability requirements. Process requires that we file objections but don't require full consensus. COGA has requested that we not publish until they have added comments but we have given them extra time. There is an impact of not publishing now - if not we won't publish until January and February. We will still include COGA comments. Are trying to mediate this disagreement. Will add a note
that publication is a solicitation for comments. We will add additional comments as necessary and can republish based on additional feedback.
janina: The note has been forwarded to the APA admin list. Do need more votes in order to move forward so please review.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
roy: No new charters
A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
Web of Things (WoT) Architecture 1.1
<Roy> - TR: https://
<Roy> - issue: https://
<Roy> - tracking: https://
<Roy> - ping: Horizontal Review for CR
roy: web of things architecture 1.1 - going to CR and requesting horizontal review
roy: review of this doc. was assigned to Janina
Janina: I am overdue, I don't believe I am the best person. Will try to get someone else to look at or will look at it in next few weeks. RQTF did meet with Web of Things - they are eager to work with us.
<matatk> Details of our meeting with WoT just before TPAC: https://
janina: our previous conversations have not found issues with architecture and api but do have some additional user requirements
janina: Happy to take help with someone else to review this
<PaulG> I'll send some notes for anything I pick up on a quick read. Lacking any accessibility considerations section is at least a warning sign.
matatk: Meeting with Web of Things was very helpful. Did happen before TPAC but was "associated" with TPAC
janina: we need to get minutes from that meeting into our wiki
janina: Gottfried and Niklaus have experience in this area and I will ping them
new on TR http://www.w3.org/TR/tr-status-drafts.html
roy: no new on TR
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
roy: nothing prepared
Spec Tracking Wiki Reminder https://www.w3.org/WAI/APA/wiki/Category:Spec_Review
matatk: we have different systems for tracking items; Sharing screen...
matatk: sharing screen from wiki, Category:Spec Review; started a long time ago, Janina confirms it was started in 2015
matatk: This system worked nicely as you can put link to a spec into more than one category; Goes to EPUB 3.3 page in wiki and it displays the categories as well as link to spec and timeline of activity on the spec
matatk: also demos WebXR Gamepads Module level 1 to review the activity and links to any comments, etc
matatk: there is a "paper" trail for all of our reviews and activities in our wiki
matatk: since it is in the wiki, anyone can modify and update as perform activities
janina: this is a very useful tool but it relies on being updated as action happens but everyone has to help
janina: looking for ideas on how to solve issues when a spec has changed its name; Thus sometimes we don't realize we have reviewed something when we did review it on under another name
<matatk> https://
matatk: notice that in this meeting Roy posted a request to review Web of Things architecture - (shares that page on screen). Switches to A11y Review comment tracker to show the request for our review via github. We need to post the outcome of our review into that github issue.
matatk: group that needs an apa review creates a github issue in their repository with a tag that flags it for us to review which generates the a11y review request
matatk: any actions that are created during an apa meeting get logged into our older action tracker
matatk: you don't have to use the tracker system but some people pefer an action that they can track. Groups that request a review need us to track results in github
<janina> http://
janina: if you only want to see your own actions, use the url above
janina: will show you all actions for all groups you are involved with
CSS Update (Paul) https://github.com/w3c/css-a11y/issues
<PaulG> https://
PaulG: there was an issue with lang selector and how * worked;
<PaulG> https://
PaulG: ruby annotations issue (above)
<PaulG> https://
PaulG: adding open and closed as pseudo selectors for items - popup api and dialogs
<PaulG> https://
<PaulG> https://
PaulG: putting out the idea of reordering columns in tables; we know from flexbox reorganization this can be an issue. spatial navigationapi was brought up; We lost track of that review in 2019
PaulG: also issues about focus group - neither of these have any info in the comment tracker but some in the wiki
PaulG: so this is something we have lost track of
janina: loss spatial navigation issue tracking, we did have a meeting about this with CSS at TPAC in Japan; I found those minutes and we should add that into tracking and follow up
janina: I went back through agendas via mail archive and looked for Amy's name (previous CSS liason) to find open items
matatk: good to follow up on spatial navigation; On some of the issues Paul shared above, there is a closed label, what criteria to they use for closing?
<janina> Sapporo 2015 TPAC meeting on spatial nav: https://
PaulG: after only one meeting, the CSS team brings it up, discusses, and takes action or continues to investigate
janina: new process started with protocols and Formats WG was broken up; ARIA was previously a task force and became a working group; APA WG was created to continue other PF work
janina: this change to PF WG to create APA set up many of our current policies and practices; for example decision process; This came from HTML WG as they needed a formal process to deal with arguments, etc. and reaching consensus
PaulG: there is a 3 hour CSS meeting next week so I will miss this meeting; Spatial navigation is up for discussion as well as many other items
janina: so thankful for Paul taking on CSS
Task Force & Deliverables Updates
janina: can skip this item unless something important to discuss
Other Business
<Roy> https://
janina: Judy Brewer announced her retirement this morning; It will take place relatively soon and she will be going part time. Look for that announcement, it will likely get wide publication throughout W3
Roy: shared link of blog post where announcement was made
janina: there is an interim replacement, Michael Cooper, and there is new position in europe, Kevin
<Roy> https://
<Roy> https://