Lisa: Definitions between jurisdictions end up meaning the same thing in different jurisdictions. We are going to put terms in a glossary.
... We also have political correctness issues. Some terms have evolved as well. We are doing the first 10 terms.
... The most important terms to understand the document. Hopefully helps people in the field.
... Hopefully clarifies if we are using US or European definitions.

Steve: Shadi pointed out that supplemental guidance was coined specifically for coga.
... It could be something that extends something.

Lisa: Maybe we drop or define supplement.

Rachael: There's a reference in WCAG that calls out COGA as a supplement. I need to dig it out.

Lisa: We did commit to making a supplement. Since we've come out with this guidance.

Shadi: If I recall, Lisa and others might have been around, this was in relation to the objection that WCAG does not go far enough for people with cognitive learning disabilities.
... The agreement was that W3C would provide further guidance on how to address these additional requirements. I wasn't involved, but that's my recollection.

Lisa: that's what I remember.

Rachael: That's Alastair's as well. May have evolved over time.

Lisa: We said at the time that there would be supplements. From other task forces as well.
... Whatever the term means, should be of interest to them too.

Steve: Judy said a week or so ago was that she didn't know what supplemental guidance meant. We've taken that out.
... David objected to the term. "Extended" rather.

Rachael: We replaced the text and discussed last week in the coga meeting. It went round and round, and went round and round again.

Lisa: This is important, that there was a commitment to make supplement.

Rachael: Some of this moves out of this meeting into a broader coordination effort. Anything else to discuss for coordination?

Steve: Thanks to the fantastic work, things have moved.

Lisa: I'd put it another way. It is a process that's moving. Opposed to a process that isn't moving. It's worth doing. Don't get put off by it taking a few weeks.

Rachael: Great way to put it. Shadi, can you speak to ACT?

Shadi: There's much, we've been working on rules from community group. Should have a batch for AG to review.
... For further publication. Also worked on an errata. CFC passed in AG group. We are slowly collecting errata.

Rachael: Any blockers or things we can help with?

Shadi: Not at this time, thanks.

Rachael: Low vision isn't here. Kim?

Kim: A couple of techniques on dragging and touch target spacing. After that, most members are looking to concentrate on silver.
... We are looking for guidance on what you want us to do after finishing up dragging and touch target spacing.

Rachael: We will need help with issues on the SC.

Kim: We should expect feedback from you.

Rachael: You'll get feedback from the public as well as us. We'll get issues, and need help for those.

Kim: What's the process for getting that feedback?

Rachael: For techniques, what I've seen is it goes to AG, we review and provide comments, and then try and approve it to integrate it into the documentation.
... We'll invite you to the meeting, pass back to you. For issues, we'll call those out, as we get those issues in. We'll alert the appropriate groups.

Kim: We'll be invited to a meeting?

Rachael: For the techniques. If you want us to come to your meeting let us know.

Kim: You'll let Kathy and I know when you need us. Then the issues, how will we get that?

Rachael: Also by email.

Kim: That works. You'll email us saying "there are these things". If there are a lot of issues it might be good to have... sometimes you have a status document. That might help people to avoid missing things.

<Rachael> ACTION: Work out Issue process and communicate it to Taskforce

Kim: Would be great to have some place to go ahead of meetings to prepare, and not miss anything.

<trackbot> Error finding 'Work'. You can review and register nicknames at <https://www.w3.org/WAI/GL/track/users>.

Rachael: I'm taking an action to write up the process and inform the task forces.

Kim: I'll let mobile know that we will have marching orders and a status document.

Chuck: Don't think so.

Michael: We may need to work out details.

Rachael: Anything else we can work with? This meeting is great for working out processes.
... Did I miss any TF?
... My topic is to ask everyone... we have a process in TF to generate some content. I'd like to hear your feedback on how we do that and how we can improve on that. Don't need to do that this meeting.
... We will have a virtual face to face with Chairs. We'd like to hear about issues with current process of moving documents through AG and improving quality.
... We'd love to hear feedback and let us know.

Michael: Some suggestions. Some of the information Rachael is looking for you will have already said, but please repeat.
... And we could create a survey for TF leaders to get input in one place.

Rachael: I'm new, Chuck is new, and you may have said some suggestions that we haven't heard before.

Lisa: Make some principals that the task forces and AG can follow.

Kim: Some quick thoughts. We talk about the issues over and over. Sometimes we are repeating ourselves. It can be solved by process. We need to be able to point to prior answers that were put together.
... That we can reference. It would help a lot if our process had the arguments in the same place, and answers in the same place. It can be an access thing.
... May not have the time to look back at thoughtful answers from before and they had to be reconstructed.
... Thinking about that through process to avoid repetitive conversations. And cross-pollination between groups can be helpful, to avoid clashes.
... Low vision, things need to be big, hand problems cause issues with scrolling. Would be good to have cross-pollination among groups.
... Like hand off something to mobile for example to review, and we can back up where we can, and identify some potential clashes.

Lisa: We try to avoid low vision, our personas, we put in someone who is old, and the vision isn't what it was. Common for people to have both.
... Janina said "you are the coga task force, don't include low vision". We may want to consider making these personas broader.
... We went along with the comment but we don't have to ongoing.

Rachael: I've taken a note.

<shadi> https://www.w3.org/Consortium/cepc/

Shadi: With my w3c hat on, there's been technical aspects, group micro-culture. There's behavioral aspects. We have a code of conduct and ethics.
... There may be some helpful things here. And maybe we can add to it. That could cover work with AG and externally.
... Want to make us aware of that. there's no space for treating each other disrespectfully.
... That's a w3c policy. It could be whatever guidance the group chooses to develop, and this policy can be improved.

Rachael: Any other topics?

Lisa: Good meeting!

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: shadi

WARNING: Fewer than 3 people found for Present list!

No ScribeNick specified.  Guessing ScribeNick: Chuck
Inferring Scribes: Chuck

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


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: work

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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.)