<Lisa_Seeman> agenda: this

<Lisa_Seeman> scribe: Kirkwood

<Lisa_Seeman> next item

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/actions/open

thaddeus: put email changes to list, where change meaning will put in an email to list

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Pre-publication_checklist

<Lisa_Seeman> for plain links (not refrences use item 6 in the checklist

naked links should be done according to prepulication checklit and make sure things according to item 6 inchecklist fix naked links. According to w3C specs in issue paper.

kurt: online payments he put in pull request, in should be able to get that paper out.

lisa: doesn’t have any pull requests, asked if its merged

Kurt: online payment seemed didn’t go through

Lisa: you need to make a pull request and michael will talk you through. I have no open pull request I’m not seeing it.

Kurt: said has not made any changes that is effecting the meaning, Lisa: as with Kirkwood, put into an email and send to list. Anything that changes maning should be emailed to list.

Rich: the first public working draft of API and formal tequest to talke a look and sub tmam to talke a look at issues. It doesn’t hurt but not necssary to look at it. He’sll have a better answer in a week or two.

Security aned Modality issue paers look pretty mature.

Nina: have not been able to get to the issue paper.

Lisa: tring to resolve Kurt’s pull request

Debbie: update on issue paer. Voice or Emotion? Adding content to voice one, sent it to list a couple of weeks ago . Working on updating repository. Forked it rather than working on master and should be able to push it back. Working on that right now. I’m getting voice done before doing the emoiton one. Eotion will be a whold new issue paper. Will use template from homepage.

<Lisa_Seeman> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2014Oct/att-0054/COGAIssuePaperTemplate.html

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Proposal_for_WCAG

Lisa: WCAG extension to go over. Went over Kurt’s comments this morning. Cross refernecng should be checked. Not sure if we should keep references. Put in as editors note. Good comments.

<Lisa_Seeman> next item

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/issue-papers/voice-menus.html

Lisa: know ddebbie wants to put more changes in voice. proposed solutions to standardize by reserving the zero for specific
... debbie has more comments to add to list, then we take this and move into gap analysis in table, simple to use voice memo systems. refernece 1.4.4 link has more examples.

Allow using 0 for a human. Do we want to put human in additional symantics. Would it make sense to do that here, back , undo, human operator.

Debbie: there is a standard for spoken language and digits, operator you say operator’ users with cognitive disabilites will not be able to ramember all of them. I could remember half of in the etsy? standard

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/semantics.html

<ddahl> ETSI standard http://www.etsi.org/deliver/etsi_es/202000_202099/202076/02.01.01_50/es_202076v020101m.pdf

Lisa: discussion of symantic based adaptablity would be an opiton for voice systems

debbie: best practice to press zero to get to operation. but we can’t have something that says operator. Could use through smaret phone, but couldn’t do it with a current phone. Datalink with phone would not be possible. But technology doesn’t exist now
... could use something lie tropo(?) or trillio(?)

lisa: skype would work

debbie: 0 for operator or say operator is as much realistically we can expect people to learn

lisa: symanitic + user agent such as skype, would enable people to not just press zero for operator we could have a standard tool bar

ddahl: visual ivr will display your choices on screen at anytime
... display navigation, worried about going back to a previous state there is cognitive load there. udoing what we are doing by going back.
... concerned about cognitive load about going back

kirkwood: what about getting a summary of what you have chosen so far

dddahl: more than three itmes in menu, company specific jargon

seeman: advertising is an issue

ddahl: keep things as short as possible, no more than three items

lisa: haven’t resolved very much here. need to make sure use best practices in wcag extension. We shoul has out what we have been discussing, low memory forget context. For epeop;e ot go cak a step can we put in an issue paper? maybe thats a meeting at TPAC?

ddahl: they are closed
... we can have some kind of discussion at TPAC

<ddahl> Voice UI guidelines

<ddahl> http://videsign.wikispaces.com/

<ddahl> can talk with Multimodal Interaction WG or a possible Voice Community Group at TPAC

<Lisa_Seeman> https://rawgit.com/w3c/coga/master/gap-analysis/semantics.html

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/sedaris/thaddeus/
Succeeded: s/dabbie/ddahl/
Succeeded: s/Debbie/ddahl/
Found Scribe: Kirkwood
Inferring ScribeNick: kirkwood

WARNING: No "Topic:" lines found.

Present: Janina

WARNING: Fewer than 3 people found for Present list!

Regrets: Chaohai_Ding John_Rochford E.A._Draffan

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

Got date from IRC log name: 25 Apr 2016
Guessing minutes URL: http://www.w3.org/2016/04/25-coga-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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