<lisa> https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.rgqn5t5157lo)TPAC

<lisa> https://docs.google.com/document/d/1YiknHDDDdKBdwVTEpxwUpyCaQL_tnpp9CfDlFjCq16E/edit#

<lisa> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#

<kirkwood> Link to page is on wiki

<kirkwood> Wednesday and Thursday is the APA meeting

<JohnRochford> WebEx trouble

<lisa> ok

<lisa> talking about tpac

<lisa> scribe: Jan

Tuesday 1:00 - 2:00 meeting with APA

<lisa> 16:30-18:00 Publishing Issues Discussion

<JohnRochford> On call now

Janina: May be interested in TPAC 4:30 - 6:00 when we meet with publishing accessibilty people - need to get an overview of their laundry list of what they want to achieve over the next few years
... want to ask publishing if they have needs that can be met, such as personalization and CSS - would like to lay out the agenda for the next few years.

Lisa: TPAC: Tuesday 2:00 - 3:00, we have the APA room where we can meet - Jan and John can meet up there and talk with Lisa on the phone about making techniques and anyone else who wants to mee.

meet

Lisa: I don't have the agenda yet for the WCAG stuff.

Janina: I have tried to note all of the times when we are leaving the APA room to meet with someone else. We are having a joint meeting with the automotive group to talk about accessibility and autonomous vehicles.

<lisa> https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017#Agenda

Janina: There's a really good master calendar on the main TPAC site

<JohnRochford> Yes, Lisa, I can hear you.

Lisa: Because not all of the SCs we wanted made it into WCAG 2.1, we decided to write an appendix for the next publication roadmap that would have all of the information on how to make COGA friendly content and this is the purpose of the document, "Making COGA friendly content and applications."
... it's not going to be worded like a specification, so we have to stay away from words like requirements, specifications, etc.
... Under system requirements, I ported the SC that had not been accepted and move them into this document.
... I put the SCs under themes, but I am not sure that that is where they should stay, so please review them.
... WCAG wants everything can be testable, normative, and unambiguous. So, I rewrote everything in clear purpose in simpler language and chunked it - it's still not testable, but hopefully it's easier to understand.
... when you say, "make the purpose of each page clear," we needed an example of how to accomplish this.

<lisa> Make the purpose of each page clear

<lisa> (Technical details: On coga github: clear-purpose.html

<lisa> wcag issue 55 https://github.com/w3c/wcag21/pull/10)

<lisa> Example: Someone with mild dementia is using online shopping. They get distracted and then when they look at the screen again they have forgotten what they were doing. Put a clear heading at the top of each page that seas clearly what the page is and what they are doing. Breadcrumbs, with a summary of each step, are also very useful for this.

JohnK: I have seen another web site that uses a clear writing style that we could use as an example. I am wondering how much research and information there is out there already that we could tap into. Do we want to incorporate that, or keep it simple and straight forward? I think we are using terminology that needs to be defined a little more.

<lisa> we need aglossary

Lisa: I am hearing that we need a glossary?

JohnK: Yes

Lisa: We should have a link to the research

JohnK: Yes

Lisa: We have some research linked, but probably not as much as we should. I think we should have research available, but that it should be under a link to keep the text simple.

JohnR: Number three - using clear language - by "clear text," do you mean simplified text and by "clear images" do you mean contextually relevant?

Lisa: Clear image is an image without a lot of clutter in it. If it's an image of a girl, it's one thing, but if you have an image of a girl sitting at a table having a cup of tea, then it could be confusing.

JohnR: I am more interested in clear text - how is that different from simple text?

Lisa: I was just trying to tie it the SC that we tried to get passed, soo I tried to stick to the phrase, "Use common words or core vocabulary." Since we're not having to be normative with this document, we could also suggest that you could have a description in simple terms.
... we could have links to more precise language or terms - we could even have an additional paragraph that would clarify what we are trying to say.

JohnR: I would not want us to depend on people reading the research in order to understand what we are saying. I think that we are going to need to do a better job describing what we need under system requirements. What do other people think?

Lisa: Let's separate two things. We need to work on short sentences to make things clear, but we need to work on making things testable.

JohnK: I was not really saying "testable," I was just saying that there are standards being implemented in the federal government around plain language that we should be sensitive to.

<kirkwood> Sorry if I added confusion but this is what I was referring to and wondering how ‘clear’ language relates http://www.plainlanguage.gov/

Lisa: I would mainly like to know if you like this format and we can work on the details later. So, for example, we have decided that we need to add a glossary and a link to research.

<JohnRochford> +1

<kirkwood> +1

<janina> +1

Lisa: So - do we like the format of a sentence, followed by some links, terms, etc.

+1

<lisa> action jan and shari to help lisa write the system requirments https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#

<trackbot> Created ACTION-249 - And shari to help lisa write the system requirments https://docs.google.com/document/d/1wcfvalvq8ps9clxuuafv9op0wxvi2yjyedj5jo23gtk/edit# [on Jan McSorley - due 2017-11-09].

https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_PageAPA support items

<janina> brb, lost audio again

<kirkwood> Jan you can loop me in on working on the doc as well.

Lisa: JohnR needs the authentication spec URL - Janina will send
... Do we have a meeting with them at TPAC?

Janina: Probably not - they (APA) are only meeting on Thursday and they already have a full agenda
... Before they leave CR, since they don't know what their calendar is, they asked if we had any comments, but they are still adding things. Jason White had some questions that he put into the APA list - I will find two pointers.

Updates on support for WCAG 2.1

<lisa> https://docs.google.com/document/d/1YiknHDDDdKBdwVTEpxwUpyCaQL_tnpp9CfDlFjCq16E/edit#

Lisa: I put in our techniques document - who is doing what implementation - we need examples of sites that show where this is being done.

<janina> Authentification Spec: https://www.w3.org/Webauthn/

Lisa: JohnR - we need you to find 4 examples of authentication and JohnK, you need to find examples that conform to our interruptions requirements.

JohnR: I can send you a list.

<lisa> https://docs.google.com/document/d/1YiknHDDDdKBdwVTEpxwUpyCaQL_tnpp9CfDlFjCq16E/edit#

Lisa: You can either send me a list now, or add it to the techniques document - at the top, I have implementation.
... I have implementations as a heading at the top of the techniques document - that is where I need you to put the links to sites that are using accessible authentication.
... Github is an example because it does not timeout for 24 hours and that is one of our techniques - so we need to give examples like that.

<JohnRochford> Must join LVTF call now.

Lisa: Need to complete the techniques you're assigned to do.
... We can work on this on Tuesday during the time we have in the APA room.

People who will be at TPAC: John Kirkwood, Jan, Janina

<lisa> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page#About_This_Page

Dates for our group are on the COGA wiki - main page

TPAC

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: janina, kirkwood, JohnRochford
Present: janina kirkwood JohnRochford jan
Found Scribe: Jan
Inferring ScribeNick: Jan

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: 

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