See also: IRC log
<scribe> Scribe: Brent
<shawn> https://github.com/w3c/wai-website-design/issues/96
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.
... Eric feels that those who need the news would have no issue searching for the information.
<shawn> http://w3c.github.io/wai-website/
Judy: However, I believe that news is something that people should be driven to.
James: Have you seen the latest prototype?
Judy: Need to be sure I am seeing the latest version.
Shawn: Prototype has been changinghourly at this point.
Judy: Would like more clarification on where things will be.
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.
... Hope to meet the needs more of those who are new to the site.
<shawn> W3C 's core business is developing standards.
<shawn> risk it looks disctinct from core business of W3C
Judy: W3C business is developing core standards. There is a risk of developers coming to the WAI site and saying this is something else.
James: What is the WAI core business?
... I see it as not developing standards but more about Accessibility Resources.
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.
... Might be a good opportuntity to highlight a resource for developers on developing standards @@.
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.
Judy: If the panels can be thematic we could cover some of these other topics and things that WAI has opportunity to support.
James: We can discuss this new angle of highlighting the things that WAI is doing across the W3C.
... Want to make the homepage "sticky". Agree with you that News is something that would help with this goal.
<shawn> [ Shawn thinks *not* for usability testing, and thinks *yes* before launch ]
James: 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.
<Zakim> Judy, you wanted to say that i'm not worried about the reporters...
Judy: I think the current design is definately an improvement.
... Would look forward to seeing some updates and will respond to them when they come.
James: That sounds good, we will followup on this current issue and other things that you have brought up.
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.
<Zakim> shawn, you wanted to note from W3C comm
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?
Shawn: Suggest that we figure out a minimum of what needs to be done for UT. Then study results and regroup the week after.
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.
Sharron: This conversation needs to happen in public.
James: The design considerations were open all along and we have asked for feedback.
... I need something definitive. It is late in the game and we need to make decisions now.
<shawn> @@ middle boxes
<shawn> Brent: Content or design an issue?
<shawn> @@
<shawn> 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.
<shawn> ... We never discussed what should be in these 4 buckets.
<shawn> ... Shawn saying OK for usability testing.
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.
James emailing out the powerpoint deck to TF members.
Charlotte: Having this baseline will give us some strong research based data on improvements that have been made to the site.
Liz sharing Powerpoint on WebEx.
Liz explained agenda for powerpoint.
Liz: Methodology: 8 participants (internal to Visa). Conducted August 23-30. Task based testing with think aloud.
... Participants: 2 devs, 2 analysts, 2 PjMs, 2 designers. Differing level of accessibility experience.
... 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.
... Getting Started: Explained tasks that were asked of testers. 74% success rate on finding info on getting started.
See slide 9 for detailed information.
Liz: Task 3: Convince others to make accessibility a priority. Details on slide 10.
... 38% success rate on this task.
... Task 11: Where to go for Color contrast requirements [contrast ratio requirements]. 14% Success.
... More details on slides 11 and 12.
... Task 12: ... error on a form. 67% success. Details on slide 13.
... Task 13: ... effectively write captions. 50% success. More details on what people hoped for on slide 14
... The next section was Designing for Inclusion.
... Task 7: Where to find info on how people with speech disability experience the web. 50% success
... Details on slide 17.
... 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.
... Task 9: ... best practices for mobile accessibility. 63% success. Comments and more details on slide 19.
... Task 14: How to Site WAI in a presentation. 0% success. more detail on slide 20.
... Next is the Planning and Implimentation Section
<shawn> from James (privately):
<shawn> https://github.com/w3c/wai-website-design/issues/96
<shawn> from James to everyone:
<shawn> https://github.com/w3c/wai-website-design/issues/96
<shawn> from James to everyone:
<shawn> https://w3c.github.io/wai-website-components/components/preview/example-home.html
<shawn> from Shawn Henry (internal) to everyone:
<shawn> from Shawn Henry (internal) to everyone:
<shawn> I'm finding this very useful!
<shawn> from Shawn Henry (internal) to everyone:
<shawn> from James to everyone:
<shawn> they thought easy checks was easy! :)
<shawn> from Shawn Henry (internal) to everyone:
<shawn> can't get back to page -- check in UT next week
<shawn> from Shawn Henry (internal) to everyone:
<shawn> design impacted trust in content
<shawn> from Shawn Henry (internal) to everyone:
<shawn> "first update the appearance"
<Zakim> shawn, you wanted to ask more about Laws and Policies