See also: IRC log
<scribe> Scribe: Brent
okay
<yatil> https://w3c.github.io/wai-website-components/components/preview/example-home
Eric: Quick update on home page.
Changes to the navigation and the general width of the
columns.
... Working on the responsiveness now. Doing more work on that
tomorrow. Just an FYI for everyone. Any questions?
No Questions
Eric: About Sharron's question about the new design templates.
Eric: 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.
Sharron: For the business case, can we put the content in the new template so that we can preview in the new design?
Eric: Yes, I will work on that so you can add content by Friday.
Sharron: Eric "on the record," you are great. Thank you.
Eric: Okay, please send me the link to the repository.
Eric: Charlotte, what are the specifics that you need?
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.
... Please send as soon as you can.
... I am going to start recruiting participants next week. If
you have ideas or recommendations for audiences, please let me
know write away.
<Zakim> shawn, you wanted to ask test plan in wiki page? to say demographics in e-mail -- anything else? to say more issues later...
Charlotte: I am also working up the usability testing plan now as well.
Shawn: I think I did put some ideas for roles and demographics for participants.
Charlotte: I don't see the demographics, please send them again.
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.
... 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. Also may have
specific questions later.
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.
... Can someone send me the URL for the new site?
Shawn: Yes, I will.
... I have been working on travel. Just want to confirm that we
are doing Sept. 19, 20, 21.
Charlotte: Yes, those are the dates.
Sharron will send information to Norah about dates to see if she can attend.
<shawn> zakim take up next
Eric: We have the main navigation items. Without javascript we need some way to link in the navigation on the pages.
<yatil> https://w3c.github.io/wai-website-components/components/preview/example-home
<Zakim> shawn, you wanted to say opinion (after others)
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.
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.
... 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.
S/navigatoin/navigation
Eric: So they would basically jump to the site map.
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.
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.
Laura: Would like to see how it is implemented to provide more feedback.
Eric: Okay, I think I have enough
feedback to test out some form of implementation.
... We have two basic navigation designs (multi level fly out
vs. single level fly out).
<Laura> +1 for multi level
Take a moment and look at the two implementations and provide initial feedback.
Eric sharing screen of both versions.
<shawn> Brent: Accessibility consideration?
<shawn> ... especially for 2nd fly-out
Brent: Are there accessibility issues with either implementation?
Shawn: Any flyouts generally cause accessibility issues.
<Zakim> shawn, you wanted to say multi-level issue: 2 columns, headings clickable
Shawn: There is a cognitive
disability issue for the two column implementation. Might be
worth testing with those with motor disabilities for mouse
use.
... Another issue is that when there is a resource with
submenu, that initial item was not going to be clickable.
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.
<Zakim> yatil, you wanted to comment on accessibility issues and to comment on clickable heading
<Sharron> +1 to Laura
<shawn> +1 to Laura
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.
... I do have a concern if we have a heading text that is not
going to be a link. Would like that on record.
Shawn: Understood. Maybe we need to revisit this when the navigation is moving along.
Eric: Okay, we will table this for later discussion. I hear that people prefer the single column with flyout.
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.
... 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.
... 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.
Brent: Will these types of resources always be outside the WAI site navigation?
Shawn: We talked about having the nav on some of these other resources.
<shawn> ... will need to decide if it
<shawn> 's on everything, or not on some. maybe on some it's collapseable (e.g., on report tool, how to meet quickref)
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.
Shawn: Maybe we don't use direct
links into the QuickREf
... We could say that the relavent links are in the resources
(like tutorial) and we don't need to show them in the
navigation.
<Zakim> yatil, you wanted to say boxes
Eric: Another solution could be to use boxes. [Eric shows implementation on a web site].
Laura: We have a call out box or something else that refers people to where they want to go.
Shawn: Maybe we make sure that their are appropriate links throughout and then remove them from the main navigation.
Laura: Agree. We need to be consistant with the navigation across the board.
<shawn> Brent: responsive design coming later?
<shawn> yatil: working on now.
Eric: okay, not other items. Meeting adjourned.