W3C

– DRAFT –
WCAG2ICT Task Force Teleconference

08 September 2022

Attendees

Present
AnastasiaLanz, bruce_bailey_, BryanTrogdon, CaraHenderson, ChrisLoiselle, Chuck, Devanshu, FernandaBonnin, GreggVan, Judy, lmiller_, maryjom, olivia-hogan-stark, Sam, shadi, ShawnT, ThorstenKatzmann
Regrets
-
Chair
Mary Jo Mueller
Scribe
dmontalvo

Meeting minutes

<ChrisLoiselle> W3C is stating I don't have privileges when following the link off of telecon page

<ChrisLoiselle> W3C is stating I don't have privileges when following the link off of telecon page

e

Welcome

[[Introductions]]

M: We are focusing on completing an update to the 2013 Note
… In addition we have now gained some experience on applying WCAG SCs to non WCAG technologies
… Also the EN301549 standard will be updated next year and this work is relevant for that

<bruce_bailey_> https://github.com/w3c/wcag2ict/wiki/Work-for-the-week#preparation-for-8-september-meeting

M: We will not be modifying the standards
… This is an interpretation of the standards only
… We expect that all the participants contribute to the work. We need everybody's help to get this done
… Everyone needs to adhere to W3C's CEPC
… If you have not read it before, a link is in the prep work for next meetings

<Judy> [CEPC = Code of Ethics and Professional Conduct]

M: All accessibility standards are developed under the Web Accessibility Initiative (WAI)
… Judy Brewer is the WAI Director

<bruce_bailey_> https://www.w3.org/wai/

M: Within WAI there are various groups focusing on specific topics
… Within the working working groups there are Task Forces, like ours

<Judy> Link to W3C's CEPC: https://www.w3.org/Consortium/cepc/

M: This TF falls under AGWG (Accessibility Guidelines Working Group)
… Chuck is one of the co-chairs and will be a liaison to the group
… He will also be an acting co-chair, this is a temporary thing for the moment
… I really thank Judy and Chuck as my partners for getting this started
… Also thanking W3C Staff, Michael Cooper and Daniel Montalvo
… Our work is under W3C consensus process
… Will be using the AGWG Decision Policy
… For next meeting prep there is a link to the Decision Polcy. It tries to reach unanimous agreement where possible
… During the meetings we will follow W3C etiquette
… IRC and queue will be used
… IF you can't join IRC please ask us to acknowledge you on the phone
… Feel free to speak, everyone has a chance to contribute
… Minutes will be sent to the list

Judy: Thanks everyone for joining
… Mary Jo and Chuck have been working for months to put together the TF Work Statement, I am very grateful for their work
… I hope what we did in 2012 can help us going forward
… Even though we do produce a Working Group Note, that will not be normative, though it could potentially become a candidate for a W3C statement get reviewed and promoted to a W3C Statement
… The process of mapping WCAG to other technologies is tricky, we need to work carefully
… I am going to ask you in advance to respect when your co-facilitator asks you to not get beyond the scope of what is discussed
… Thank you Chuck for standing up as we work on a possible European liaision

Chuck: A pleasure to work ith you all

MJ: Questions?

Short-term meeting dates

MJ: This coming week is TPAC, during that week there will be no WCAG2ICT meeting
… The 15th there is no meeting, we will resume on the 22

<Chuck> dmontalvo: can you Email with link to survey? There was an issue with previous one.

<maryjom> https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-weeks-available/

MJ: The survey will remain open, you can update your answers whenever your availability changes

Introductions

[[Round of introductions]]

<philday> Apologies all - I have to drop for another meeting. Hope to join you for the full time next week

<Chuck> dmontalvo: W3C staff since 2019. Previously accessibility tester, consultant and trainer. Still working in training.

<bruce_bailey_> Bruce Bailey, IT Specialist at U.S. Access Board, IE w/ AG WG, provide technical assistance on 508 regulation, suggested WCAG for non-web software and docs in 2011

<bruce_bailey_> so nice to see old friends and meet new ones !

<Chuck> You are very welcome Thorsten!

<Chuck> Welcome to all our first timers!

Identify unfilled roles and potential interest

MJ: We need to fill in some positions
… We need a editors who are (or can become) familiar with GitHub
… Contact Chuck or myself if you are interested
… Chuck and I think everybody should have the right to contribute and would try to avoid being editors ourselves
… Formats will be discussed later

<Zakim> bruce_bailey_, you wanted to ask why TF wants additional co-chair ?

Bruce: IS this because we don't want to have only industry in the editor's position?

Judy: We are trying to carefully separate roles
… This may not matter now, but it may matter in the future
… We are trying to ensure representation from disability communities as well as some other stakeholders

Chuck: I hope that filling in this TF leadership is temporary, being an AGWG Chair is time consuming in itself. My role in this team is not going to be to represent Oracle interests but to represent AGWG interests
… Hopefully someone will fill in that position and I can get back to liaisoning

MJ: I am also impartial and Torsten is taking the IBM hat

<bruce_bailey_> Mike Pluke as co-facilitator

<bruce_bailey_> last time

Greg: Are we trying to do the same European involvement: involvement here?

Judy: Yes, conversations are going on

Gregg: Are we having co-facilitators for this group instead of chairs?

Judy: Yes,

Getting started with W3C and the WCAG2ICT wiki

<maryjom> https://github.com/w3c/wcag2ict/wiki

<Chuck> https://github.com/w3c/wcag2ict/wiki

MJ: I have established this wiki as the starting point for this TF
… We have several useful links to IRC, minute-taking, meeting logistics, etc
… There are some placeholder pages as well
… We need to discuss which tools work best for each of us
… We have links to the new WCAG21 SCs

<Zakim> bruce_bailey_, you wanted to ask about first pass draft David McDonald did (on his own) some years back ?

MJ: If you have any unanswered questions let me know, I will try to answer as soon as I can

Bruce: Does anyone have a link to the work that David McDonald started?

MJ: Good point, I have it and will add it

Gregg: Someone said we were going to update the old document. Is this what we are going to do?

MJ: Let's discuss

Initial priorities for the group

Initial priorities for the group

MJ: First we need to agree on the Work Statement and also for AGWG to approve
… Once approved, we can move on to work on the document itself

MJ: I think the biggest priority is to include WCAG 2.1 and 2.2 SCs
… There are also new issues with current technologies and open issues that have been logged on GitHub
… I also know that there are problems with some technologies that we need to be clearer about
… We may have to publish and then continue based on timing
… But we need to prioritize to get things done and to be ready for EN301549 updates

Gregg: Will there be links for the priority draft? Could you put a link to the GitHub issues as well?
… Would you also add the link from David McDonald?

MJ: I guess I could put the links directly on the wiki

MJ: I will fix all of this for the next meeting

Sam: Could you touch on what timelines we have as per EN301549?

Torsten: Standardization Request has not been signed yet, I think the timeline is next week or the week after for that to happen

<Chuck> 4 minute warning

<bruce_bailey_> In main wcag repo there is a label: https://github.com/w3c/wcag/issues?q=label%3Awcag2ict

<bruce_bailey_> not much there right now

Torsten: Then we will have about three years time to finish the work, that means one or one and a half year to work on the content, the rest will be mostly devoted to process

MJ: I think this shows why this work is now time sensitive
… There are a lot of review cycles after we finish the content, and some further steps to completion after those reviews

<AnastasiaLanz> Are there any resources about what was said about the European Union and timelines?

Judy: I ask people to be patient with our co-facilitators. IF people have questions, feel free to use email
… I hope we can have some homework to do during the next two weeks

Getting started with W3C and the WCAG2ICT wiki

Homework / preparation for the next meeting

MJ: We'll have to talk offline what tools work best for us, please do some prep for discussions
… Next meeting is going to focus on the draft Work Statement, I am in the process of creating a survey, getting close
… It will have questions on each of the Work Statement sections, please try to complete by the night before the next meeting

MJ: I appreciate everybody's time. We will meet again in a couple of weeks
… Hopefully you all will have a GitHub id and will have linked it to W3C

Chuck: Please present+ yourselves on IRC to signal that you have attended the meeting

<Zakim> Chuck, you wanted to say to present+ yourself

Anastasia: Are there any link that i can have a look at to learn more about the European context?

<Sam> https://ec.europa.eu/social/main.jsp?catId=1202#:~:text=The%20European%20accessibility%20act%20is,EU%20leading%20to%20costs%20reduction

MJ: It is difficult as there are things that they are working on now, like the standardization request which I'm not sure is publicly available in its final form yet.

<GreggVan> https://en.wikipedia.org/wiki/EN_301_549

<bruce_bailey_> can also look for "mandate 376"

<maryjom> s/I'm late late late for a very important date//

<maryjom> s/Hi, is there a link and passcode for this invite? W3C is stating I don't have privileges when following the link off of telecon page//

<maryjom> s/Hi, is there a link and passcode for this invite? W3C is stating I don't have privileges when following the link off of telecon page//

<maryjom> s/W3C is stating I don't have privileges when following the link off of telecon page//

<maryjom> s/W3C is stating I don't have privileges when following the link off of telecon page//

<maryjom> s/W3C is stating I don't have privileges when following the link off of telecon page//

<maryjom> s/ the 22 / September 22 /

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

Diagnostics

Succeeded: s/2014/2013/

Succeeded: s/Working Group Note, that can eventually/Working Group Note, that will not be normative, though it could potentially become a candidate for a W3C statement/

Succeeded: s/no much there right now/not much there right now

Succeeded: s/present+ yourselves/present+ yourselves on IRC to signal that you have attended the meeting

Succeeded: s/Mary Jo, can you or dmontalvo deal with the meeting minutes?/

Succeeded: s/I'm late late late for a very important date/

Failed: s/I'm late late late for a very important date//

Succeeded: s/There is a lot/There are a lot/

Failed: s/Hi, is there a link and passcode for this invite? W3C is stating I don't have privileges when following the link off of telecon page//

Succeeded: s/I'm getting Sorry, Insufficient Access Privileges :(//

Failed: s/Hi, is there a link and passcode for this invite? W3C is stating I don't have privileges when following the link off of telecon page//

Succeeded: s/+present//

Succeeded: s/Hi, is there a link and passcode for this invite?//

Succeeded: s/Hi, is there a link and passcode for this invite?//

Succeeded: s/pudate/update/

Succeeded: s/ ot/ to/

Failed: s/W3C is stating I don't have privileges when following the link off of telecon page//

Failed: s/W3C is stating I don't have privileges when following the link off of telecon page//

Succeeded: s/ ot / to /

Failed: s/W3C is stating I don't have privileges when following the link off of telecon page//

Succeeded: s/aninterpretation/an interpretation/

Succeeded: s/ ont / not /

Succeeded: s/groups/working groups/

Succeeded: s/groups/working groups/

Succeeded: s/ na / an /

Succeeded: s/ my partners / Chuck as my partners /

Succeeded: s/MOntalvo/Montalvo/

Succeeded: s/Decission/Decision/

Succeeded: s/Decission/Decision/

Succeeded: s/ 15 / 15th /

Failed: s/ the 22 / September 22 /

Succeeded: s/your answers as long whenever your availability changesavailability/your answers whenever your availability changes/

Succeeded: s/ form disability communities/ from disability communities/

Succeeded: s/toher/other/

Succeeded: s/iBM/IBM/

Succeeded: s/converstaions/conversations/

Succeeded: s/ ahve/ have/

Succeeded: s/There is also new/There are also new/

Succeeded: s/konw/know/

Succeeded: s/clrearer/clearer/

Succeeded: s/ghe/the/

Succeeded: s/TigHub/GitHub/

Succeeded: s/wll fix all of this for thenext/will fix all of this for the next/

Succeeded: s/ocntent/content/

Succeeded: s/homeworkto/homework to/

Succeeded: s/on the process/in the process/

Succeeded: s/section/sections/

Succeeded: s/that there are/that they are/

Succeeded: s/working on now/working on now, like the standardization request which I'm not sure is publicly available in its final form yet./

Maybe present: Anastasia, Bruce, Greg, Gregg, M, MJ, Torsten