Brent: Welcome back, thanks for your good work yesterday. In the same way that we made considerations of WAI-Dev and existing resources for maintaining them, we want to do the same kind of consideration today with the idea of promoting them to the wider world to improve uptake and use. We will also do some hands-on consideration of a couple of issues still outstanding on a few of the specific WAI-Dev resources - the Showcase and the Web for All doc.

Outreach

<shawn> https://www.w3.org/WAI/EO/wiki/EOWG_Participation_Info#EOWG_document_review_stages

<shawn> https://www.w3.org/WAI/EO/wiki/EOWG_Participation_Info#EOWG_document_review_stages

https://www.w3.org/WAI/EO/wiki/EOWG_Participation_Info#EOWG_document_review_stages

<shawn> ACTION: James and Shawn and others interested will look at https://www.w3.org/WAI/EO/wiki/EOWG_Participation_Info#Review_Stages [recorded in http://www.w3.org/2016/03/22-eo-minutes.html#action01]

<trackbot> Created ACTION-336 - And shawn and others interested will look at https://www.w3.org/wai/eo/wiki/eowg_participation_info#review_stages [on James Green - due 2016-03-29].

<Zakim> yatil, you wanted to say: next review should be in the status of the document

<scribe> ACTION: EricE to create a way to add the review cycle information to Github projects so we can use it programatically. [recorded in http://www.w3.org/2016/03/22-eo-minutes.html#action02]

<trackbot> Created ACTION-337 - Create a way to add the review cycle information to github projects so we can use it programatically. [on Eric Eggert - due 2016-03-29].

<shawn> FUTURE TASK/AGENDA: addressing public comments - process, templates, etc...

Sharron: What are the outreach responsibility for EO?

Shawn: EOWG is responsible for the outreach of all WAI deliverables.
... ALL WAI DELIVERABLES.
... Two years ago we did outreach on ATAG with buttons and cards.
... Outreach is also one of my goal. More time supporting outreach.

Sharron: We translate technical standards to the masses.

<shawn> https://www.w3.org/WAI/EO/wiki/Outreach_for_ATAG_2.0

<Adina> :-)

<shawn_> https://www.w3.org/WAI/EO/wiki/Contacts_for_promotion

<shawn_> meetups

<shawn_> sample slides for others

<shawn_> https://www.w3.org/WAI/EO/wiki/Promoting_Accessibility_in_Courses

<Zakim> yatil, you wanted to say that people who are target of outreach likely not interested in doing outreach themselves and to say we don't need to speak for free and to say German

<shawn> https://www.w3.org/WAI/EO/Drafts/wai-pages

<shawn> https://www.w3.org/WAI/EO/Drafts/wai-pages

<scribe> ACTION: Sharron to put the Resource Development + Maintenance Life Cycle into a (interactive) graphic, assisted by EricE. [recorded in http://www.w3.org/2016/03/22-eo-minutes.html#action03]

<trackbot> Created ACTION-338 - Put the resource development + maintenance life cycle into a (interactive) graphic, assisted by erice. [on Sharron Rush - due 2016-03-29].

<scribe> ACTION: Brent to capture and create a wiki page for the outreach initiatives. [recorded in http://www.w3.org/2016/03/22-eo-minutes.html#action04]

<trackbot> Created ACTION-339 - Capture and create a wiki page for the outreach initiatives. [on Brent Bakken - due 2016-03-29].

<scribe> ACTION: EricE to be the Resource Manager for the Tutorials, working with Susan, Adina & Shadi. [recorded in http://www.w3.org/2016/03/22-eo-minutes.html#action05]

<trackbot> Created ACTION-340 - Be the resource manager for the tutorials, working with susan, adina & shadi. [on Eric Eggert - due 2016-03-29].

<scribe> ACTION: EricE to be the resource manager for the Presentations and make edits and changes to the CSS. [recorded in http://www.w3.org/2016/03/22-eo-minutes.html#action06]

<trackbot> Created ACTION-341 - Be the resource manager for the presentations and make edits and changes to the css. [on Eric Eggert - due 2016-03-29].

<Brent> https://w3c.github.io/

<Brent> https://w3c.github.io/

Showcase - issues for finalizing

https://github.com/w3c/wai-showcase-examples

Shadi: recap of the goals and purpose of the Showcase - it is a series of very short videos to illustrate barriers and the implications for people with disabilities.
... each introduces an accessibility feature and provides an onramp to get people into more and more resources.

http://w3c.github.io/wai-showcase-examples/script2.html

Eric: suggest not to put video title on the opening screen
... to maintain the element of surprise
... will take away the relevation aspect.

Susan: but what if they are linked from elsewhwere?
... why would that heighten the suspense?

Shawn: (not my position) Eric's point: because the first thing we see might have nothing to do with people with disabilities on the web

Eric: There is an element of surprise in many of these and we should not give that away up front. But I don't feel strongly and am happy with what the group decides. I find it to be revealing too much and possibly little help for people currently outside the accessibility space but I don't really feel strongly.

James: Won't people wonder if they made the right choice, more important than the element of surprise.

Brent: There is a survey question about this for this week.

Shadi: Intro music during the text display and perhaps throughout?
... what kind of music?

Shawn: Cool, furturistic music.

Sharron: +1

Shadi: more a matter of tone

Howard: Neutral piano music, just a motif

Brent: not too light or lighthearted

James: hard to say until we see them.

<yatil> [Eric has no real knowledge of music, leaves it to the group/production.]

Howard: can we hear samples?

Adina: what is their recommendation? we have an idea in our head, but they may have some experience to guide us.

<shawn> Sharron: Task Force descretion

<Zakim> shawn, you wanted to offer to contribute to TF on music

Sharron: I suggest that the TF make the decision with input form the development compnay

Shawn: and I am happy to help with that.

<Howard> +1

<Adina> +1

Shadi: Narration and the voices?
... do we direction, instructions of the choice of voices?

Eric: can we both male and female voices?

Shadi: will be more on the British side since the production compnay is in the UK
... my suggestion was to have 5 male, 5 female with neutral accents.

Adina: Voice actors often have what is called standard english accent

Shadi: anything else about the voices?
... on the branding aspects? are there colors we should use, visual tone?

Shawn: The W3C blue will live forever, we should use it, maybe the WAI orange rust red?

Susan: can we say here is the main color (W3) and go with that and make it more fun?

Wayne: Videos themselves will be done in these colors or the text slides or what?

Shadi: for the text slide

Susan: we want them to be more engaging, less formal.

<shawn> w3c blue #005A9C

<shawn> wai rust/orange/red #930

Web for All : Accessibility, Usability, and Inclusion

http://w3c.github.io/wai-inclusion/

Shadi: history is that this document was Accessibility and Usability, how they interrelate. To counteract the idea that accessibility is just a subset of usability and the #a11y community pushing back to say no, accessiiblity requires more research and understanding.
... introduced notion of usable accessibility, beyond the checklists. Usability experts can really excel when they are aware of accessiiblity features and requirements.
... discussion has been extended into global concerns for "inclusion."

Sharron: yes we saw that recently at SXSW where disability considerations were made as part of the disussion on inclusion.

Shadi: but basic message of this document is to explain that accessibility is really addressing a situation of discrimination not common to other forms of exclusion such as bandwidth, training etc. The point here is to approach the topic wholistically.
... as a response to anti-discrimination efforts.
... walk through the current draft of the document
... this is to the rough draft stage from our perspective, maybe a draft.
... this is the first time the group has seen it. First reaction?

<Zakim> yatil, you wanted to channel Sharron: TERSIFY! and to say icons/graphics/lists

Eric: Quite long, many things in there, can bullet, make easier to parse.

Sharron: Much is documented already, seems redundant.

Eric: Who is the audience? Usabiltiy professionals? If it is an introduction of accessibility as a question related to usability and inlcusion, here is the basics and here is a place to go for more.

Brent: Introducing people to more about what is accessiiblity, seems introductory and why separate it from what already exists? Where would this be in the nav schme?

Shawn: Designing for inclusion

Brent: and I agree with Eric as well...too long.

<shawn> Requirements Analysis: https://www.w3.org/WAI/EO/wiki/Accessibility_and_Inclusive_Design/Requirements_Analysis

Eric: we can tersify the defintion of accessibility and maybe the others as well. Definaitions may be able to be inlcuded below.
... value would be to explain as clearly as possible what are the differences and overlaps between the concepts.

Howard: What is written here is well written and explains this very well but is also another intro document. Wondered as well where it went in the nav scheme?

<shawn> ... it is an important issue - people using those terms -- but wonder if it fits other than int he main navigation. like glossary...

Howard: may need some links to more info

Susan: Was going to ask for requirements and find that it is an example of what we spoke of about streamlining our resources.

Adina: would be interesting to do some usability testign to see what people actually read on the page. My own experince is never to read an intro. Esp on the web, people want only one or two sentences in a paragraph
... this needs to be scannable

Eric: A graphic, illustration of relationships and overlaps seem as thought it would be beneficial

<yatil> +1 to have the quote more standing out

Howard: It is a great quote, should be made more prominent, cut down on words, use pictures and more visual hierarchy, structure, bullets, etc.

<Susan> +1 to breaking these out - including bullets, pull quotes, etc. (comment applies to most of all of our resources.)

Shadi: merge the document?

Adina: is this capturing your attention in 3 seconds?

Shawn: Channeling Howard, maybe it is a stand alone doc that answers a question.

Wayne: yes like Dept of ed answering the question what do I do about this parasite?

Susan: seems irrelvant whether it is in the nav or not, we have info that is repeated elsewhere.

Shadi: But linking out has its own problems. We meant this to be an ultra summary, it is a very short explanation to se the frame for this.

<shawn> s/Channeling Howard, maybe it is a stand alone doc that answers a question./howard's point about not really fit in the nav. this is a different type of document. this is answering a specific issue -- more like an article/blog

Susan: Three of the four audience targets are accessiiblity documents. Far too heavy, would like to see us take our resource not as a stand alone but in relation to the others - as a body of work.

Sharron: +1

Adina: Take the tried and true approach - this is what i will tell you - then tell - then repeat what I told you. Shoudl we take that approach?

<Wayne> q

<Wayne> q/

Howard: a sparate FAQ or article, blog post, something like the WebAIM model.

Wayne: I have found that many people who know about accessiiblity mix up the usability aspect.
... may need context to tell the difference.

Eric: Employ our new model, perhaps publish it and work on it later.

Brent: Will we get to approval to publish?

<Howard> + to Eric's suggestion

Eric: Just one cycle is what we are working toward with the understanding that we will have another opportunity during the review process.
... I don't think this is a bad resource, could be improved by tersification, structural improvements, etc but could be OK.

Shadi: We do not yet have agreement on the structural, conceptual level.

<Zakim> moves, you wanted to take this discussion in to the draft phase work. github

Adina: I can take this on as RM

Shadi: but I have to do this, it is part of my project - the question was a stand alone or merge, needs oversight of the group.

Brent: I agree it should be merged.

Shadi: Will you take it on?

<yatil> [Eric thinks it should be an intro to the differences in our suite of intros on the page.]

Brent: yes, I am happy to work with a group and don't feel like today is the day to take that one.

Shadi: Great if you will take it on, I will be happy to fill in the blanks.

Brent: OK - Adina, Denis, and I will consider this question and include Shadi and Shawn.

Wrap-Up

Sharron:We are at the end of our time and I just wanted to thank everyone for taking this deaprture from the standard way to conduct our face to face meetings. Brent and I have been thinking of how to change the dynamic, make the group more productive, and get our resources moving thorugh the processes to publication and keep them living and relevant. We knew that if we brough this to the group as an open question that you would help and you have stepped up in ways we could only have hoped for -thank you!

Brent:We will take all the information collected on these flip charts and will transcribe and post them to the wiki. We can let these ideas percolate and see where they lead. Remember we have another face to face coming right up in May in Austin so we can build on what we have done here.

Susan: I just wanted to add that I think this momentum is awesome. I am excited to move forward and dig in

Brent:If you have not done so, please complete the skills and interest survey so we can get a broad sense of what skills we have and what we need to recruit. Thanks again, see you around the conference and then again in May!

https://www.surveymonkey.com/r/HN9V6YW

https://www.w3.org/Consortium/Member/List

<shawn> ACTION: Shawn check on guest contributors [recorded in http://www.w3.org/2016/03/22-eo-minutes.html#action07]

<trackbot> Created ACTION-342 - Check on guest contributors [on Shawn Henry - due 2016-03-29].