– DRAFT –
WCAG2ICT Task Force Teleconference

Announcements

MaryJo: Talks to editor roles. We are going to have Phil Day, myself and Chris Loiselle as editors. Thanks Gregg for the ask and will call on as needed.

MaryJo: Tutorial about GitHub is major goal of this meeting.

Gregg: For training, you may want to record the training session. I know we don't record the meetings in general.

Judy: I want to make sure we can ask any question about GitHub during this call .

MaryJo: If questions are captured in meeting minutes, we can add those to wiki and point to GitHub help . We want people to be comfortable , no question to small , we want people to learn.

Next steps for the WCAG2ICT Work Statement

Mary Jo : Next steps for work statement. As a task force, it has to go to full review for AGWG . AGWG will review again . They may come back with comments.

<Rachael> Just confirming it will be discussed at the October 18th meeting

Mary Jo : Will discover result of survey and call for consensus (CfC) will be sent out

Mary Jo : As task force members, you are also able to respond .
… any questions?

Begin learning GitHub

Mary Jo : shares her screen, showcasing url github.com/w3c/wcag2ict

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

if you want to edit notifications , you want to find the unwatch element , notifications for participants and mentions vs. all activity is discussed. If you @ the person , they will be notified . As a facilitator , Mary Jo monitors all activity. You can restrict to your liking. Talks to ignore functionality but reviewing tasks individually.

Shadi: talks to unwatch and custom functionality, one is pull request on changing text , the other is raising or commenting on an issue to check certain level of detail you want to receive
… only issues mentioned on, etc.
… might be useful for editors , pull requests and changes

Mary Jo : I plan to use issues to track our work.

Mary Jo : I will look to create project and define milestone within the tool

<Zakim> ShawnT, you wanted to say something about discussions in Github

ShawnT: We have been using discussions , where discussions are topics or future additions . It is enabled within settings administratively.

typically found here https://github.com/discussions

MichaelC: We can review and set up outside of call if need be. I'd need user ids , etc.

Mary Jo : Please send user ids to me rather than Michael C.

MichaelC: worthwhile to use in this group

Mary Jo : That would be helpful and agree.

MichaelC: I've made the change.

<ShawnT> Thanks to Sam Ogami https://docs.github.com/en/discussions/quickstart

Mary Jo : Issues is an option within GitHub. Creating an issue, tracking an issue, labeling issues, @'ing people . You can filter by author, label, projects , milestones, assignee

Thanks, Sam!

https://github.com/w3c/wcag2ict/issues is the main area that Mary Jo is highlighting on her screen

Mary Jo : You can open a new issue, it will not save unless you put in a title . Submit new issue button is disabled until you name the issue. Once titled, the submit new issue button is enabled.

Mary Jo : If you are adding an issue, you can assign yourself and choose labels as appropriate. Expect labels for new Success Criteria so we can filter by Success Criteria (SC) .
… talks to label of internal , help wanted

<ShawnT> is there's a way to share labels between repositories?

Mary Jo : you can @ mention in the issue you are filing.

Mary Jo : you can preview what you wrote as well.

talks to square bracket around text , then parens around url string. displays list with hyphen and indent to showcase an unordered list

Phil: With assignees, can you filter notifications or do you have to log in and then filter?

Mary Jo : Watching or Unwatch , then when you are participating , you are assigned. Recommends trying out the participating and mentions vs. custom . Then talks to filters

<Zakim> FernandaBonnin, you wanted to say should we do a survey for GH handles so its easier to know everyone's?

Fernanda: How about we set up a survey and talk to our handles in GitHub there

Mary Jo : I will set up a survey to pursue that yes, great idea!

Shadi: If you click on one issue, then scroll down. There are notifications for this particular issue...so you can unsubscribe to particular issues.

this is only possible if you aren't watching ALL activity

Mary Jo : This is good for limited emails on these type of long threads.

<Zakim> ShawnT, you wanted to speak on putting our github handles in our W3C profiles?

Mary Jo : You can also set up email rules to move to dedicated folders to manage W3C related emails .

<ShawnT> https://www.w3.org/groups/tf/wcag2ict/participants

Shawn T : We have our GitHub user names placed in participants off of wiki

<Sam> github uses Markdown - here is a basic cheat sheet https://www.markdownguide.org/cheat-sheet/

Sam: If you are familiar with markdown, https://www.markdownguide.org/cheat-sheet/ is great resource

thanks , Sam!

Daniel: Talks to Toolbar as well .

Mary Jo : If you are writing in draft format , say in Word, you can drop the Word file in the issue and you can track issue there with file as part of issue.

Mary Jo : You can also set up reference other issues, using the pound sign (#) then followed by the issue you want to include. This can be done in comment section on a given issue or when writing and creating the actual issue

Mary Jo : Any other questions about issues? Any other tips?

Mary Jo : You can unassign or assign yourself as well on issues.

Mary Jo : talks to how we review code. There is a code link within the toolbar. There is a code dropdown select after the add file button.

Mary Jo : Recommends GitHub Desktop application in addition to the web version

Daniel: GitHub Desktop is not entirely screen reader accessible

Daniel: I have workarounds such as visual studio cloud, you can follow up with me if you have details on workarounds on desktop

Judy: If you have barriers, please feel free to let us know so we know what parts have limitations . We can collect those known issues.

We can approach and work with GitHub on those items as we've been engaged with some other vendors in the past, occasionally with bits of success

<ShawnT> I'm surprised no one from Github / Microsoft is part of the W3C

Mary Jo : We will definitely pursue these as they come up.

ChrisLoiselle: In general, https://docs.github.com/en is a great resource to learn more on all of these items discussed

Mary Jo : Showcases https://github.com/w3c/wcag2ict/projects?query=is%3Aopen

Apologies, https://github.com/orgs/w3c/projects/13 is the correct URL for Note Update Project

talks to status, assignee , etc.

<Zakim> pday_, you wanted to clarify the differences between documents and code

Phil D: Can you clarify on GitHub web vs. desktop version ? Is there a need to use one or the other or both?

Mary Jo : Most of what we are doing is within index.html and it is all in mark up with basic HTML for code editing...that is why we are using the edits in GitHub. Talks to branches and editing , then talks to copy of code that you'd edit and then once changes are made , pull request is made
… before pull is put in to main, opportunity to review is available, then we can merge into main branch after the content has been updated.

Mary Jo : We have a published draft (2013) then an editor's draft. We will continue in the editor's draft.

Mary Jo : There is an entire process on the editor's draft commenting process , so on and so forth. Then we publish again. Iteratively.

<Zakim> ShawnT, you wanted to speak on using Github's web browser UI to make changes

Shawn T : I am wondering if we could do another session about web based UI and not pulling to machine. We are looking into that as a process within web interface

Mary Jo : Note to try that moving forward , perhaps next meeting.

Shawn T : I'd be willing to pursue with Mary Jo to talk to this topic

Mary Jo : Great.

<bruce_bailey> +1 to what @ShawnT says about positive experience with GitHub

Gregg: I agree, recording to fall back on is great.

<ShawnT> GreggVan I think that's only if we are using markdown

Gregg: I'm asking how to view non HTML version ?

<bruce_bailey> +1 to what Gregg is askin

<FernandaBonnin> * if you go to edit it allows you to preview too

MichaelC: Go to raw view of source, then change rawgit.com

MichaelC: I will follow up with Mary Jo. You can edit in your editor of choice also, but we can talk to push and pull options.

<ShawnT> There are more ways to contribute than updating the content

Gregg: talks to technical aspects of this vs. non technical aspects of updating , etc.

Mary Jo : other teams have used Google docs then converting later...

I lost the connection

@mary Jo , can you make minutes?

<pday_> so did I - but have to leave for another meeting. Thanks all

thanks!

I'd like a tutorial on push , pull etc. as we were covering

thanks so much !

will you send out minutes?"

My connection dropped at the hour from Zoom.

<ShawnT> This came up in the COGA meeting today: Collaboration Tool Accessibility https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Collaboration_Tool_Accessibility