Education and Outreach Working Group Teleconference -- 01 Mar 2018

<Sharron> Scribe: Sharron

<Chris> just finishing up another call - will jump on shortly

WAI site redesign (beta)

Shawn: We are excited to announce that we will launch the beta version of the new WAI website,probably on the Thursday before CSUN.
... what we want to make sure is that it works well. We are not actively seeking feedback as much as if there are bugs, accessibility issues. Want to do an actual official launch in April and just want to be sure we have caught any problems.
... truly we want to show it off, the visual design, content update, revised resources, IA, all of the hard work we have done. Want to celebrate!

<Vivienne> Agree completely too!

Laura: I agree that it is a great idea to celebrate. May get great feedback and maybe some that we don't want:) People will comment even on things we don't want to hear, take those with a grain of salt. It is a good thing!

Brent: What will be the indication that it is in beta? Will we let people know the anticipated launch date?

Shawn: We will have a banner that says it is beta and maybe even a banner on the exisiting site that lets people know there is a beta. Will be good transition.
... hope to flip the switch during the week of 16 April.
... we have a lot of back end work to do. From the EO perspective it is the Business Case, and a few smaller resources that need minor edits, that kind of thing.
... there are several things we said we would do after launch and that is now, so we can start working on those.

Brent: Exciting, good idea to have a beta to help people get used to it.

Shawn: I was thinking Thursday, especially in the morning to give people a chance to see it before travelling.

<Vivienne> no problem

<Howard> Thursday before sounds good

<Chris> Thursday is fine

<AMace> I'm fine with that date

Brent: That seem OK to all or any other ideas for when to announce?

<Andrew> is there a draft announcement?

Shawn: No draft announcement yet, coming soon.

Brent: Thank you Shawn.

Resource editor needed

Brent: Two documents that we will take up next. Authoring Tools and Better Browsing. Before we start looking at requirements etc, we wanted to identify editors to be active in those discussions.
... have had a little interest, need someone who can shepherd the resurce to the next iteration. Could work alone or as part of a team of two.
... remember that the editor does not have to do all the work alone but to shape the nxt version, provide suggested edits to the group, collecting feedback, and implementing it.

Sharron: Please help

<Vivienne> I'm happy to help with selecting tools, but will need to just provide input rather than lead because of my work on the other resources

Shawn: Selecting Tools is a very old document and needs significant updating and revision. Guessing that Better Web Browser is less significant, needs more if an update to current technology.

Andrew: Yes probably needs mention of mobile, think it is about 8 years old.

Brent: Vivienne said she would help but not lead. Think we can have a small team or do the editor work in the full group. Either way, appreciate that you can be a part of it.

<AMace> I'm happy to pair with someone as co-editor on Better browsing

Brent: any takers?
... Thank you for being will to co-lead and we will make note of that.
... any questions about what it means to be an editor?
... I encourage you to think about it, think about the timing and the bandwidth, will have support of chairs and Shawn to keep things on track. If you have interest send email to the plannig team. The idea is to name a couple of editors and maybe kck it off by CSUN or at CSUN.

The Business Case

<Brent> Scribe: Brent

<Sharron> Brent: This was on the weekly survey and have made update

<Sharron> https://w3c.github.io/wai-bcase/business-case/

Sharron: This iteration is different than what is currently on the website.
... The idea is that we have these four driver areas. On the main landing page there is one short paragraph defining the driver and then there is a link that goes to a pager that dives deeper into the driver.
... Each sub-page has a case study, or a place for a future case study. Would love to have more case studies to add to the pages, especially from countries other than the U.S.

<Sharron> https://w3c.github.io/wai-bcase/business-case/legal-risk/

Sharron: You will notice that some of the content from the landing page is also repeated on the sub-pages. This is a bit of a concern to me right now. Don't want it to add confusion. What do people think about this format.

<Vivienne> I'm okay with it there, but would like the summary section more clearly outlined

Andrew: Some users will come through the landing page, others will come directly to a sub-page. To me what is missing is a heading at the real introductory paragraph.

<Sarah> Agree with Andrew RE heading at the start of the main content after Summary

Andrew: Either semantically or visually. Minor if visual.

Howard: It seems like a long way down to the case study on the page. It seems like what we said we are trying to aviod (wall of text) are still there when it is all repeated.
... The case study is such a good addition. If there was some type of cut out or something to draw people to get to and read the case study.

Sharron: So maybe putting the case study higher and then supporting information below it.
... Some of the key points could be in call out boxes on the side as well. Then reorganize to make more of a bulleted list.

<Vivienne> I think the idea of having the case study above the fold so everyone sees it

Laura: Agree with what others are saying. Having all the content together is important because of people coming to a sub-page first. Agree also the case study is a little lower on the page that I would like. Don't see that it is a "big" wall of text. Not too much of a problem.

Amanda: I don't mind having a summary at the beginning, but it seems long. Could it be summarized in a few main bullet points (not bring the entire paragraph over from the landing page) and get to the case study sooner.

<Chris> I agree with that approach

Shawn: What about the overview page having the shorter bullets and the meat of the content being on the sub-page.

Chris: The approach I like is the lead in from the overview page with more content on the sub-page.

<Vivienne> could we have a link to a "one page printable"?

Sharron: What about for those that want the one page version?
... Could have a print version of a one pager.

<Vivienne> Presently in the training resources, there are links to handouts, but we have removed most of them because they were too old.

Chris: Could even make that a seperate HTML page that is linked.

<Vivienne> Kinda of. I'm happy to keep them updated, but it is just that we need replacements for the current

<Vivienne> perfect, sharon

Sharron: Summary of what I am hearing. 1) Seriously minimize what is on the landing page, 2) put the bulk of the content on the sub-page

<Vivienne> +1

<Chris> +1

<Laura> +1

Sharron: 3) Would have a link to print a one pager for those that want it.

<Andrew> +1

<Sarah> +1

Sharron: People are agreeing. That is helpful. Thanks.

<Howard> +1 but if you can do a sidebar with a mention of the specific case study, I think that would pull people in

<Sharron> https://w3c.github.io/wai-bcase/business-case/drive-innovation/

<Howard> +1

<Vivienne> Sharon, while I realise that you're wanting to have the good case studies now, but I wouldn't stress too much, we can add more case studies as we find them. We could also start to reach out to the general community to get more.

Sharron: I also would like some support on the case studies. Some don't have the numbers or specific quantifiable data. Innovation case study, for example has a case study without particular data. Is this still a valid case study?

Howard: I think the Innovation page case study is valid and worth while.
... If you go to 3Play Media there are case studies there specifically about captioning.

Sharron: That is where the NPR one came from.

Howard: There are some others there that are good too.

<Vivienne> I'm emailed a senior contact at Microsoft to see if they have some good stuff

Shawn: Another thing that we can do when we announce the site is to say, "here is our site and here are some case studies that we are tying to gather..."

Sharron: I do have a number of people who are planning to provide something.
... Anyone who has case studies to share, I am really happy to have and use those.

<Chris> http://g3ict.org/download/p/fileId_938/productId_248 (G3ICT report)

<Chris> going through it now

<Sharron> Brent: The two case studies seem equally valid

Laura: Agree with both Howard and Brent. They are different but both are valid and persuasive.

Sharron: The one on the current site stresses "doing the right thing" and "compassion". I have not done that in this version. Is it okay to take this approach and focus on business reasons?

<Vivienne> I think people are looking for really good business purposes, beyond that of doing the right thing. There is a lot of information about 'doing the right thing' etc., but the gap is the ROI type of info.

<Sharron> Sarah: No problem at all with making an entirely business arguement

Sarah: Have no problem with the business approach.

Sharron: Great feedback. I will work on the next iteration and work on the Case studies more.

<Sharron> scribe: Sharron

WrapUp

Brent: Notice a survey coming looking at the specific resources, minor edits, diff files to compare. Another consideration of Making Presentations Accessible by mid week. Look for that next week
... will send reminders, will get this week's survey out sometime tomorrow.

<Andrew> F2F Wiki - https://www.w3.org/WAI/EO/wiki/EOWG_F2F_March_2018

Sharron: and add f2f items to the wiki agenda as they occur to you

<Brent> Face-2-Face wiki page. look over topics for agenda.

Sharron: Monday would be the opportune time to have the EO dinner
... please plan on that and we can pick a place as the date gets closer.Any other business?

<Chris> take care, everyone

<Vivienne> bye all

Sharron: thank you for the discussion, for your participation.

<Sarah> Thank you!

trackbot, end meeting

- DRAFT -

Education and Outreach Working Group Teleconference

01 Mar 2018

Attendees

Contents

WAI site redesign (beta)

Resource editor needed

The Business Case

WrapUp

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output