<Lisa_Seeman> agenda: this

<janina> Hi, Lisa. I'll be moving about during the COGA hour today, but will try to stay on phone.

<Lisa_Seeman> scribe: JohnRochford

preview agenda

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

<Tony_Doran> Apologies everyone, I can't seem to get a phone connection to hold up.

Kinshuk sends his regrets

Joseph: Non-vocal gap analysis not yet finished, profiles/personas needed

Debra: Down Syndrome gap analysis - John Foliot will add content provided by Debra

Lisa: contacted WebAIM, Jared Smith may join task force
... gap analyses will include technologies in a broader space, from an architectual point of view
... informal meeting after call about what to put into a gap analysis

John & Neil: About autism gap anaylis - new info about profiles/personas to be added this week

Lisa: current plan for gap analyses - 6 weeks internal review, 6 weeks external review, disability user groups, technologies review
... pre-review and review of background research before submission to parent groups
... timeframe = about 3 months
... Are people comfortable with this timeline?
... time frame of 3 months started last week

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Reports#June_2014_-_Task_Force_Report

Rich: Do we have a criteria by which we will evaluate the gap analyses?

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Gap_Analysis/Introduction#Methodology_in_User_Research

Lisa: responds to Rich by providing web addresses of examples

<richardschwerdtfeger> https://docs.google.com/spreadsheet/ccc?key=0AkuU97mmSy0mdGMxRm5IdVVOUllhTThqeE9tYnZuMnc&usp=drive_web#gid=0

Rich: Web address is to example of what he thinks is needed for gap analyses
... Task Force is welcome to use anything from the info he just provided

Lisa: Does anyone prefer to hold out on short summaries until metrics of technologies are decided?

<richardschwerdtfeger> +1

<Elle_Waters> I think that's best, yes.

<Ryladog> +1

<neilmilliken> I would like a skeleton

<neilmilliken> with limited info and links

<neilmilliken> not a finished summary.

Lisa: Proposition 1: Hold out on summaries until tech piece.
... Proposition 2: Iterative approach to summaries first

<Lisa_Seeman> 1. hold out on short summaries until metrics of technologies are decided?

<Lisa_Seeman> 2. iterative approach and summaries now.

Lisa: summaries refer to technologies such as GPII and Fluid

<richardschwerdtfeger> +1 to 2

<neilmilliken> 2 for me

<Elle_Waters> 2 is good for me

+1 to 2

<slee> 2

<Elle_Waters> (as long as we actually iterate! :) )

<ddahl> 2 for me

Lisa: Motion for proposition 2 has been carried

<Lisa_Seeman> Assistive technologies such as AAC and AAC core vocabularies

<Lisa_Seeman> Reading techs

<Lisa_Seeman> Adaptability

<Lisa_Seeman> APIP and IMS

<Lisa_Seeman> Daisy and epub

<Lisa_Seeman> Aria

<Lisa_Seeman> Indi ui

<Lisa_Seeman> Fluid

<Lisa_Seeman> ISO

<Lisa_Seeman> Voice ML and menu systems

<Lisa_Seeman> RDFA

<Lisa_Seeman> Web Security (Including CAPTUR)

<Lisa_Seeman> Web RTC (real time communications)

<Lisa_Seeman> WCAG

<Lisa_Seeman> Access for all and GPII

<Lisa_Seeman> EMMA

<Lisa_Seeman> Also see HTML 5 wishlist

<Ryladog> +1 to 2

<richardschwerdtfeger> ISO?

<slee> ISO 24751

<Ryladog> http://www.imsglobal.org/accessibility/

<Lisa_Seeman> add userbility knowlage

<neilmilliken> agree with elle there are various strands

<neilmilliken> I have already done som cross over mapping

<neilmilliken> elle do you want to work with me on this?

<Lisa_Seeman> ACTION: elle do useability review - step 1: defining scope and terms [recorded in http://www.w3.org/2014/06/16-coga-minutes.html#action01]

<trackbot> Created ACTION-17 - Do useability review - step 1: defining scope and terms [on Elle Waters - due 2014-06-23].

Elle: Wants feedback about defining terms and scope

9mostly)

Elle: wants feedback mostly about defining terminoligy and language

<EA> Readability scores - Flesch and Fog Analysis?

<slee> EA: yes that sort of thing

<slee> and tools that support them

<EA> Readability tends to measure the length of words used in sentences and scores on that basis - so could be used for saying how easy a piece of text might be.

<Elle_Waters> elle@simplyaccessible.com

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

<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Gap_Analysis/Introduction#Methodology_in_User_Research

<EA> How do we gather information from users with Aphasia etc when we do not have ethics? I think I could only do it from experience and friends

<Lisa_Seeman> https://www.w3.org/Member/Mail/

<josephoconnor> Lisa, can you send the last link again?

<Elle_Waters> cheers!

<slee> :)

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JohnRochford
Inferring ScribeNick: JohnRochford
Default Present: Lisa_Seeman, JohnRochford, Joseph_O´Conno, DebraRue, slee, Michael_Cooper, neil, +1.512.659.aadd, Susann_Keohane, Debbie_Dahl, Elle_Waters, EA_Draffan, Janina, Rich_Schwerdtfeger, Katie_Haritos-Shea, [IPcaller]
Present: Lisa_Seeman JohnRochford Joseph_O´Conno DebraRue slee Michael_Cooper neil +1.512.659.aadd Susann_Keohane Debbie_Dahl Elle_Waters EA_Draffan Janina Rich_Schwerdtfeger Katie_Haritos-Shea [IPcaller]
Regrets: Kinshuk

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: 16 Jun 2014
Guessing minutes URL: http://www.w3.org/2014/06/16-coga-minutes.html
People with action items: elle

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