16:58:06 RRSAgent has joined #eo 16:58:06 logging to http://www.w3.org/2017/08/23-eo-irc 16:58:08 RRSAgent, make logs world 16:58:08 Zakim has joined #eo 16:58:10 Meeting: Education and Outreach Working Group Teleconference 16:58:10 Date: 23 August 2017 16:59:08 Laura has joined #eo 16:59:10 agenda+ Implementation: Update (Eric) 16:59:10 agenda+ Using new template for resources (Sharron) 16:59:10 agenda+ Testing: What is needed when? (With Charlotte) 16:59:10 agenda+ Navigation: Where would main navigation links go? (Eric, https://github.com/w3c/wai-website-design/issues/79) 16:59:11 agenda+ Navigation design direction: Multi-level fly-outs (https://w3c.github.io/wai-website-components/components/preview/example-home) or One level mega-ish menu (https://w3c.github.io/wai-website-components/components/preview/example-home-alt) 16:59:11 agenda+ IA: Quickref Links in main navigation (Eric, https://github.com/w3c/wai-website-design/issues/77) 16:59:43 zakim, who is on the phone? 16:59:43 Present: (no one) 16:59:46 present+ 17:00:26 present+ Brent, Charlotte, Laura 17:00:58 Scribe: Brent 17:01:48 okay 17:01:48 present+ Sahrron 17:01:59 Present+ Sharron 17:02:07 zakim, take up item 1 17:02:07 agendum 1. "Implementation: Update (Eric)" taken up [from yatil] 17:02:17 present- Sahrron 17:02:23 https://w3c.github.io/wai-website-components/components/preview/example-home 17:02:53 Eric: Quick update on home page. Changes to the navigation and the general width of the columns. 17:03:43 ... Working on the responsiveness now. Doing more work on that tomorrow. Just an FYI for everyone. Any questions? 17:03:53 No Questions 17:04:35 Eric: About Sharron's question about the new design templates. 17:05:24 zakim, take up next 17:05:24 agendum 2. "Using new template for resources (Sharron)" taken up [from yatil] 17:05:28 ... Yes, everything (current resources and new resources) will go in the templates of the new design. At some point we will be able to work on getting the QuickRef in the new design as well. 17:06:57 Sharron: For the business case, can we put the content in the new template so that we can preview in the new design? 17:07:11 Eric: Yes, I will work on that so you can add content by Friday. 17:07:39 Sharron: Eric "on the record," you are great. Thank you. 17:07:49 Eric: Okay, please send me the link to the repository. 17:07:52 zakim, take up next 17:07:52 agendum 3. "Testing: What is needed when? (With Charlotte)" taken up [from yatil] 17:08:18 Eric: Charlotte, what are the specifics that you need? 17:08:34 q+ 17:08:55 Charlotte: Any specific questions and tasks that you want people to perform on the site during usability testing. Or anything else that you are curious about. 17:09:06 ... Please send as soon as you can. 17:09:46 q+ to ask test plan in wiki page? to say demographics in e-mail -- anything else? to say more issues later... 17:09:47 ... I am going to start recruiting participants next week. If you have ideas or recommendations for audiences, please let me know write away. 17:09:57 ack me 17:09:57 shawn, you wanted to ask test plan in wiki page? to say demographics in e-mail -- anything else? to say more issues later... 17:10:03 ack shawn 17:10:05 ... I am also working up the usability testing plan now as well. 17:10:42 Shawn: I think I did put some ideas for roles and demographics for participants. 17:11:06 Charlotte: I don't see the demographics, please send them again. 17:11:53 Shawn: Will the test plan be in a Wiki page or in a Word doc? Would be nice to put it in a Wiki so all can see, including Visa. 17:11:57 Chair: Eric 17:12:05 regrets: James 17:12:38 ... We are also working on final draft of IA and some of the renaming titles of a few of the documents. We are going to try and get those to you as soon as possible. 17:13:23 Charlotte: We can also bring the naming recommendations to the research participants as well. Let them look at the resource and ask which proposed name is best. 17:13:38 ... Can someone send me the URL for the new site? 17:13:45 Shawn: Yes, I will. 17:14:24 Shawn: I have been working on travel. Just want to confirm that we are doing Sept. 19, 20, 21. 17:14:33 Charlotte: Yes, those are the dates. 17:17:41 Sharron will send information to Norah about dates to see if she can attend. 17:18:23 s/We are going to try and get those to you as soon as possible./We are going to try and get those to you as soon as possible. Also may have specific questions later. 17:18:56 zakim take up next 17:19:00 zakim, take up next 17:19:00 agendum 4. "Navigation: Where would main navigation links go? (Eric, https://github.com/w3c/wai-website-design/issues/79)" taken up [from yatil] 17:20:19 Eric: We have the main navigation items. Some navigation items have no pages behind them. Without javascript we need some way to link in the navigation on the pages. 17:20:31 https://w3c.github.io/wai-website-components/components/preview/example-home 17:20:39 s/Some navigation items have no pages behind them./ / 17:21:37 q+ 17:22:17 q+ to say opinion (after others) 17:22:21 ack l 17:22:34 ack s 17:22:34 shawn, you wanted to say opinion (after others) 17:22:37 Laura: I am curious what Charlotte thinks. I've seen in the past where there is an aggregate page of all items in that menu. We don't do this at LOC. 17:23:29 Shawn: I strongly think we need to go to a page that has all the navigation. If they go to one resource then they won't have the navigation, which is what we are trying to move away from. 17:24:00 q+ 17:24:27 ... One of our goals is to make it easy for people to see what is on the whole site. I am leaning towards one page that has all the nav. Instead of having to click on multiple links to get to the full navigatoin. 17:24:39 S/navigatoin/navigation 17:25:14 ack l 17:25:22 Eric: So they would basically jump to the site map. 17:25:58 Laura: Not sure I like that idea because then every main navigation item would have the same page that you are going to instead of drilling down to the second level. 17:27:12 Shawn: Use case - no javascript... If they click on the first menu item, then they need to click to go back and click on the second menu item. Instead they would be presented with all of the items that they can choose from. 17:27:43 Laura: Would like to see how it is implemented to provide more feedback. 17:28:08 zakim, take up next 17:28:08 agendum 5. "Navigation design direction: Multi-level fly-outs (https://w3c.github.io/wai-website-components/components/preview/example-home) or One level mega-ish menu 17:28:11 ... (https://w3c.github.io/wai-website-components/components/preview/example-home-alt)" taken up [from yatil] 17:28:17 Eric: Okay, I think I have enough feedback to test out some form of implementation. 17:28:56 Eric: We have two basic navigation designs (multi level fly out vs. single level fly out). 17:29:42 Sharron has joined #eo 17:30:00 +1 for multi level 17:30:40 Take a moment and look at the two implementations and provide initial feedback. 17:31:08 Eric sharing screen of both versions. 17:32:56 q+ to say multi-level issue: 2 columns, headings clickable 17:34:07 Brent: Accessibility consideration? 17:34:29 ... especially for 2nd fly-out 17:34:53 Brent: Are there accessibility issues with either implementation? 17:35:07 q+ to comment on accessibility issues 17:35:09 Shawn: Any flyouts generally cause accessibility issues. 17:35:17 ack s 17:35:17 shawn, you wanted to say multi-level issue: 2 columns, headings clickable 17:35:50 q+ 17:36:29 ... There is a cognitive disability issue for the two column implementation. Might be worth testing with those with motor disabilities for mouse use. 17:37:07 q+ to comment on clickable heading 17:37:16 ack l 17:37:17 ack l 17:37:20 ... Another issue is that when there is a resource with submenu, that initial item was not going to be clickable. 17:38:26 Laura: I prefer the first option, the flyout option. When there are multiple columns, it is confusing visually as the second column seems to be under the next main navigation item. 17:38:36 q+ 17:38:38 ack y 17:38:38 yatil, you wanted to comment on accessibility issues and to comment on clickable heading 17:38:44 +1 to Laura 17:38:49 +1 to Laura 17:39:59 Eric: I feel strongly that I like the two column option better. I tried a version without linking the headings of resources with submenu. It did not look very good because of the format of the bold text in some headings. 17:43:00 Eric: I do have a concern if we have a heading text that is not going to be a link. Would like that on record. 17:43:48 Shawn: Understood. Maybe we need to revisit this when the navigation is moving along. 17:44:07 agenda? 17:44:39 zakim, take up next 17:44:39 I see a speaker queue remaining and respectfully decline to close this agendum, shawn 17:44:42 Eric: Okay, we will table this for later discussion. I hear that people prefer the single column with flyout. 17:44:45 q? 17:44:48 ack brent 17:44:52 zakim, take up next 17:44:52 agendum 6. "IA: Quickref Links in main navigation (Eric, https://github.com/w3c/wai-website-design/issues/77)" taken up [from yatil] 17:44:53 q- 17:46:18 Eric: Links to QuickRef. In current IA we have links directly out to the quickref. There are links to it in multiple main nav categories. They link directly out to more "stand alone" applications. 17:46:57 ... It would be hard to link back to where you are in the WAI site. Need to think about how this will affect the navigation highlighting, and other things. 17:47:45 ... Do we need to have a special text or icon to alert user to the fact that this goes out to an external resource/application. There are more things to consider. Would like to hear others opinions. 17:48:50 Brent: Will these types of resources always be outside the WAI site navigation? 17:49:04 Shawn: We talked about having the nav on some of these other resources. 17:49:32 ... will need to decide if it 17:50:00 's on everything, or not on some. maybe on some it's collapseable (e.g., on report tool, how to meet quickref) 17:50:20 Eric: Yes we can do that. The question is how do we ensure that people will not be confused. We need to let them know that this is a stand alone resource or a supplimental resource. 17:50:27 q+ to say boxes 17:50:41 Shawn: Maybe we don't use direct links into some of these resources. 17:51:08 q+ 17:51:10 s/ into some of these resources./ into the QuickREf 17:51:30 ... We could say that the relavent links are in the resources (like tutorial) and we don't need to show them in the navigation. 17:52:06 ack me 17:52:06 yatil, you wanted to say boxes 17:52:12 ack l 17:52:18 Eric: Another solution could be to use boxes. [Eric shows implementation on a web site]. 17:52:45 Laura: We have a call out box or something else that refers people to where they want to go. 17:53:33 q+ 17:54:24 ack l 17:54:38 Shawn: Maybe we make sure that their are appropriate links throughout and then remove them from the main navigation. 17:54:59 Laura: Agree. We need to be consistant with the navigation across the board. 17:55:13 agenda? 17:55:28 Brent: responsive design coming later? 17:55:39 yatil: working on now. 17:57:11 rrsagent, draft minutes 17:57:11 I have made the request to generate http://www.w3.org/2017/08/23-eo-minutes.html yatil 17:57:17 Eric: okay, not other items. Meeting adjourned. 17:59:07 present: Shawn, Brent, Sharron, Charlotte, Laura, Eric 17:59:15 rrsagent, draft minutes 17:59:15 I have made the request to generate http://www.w3.org/2017/08/23-eo-minutes.html yatil 17:59:37 scribeOptions: -final -noEmbedDiagnostics 17:59:37 rrsagent, draft minutes 17:59:37 I have made the request to generate http://www.w3.org/2017/08/23-eo-minutes.html yatil