13:57:28 <RRSAgent> RRSAgent has joined #eo-plan
13:57:28 <RRSAgent> logging to http://www.w3.org/2017/08/11-eo-plan-irc
13:57:30 <trackbot> RRSAgent, make logs world
13:57:30 <Zakim> Zakim has joined #eo-plan
13:57:32 <trackbot> Zakim, this will be 3694
13:57:32 <Zakim> ok, trackbot
13:57:33 <trackbot> Meeting: Education and Outreach Working Group Teleconference
13:57:33 <trackbot> Date: 11 August 2017
13:57:35 <Sharron> Sharron has joined #eo-plan
13:57:47 <Sharron> trackbot, start meeting
13:57:50 <trackbot> RRSAgent, make logs world
13:57:53 <trackbot> Zakim, this will be 3694
13:57:53 <trackbot> Meeting: Education and Outreach Working Group Teleconference
13:57:53 <trackbot> Date: 11 August 2017
13:57:53 <Zakim> ok, trackbot
13:58:05 <Sharron> Topic: How PWDUW
13:58:35 <Sharron> Decisions: Keep landing page as is (strong branding, recognition of established resource)
13:59:16 <Sharron> - Accessibility principles, use exisiting name, pull into its own
13:59:59 <Sharron> - Stories of Web users, leave name, edit content
14:00:14 <shawn> idea for middle 2 page titles "Diverse Abilities and Disabilities" and "Tools and Techniques People Use" -- but those are just input, not necesaaruly strong suggestions
14:00:29 <Sharron> - other two sections need to be renamed, suggestions above for editing group.
14:01:01 <Sharron> Shawn: strong feeling on the order?
14:01:20 <Sharron> Brent: Not a strong preference at this time.
14:02:40 <Sharron> ...making decisions that will be implemented
14:03:47 <Sharron> Topic: Easy Checks
14:04:37 <Sharron> Shawn: Suggested is "Intro to Accessibility Evaluation - a first review of accessibility"
14:04:38 <shawn> Intro to Accessibility Evaluation - A First Review of Web Accessibility
14:05:44 <Sharron> Shawn: This is not a real intro to evaluation and has some brand recongition in the community.
14:05:58 <shawn> Easy Checks for [Some] Common Web Accessibility [Errors|Bugs|Barriers]
14:06:02 <Sharron> Sharron: recognition not as strong as HPWDUW
14:06:34 <Sharron> Shawn: An idea that emerged was common accessibility issues
14:06:43 <shawn> Easy Checks for [Some] Common Web Accessibility [Problems|Errors|Bugs|Barriers]
14:07:25 <Sharron> Laura: I like that, and like errors a bit more. May be too developer attuned
14:09:21 <Sharron> Sharron: Be aware of the fact that there is a strong feeling that these are not "Easy"
14:09:38 <Sharron> Laura: That is true.
14:10:35 <Sharron> Shawn: So this resource needs a title revisit.
14:11:18 <Sharron> Topic: Essential Componenets
14:12:00 <Sharron> Shawn: James suggestion is How Accessibility Works
14:12:32 <Sharron> Brent: the one with the graphics on it
14:13:02 <Sharron> Laura: I like it too
14:13:57 <Sharron> Group favors: How Accessibility Works
14:14:37 <shawn> ftr, Shawn will need to sleep on changes ;-)
14:15:39 <Sharron> Shawn: Web Accessibility Perspectives Videos should be the short name - agree
14:16:23 <Sharron> s/Web Accessibility Perspectives Videos should be the short name - agree/ Web Accessibility Perspectives - add Videos to title
14:16:51 <Sharron> Shawn: Shorter name for Business Case, consider the one James suggested
14:19:20 <Sharron> Brent: suggestion is to keep "First Aid" title as is for now?
14:19:44 <Sharron> Shawn: Yes
14:20:09 <Sharron> Brent: also keep "policies" title as is?
14:21:09 <Sharron> Shawn: Another suggested change is to Presentations, he suggested "Pre-Made Presentations"
14:21:25 <Sharron> Laura: Prefer the way it is
14:21:50 <Sharron> Shawn: Presentations You Can Use
14:22:00 <Sharron> Brent: Yes, I like that very much
14:22:10 <Sharron> Laura: +1
14:22:15 <Sharron> Robert: +1
14:24:01 <Sharron> Shawn: Next question is high level navigation. Treas in the TF list
14:24:11 <Sharron> s/Treas/thread
14:24:48 <Sharron> https://w3c.github.io/wai-website-components/components/preview/example-home.html
14:26:04 <Sharron> Shawn: Change I am New ... to Accessibility Fundamentals
14:26:16 <Sharron> ..Plan and Manage OK
14:26:31 <Sharron> ...Design & Write OK
14:28:53 <shawn> good point - Robert, CONTENT first, so Write & Design
14:28:58 <Sharron> Robert: advocate for the fact that content needs to be in place before you design
14:30:07 <Sharron> ...based on that, change to Write and Design
14:30:25 <Sharron> ...will skip Develop for now
14:30:44 <Sharron> ...Suggest to change to Test and Evaluate
14:31:24 <Sharron> Laura: In my experience, aproblem is identified which is evluation and then testing happens
14:31:59 <Sharron> ...but I don't feel strongly
14:32:35 <Sharron> Shawn: In one place we thought about only Test (but people don't like tests so was rejected)
14:32:51 <Sharron> ...main issue was what will target audience look for?
14:33:25 <Sharron> Laura: Bruce Bailey pointed to all of our resources and so we can expect a lot of attention from the 508 coordinators.
14:33:38 <Sharron> Brent: People really are searching for both.
14:34:06 <shawn> WSTF telecon decision: "even though they are the same thing, no harm in including both"
14:34:12 <shawn> Test & Evalute
14:34:21 <Sharron> ...developers will look for tests, accessibility advisors will look for evaluation, need both words.
14:34:28 <Sharron> Sharron: Test should go first.
14:35:16 <Brent> +1 for Teach & Advocate
14:35:30 <Sharron> Shawn: Next is "Teach" and currently contains presentations, will have Tips for Advocating, should it be Teach and Advocate
14:35:58 <Sharron> ...it is a word that we had before and removed
14:36:43 <Sharron> Robert:Is Lead an appropriate word? Is this for leadership?
14:37:06 <Sharron> Sharron: I don't think we have much content for leaders or the leadership team.
14:38:13 <Sharron> Shawn: So coming back to Develop, that is the only one that is one word.
14:38:23 <Sharron> ...how about Code and Develop?
14:38:47 <Sharron> Sharron: Yes for clarity and consistency
14:39:47 <Sharron> Brent: And the way it looks, the ampersand stays on the first line, rather than hanging off the edge.
14:40:05 <shawn> force "&" on first line -- so key words are left aligned
14:40:23 <Sharron> ...short word on top with ampersand.
14:41:59 <Sharron> Brent: And the way it looks, the ampersand stays on the first line, rather than hanging off the edge.
14:42:11 <shawn> rrsagent, make logs public
14:48:48 <Sharron> Shawn: Need to figure out the way the secondary/tertiary nav to work form the main nav. It is complex and I wonder if we could only have the primary landing pages, no sub-pages.
14:49:18 <Sharron> Brent: My guess is that we couold see where they fall not that they need to be in the nav.
14:51:13 <Sharron> Shawn: So I am suggesting that only major landing pages show up in the nav and consider a mega nav with sub pages in a footer nav. Not expand, not fly out
14:51:38 <Sharron> James: No tertiary, ever?
14:52:08 <Sharron> Sharron: So you are making the user click through more often
14:52:36 <Sharron> Shawn: Yes, but those are very few.
14:54:57 <Sharron> Shawn: So there are three options - first is simple, no flyouts; second is what Eric built, one level of flyout; finally what Alicia designed with a complex nesting of links
14:55:56 <Sharron> James: Trying to get away from landing pages
14:59:59 <Sharron> Before I leave, want to weigh in on the side of simplicity in the nav. Tertiary seems unecessary, I like Eric's implemetation
15:02:13 <Brent> Sribe: Brent
15:02:21 <shawn> If some menu items are links and some are fly-out then need affordance of the difference
15:03:48 <yatil> s/Sribe:/Scribe:/
15:08:17 <Brent> Scribe: Brent
15:08:39 <Brent> Laura: I prefer the way Eric developed it out.
15:10:14 <shawn> e.g., carrot indicates flyout in https://www.microsoft.com/en-us/defaultb.aspx and underline on hover shows link
15:11:07 <Brent> James: I prefer Eric's implementation, and think we need to include terciary links
15:18:45 <shawn> rrsagent, draft minutes
15:18:45 <RRSAgent> I have made the request to generate http://www.w3.org/2017/08/11-eo-plan-minutes.html shawn
15:19:01 <shawn> trackbot, end meeting
15:19:01 <trackbot> Zakim, list attendees
15:19:01 <Zakim> As of this point the attendees have been (no one)
15:19:09 <trackbot> RRSAgent, please draft minutes
15:19:09 <RRSAgent> I have made the request to generate http://www.w3.org/2017/08/11-eo-plan-minutes.html trackbot
15:19:10 <trackbot> RRSAgent, bye
15:19:10 <RRSAgent> I see no action items
15:21:53 <RRSAgent> RRSAgent has joined #eo-plan
15:21:53 <RRSAgent> logging to http://www.w3.org/2017/08/11-eo-plan-irc
15:22:07 <shawn> present: Shawn, Sharron, Brent, Laura, Robert, James
15:22:13 <shawn> rrsagent, draft minutes
15:22:13 <RRSAgent> I have made the request to generate http://www.w3.org/2017/08/11-eo-plan-minutes.html shawn
15:22:44 <shawn> scribe: Sharron, Brent
15:22:46 <shawn> rrsagent, draft minutes
15:22:46 <RRSAgent> I have made the request to generate http://www.w3.org/2017/08/11-eo-plan-minutes.html shawn