W3C

WAI Coordination Call

02 November 2022

Attendees

Present
jeanne, kevin, matatk, shawn, tzviya, valerie_(spectranaut_)
Regrets
Janina, Katie
Chair
MichaelC
Scribe
matatk, matatk:

Meeting minutes

Update on transition status

MichaelC: As Judy steps back, this is one of the groups I'll be taking over. Doing the same with the WAI Team calls. Judy will likely stop in on some of these calls.
… One group suggested that I join the groups to talk to them individually. Have arranged that with some groups. If you'd like me to attend your group, please arrange it via the group's chairs.

Group activity summaries

MichaelC: I think we should use the WAICC to keep in touch with eachother about what's going on in our groups. Not just publications. Don't want it to become redundant, but helpful to coordinate.

+1 good idea IMHO :-)

<jeanne> +1 Let's do it

MichaelC: Not sure about doing a 2-minute round robin. How does a wiki page or email update work?

<shawn> +1 for updates when useful

tzviya: If you need 2.5 mins or 30sec that's OK; this seems to work well.

+1 to 2-min round robins

<MichaelC> acj tz

<Zakim> shawn, you wanted to discuss EOWG update and to

<shawn> https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects#Current_Work

tzviya: EPUB is focused on testing; not meeting regularly. Testing wrapping up end of November. Accessibility TF focused on mapping embedded accessibility data to Library metdata called MARC.

shawn: EO's got a lot of work on. E.g. authoring tools with accessibilty support.
… Making ATAG industry specific briefs, e.g. for people developming LMSes.
… Creating videos on how PWD use the web (as previously discussed).
… Will be brining things to you for review.

MichaelC: What timelines do people here need to know?

shawn: We've sent the videos out. Need feedback on those as a priority.

kevin: The priority project from my perspective is WAI Guide, specifically the videos (as require the most time devoted to them). We have to have these submitted by the end of the year.
… Working hard to get many perspectives on the videos. Have to be tight with deadlines. Will know more in next couple of days wrt project timings.
… Just agreed a partner to support us with the videos.

MichaelC: If people in your groups are likely to want to review these thigns, they should be prepared for that, and set time aside.

<Zakim> jeanne, you wanted to discuss EOWG update and to

jeanne: WCAG 3 has been working on conformance for past few months. Soliciting proposals for various aspects of conformance. Meetings progressing well. AGWG charter is out for review, closing in a month. WCAG 2.2 is working on test implementations for CR.

<Zakim> matthew, you wanted to discuss EOWG update and to

matatk: CTAUR progressing well from RQTF; hoping to have good news re Adapt symbols, aiming for CR very soon; Paul Grenier is our new CSS liaison and doing a great job.

<MichaelC> https://www.blissymbolics.org/

MichaelC: Also: Adapt [symbol] registry. This is work in collaboration with Blissymbolics Communication International (Bliss) to help us map concepts in web content to users' symbol sets.

<Zakim> daniel, you wanted to discuss EOWG update and to

<MichaelC> https://w3c.github.io/adapt-registry/

daniel: Working on implementing ACT rules based on agreed WCAG SCs. Moving this work back to the WAI website.
… Also working on updating the rules format to 1.1
… We are going to give a presentation to the government of Canada tomorrow, discussing the main challenges on standards harmonization.

<Zakim> mary_jo, you wanted to discuss EOWG update and to

daniel: Also including news of WCAG 2.2 and 3.

maryjom: WCAG 2 ICT TF got our work statement approved. Been training people on using GitHub. Several new to W3C.
… Created new templates for adding guidance on WCAG 2.1 and 2.2 SCs.
… Created a project plan via GitHub Projects for managing the tasks for getting the WCAG ICT Note to completion.
… Excited to use new tools.

MichaelC: As part of that, Daniel and I are working on getting the content into Markdown format rather than HTML.

<Zakim> valerie, you wanted to discuss EOWG update and to

Valerie: ARIA 1.2 getting closer to being published; blocked on an implementation report. 1.3 is coming to a close. Dealing with the related specs becoming evergreen. Wondering if ARIA itself should be evergreen.
… We've been working on a better WG process, having now some evergreen specifications.

<MichaelC> https://www.w3.org/WAI/ARIA/workflow

MichaelC: ARIA has been working under the above workflow for several years. As we work on these, we want to share with the other groups.

Valerie: When we finalize the processes, we codify them; will share links as appropriate.

<Zakim> michael, you wanted to discuss EOWG update and to

MichaelC: I've been learning what tasks Judy had, and what I need to do on them, get into different areas of WAI work, and how to prioritize. To help with this, Roy is taking over fully as APA staff contact.
… For ARIA, Daniel is getting started as staff contact, having previously worked with ACT. Will transition over to him gradually. Keeping my time in AG for the moment until we sort out what's happening staffing-wise. Expect transition to be ~3mo.

kevin: I'd be interested in maryjom's experiment with GitHub Projects, how that works out.

<MichaelC> https://github.com/orgs/w3c/projects/13

shawn: The ARIA APG has used GitHub Projects too.

maryjom: I think the Mobile TF did too.

<MichaelC> https://github.com/w3c/aria-practices/projects?type=classic

maryjom: We have used other tool at work, but it was not keyboard-accessible.

maryjom: Found it very easy to set up.

Upcoming review requests

MichaelC: This is cross-group review requests.
… I took the existing agendum for now; for review requests I may want to change the process around this.
… ACK EO WAI Guide videos.
… Any urgent reviews for the next month?

Upcoming publications

<shawn> https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#Planning_Upcoming_Announcements

MichaelC: We talked about this in WAI Team today. Want to take most of this out of WAICC and into WAI Team.

shawn: Make sure your staff contact knows this move is coming up.
… We'll continue to improve the process. You're welcome to draft your announcements in GitHub, Google Docs. Will try different methods and see which work best. You don't all have to do the same thing. One important thing: the wiki page above has links to all the important information. We need the links on the wiki page in order to be able to find everything from one place.
… Questions, comments?

MichaelC: Looks like WCAG 2.2 PR would have to be December. More on that separately.

WAI-CC activities during transition

MichaelC: Want to hear from you: what do you want more of, less of, on these calls?

matatk: I really like the round robin stuff; great to get a high-level overview of what people are working on.

<maryjom> /me I am unable to log into the planning upcoming announcements page.

MichaelC: Will pick up over email. Thinking of sticking to once every two weeks schedule. OK with people?

<jeanne> +1

+1

MichaelC: I'll send round a scheduling survey; Roy can't participate at this time.

<maryjom> +1

MichaelC: Next meeting: until we change, next meeting is November 16 at the same time.

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).

Diagnostics

Succeeded: s/a library's metadata/Library metdata called MARC

Maybe present: daniel, maryjom, MichaelC, Valerie