Meeting minutes
Agenda Review & Announcements;
<janina> https://
janina: we have a CFC running through next week
TPAC Planning https://www.w3.org/wiki/TPAC/2021/GroupMeetings
becky: once meetings are on that page as confirmed, I'm adding them to the official TPAC page
janina: apparently the whole first week is for breakout sessions but we've already confirmed several cross-group meetings in the first week so we'll leave things as they are
janina: we still have some meetings to schedule
janina: we'll possibly be done scheduling after a week or two
Task Force Updates;
janina: RQTF CFC for FPWD and a couple more documents coming behind that, not quite ready. There's a moratorium on publishing next week.
janina: personalization is in good shape but never requested an accessibility review
janina: there's an open issue with i18n and they agreed to meet before TPAC will hopefully resolve that issue
PaulG: working on edits to include in next FPWD;
FAST Progress
Joshue108: reviewing Jake's proposal. Nothing to show yet.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
MichaelC: for HTML we requested liason to APA
MichaelC: ARIAWG has done decentralized identifiers
Accessibility Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
MichaelC: nothing new to our attention
<becky> https://
<becky> https://
MichaelC: that should have shown up in closed but it didn't
MichaelC: there's nothing we need to do
new on TR http://www.w3.org/TR/tr-status-drafts.html
<MichaelC> https://www.w3.org/TR/epub-multi-rend-11/
MichaelC: rendition isn't explained
janina: they usually know their way around accessibility but they might have missed something like explaining multiple renditions
janina: they've requested we give their specs a close read before TPAC
<MichaelC> EPub specs in our tracker
janina: I'll clarify which documents need an APA review and we can start to divvy them up.
<MichaelC> Incremental Font Transfer
MichaelC: two methods to transfer portions of fonts over multiple requests
becky: I think we can skip this
<MichaelC> CSS Display Module Level 3
<MichaelC> https://
MichaelC: we have an open issue on this that has not been addressed
MichaelC: issue will be assigned to Amy
Review Requests https://github.com/w3c/a11y-request/issues
<MichaelC> https://
MichaelC: css scrollbars
JF: I personally reject the response we got from CSSWG.
<MichaelC> https://
MichaelC: we could consider it reviewed or re-review it
becky: browsers have always been given a pass on contrast issues
janina: it might be worth an accessibility note, warning of what's to come
MichaelC: I'll block it based on the thick/wide scrollbar
<MichaelC> https://
<MichaelC> https://
<MichaelC> https://
MichaelC: we also have open issues on this one
MichaelC: do we want to do a generic review or just continue working these issues
becky: Amy's always been good about following up
<MichaelC> https://
MichaelC: I'll update the permissions and assign it
MichaelC: it looks like our template was copied
MichaelC: a week ago we said we didnt' want to review it
CSS Update (Amy) https://github.com/w3c/css-a11y/issues
becky: Amy's not here for updates
IanPouncey: nothing to report that I'm aware of
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
<MichaelC> https://
MichaelC: WoT profile
janina: we'll come back to this in the next walk-through
janina: I'll let Jason and Scott know
janina: and Josh
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
<MichaelC> https://
<MichaelC> https://
janina: let's drop File API
<MichaelC> https://
FredrikFischer: I looked at it and it's too low level, it's more a technical process document
MichaelC: the note was to enhance the accessibility considerations section
FredrikFischer: I think it's out of scope
MichaelC: so, we can drop this review?
becky: I think we're good
MichaelC: for PIP we filed a comment
<MichaelC> https://
MichaelC: mitigating browser fingerprinting
<MichaelC> https://
FredrikFischer: I don't think there's anything to address
MichaelC: notifications API
<MichaelC> https://
<MichaelC> https://
MichaelC: next steps from 2017 is accessibility considerations section
MichaelC: a11y-needs-resolution will add this to our comment tracker
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
janina: we'll need to update the community groups soon
becky: do we really need to stay on top of these/
MichaelC: there's horizontal review instructions that points them to us
janina: I'll bring it up at our next meeting