Brent: Full agenda today, will quickly update and make resolution for a couple of things and get them done so we can move on to the things that need more consideration.

Planning and Managing Web Accessibility

Brent: We are in that place in the cycle to do thorough review and next would be public review. Because we have been so detailed in our general review, we will combine these two steps.

<kevin> http://w3c.github.io/wai-dynamic-planning/

Kevin: Here is the URL to the current draft of the resource, part of a group of resources targeted to Managers of projects or programs regardless of organization size. We group them by program phases, not meant to provide detailed solutions ofr all of tehse but rather to give a roadmap to what must be considered. Last activity flurry was just before the end of year holidays. At this stage, we are looking for publication. It will replace the "Strategic Planning" document once we get it published. So there is a survey for this, the aim is to have public review as well. Need to carefully look at the text, dot all i's, cross all t's etc

Brent: This will be a separate survey from Mar 7th to the 15th and will give you the opportunity to make any final comments before public review. The survey will combine the thorough review stage with approval for public review.

WCAG-EM Report Tool

Brent: We have come to the point where we have a published version and have been adding features and updating the tool. Wilco has been doing the work to publish version 1.1 of this resource.
... please review the links in the agenda, to the tool and previous discussions.

https://www.w3.org/2002/09/wbs/35532/EOWG14Dec2015/results

https://www.w3.org/2015/12/18-eo-minutes.html#ResolutionSummary

http://w3c.github.io/wcag-em-report-tool/dist/#/

Brent: EO previously resolved to retain the title and we are ready to move to publication with the approval of the group.

Shadi: Looking forward to publishing before CSUN. Any questions, comments, concerns?

All: none

<Susan> no concerns/Qs

RESOLUTION: Publish version 1.1 of WCAG-EM Report Tool with the current updates.

Sharron: +1

<Susan> +1

<Brent> +1

<howard> +1

<shadi> +1

<George> +1

<kevin> +1

<yatil> +1

Showcase Examples with Video

Brent: Have been working with the TF and the production company to process EO comments and have edited the scripts, visuals and are ready to move into productions. Shadi will take us through unresolved issues.

Shadi: Thanks for the comments and input, they have been very helpful, over 100 issues and commits. Have worked through most of them and only a handful remain, some related to the web page itself. Thanks again.
... second batch - the scripts number 6 to 10 had fewer comments. I think the groups learned from your comments and implemented an approach more aligned to expectations. Changes to Scripts 4 and 5 have had recent changes based on comments.
... the text to speech script is more experiential and we see screen text highlighted as read and have (fingers crossed) recruited a person with a guide dog for the filming. later in the script we go on to the broader issues
... Howard your objections to Script 5 were considered, we took another pass for clarity and impact for PWD vs the broader benefits for all. Please look to confirm that we have addressed your concerns.

<shadi> http://w3c.github.io/wai-showcase-examples/script5.html

<shadi> http://w3c.github.io/wai-showcase-examples/script4.html

<howard> done

<Susan> done

<George> done

<Brent> done

<yatil> done

<kazuhito> done

<kevin> done

Howard: Yes it looks good from what I have seen this round, clear, very good.

<shadi> Howard's comment: https://github.com/w3c/wai-showcase-examples/issues/114

Susan: My concern about the gender specificity was that we had two scripts of women doing domestic tasks. If that is addressed, it removes my concern

Shadi: Any other comments?

<shadi> old version: https://www.w3.org/WAI/EO/Drafts/showcase/12Feb16/script5.html

Kevin: In sequence 5 there is a cut to screen magnification. The relationship between that and the other web site may be lost. Need to be sure to keep the connection clear since it is easy to lose when the text is enlarged.

Shadi: These will be fake web sites that look real but not fully functional, maybe you can help prepare it as a prop.
... if these are good to go, maybe we can move to resolution

Sharron: The connecting phrase?

Shadi: I would like resolution from the group to approve the visuals and the scripts with the understanding that the closing phrase will be that connection of all of them to the whole.
... any other concerns?

<yatil> http://w3c.github.io/wai-showcase-examples/script4.html

Shadi: shall we look at Script 4, have a look through that especially the first few sequences

<Susan> done - already read

<kevin> done

<yatil> done

<scribe> done

<Brent> done

<kazuhito> done

<George> done

<howard> done

<shadi> Shawn's comment: https://github.com/w3c/wai-showcase-examples/issues/106

Shadi: Shawn felt that the emphasis on the needs of people with disabilities was weak. I think now it is a bit more worked out, what about others, do you think those needs are addressed?

All: No objections

Howard:Seems to address Shawn's concerns well, the fact that this is necessary to people with disabilities is clearly made.

Proposed resolution: Scripts are accepted in general - the visuals and the general tenor of the scripts - with the understanding that the closing phrase and other minor word edits may occur.

<yatil> +1

<kevin> +1

<Susan> none

<Susan> +1

RESOLUTION: Scripts 1 through 10 are accepted in general - the visuals and the general tenor - with the understanding that the closing phrase will be reviewed and other minor word edits may occur.

<yatil> +1

<Brent> +1

<kevin> +1

<howard> +1

<shadi> https://github.com/w3c/wai-showcase-examples/issues/41

<shadi> https://github.com/w3c/wai-showcase-examples/issues/47

<George> +1

<shadi> https://github.com/w3c/wai-showcase-examples/issues/109

Shadi: next step will be to look in more detail at the narration, particularly the aspects that these features are vital, essential for people with disabilities and to make sure that the main point is not lost. Previously the attempt at humor or light hearted approach may have lost the point. Also consider the catchy phrase at the end - to re-emphasize the importance for PWD and the overall benefits

for all.

<shadi> http://w3c.github.io/wai-showcase-examples/Overview

Shadi: thank you all very much, we are pleased and excited by the evolution of the scripts. We now will move into production. You may have noticed that the launch page for the scripts is starting to take shape and we need a catchy and meaningful title to segue into the next topic.

Resource Title of the showcase

Brent: While the videos are the focal point, there will be other resources on this page, supporting info for each point and more. We have started a dialogue about the name, TF has come up with a list that we have posted as a dartboard to start everyone throwing ideas around.

<Brent> https://www.w3.org/2002/09/wbs/35532/26-Feb-weekly/results#xq8

Brent: First shot at a name was not accepted as catchy, interesting, intriguing enough. Susan's comment that it was too generic struck home and we realized we need more input.
... put list of these brainstorms into the survey, people are honing in on - see for yourself; impact; Want to open discussion/brainstorm about the name, spend time throwing out and discussing possibilities

Brent: current proposal is Web Accessibility: Impact and Benefits and I want to open the floor for discussion.

Susan: I want to know what others think, this does seem generic and that it could be applied to so many of the other resources. Seems way too general. Something shorter, more invitational. I don't like this.

Howard: I agree with Susan but not sure what the solution is

<kevin> [See the benefits and impact of Web Accessibility]

<howard> How about "Web Accessibility in Action"

<yatil> Web Accessibility in Motion?

Sharron: We need a title that emphasizes the invitational, interactive aspect

Adina: Building Awareness?

<kazuhito> catchier is better

Susan: seems also like expecting them to do comething

<howard> "See Web Accessibility in Action"

Howard: To follow on to the action idea, I think there needs to be a more catchy phrase to distinguish from others

<George> +1 Kevin (benefits & impact)

Shadi:Say more about the interactivity, it is not really an interactive resource.

Sharron: I mean engaging I guess more that interactive...words like wake up, come see, join in, things that make people understand that this is a demonstration and there is illustration of needs, impacts, and benefits.

Brent: People still like the words benefit and impact.

<yatil> See how web accesssibility benefits impact your life!

<howard> "See Benefits of Web Accessibility in Action"

<kevin> Web Accessibility in ACTION: Benefits and Impacts

Susan: Wake Up to the Impact of Web Accessiiblity

Adina: View or Watch Accessibility in Action

<Susan> Look at the Impacts of Web Accessibilty

Shadi: Just to remind that the video is a focus mechnaism and to remember that there are text and links to resources that surround the videos and provide people with more info...it is a lure into the other resources.

Sharron: Jump in

<Kazuhito> "Jump in" sounds good.

Adina: As a developer if I see jump in, I will expect code or some practical thing to apply. Not think immersion but would be looking for instructional materials

<kazuhito> that reminds me of "Dive Into Accessibility"

<Brent> "Why? Web Accessibility"

<Brent> "What is it good for? Web Accessibility"

Susan: I like "Wake up" or "Check Out," Look probably doesn't address what Shadi said as well

<George> Accessibility: Get Up Offa That Thing and Dance (James Brown)

Brent: What is our timeline for naming this resource?

Shadi: We have very little time, the sooner the better is to create the URL where it will be hosted, it must appear in the film, in the video
... need a firm decision wihin the next week or so.

<shadi> participate

<shadi> invitation

<shadi> impact & benefit

Sharron: It seems to me that EO is looking for something title that conveys invitation, experince of accessiiblity, an indication of interactivy, with consideration of the words impact and benefit

<yatil> Wow! Web Accessibility!

<yatil> Web Accessibility Words of Wisdom - Web Accessibility WoW!

<shadi> experiential

<shadi> see people with disabilities

<shadi> demonstrate/illustrate/illuminate

<shadi> this is something that applies to you

<shadi> we invite you to learn about a11y

Susan: The reason I like that is not so much that they will interact with the page but they will be invited to participate in Web Accessiiblity overall

<shadi> invitation to a challenge

Brent: Almost like an invitation to a challenge - the challenge of web accessiiblity and your relation to it.

Shadi: Thanks, any further thoughts?

Howard: I like the word of experience - Experience Web Accessibility in Action!

<shadi> experience web accessibility in action

<George> +1 Howard

<Brent> +1

<yatil> +0.1233333

<shadi> experience web accessibility in ACTION learn about impacts and benefits for everyone

Brent: To get developers to understand, we often put people in the seat of a person with a disability and it is powerful and it does help them understand the impact.

Shadi: with a subtitle?

<shadi> showcasing

<George> awareness of web accessibility in action

Eric: Not to be the party pooper, but this is not really experiencing web accessiiblity here, it is more of a showcase, a demonstration.

<Susan> +1 to Eric

<shadi> see web accessibility in ACTION: learn about impacts and benefits for everyone

<yatil> probably without see. Just 'Web Accessibility in Action'

Brent: Well, that goes right back to the boring title for me

<shadi> web accessibility in ACTION: learn about impacts and benefits for everyone.

Shadi: Are we not back to generic then, applying to many resources.

<yatil> watch web accessibility in ACTION: learn about impacts and benefits for everyone

Brent: We can review the minutes and propose some new candidates.

Susan: we need an action verb!

Accessible UI Components List

Brent: As you know, Eric has been working on this tool to accept submission for widgets, templates and frameworks that are accessible, Eric will walk us through.

Eric: We got some feedback about the categories and have two things to consider. As people use the tool, they have pointed to little templates that are more like code snippets in HTML and CSS as well as CMS solutions. We ate thinking of replacing Templares with Thems

<Howard_> eowgnow

Eric: Some CMS providers may indicate accessibility in their themes, but it is not always reliable. In any case, we are considering replacing "Templates" with "Themes" and will put a survey question about that.

Sharron: Why does it have to be one or the other? why not both?

Eric: A template seems an intermediate step, having a public category may not be worth the effort there are so few of them.

Shadi: I have been asking many questions about this as well. Do I understand correctly that template as a term is being replaced by themes? We have also looked at code snippets to which you apply your own styles?

Eric: A theme comes with all its own JS, CSS, and HTML that can be used immediately, usually called themes (occasionally skins) within CMS
... a template is much more general and snippets are short bits that can be tucked into another code base, not a boilerplate for everything else.

Adina: Are you considering Frameworks such as Google Polymer?

Eric: That is basically a library for doing web components not UI components, what really counts for this polyfill library are snippets that can be used within Polymer.

Adina: It seems to use its own XML that is not rendered well by screen readers.

Eric: Yes the APIs are not well defined and require a lot of ARIA to impose accessiblity so would not be a likely candidate for this tool.

Shadi: So I do not see that we are replacing one with the other but only to add a category of Theme, yes?

Sharron: +1 to Shadi

Shadi: The difference with themes is that they are tied to a specific CMS, is that right?
... so how will it work in terms of tagging the input?

Eric: We have vendors now so it would be the vendor as a straightforward guide to the specific CMS

Shadi: But vendors can make a WP theme, so it would be trickier to categorize.

Eric: Yes, it will be useful to have a search for accessible theme for specific CMS. We had a look and there are many demos that people are creating for learning, huge libraries of code samples. Therefore we are considering adding a category for snippets or demos. We have had a lot of those, I think it will be beneficial for the tool, must think of how to categorize them.

Shadi: It seems that the line between templates and snippets is not clear.
... can they be one category?

Sharron -1 to Shadi

Kevin: The difficulty is that a template has taken on a bigger meaning beyond a snippet. It is an entire page, almost a theme but maybe just for one page. Snippets are more specific to one task, small nuggets of code.

<Susan> +1 to Kevin

Kevin: example might be how to expand/collapse content

Shadi: So we need separate categories for templates and snippets?

Kevin: Yes, and not sure if templates will have any use but would not lump them together. Question is do we need templates at all?

Sharron: Have any templates been submitted?

<Susan> Could we please list current categories again?

<yatil> Widgets, Frameworks, Templates

Eric: Yes but it is really a theme, either they call themselves bootstrap frameworks or something.

Susan: Is it possible to combine snippets with widgets, those seem more related?

Eric: Widgets can be stuck into a page and will work, snippets are more dependent on what is around it and integration.
... Thanks for the discussion, we will try to reflect this in the survey.

Shadi: I am afraid we are creating categories for things that are not well defined and what the long term implications will be.

Eric: For the first version, we should err in my opinion on too few categories rather than too many.

Eric: looking at the submit process, we received good feedback. Some have submitted widgets directly into the tool which was great. It will be *really, really* good if each of us in EOWG would submit at least one item to get a good understanding ofthe tool.

Kevin: One thing I bumped into was the question of if I was adding something that was already there, not always sure that they would have categorized it in the same way that I did. How are you checking for repetition?

Eric: Only can search for the vendor, compare the URL but no real flag for that.

Brent: We have asked in the past for people to submit, but if you can consider this a real assignment and try to do this. In future we will have discussions about the interface and it will be important that we all have had experince. Please do try to submit at least one component and to reach out to others to do it and provide feedback as well.

UI Tool demo

<yatil> https://www.dropbox.com/s/ag6zzosn6tj8yun/acuil-add-content.mp4?dl=0

Eric: Here is demo of me putting the PayPal HTML 5 player into the tool, let me know when you have finished watching

<Howard_> Volume too low for me to follow _ sorry

<Brent> done watching

<shadi> done

<Susan> done

Sharron: done

<Brent> done

<Brent> straight forward

<Brent> good video

<Susan> I'm good with it

<kevin> Missed the tags when I submitted stuff :)

Eric: Will put this video link into the survey.

<George> good job

Brent: We will have this in the survey, ask everyone to submit at least one component.

Wrap-Up

Brent: Weekly survey coming with video names, the need to upload a component, will have more info about the text edits. There will be a separate survey on thorough review and permission to go to public review and will communicate when they are available.

<Howard_> Bye all

Sharron: Please add to the wiki any information, topics, clarification needed at the upcoming F2F. Even if you will not attend in person, we will have phone lines open both days, please let us know what you need to do your work more effectively.

Brent: Thanks everyone for your participation and have a good weekend.