Education and Outreach Working Group Teleconference

<shawn> scribe: Brent

James calls meeting to order.

Information Architecture Feedback

James: Charlotte and I can do another round of updates based on feedback provided by Shawn.
... Is that okay with everyone?

Shawn: Yes

No other comments.

Development work

Eric: Caleb and I are working on the structure of the site. Working on some components and the front page. When I have something more to show, I will send it our for comment.

James: Good, Thanks Eric.

Reviewing open issues

Issue #72: Spacing and Proximity

Shawn: Spacing looks much better.

James: Adding comment that it looks good to task force.

Shawn: What about the bullet?

Eric: Worked on that. I think I have it working in any combination.

Shawn: Looks great. Thank you Eric.

Issue #71: nav - current page indicator

#71: nav - current page indicator

James: Alicia worked on the visual of the page indicators.

<shawn> SLH: maybe make the separator lines quieter

<shawn> Brent: triagnles are enough indication

Eric: I think the indicator triangle is okay. We should try it for a while and can adjust later if needed.

Shawn: Lines quieter means making them a little darker, less pronounced.

James: #71, adding task force is okay with triangles for now and closing issue.

#70: suggest slightly darker lines, and remove the last line (see comment).

Action - yatil add Alicia to the EO group in GitHub so assignments can be given to her.

<trackbot> Error finding '-'. You can review and register nicknames at <http://www.w3.org/WAI/EO/track/users>.

ACTION yatil add Alicia to the EO group in GitHub so assignments can be given to her.

<trackbot> Created ACTION-381 - Add alicia to the eo group in github so assignments can be given to her. [on Eric Eggert - due 2017-08-16].

#69 - Home Page Content

James: Shawn's concern is that we decide what the home page content is. What is included.

Shawn: Yes, some of that content will need to be created.
... There are areas that we have visual design for, we need to make decisions on what we are going to include, and if it is included then we need to start working on it.

yatil: We do have some of the content and iconography that would/could be used.

James: Should we create another "resource" for Home Page Content that we assign people to and have people work on?

Shawn: Featured resource, tip of the day, featured video are easier to do.
... The middle [showcase] boxes that are there need some decision of what we will put there and what content needs to be created or linked to.

James: These four slots could be our high quality, or high priority resources that we want to lead people to.

<yatil> Homepage link: https://visa.invisionapp.com/share/YPAVCUZA9#/screens/234693428

<shawn> Brent: label them, not showcase, mabe "Leader boxes"

<shawn> +1 for section headingg

Yatil: Some examples - BAD, Policies, Tutorials, Etc...

<shawn> Shawn: make clear if those are going to change

<shawn> Brent: let's say on leads to BAD, and they don't see it in the nav. they use that leader box to lead them to BAD. then we change it, and then they feel frustrated

<shawn> ... do think they should change. And think some title to make clear they'll change

<shawn> eric: featured resource

<shawn> james: already have at top. do we related these?

Shawn: If they are not going to be static, need some indication so that people will know that these "feader boxes" will change.

<shawn> Eric: link to all featured resource

<shawn> +1 to link to all !!!

James: Idea - integrate it with "Featured Resources" at the top and cycle them down.

<shawn> +1 for link to all for all rotating content, including tip of the Week

<yatil> [ Eric: We could have an additional link to all tips. ]

James: Propose that we make this Home Page Content another "resource" to work out a plan and content proposal and do the work and bring to the Task Force for approval of the home page content.

<shawn> Shawn: This is not formal EOWG deliverable -- good to get input, but not need formal WG approval

James: shawn and Brent, do you want to come up with the strategy/plan and recommendations?

Shawn: Yes, but may not be next week.

<shawn> Brent: tip of the week... concern with that.

<shawn> ... know what we're getting into. we'll burn through that content in 1/2 year

<shawn> ... when fit end, either start over, or have people to write it

<shawn> .... We do that in our group, and it is a big challenge to come up with good quality, vetted content. spend about 3 hours / week

<yatil> close action 381

Yatil: I was thinking they would be direct links to the quick tips content.

<Zakim> shawn, you wanted to say denis; can start over; can add some and to say quick tip / week/ day

Yatil: Not too concerned about the amount and starting over.

Shawn: Agree we could start over and rotate them. We can add some. Denis said he wanted to create many of these and have them somewhere.
... Another idea could be that we drop "week" and just have tips that are shown.

James: Could say "design tip", etc. and have a bunch of them that could randomly load.

Shawn: Need to do more thinking about this. Some of them we want to get them to the details of the tip content.

<Zakim> yatil, you wanted to say make the random one sticky for 24 hours using javascript

Yatil: Would be good to show a random one but let it stick for a while before moving to the next random one.

James: Shawn and Brent will take up this "tip of the week" issue as well as part of the Home Page Content plan. Bring back to Task Force when ready.

#68 - Homepage Sponsors and Funders

James: Alicia has already added that to the page footer.

Shawn: One issue is the two columns.

Yatil: I will be able to take care of that.

James: closing issue #68.

#66 - no "learn more" links

Shawn: This is complete, close issue.

#65 - Above the fold

Yatil: I am okay with having "About WAI" where it is. Don't need to have it higher on the page.

Shawn: I am fine with this. I still wish the static content was a little visually different than dynamic content, but I am okay with this.

#64 - Big Footer Nav

<shawn> Shawn: still think would be better to have static content look differently than chaning content, but don't feel super strongly about it

James: This one needs to stay as is until we finish edits to the IA.

#50 - Design Mockups: Ideas for fly-out menu on sub pages?

Shawn: Need to keep this open as it is a big issue. From a usability / accessibility standpoint.

#41 - Design Mockups: In-page links

Yatil: This was a long time ago. I think there have been changes and we are good with this issue now.

James: Closing #41

#32 - Translations

Shawn: Need a little more focus on what the translation interface will be, what it will look like, how it will work.

James: Okay, adding that to issue.

Next Meeting

James: Do we need to meet next week?

<inserted> [Tentatively: IA questions meeting lead by Shawn]

User Testing

Charlotte: Going to treat everyone like I treat others who come through the lab.
... Have a information sheet that I would like Shawn, Sharron, and Brent to fill out. Would like this by next week.
... There are other items on a timeline to prep for the user studies. I will send out the timeline.
... In order for this to all happen in mid September we need to be sure that we have a solid IA in place for testing (not a lot of changes taking place to the site). Need by the 11th, no later.
... Anything we want tested needs to be in final state by September 11.
... Pushing the user testing out to October will be an issue with completing the site by TPAC.

Shawn: There are comments that I had made for the IA (some questions, some things missing). Have not received any comments back on this feedback.

Yatil: What about putting those into GitHub and going through them one by one next week so that we can decide on each?

James: Let's get the IA done. Charlotte and I can go through Shawn's comments and work through the issues.

Shawn: Would like for the three of us to do this together. It will save a lot of going back and forth.

James: Better yet, Shawn take your comments and make the changes and we will implement.
... Next week we will work at final discussion of IA and have a complete IA in place. We will also have completed survey forms to Charlotte (from Shawn, Brent, Sharron) so we can move deeper into prep planning for user studies.
... Anything else for this week?
... Meeting adjourned.

<yatil> [ Eric added Alicia to the EO Team on Github. ]

<yatil> trackbot, end meeting