16:59:54 RRSAgent has joined #eo 16:59:54 logging to http://www.w3.org/2017/09/27-eo-irc 16:59:56 RRSAgent, make logs world 16:59:59 Meeting: Education and Outreach Working Group Teleconference 16:59:59 Date: 27 September 2017 17:00:12 present: Shawn, Brent, James 17:00:18 Regrets: Eric, ?Sharron 17:03:45 Present+ Alicia, James, Judy 17:03:55 present+ Brent 17:04:04 Scribe: Brent 17:04:41 Judy has joined #eo 17:05:29 https://github.com/w3c/wai-website-design/issues/96 17:05:59 Topic: Size and Positioning of Blocks and Topics 17:07:12 Judy: Experience as a user, when looking at this over and over, I was getting a lot of panels of resources (which would seem static), then I got down to the news. 17:07:41 ... Eric feels that those who need the news would have no issue searching for the information. 17:08:11 http://w3c.github.io/wai-website/ 17:08:23 ... However, I believe that news is something that people should be driven to. 17:08:35 James: Have you seen the latest prototype? 17:08:50 Judy: Need to be sure I am seeing the latest version. 17:09:03 Shawn: Prototype is changing hourly at this point. 17:09:20 s/Prototype is changing /Prototype has been changing 17:09:53 Judy: Would like more clarification on where things will be. 17:10:17 q+ 17:10:35 q+ to say that i'm not worried about the reporters... 17:10:35 James: As far as news, it is important to specific groups. My thought is that if they are coming to the site to get news, they will search harder and find what they are looking for. 17:10:53 ... Hope to meet the needs more of those who are new to the site. 17:11:23 W3C 's core business is developing standards. 17:11:48 risk it looks disctinct from core business of W3C 17:11:57 Judy: W3C business is developing core standards. There is a risk of developers coming to the WAI site and saying this is something else. 17:12:15 James: What is the WAI core business? 17:12:37 ... I see it as not developing standards but more about Accessibility Resources. 17:13:49 Judy: EOWG is a W3C working group. This is not a website for EO, but a website for all accessibility work for the W3C. This gives us the opportunity to leverage more. 17:15:26 ... Might be a good opportuntity to highlight a resource for developers on developing standards @@. 17:16:10 James: Going back to the question of the placement of the news section. Are you okay with having people have to search more for news. 17:18:13 Judy: If the panels can be thematic we could cover some of these other topics and things that WAI has opportunity to support. 17:18:48 James: We can discuss this new angle of highlighting the things that WAI is doing across the W3C. 17:19:16 ... Want to make the homepage "sticky". Agree with you that News is something that would help with this goal. 17:19:19 [ Shawn thinks *not* for usability testing, and thinks *yes* before launch ] 17:20:06 ... We are not in position right now to change the design significantly. But want to hear what you are wanting so we can take an approach after relaunch. 17:20:28 q? 17:20:31 ack Judy 17:20:31 Judy, you wanted to say that i'm not worried about the reporters... 17:20:35 Judy: I think the current design is definately an improvement. 17:20:41 q+ to note from W3C comm 17:21:00 ... Would look forward to seeing some updates and will respond to them when they come. 17:21:29 James: That sounds good, we will followup on this current issue and other things that you have brought up. 17:22:35 Shawn: Just a reminder that some of the design work on the WAI site has/may be taken up by the W3C comm group that they feel are good to implement. 17:22:55 ack me 17:22:55 shawn, you wanted to note from W3C comm 17:24:10 James: Just to clarify. Are we needing to check with more stakeholders on design to see if there are further changes that need to be made? 17:24:50 Shawn: Suggest that we figure out a minimum of what needs to be done for UT. Then study results and regroup the week after. 17:25:38 James: If you think we are going to need to make changes to make WAI look more with W3C then we need to do that as soon as possible. 17:26:03 Sharron: This coversation needs to happen in public. 17:26:38 s/coversation/conversation 17:27:12 James: The design considerations were open all along and we have asked for feedback. 17:27:55 ... I need something definitive. It is late in the game and we need to make decisions now. 17:29:00 @@ middle boxes 17:29:13 Brent: Content or design an issue? 17:32:12 @@ 17:32:28 Judy_alt has joined #eo 17:33:17 Brent: Alicia great job desiging look & feel. Had those boxes, but didn't know what was going in those boxes. Shawn asked us to work on the home page. Didn't get to it. Finally Brent stepped up to draft idea of what to go where. Shawn made some tweaks. And we put that out there. 17:33:32 ... We never discussed what should be in these 4 buckets. 17:35:16 ... Shawn saying OK for usability testing. 17:41:49 Topic: Base Line User Testing with current WAI Site 17:43:01 James: Liz is an associate UX tester on the Visa team. She did some baseline testing on the current site. We can now look at some of the results of that testing. 17:43:20 James emailing out the powerpoint deck to TF members. 17:44:05 Charlotte: Having this baseline will give us some strong research based data on improvements that have been made to the site. 17:44:42 Liz sharing Powerpoint on WebEx. 17:45:20 Liz explained agenda for powerpoint. 17:46:57 Liz: Methodology: 8 participants (internal to Visa). Conducted August 23-30. Task based testing with think aloud. 17:47:45 ... Participants: 2 devs, 2 analysts, 2 PjMs, 2 designers. Differing level of accessibility experience. 17:49:08 Liz: First impressions: Had a negative first reaction. Site looks dated. Looks academic or legal. Half participants usually visit by going in from a google search link. 17:50:20 Liz: Getting Started: Explained tasks that were asked of testers. 74% success rate on finding info on getting started. 17:50:50 See slide 9 for detailed information. 17:51:42 Liz: Task 3: Convince others to make accessibility a priority. Details on slide 10. 17:52:09 ... 38% success rate on this task. 17:53:08 Liz: Task 11: Where to go for Color contrast requirements [contrast ratio requirements]. 14% Success. 17:53:37 ... More details on slides 11 and 12. 17:55:26 Liz: Task 12: ... error on a form. 67% success. Details on slide 13. 17:56:22 Liz: Task 13: ... effectively write captions. 50% success. More details on what people hoped for on slide 14 17:57:00 Liz: The next section was Designing for Inclusion. 17:58:11 Liz: Task 7: Where to find info on how people with speech disability experience the web. 50% success 17:58:23 ... Details on slide 17. 17:59:18 Liz: Task 8: Find information on screen readers. 0% success. Most to the right page but didn't find the infomatoin. Detailed info on slide 18. 18:00:39 Liz: Task 9: ... best practices for mobile accessibility. 63% success. Comments and more details on slide 19. 18:01:36 Liz: Task 14: How to Site WAI in a presentation. 0% success. more detail on slide 20. 18:02:28 Liz: Next is the Planning and Implimentation Section 18:09:10 Judy_alt has left #eo 18:22:05 from James (privately): 18:22:05 https://github.com/w3c/wai-website-design/issues/96 18:22:05 from James to everyone: 18:22:06 https://github.com/w3c/wai-website-design/issues/96 18:22:06 from James to everyone: 18:22:06 https://w3c.github.io/wai-website-components/components/preview/example-home.html 18:22:07 from Shawn Henry (internal) to everyone: 18:22:07 from Shawn Henry (internal) to everyone: 18:22:08 I'm finding this very useful! 18:22:08 from Shawn Henry (internal) to everyone: 18:22:08 q+ to ask more about Laws and Policies 18:22:09 from James to everyone: 18:22:09 they thought easy checks was easy! :) 18:22:09 from Shawn Henry (internal) to everyone: 18:22:10 can't get back to page -- check in UT next week 18:22:10 from Shawn Henry (internal) to everyone: 18:22:10 design impacted trust in content 18:22:11 from Shawn Henry (internal) to everyone: 18:22:11 "first update the appearance" 18:27:20 ack shawn 18:27:20 shawn, you wanted to ask more about Laws and Policies