<LisaSeemanKestenbaum> finding your way around the document and more work in the design requirements process some issues
<LisaSeemanKestenbaum> finding your way around the document and
<LisaSeemanKestenbaum> more work in the design requirements
<LisaSeemanKestenbaum> process some issues
<LisaSeemanKestenbaum> scribe: roy
<JohnRochford> +1 to work on new schedule for calls
Lisa: find a new time to have this meeting in new year.
<kirkwood> I’m sure I will be able to work it out
Lisa: we need work on more
recruiting
... any ideas for recruiting?
<kirkwood> my understanding: recruiting need is for, subject matter experts, technology pros
Lisa: pls keep eye on any conference on any possible to recruiting.
john: still work on Easy reading
<LisaSeemanKestenbaum> ACTION: john rochford to do easy reading summary
<trackbot> 'jr' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., jfoliot, jkirkwoo, JohnRochford).
<LisaSeemanKestenbaum> ACTION: JohnRochford to do easy reading summary
<trackbot> Created ACTION-289 - Do easy reading summary [on John Rochford - due 2018-08-02].
<LisaSeemanKestenbaum> https://w3c.github.io/coga/gap-analysis
lisa: give design requirements for developers
<JohnRochford> BRB
lisa: make sure what we say, avoid timeout, let them know what time it is.
jk: will do that part.
lisa: use the plain language to have this doc
<JohnRochford> I'm back.
lisa: try let people know what
you want to do, example: use ADD will cause confuse.
... assign work to Shari.
<LisaSeemanKestenbaum> User testing - Does the user understand what things are and know how to use them
<LisaSeemanKestenbaum> Test for the following:
<LisaSeemanKestenbaum> Does the user know what the page is about
<LisaSeemanKestenbaum> Does the user know what actions they can take on a page
<LisaSeemanKestenbaum> Does the user know where they are in a website, an application or a multistep process
<LisaSeemanKestenbaum> Can the user easily find the different section of content
<LisaSeemanKestenbaum> Identify the different activities that the user may want to complete on the page.
<LisaSeemanKestenbaum> Can they achieve the activities without asking for help
<LisaSeemanKestenbaum> Does the user make errors trying to achieve the activities
<LisaSeemanKestenbaum> Does they user find them easy to achieve
<LisaSeemanKestenbaum> Example user stories: Does the user understand what things are and know how to use them
<LisaSeemanKestenbaum> This leads to the following user stories:
<LisaSeemanKestenbaum> I am familiar with the user interface (UI) where everything happens, and I know how to work it and what will happen when I work it.
<LisaSeemanKestenbaum> I know what to click to make things happen
<LisaSeemanKestenbaum> I like content delivered in an easy-to-understand mode.
<LisaSeemanKestenbaum> I like simple content with few options and consistent text .
<LisaSeemanKestenbaum> I know what this page does
<LisaSeemanKestenbaum> I know how to do XXX
lisa: Theme: Help users understand what things are and know how to use them
<kirkwood> +1 to Janina
<JohnRochford> How about "Design Requirements Best Practices"?
janina: use the best
practices
... good way to tell reader this is a good way to practices
<kirkwood> valid point that best practices might be too loose
lisa: we can raise the open issue
for change the name to practices
... give everybody have a chance to think about that.
<LisaSeemanKestenbaum> themes less wordy
<LisaSeemanKestenbaum> achtion Johnk to make themes less wordy
<LisaSeemanKestenbaum> action Johnk to make themes less wordy
<trackbot> Created ACTION-290 - Make themes less wordy [on John Kirkwood - due 2018-08-02].
<LisaSeemanKestenbaum> ack l\
<LisaSeemanKestenbaum> ACTION: roy to make script to alow sections to expand
<trackbot> Error finding 'roy'. You can review and register nicknames at <https://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.
<LisaSeemanKestenbaum> ACTION: ran to make script to alow sections to expand
<trackbot> Created ACTION-291 - Make script to alow sections to expand [on Ruoxi Ran - due 2018-08-02].
<LisaSeemanKestenbaum> ACTION: ran to seperate apendix
<trackbot> Created ACTION-292 - Seperate apendix [on Ruoxi Ran - due 2018-08-02].
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) Succeeded: s/john/jr/ Succeeded: s/no quarum// Present: janina Roy LisaSeemanKestenbaum JohnRochford kirkwood Regrets: EA glenda Alister Found Scribe: roy Inferring ScribeNick: Roy 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: john johnrochford ran rochford roy 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]