Meeting minutes
FYI next week is annual staff "Geek Week"; reduced availability for regular meetings
judy: reminder once a year, W3C staff have option to focus on a project, project planning, writing
… team contact may be less available than usual
janina: publication moratorium?
judy: yes
Auto-Timestamping W3C Documents?
judy: janina sent context earlier
janina: date documents for major updates
judy: additional context - technical reports are date stamped. is it wiki pages that have no date?
janina: COGA work statement had been updated
judy: that is a wiki page and should have a footer that forces time stamp, but see copyright 2018 but no date stamp
… could be the last redesign may have suppressed date stamp
janina: would like every page to have a date stamp. Would be useful over time.
judy: a site update may update date on each page. May not be good.
janina: would be better than not having a date at all
<Zakim> Judy, you wanted to ask permission for live transcript
jeanne: would prefer to avoid machine updates. Has been problematic in github when docs get a date refreshed when no changes made.
james: agree to avoid machine updates. Aria practices have no date indication.
judy: will follow up with Shawn
Scheduling WAI-Wide Glossary conversation during TPAC
FYI Publishing Open House https://lists.w3.org/Archives/Public/public-wai-cc/2021Sep/0000.html
george: can send invitation for Sept 4
… will have speakers from business, community, working group to update on publishing at W3C.
… publishing and document accessibility interest. all publishing content
janina: videos?
george: embedded videos are in scope. Sync'd media also in scope. If not embedded, maybe not in scope.
judy: has this open house been effective to give people an informal check in?
george: this is the second time. first time we surveyed, had many misunderstandings and confusion. Accessibility was very confused.
… putting videos up in advance this time. very active in higher ed.
judy: are other groups struggling with energy/morale?
george: project Gutenberg started in the 80s. open educational resources mandated by states are flying under radar of accessibility.
judy: are groups struggling with participation?
james: it's hard making progress when everyone has many jobs and hats and finding time for optional work
judy: a refresh function is ordinarily part of a conference. would it help for each group to talk about what you're doing?
james: I don't think so
<Judy> [JB why Pubs are necessary for Publishing]
jeanne: another online meeting would not help.
<Zakim> jeanne, you wanted to say that the problems getting task force work approved by main group. Part of the problem may be the lack of bar conversations
george: trying to recruit and nurture people who come to W3C community. Not aware of irc, zakim, how to get involved. Need some younger people in WGs who are energetic.
judy: if I did a written update on WAI and how to get involved, maybe a blog, would something written help?
kim: husband's company sent chocolate. What about a virtual pub with real beer?
<Judy> [JB appreciates the suggestion!]
<jeanne> -1 too many of those, too.
kim: something informal, and maybe interest younger folks
janina: can interns be in wg?
judy: appreciate ideas
Publication announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
<janina> https://
janina: APA has CFC out. looks promising. Hope for fpwd in late Sept.
… if video and audio are out of sync, very problematic
janina: we have scheduled joint meeting with timed text
… hoping to publish week after next.
judy: give Shawn at least normal lead time to review announcements
janina: Personalization Task Force in CR by end of month. Announcements in process.
… one issue remaining with Internationalization. They meet with us on Monday.
george: User experience guide will wait until after moratorium.
… announcements still pending
judy: are you updating announcement page?
janina: yes, with Josh
Any new documents in your WG or TFs to let other WAI WGs or TFs know about?
james: not new but talking with SVG. They seem to be in agreement.
… to take over SVG Accessibility API Mapping (AAM)
george: announcements page also for CG reports?
janina: it's on our joint agenda for TPAC. got a lot of questions.
judy: when CGs were established about 8 years ago, one caveat is not to assign staff time. Over time, exceptions made to provide an essential bridging function.
… something lightweight/informative could go on announcements. Chat with Shawn.
janina: how to normatively reference registry in W3c spec?
george: this is a WG issue and good question.
judy: there may have been a process change.
… will ask Ralph
TPAC accessibility question(s) carry over from last year
judy: sounds like planning for TPAC is coming along. Opportunity to propose sessions for the next few weeks.
… feedback on virtual TPAC from last year. Heard the format was confusing, help section hard to find. Other feedback?
judy: yes
<jeanne> https://
becky: add it to the wiki table, which is difficult
becky: I've only been doing breakout meetings. Don't think format is different.
judy: sounds good josh, coordinate with Michael?
judy: TPAC help issue, people didn't see it as I recall.
becky: where is value of checking all the CGs, tedious to check.
judy: felipe had a data scrape to help monitor
becky: yes, helpful, but where's follow up? what is purpose in monitoring?
judy: threshold case - in CG brewing a technical standard that may impact accessibility. This is outside of horizontal review requirement so no feedback on accessibility.
janina: sometimes no additional follow up and that may be the breakdown
becky: going through charter would get the review. are you saying to get to them sooner?
judy: yes, before mature substantially.