W3C

- DRAFT -

Accessibility Education and Outreach Working Group (EOWG) Teleconference

17 Nov 2023

Attendees

Present
kakinney, BrianE, Michele, shawn, Laura, Len_B, Sharron, Jayne, Mark, Lucy, Frankie
Regrets
Jedi
Chair
SV_MEETING_CHAIR
Scribe
Sharron

Contents


Github Training

<MarkPalmer> +1 to recording

<shawn> EOWG Participation Info

<shawn> Comments section : https://www.w3.org/WAI/EO/wiki/EOWG_Participation_Info#Comments

<shawn> EO "team" in GitHub https://github.com/orgs/w3c/teams/wai-eo

<scribe> scribe: Sharron

EOWG To Do

KrisAnne: In the agenda find links to in progress projects. We've been working to get them finished as required by the current charter. High priority. We also have a library of resources that have been published for a long time and need updated. We want to talk about what we have and if we take a step back and rather than startiong new resources, we review and update the resources we have.
... as well, let's hear from you about how you like to work - alone, in groups, in pairs? For example, the work that Jayne has =done has been invaluable - the updates to the HPWDUW. So we want to discuss, as we have new members, how do you use and recommend resources, what updates are you aware of, how you would like to contribute to making them, etc? Let's talk about all this?

,,,we re not signing you up for anythinbg today but just want to ehar?

Len: The pages you are the HPWDUW and especially the user stroies, It short cuts our office work, it has the authority of the W3C, means we don't have to re-invent. I am starting to see deeper value in Tutorials and expect to use them more.
... I am willing to work with etech staff, work alone, work on committee - willing to do all that.

Brain: One of the things we have talked about in planning meetings is whather to revitalize the community group which allows participation by people who are not employed by member orgs. We could see an EO particpant make their own small committee to join the community group with people who may not be W3C mebers but could work within the community group, with a liaison to EO.
... sub-groups do major part of work and it comes to EO for review and approval.

Len: A collegue of mine is working with COGA and has asked for support from EO - that could happen within the community group.

KrisAnne: Until I became co-chair I was liaison with COGA and we need to continue to do that collaborative effort with other groups early in their process. We have had that kind of unfortuante timing issue with groups in the past where we are brought in later in teh process and there were inconsiditancies in tone and approch that could have been addressed if we has collaborated sooner.

Frankie: I joined to create content. I would be perfectly happy if you gave me a list of content that needs updating, writing, editing, media editing. I can do any of it and happy to do it while on the road.

<kakinney> https://docs.google.com/spreadsheets/d/13XC9su-Xc7Yyl7Ke0KOcxXfafp1nn8e2Y1GoS0esP8g/edit#gid=315849256

Brian: The Google doc identifies resource status and indicates the processes needed for update.

Shawn: As for video editing, please be in touch so we can arrange that - it would be quite helpful.

Franki: I also do graphics, and writing.

Shawn: SVG?

Frankie: That would be a reach, maybe cleanup but not creation.

Shawn: Yes that is the task - cleaning up SVG files.

Len: No graphic skills here, but can edit text, video, audio. I am here to help in any way needed.

s/yest/text

KrisAnne: Take a look at the Google sheet and sign up for tasks

Brian: (shares screen with doc) If I go a linked page and use the GitHub repo link, can see the open issues and if you have the interest, you can help resolve and even take ownership over this area. Can move the issue forward to the point of rewriting and resolving some of this big backlog of issues.

Shawn: Can you think about coordinating the work so that we have a clear process of claiming an issue, addressing the task, it will be a coordination between the EO Chairs and the prvious editor. Making sure we have the bandwidth to fully process the effort.

Brian: The first thing of course is to find something that you are interested in and then coordinate as Shawn said with Chairs to be sure we are in sync on how to proceed. We will help you prioritize.

Michele: I appreciate the Chairs asking us to step up. Do you want to hear about our skill, sign up - how do we help you, what is the process?

KrsiAnne: I am thinking that a survey to ask for skills and interests. If you are happy to be assigned something, it would be great to know what your skills and highest interests are. I appreciate that Michele. As we continue the chartering process, we want to be sure we define what we exepct to do over the next chartered period.

Lucy: Can you share the resource list with me since I'm struggling finding the current projects

Shawn: Lucy, we have a dedicated resource to help with translations through the end of the year - if you know anyone else who may be interested in translation, now is the time.
... they may not need to join a group and handle it separately - please let people know that anyone who can translate in any language is highly welcome.

Brian: To wrap up, we want to get a better idea of people's interest, avaialbility, skills to contribute - will ahve a survey for that.

KrisAnne: Current survey addressing second interation the list of accessibility courses, things that we had posted in GitHub have been addressed.

Laura: I looked this morning and there is a serious break, been flagged and untilmthat major problem is addressed, we really can't publish.

KrisAnne: I will let Leticia know.

Laura: If it is a preview issue, that is a problem too.
... we need to test fundtion before we post for Approval to Publish

Brian: That's all for today

Laura: And Happy Thanksgiving to those in the US

Brian: yes, Happy Thanksgiving to those in the US, everyone else will ahve a quiet day. No meeting next week.

Shawn: Safe travels to all who are traveling, thanks to all for this useful encouraging info. Cheers.

trackbot, end meeting

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.200 (CVS log)
$Date: 2023/11/17 15:23:28 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

FAILED: s/yest/text/
Succeeded: s/yext/text/
Succeeded: s/WAI course list/list of accessibility courses/
Default Present: kakinney, BrianE, Michele, shawn, Laura, Len_B, Sharron, Jayne, Mark, Lucy, Frankie
Present: kakinney, BrianE, Michele, shawn, Laura, Len_B, Sharron, Jayne, Mark, Lucy, Frankie
Regrets: Jedi
Found Scribe: Sharron
Inferring ScribeNick: sharron

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]