[17:06:00] ‹Jennie› Lisa: decide what to do to publish the gaps analysis. [17:06:04] ‹LisaSeemanKestenbaum› https://docs.google.com/document/d/1aNl2uIkNlbch1QXoBHY675DC9vnOuoKFq20arP1q3Oo/edit [17:07:10] ‹Jennie› Lisa: iterative, still to-dos. Abstract ready? [17:07:30] ‹LisaSeemanKestenbaum› a
[17:01:42] ‹Jennie› Present+ Jennie [17:02:49] ‹LisaSeemanKestenbaum› regrets: janina [17:03:28] ‹alastairc› present+ [17:03:45] ‹LisaSeemanKestenbaum› scribe: Jennie [17:04:26] ‹kirkwood› present+ [17:04:47] ‹LisaSeemanKestenbaum› lisa: how to do miniets [17:05:06] ‹LisaSeemanKestenbaum› sc
[16:48:37] ‹LisaSeemanKestenbaum› rrsagent, make logs public
[16:49:17] ‹LisaSeemanKestenbaum› agenda+ what else is needed to publish the making content usesable and the next version of the gap analisis. See https://docs.google.com/document/d/1aNl2uIkNlbch1QXoBHY675DC9vnOuoKFq20arP1q3Oo/edit and the design requirments .
[12:01:11] * Zakim notes agendum 1 added
[16:53:20] ‹LisaSeemanKestenbaum› agenda+ can design requirments be embeded ? if so how
[12:01:11] * Zakim notes agendum 2 added
[16:59:23] → Jennie (~Jennie@public.cloak) has joined
[17:01:42] ‹Jennie› Present+ Jennie
[17:02:49] ‹LisaSeemanKestenbaum› regrets: janina
[17:03:28] ‹alastairc› present+
[17:03:45] ‹LisaSeemanKestenbaum› scribe: Jennie
[17:04:26] ‹kirkwood› present+
[17:04:47] ‹LisaSeemanKestenbaum› lisa: how to do miniets
[17:05:06] ‹LisaSeemanKestenbaum› scribe: Jennie
[17:05:09] → steve (~steve@public.cloak) has joined
[17:05:46] → Glenda (~goodwitch@public.cloak) has joined
[17:06:00] ‹Jennie› Lisa: decide what to do to publish the gaps analysis.
[17:06:04] ‹LisaSeemanKestenbaum› https://docs.google.com/document/d/1aNl2uIkNlbch1QXoBHY675DC9vnOuoKFq20arP1q3Oo/edit
[17:07:10] ‹Jennie› Lisa: iterative, still to-dos. Abstract ready?
[17:07:30] ‹LisaSeemanKestenbaum› are we happy can i put this to cfc (whole doc)
[17:07:35] ‹kirkwood› +1
[17:07:42] ‹steve› what is it with WebEx recently - fighting to get it to work, again
[17:07:49] ‹alastairc› +1
[17:07:54] ‹LisaSeemanKestenbaum› im sorry streve
[17:07:55] ‹Glenda› +1
[17:08:23] ‹Jennie› +1
[17:09:33] ‹LisaSeemanKestenbaum› https://docs.google.com/document/d/1aNl2uIkNlbch1QXoBHY675DC9vnOuoKFq20arP1q3Oo/edit#
[17:09:36] ‹kirkwood› present+
[17:09:46] ‹Glenda› present+
[17:09:53] ‹Jennie› Resolution: Gap Analysis iteration is ready
[17:10:14] ‹LisaSeemanKestenbaum› https://rawgit.com/w3c/coga/separate-usable-doc/content-usable/usable.html#design_requirements
[17:10:48] ‹Jennie› Lisa: link includes design requirements. Might want an easy reading introduction.
[17:11:53] ‹Glenda› I do like the idea of an easy reading intro. I think it helps everyone.
[17:12:14] ‹Jennie› Can it be published with an easy reading executive summary?
[17:12:45] ‹Jennie› Glenda: summary will help everyone.
[17:13:06] ‹Glenda› Have you tried: https://contentclarifier.mybluemix.net
[17:14:38] ‹kirkwood› +1
[17:16:36] ‹Jennie› Lisa: public facing
[17:16:38] ‹Jennie› +1
[17:16:46] ‹steve› +1
[17:17:06] ‹Glenda› Here is what Content Clarify created as a summary for the Design Requirements:
[17:17:08] ‹Glenda› This document aims to provide guidance on how to make websites and applications that are friendly for people with cognitive impairments by providing guidance for your designs, and design process. Things making friendly for people with cognitive impairments are best dealt with as part of the overall design process. Scope should be for taking a user-centred design process. People with cognitive impairments are [CUT]
[17:17:09] ‹Glenda› An organization should expend How much effort. For organizations that provide public services, or are national (or international) private service providers and already conduct user-research, they should: * Include people with learning and cognitive disabilities as part of user research such as usability-testing; Organizations do not include usability testing as part of the process.
[17:17:23] ‹LisaSeemanKestenbaum› https://w3c.github.io/coga/gap-analysis/#people-with-cognitive-and-learning-disabilities-and-the-web
[17:17:43] ‹LisaSeemanKestenbaum› with ad note . - we intend to sdd to this section
[17:18:57] ‹Jennie› Lisa: add a summary of user needs in this section. Consider getting rid of user needs for now.
[17:20:28] ‹Jennie› Lisa: how much do we want to do before we publish?
[17:21:39] ‹Jennie› Alastair: need to approve as a first draft. Should have an abstract, formatting should be correct.
[17:22:50] ‹Jennie› Lisa: Design Requirements section 5.1 has better draft in Google Docs
[17:23:31] ‹Jennie› Alastair: if accordion style or other format is decided, it will need to go somewhere else.
[17:23:44] ‹Jennie› Alastair: e.g. WCAG QuickRef
[17:23:47] → Roy_ (ran@public.cloak) has joined
[17:25:01] ‹Glenda› Taking User Needs and making a quick table of contents like this:
[17:25:07] ‹Glenda› User Needs
[17:25:08] ‹Glenda› 1) Authentication and Safety
[17:25:09] ‹Glenda› need a method of secure website authentication that I find easy to use
[17:25:11] ‹Glenda› need a safe way to interact online.
[17:25:12] ‹Glenda› 2) Context and Distractions
[17:25:14] ‹Glenda› need to consume content or complete a task without unnecessary distractions
[17:25:15] ‹Glenda› need to know the context, where I am, and what I just did, or what just happened to me.
[17:25:17] ‹Glenda› need to restore context when I forget where I am or get distracted
[17:25:18] ‹Glenda› need to restore context in multimedia. I need to go back to that bit I just missed, or reorient myself if I lost context
[17:25:20] ‹Glenda› need reminders of important information
[17:25:21] ‹Glenda› need to turn off distractions 1) to be a default, and 2) to be a trivial option in real time
[17:25:21] ‹Glenda› 3) Entering Data, Error Prevention, & Recovery
[17:25:26] ← Roy (ran@public.cloak) has quit ( Ping timeout: 180 seconds )
[17:25:56] ‹kirkwood› agreed
[17:26:39] ‹Jennie› Glenda: volunteers
[17:26:45] ‹LisaSeemanKestenbaum› gleda to do user needs!
[17:29:34] ‹LisaSeemanKestenbaum› https://rawgit.com/w3c/coga/separate-usable-doc/content-usable/usable.html#design_themes
[17:30:40] ‹Jennie› Lisa: assuming there is a pull out document, do we want bullet points of design requirements?
[17:31:05] ‹LisaSeemanKestenbaum› https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.45rzy595ojw1
[17:34:04] ‹Jennie› Lisa: Design requirement themes and link? Design requirements in bullet points? Themes separated out from design requirements?
[17:34:54] ‹Jennie› Steve: I would be happy with a linking summary.
[17:36:09] ‹Jennie› Alastair: linking from Make Usable document.
[17:36:35] ‹Jennie› Lisa: Google doc will be moved over
[17:40:44] ‹LisaSeemanKestenbaum› https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.gmpmiu9yrnze
[17:40:59] ‹Jennie› Lisa: Roy will be moving the design requirements to HTML when it is time, how much time will that take?
[17:41:35] ‹Jennie› Roy: A week?
[17:42:31] ‹Jennie› Lisa: wait a week to enable everyone else to review, delete comments that have been dealt with
[17:44:00] ‹Jennie› Roy: 2-3 days to complete the work, fit in during a week
[17:45:54] ‹kirkwood› +1
[17:45:57] ‹Glenda› +1
[17:46:00] ‹Jennie› Lisa: group comfortable with this plan? Not the collapsible interface for this version
[17:46:22] ‹LisaSeemanKestenbaum› https://rawgit.com/w3c/coga/separate-usable-doc/content-usable/usable.html#user-group-mapping
[17:48:50] ‹Jennie› Lisa: rework section 5, add abstract, add Glenda's item
[17:49:11] ‹LisaSeemanKestenbaum› https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#
[17:49:14] ‹Jennie› Lisa: moving to Design Requirements
[12:01:11] * alastairc I couldn't find any with my name next to them, so I did one of the ones with an editors note.
[17:49:54] ‹Jennie› Steve: I have added information into the document, and have comments people can respond to
[17:50:25] ‹Jennie› Steve: summary of long documents, provide human help (may not have right voice)
[17:51:26] ‹kirkwood› its about correcting, no?
[17:51:58] ‹kirkwood› fix?
[17:52:25] ‹kirkwood› agreed on your interpresation of undo
[17:54:14] ‹Jennie› Lisa: possible overlap between undo and go back
[17:54:44] ‹Jennie› Lisa: put into more details that this shouldn't be done if it can't be done securely
[17:57:14] ‹Jennie› Lisa: this is a note, not a requirement.
[17:57:33] ‹LisaSeemanKestenbaum› q?
[12:01:11] * Zakim sees no one on the speaker queue
[17:57:50] ‹alastairc› q+
[12:01:11] * Zakim sees alastairc on the speaker queue
[17:58:58] ‹Jennie› Lisa: Steve and Jennie will be complete their drafts in the next few days
[17:59:07] → laura (~laura@public.cloak) has joined
[17:59:45] ‹Jennie› Lisa: can I remove some of the introduction pieces added by John?
[18:00:00] ‹Jennie› John: Yes.
[18:00:51] ‹Jennie› Lisa: Glenda can I move yours into clear text?
[18:00:54] ‹Jennie› Glenda: yes
[18:01:54] ‹Jennie› Lisa: I will try on Monday to have group review before it goes to Roy. There will be a short time to review. Deal breakers only.
[18:02:00] ‹Jennie› +1
[18:02:16] ‹alastairc› https://www.w3.org/2002/09/wbs/35422/process-results-pt1/results
[18:03:00] ‹Jennie› Lisa: this will go onto agenda for next week
This is scribe.perl Revision: 1.153 of Date: 2018/09/19 14:40:21 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) WARNING: No "Present: ... " found! You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy <amy> Present+ WARNING: Possible internal error: join/leave lines remaining: <LisaSeemanKestenbaum> [16:59:23] → Jennie (~Jennie@public.cloak) has joined <LisaSeemanKestenbaum> [17:05:09] → steve (~steve@public.cloak) has joined <LisaSeemanKestenbaum> [17:05:46] → Glenda (~goodwitch@public.cloak) has joined <LisaSeemanKestenbaum> [17:23:47] → Roy_ (ran@public.cloak) has joined <LisaSeemanKestenbaum> [17:59:07] → laura (~laura@public.cloak) has joined No ScribeNick specified. Guessing ScribeNick: LisaSeemanKestenbaum Inferring Scribes: LisaSeemanKestenbaum 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: WARNING: Possible internal error: join/leave lines remaining: <scribe> [16:59:23] → Jennie (~Jennie@public.cloak) has joined <scribe> [17:05:09] → steve (~steve@public.cloak) has joined <scribe> [17:05:46] → Glenda (~goodwitch@public.cloak) has joined <scribe> [17:23:47] → Roy_ (ran@public.cloak) has joined <scribe> [17:59:07] → laura (~laura@public.cloak) has joined WARNING: Possible internal error: join/leave lines remaining: <scribe> [16:59:23] → Jennie (~Jennie@public.cloak) has joined <scribe> [17:05:09] → steve (~steve@public.cloak) has joined <scribe> [17:05:46] → Glenda (~goodwitch@public.cloak) has joined <scribe> [17:23:47] → Roy_ (ran@public.cloak) has joined <scribe> [17:59:07] → laura (~laura@public.cloak) has joined 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 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.)[End of scribe.perl diagnostic output]