<Sharron> trackbot, start meeting

<trackbot> Meeting: Education and Outreach Working Group Teleconference

<trackbot> Date: 11 August 2017

How PWDUW

<Sharron> Decisions: Keep landing page as is (strong branding, recognition of established resource)

<Sharron> - Accessibility principles, use exisiting name, pull into its own

<Sharron> - Stories of Web users, leave name, edit content

<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

<Sharron> - other two sections need to be renamed, suggestions above for editing group.

<Sharron> Shawn: strong feeling on the order?

<Sharron> Brent: Not a strong preference at this time.

<Sharron> ...making decisions that will be implemented

Easy Checks

<Sharron> Shawn: Suggested is "Intro to Accessibility Evaluation - a first review of accessibility"

<shawn> Intro to Accessibility Evaluation - A First Review of Web Accessibility

<Sharron> Shawn: This is not a real intro to evaluation and has some brand recongition in the community.

<shawn> Easy Checks for [Some] Common Web Accessibility [Errors|Bugs|Barriers]

<Sharron> Sharron: recognition not as strong as HPWDUW

<Sharron> Shawn: An idea that emerged was common accessibility issues

<shawn> Easy Checks for [Some] Common Web Accessibility [Problems|Errors|Bugs|Barriers]

<Sharron> Laura: I like that, and like errors a bit more. May be too developer attuned

<Sharron> Sharron: Be aware of the fact that there is a strong feeling that these are not "Easy"

<Sharron> Laura: That is true.

<Sharron> Shawn: So this resource needs a title revisit.

Essential Componenets

<Sharron> Shawn: James suggestion is How Accessibility Works

<Sharron> Brent: the one with the graphics on it

<Sharron> Laura: I like it too

<Sharron> Group favors: How Accessibility Works

<shawn> ftr, Shawn will need to sleep on changes ;-)

<Sharron> Shawn: Web Accessibility Perspectives - add Videos to title

<Sharron> Shawn: Shorter name for Business Case, consider the one James suggested

<Sharron> Brent: suggestion is to keep "First Aid" title as is for now?

<Sharron> Shawn: Yes

<Sharron> Brent: also keep "policies" title as is?

<Sharron> Shawn: Another suggested change is to Presentations, he suggested "Pre-Made Presentations"

<Sharron> Laura: Prefer the way it is

<Sharron> Shawn: Presentations You Can Use

<Sharron> Brent: Yes, I like that very much

<Sharron> Laura: +1

<Sharron> Robert: +1

<Sharron> Shawn: Next question is high level navigation. thread in the TF list

<Sharron> https://w3c.github.io/wai-website-components/components/preview/example-home.html

<Sharron> Shawn: Change I am New ... to Accessibility Fundamentals

<Sharron> ..Plan and Manage OK

<Sharron> ...Design & Write OK

<shawn> good point - Robert, CONTENT first, so Write & Design

<Sharron> Robert: advocate for the fact that content needs to be in place before you design

<Sharron> ...based on that, change to Write and Design

<Sharron> ...will skip Develop for now

<Sharron> ...Suggest to change to Test and Evaluate

<Sharron> Laura: In my experience, aproblem is identified which is evluation and then testing happens

<Sharron> ...but I don't feel strongly

<Sharron> Shawn: In one place we thought about only Test (but people don't like tests so was rejected)

<Sharron> ...main issue was what will target audience look for?

<Sharron> Laura: Bruce Bailey pointed to all of our resources and so we can expect a lot of attention from the 508 coordinators.

<Sharron> Brent: People really are searching for both.

<shawn> WSTF telecon decision: "even though they are the same thing, no harm in including both"

<shawn> Test & Evalute

<Sharron> ...developers will look for tests, accessibility advisors will look for evaluation, need both words.

<Sharron> Sharron: Test should go first.

<Brent> +1 for Teach & Advocate

<Sharron> Shawn: Next is "Teach" and currently contains presentations, will have Tips for Advocating, should it be Teach and Advocate

<Sharron> ...it is a word that we had before and removed

<Sharron> Robert:Is Lead an appropriate word? Is this for leadership?

<Sharron> Sharron: I don't think we have much content for leaders or the leadership team.

<Sharron> Shawn: So coming back to Develop, that is the only one that is one word.

<Sharron> ...how about Code and Develop?

<Sharron> Sharron: Yes for clarity and consistency

<Sharron> Brent: And the way it looks, the ampersand stays on the first line, rather than hanging off the edge.

<shawn> force "&" on first line -- so key words are left aligned

<Sharron> ...short word on top with ampersand.

<Sharron> Brent: And the way it looks, the ampersand stays on the first line, rather than hanging off the edge.

<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.

<Sharron> Brent: My guess is that we couold see where they fall not that they need to be in the nav.

<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

<Sharron> James: No tertiary, ever?

<Sharron> Sharron: So you are making the user click through more often

<Sharron> Shawn: Yes, but those are very few.

<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

<Sharron> James: Trying to get away from landing pages

<Sharron> Before I leave, want to weigh in on the side of simplicity in the nav. Tertiary seems unecessary, I like Eric's implemetation

<Brent> Scribe: Brent

<shawn> If some menu items are links and some are fly-out then need affordance of the difference

<scribe> Scribe: Brent

Laura: I prefer the way Eric developed it out.

<shawn> e.g., carrot indicates flyout in https://www.microsoft.com/en-us/defaultb.aspx and underline on hover shows link

James: I prefer Eric's implementation, and think we need to include terciary links

<shawn> trackbot, end meeting

<shawn> scribe: Sharron, Brent

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/Web Accessibility Perspectives Videos should be the short name - agree/ Web Accessibility Perspectives - add Videos to title/
Succeeded: s/Treas/thread/
Succeeded: s/Sribe:/Scribe:/
Default Present: (no_one)
Present: Shawn Sharron Brent Laura Robert James
Found Scribe: Brent
Inferring ScribeNick: Brent
Found Scribe: Brent
Inferring ScribeNick: Brent
Found Scribe: Sharron, Brent

WARNING: 3 scribe lines found (out of 117 total lines.)
Are you sure you specified a correct ScribeNick?

Scribes: Brent, Sharron, Brent

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 11 Aug 2017
Guessing minutes URL: http://www.w3.org/2017/08/11-eo-plan-minutes.html
People with action items: