See also: IRC log
<trackbot> Date: 21 April 2015
<MichaelC> trackbot, make log world
<trackbot> Sorry, MichaelC, I don't understand 'trackbot, make log world'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.
<MichaelC> meeting: Cognitive Accessibility Task Force Face to Face, Day 1
<Lisa_Seeman> hello michael
<janina> Hello, Lisa!
<Lisa_Seeman> Hello Janina!
<Lisa_Seeman> We are helping people find the building
<Lisa_Seeman> and the room
<Lisa_Seeman> we are calling in
<Lisa_Seeman> ok, try again
<Lisa_Seeman> the plug feel
<Lisa_Seeman> fell
<Lisa_Seeman> will need to tell people more when we are going out the room
<neilmilliken> Good morning
<Lisa_Seeman> scribe: slee
<Lisa_Seeman> -
<Lisa_Seeman> Meeting technologie
<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page
<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/FTF_issues_and_agenda
https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/FTF_issues_and_agenda
Our mandate is to produce a Gap analysis and roadmap to guide W3C in supporting coga
we have produced a User Research is a collection of information used to inform other work. Is at 1st Draft status
User research is now on github
Now creating techniques to collate and guide devs - 1st editors draft
Also creating issue papers to cover areas that need attention
<neilmilliken> https://github.com/w3c/coga/tree/master/issue-papers
<MichaelC> https://w3c.github.io/coga/issue-papers/index.html
issue papers and techniques also on git hub at https://github.com/w3c/coga/tree/master
WCAG - we will impact their deliverables (WCAG)
PF - we influence ARIA and other key W3C technology specs
in both cases we have opportunity to ensure coga is well supported
Also we can see how existing tech can share concepts to support coga by getting involved in conversations
WCAGs new draft charter specifically includes coga
WCAG want 1st working draft of coga extension by Nov
The details of WCAG extensions are being worked out. currently 2: coga, mobile.
<janina> RFC2119 defined at https://tools.ietf.org/html/rfc2119
<Lisa_Seeman> thanks
<Lisa_Seeman> sorry for interrupting michael - i just didnt want people to not understand the terms
They are likely to be layered on top of WCAG and will be normative (see RFC2119 defined at https://tools.ietf.org/html/rfc2119)
For example techniques are not normative
it is not yet clear if extension can override the core spec - we need to think about that
also not clear if A/AA/AAA will apply to extensions
we can influence the structure of the coga extension by discussing with WCAG
<Lisa_Seeman> http://www.w3.org/2015/04/21-coga-minutes.html
the coga strategy is to concentrate on what needs to be done then what can be done and by keeping the gap analysis showing how it can fit it with WCAG once extension and refresh once details of extensions are clearer
<ayelet_s> I can't hear very well - is it just me?
<ayelet_s> thank you
Lisa using a tree chart to help analyse coga support of/in WCAG
Can suggest techniques to be added to WCAG
Very likely to need to look at conformance levels. Thoughts that some coga issues are currently at AAA but we'd most likely like them at AA so more often implemented
do we need additional success criteria for similar reasons
<MichaelC> http://www.w3.org/TR/wcag2-req/
Criterion that are testable are more likely to be adopted by WCAG
providing a testing methodology will help (doesn't have to be tool testing,can be user)
coga and mobile extension will interplay
wearables are poised to be highly popular and used under cognitive load
iOT is also important (we have an issue paper already)
Aria and IndiUI are related to our work and also have modules,
However for coga design and contenta are very important and may not be directly handled in other activities
Other W3C activities like VoiceML where we can have important impact
Providing extended help can be supported via technology like ARIA or standards cross content design
<Lisa_Seeman> http://www.w3.org/2015/04/21-coga-minutes.html
<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Gap_Analysis
<Lisa_Seeman> scribe:tony
<Tony_Doran> New table of contents for Gap Analysis
<Tony_Doran> Need to identify types of Gaps
<Tony_Doran> Important to state limitations in gap analysis
<Tony_Doran> Roadmap solutions are based on gap analysis
<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Methodology_for_gap_analysis
<Lisa_Seeman> topi: methodogy
<Tony_Doran> Gap analysis feeds into roadmap.
<Tony_Doran> We do not need research provided experts are confident. Reasearch is the Gold standard but is not necessary.
<Tony_Doran> If the WG has concensus.
<Tony_Doran> Company specific research needs to be evaluated.
<Tony_Doran> it may be skewed. Caution is advised.
<Tony_Doran> Gap is defined as "When a person could theoretically do something but is hindered by design/implementation"
<Tony_Doran> Content may also be the issue.
<Tony_Doran> Undeclared disability is an issue
<Tony_Doran> Stigma and privacy is also an issue - people may not request accomodations as it may draw attention
<Tony_Doran> Gap analysis category format is preferred.
<Tony_Doran> Tables to be used under category.
<Tony_Doran> Headings - Suggestion, Reason, Confidence level, Who it helps and See Also
<Tony_Doran> See Also may reference other WG work, references or relevant information
<Lisa_Seeman> 15 minit lunch and bathroom
<ayelet_s> would you be able to write on the irc channel when you begin? Thanks
<Lisa_Seeman> scribe: mike
<Lisa_Seeman> scribe: Mike_Pluke
Starting to look at a gap analysis on privacy and security
<Lisa_Seeman> https://w3c.github.io/coga/issue-papers/index.html
<ayelet_s> I was worried it was just me
<slee> we are back now
<slee> ayelet_s: ^
<Lisa_Seeman> thanks neil
<ayelet_s> thanks :)
<Lisa_Seeman> https://w3c.github.io/coga/issue-papers/privacy-security.html
<Lisa_Seeman> https://w3c.github.io/coga/issue-papers/privacy-security.html
<ayelet_s> Lisa, would it be possible for you to get closer to the microphone? thanks
<Lisa_Seeman> ok
<ayelet_s> thank you
The ease of use section of the web security proposed solutions contain some very important but very broad topics e.g. Develop and use common sets of vocabulary and iconography across web security and privacy technologies
These are probably outside the remit of W3C alone
In the category of new requirements we might have to indicate that copying is not an acceptable task for users
The only way to progress the work will be to bring a "solution" to a meeting and then iteratively change it.
<scribe> NEW TOPIC: User research document
<Lisa_Seeman> https://w3c.github.io/wcag/coga/user-research.html
<Lisa_Seeman> https://w3c.github.io/wcag/coga/user-research.html
restructuring the user research document
Discussion of the possibility of a phase 2 of user research
<ayelet_s> Mike, could you put in the 2 options?
Suggesting that the Downs Syndrome should be reconsidered alongside intellectual disabilities (with Downs Syndrome as an example). John has volunteered to do the work.
Mike will attempt to separate the Aging and Dementia category - whilst maintaining the link
<ayelet_s> thanks Mike
<Lisa_Seeman> ACTION: john to change down syndrom section to Intelectual disabilities and use DS as an example , with discalimer [recorded in http://www.w3.org/2015/04/21-coga-minutes.html#action01]
<trackbot> 'john' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., jfoliot, JohnRochford).
<Lisa_Seeman> ACTION: JohnRochford to change down syndrom section to Intelectual disabilities and use DS as an example , with discalimer [recorded in http://www.w3.org/2015/04/21-coga-minutes.html#action02]
<trackbot> Created ACTION-88 - Change down syndrom section to intelectual disabilities and use ds as an example , with discalimer [on John Rochford - due 2015-04-28].
<Lisa_Seeman> ACTION: Mike to seprate aging and demaintia in user reaserch [recorded in http://www.w3.org/2015/04/21-coga-minutes.html#action03]
<trackbot> 'Mike' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., mpluke, mikes).
Age-related cognitive decline is a common term - but aging is not a disability!
<Lisa_Seeman> ayelet?
<ayelet_s> yes
TOPIC Getting citations right
<Lisa_Seeman> we can here
<Lisa_Seeman> hear
<ayelet_s> • https://github.com/tobie/specref
Step 1: Check if citation already exists
<ayelet_s> https://github.com/w3c/coga/blob/master/common/biblio.js
<ayelet_s> "Banaschewski-1": { "title": "Colour perception in ADHD", "authors": "Banaschewski, T.", "etAl": true, "publisher": "Journal of child psychology and psychiatry, and allied disciplines, Vol 47 Issue 6", "publishDate": "2006", //"pages": "568-572", },
<ayelet_s> "authors": [ "de Cock, M.", "Maas, Y. G.", "Van De Bor, M." ],
If the reference exists, then just put the reference within double square brackets e.g. [[APA-1]]
If not present - send an email to Ayelet and say that [[LISA-1]] is this reference - and quote the reference from LISA.
<ayelet_s> my email is ayelet.projects1@gmail.com
<Lisa_Seeman> https://github.com/w3c/coga/blob/master/common/biblio.js
<ayelet_s> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Citations
<ayelet_s> this is the wiki of the citations, it's slightly out of date, but I hope to update it tonight
<Lisa_Seeman> thanks!!
<ayelet_s> welcome!
<Lisa_Seeman> https://lists.w3.org/Archives/Public/public-coga-comments/2015Feb/0000.html
Feedback not addressed being discussed
<ayelet_s> I'm not catching much, so I think I will join Rich.
<Lisa_Seeman> ayelet?
<MichaelC> Better view of the references now being output: https://w3c.github.io/coga/user-research/#references
One comment proposed basing categories on ICF, ICD-10 and DSM. This is the approach taken by ETSI STF 488.
<Lisa_Seeman> 211taxonomie.org
<Tony_Doran> https://211taxonomy.org/
<Lisa_Seeman> http://www.who.int/classifications/icd/en/
<Tony_Doran> http://www.dsm5.org/Pages/Default.aspx
<Lisa_Seeman> http://www.dsm5.org/Pages/Default.aspx
<Lisa_Seeman> also the ICF
<Lisa_Seeman> ACTION: Ayelet to look at harminze with the who and eman http://www.who.int/classifications/icd/en/ and dsm and ICF , ISM [recorded in http://www.w3.org/2015/04/21-coga-minutes.html#action04]
<trackbot> Created ACTION-89 - Look at harminze with the who and eman http://www.who.int/classifications/icd/en/ and dsm and icf , ism [on Ayelet Seeman - due 2015-04-28].
John Rochford drew attention to the AIRS/211 LA County Taxonomy of Human Services.
Ayelet has agreed to take a look at this and John Rochford has agreed to pay for her subscription to do this.
<Lisa_Seeman> scribe: Chaohai_Ding
<scribe> New Topic: GPII and Adaptable Content
<Tony_Doran> http://wiki.gpii.net/w/Architecture_Overview
Introduce the the GPII Architecture Illustrated
User listeners component will detect this key and send it to the Flow Manager
All the architecture design is done , but no budget to run the GPII server.
The finance support for AT products or services and collaboration with industrial companies is discussed.
<slee> http://www.tamercrea.es/rtf/wp-content/uploads/GPII.png
Steve Lee introduced the major components in GPII
discussed the AT products and the important of content design
<slee> http://wiki.gpii.net/w/Preference_Terms_Dictionary
<slee> http://terms.raisingthefloor.org/details/magnification
Introduce the framework of GPII preference terms and the terms are crowdsourced data
<Lisa_Seeman> https://dl.dropboxusercontent.com/u/573324/presentations/CSUN2015/INotifier/index.html
<Lisa_Seeman> https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Syntax_for_adaptable_links_and_buttons
<neilmilliken> http://restylethis.com/site/
<janina> We need to fix the audio
<janina> No one seems to be scribing!
Now discuss the issues for implementing the adaptable content
The needs for building a demo fro adaptable symbols is also discussed.
Steve Lee stated the symbol based user interface and there are 4 volunteers trying to build the demos from different ways.
<Lisa_Seeman> ACTION: Lisa to write a speck for json/rest personlisation thing [recorded in http://www.w3.org/2015/04/21-coga-minutes.html#action05]
<trackbot> Created ACTION-90 - Write a speck for json/rest personlisation thing [on Lisa Seeman - due 2015-04-28].
Now discuss what other specification needed for this json/rest personlization thing
The need of place for registrate the JSON-based profile is discussed.
<Lisa_Seeman> ACTION: steve to identify what pieces are needed for thejson speck [recorded in http://www.w3.org/2015/04/21-coga-minutes.html#action06]
<trackbot> Created ACTION-91 - Identify what pieces are needed for thejson speck [on Steve Lee - due 2015-04-28].
<janina> 1. Dial +44-20-7100-6747
<janina> 2. At the prompt dial *5032220#
<janina> 3. At the Zakim prompt dial 2642#
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: slee Inferring ScribeNick: slee Found Scribe: tony Found Scribe: mike Found Scribe: Mike_Pluke Inferring ScribeNick: Mike_Pluke Found Scribe: Chaohai_Ding Inferring ScribeNick: Chaohai_Ding Scribes: slee, tony, mike, Mike_Pluke, Chaohai_Ding ScribeNicks: slee, Mike_Pluke, Chaohai_Ding WARNING: Dash separator lines found. If you intended them to mark the start of a new topic, you need the -dashTopics option. For example: <Philippe> --- <Philippe> Review of Action Items WARNING: No "Present: ... " found! Possibly Present: Chaohai_Ding JohnRochford JohnRochford_ John_Rochford Lisa_Seeman MichaelC Michael_Cooper Mike_Pluke NeilMilliken P1 P3 P4 P9 Rich_Schwerdtfeger Steve_Lee Tim Tony_Doran ayelet_s ayelet_s_ coga ea https janina joined richardschwerdtfeger slee topi trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Agenda: https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/FTF_issues_and_agenda Found Date: 21 Apr 2015 Guessing minutes URL: http://www.w3.org/2015/04/21-coga-minutes.html People with action items: ayelet john johnrochford lisa mike steve WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]
