Meeting minutes
Introductions, new WAI staff ! Kosi
Group updates
kevin: Quiick updates, please ...
Lisa: New schedule
lisa: Focussed on research
lisa: mental health
matatk: Nothing for APA pressing
<lisa__> coga time line
Lionel_Wolberger: APA's Adapt tackling symbols and well known destinations
Lionel_Wolberger: Need a Co-Facilitator ...
Valerie: Published fpwd of ARIA 1.3
Infoshare
kevin: Anything to report?
lisa: Notes Step A mtg coming in Norway
WAI at CSUN
<lisa__> https://
matatk: Some of APA will be attending, though likely not enough to do actual work
matatk: Interest in observing what will be going
<lisa__> this is the github i put up for them a-STEP-action/
kevin: AG not meeting -- Chairs not going
kevin: I have responsibility for organizing social event, dinner, etc
kevin: A slack a11y channel ...
#csunatc in the a11y Slack instance
kevin: Carl Groves doing some organizing
matatk: No APA mtgs ...
kevin: Lots of AG people, but unclear whether a mtg
matatk: unsure whether slack uri should be public?
IE Onboarding process
matatk: We've noted problems adding IE to APA recently -- we've had a few joins and hit several issues
matatk: Still unclear exactly what
matatk: People forward application which can take awhile
matatk: They get an email back but seem to miss they've one more step to do
matatk: When we reach out, they may actually do that step
matatk: That's the main problem, note that it's been several folks
matatk: Suggest: "Action Required: on email Subject
matatk: Phps also prepare applications that the form isn't the end, there will be additional steps when they're approved
kevin: Say more
matatk: We don't see the application process, but suggestion is to emphasis that submitting the application
. still requires time
. When successful they need to understand there's still another step from them
. Submitting isn't everything
kevin: So making the steps clearer is the need?
kevin: That would help?
matatk: yes
matatk: They get "Congrats email, but miss they need to actually join
lisa__: Could I have the steps? I don't think I know them all.
kevin: Will follow up; phps making it clearer on the application will take care of it
WG/TF pages updates
matatk: People following the joining process have noted out of date instructions ...
matatk: lots of outdated info; hard to keep up
matatk: Things like call times; WG participants is info that's duplicated
matatk: wg and tf pages should have current work pointers
matatk: the remainder should rely on W3C Groups
matatk: An explicit link for what to do to join should be in Groups
. The step to ask Staff Contact to join a TF
. New people don't realize TF inside a WG
kevin: Have been looking at how we manage pages
kevin: It's team, and not many of us
kevin: Would like to move into github
kevin: to enable chairs and facilitators to keep things updated
kevin: Also to avoid duplication between w3.org and w3.org/wai
kevin: good info to potential participants something we need to improve
kevin: Can't yet commit to timeline
lisa: What we say about the time commitment isn't always completely honest
… Some people may not join because they can't give four hours a week
… But if someone does weekly meeting plus large bit of work each month then that could be good participation
kevin: It might be that we can better present what good participation looks like but we have to recognise that being accepted as an Invited Expert does come with an expectation of participation.