Tutorials

Eric: I have processed all comments I received through the survey - at least all but one that Shadi and I must reconcile. Also addressed a couple of bug fixes.
... not sure how much longer to address that last issue and unsure if we will need another round of review or will be able to ask for approval. Very happy with survey results, lots of good comments, very helpful.

Brent: We are eager to publish and just have one more issue to resolve, any other comments?

Shadi: Excellent work, Eric

<Caleb> Yes!

Sharron: +1, thank you Eric

Brent: and good job for everyone indicating the priority of comments making Eric's processing of issues much clearer.

How People Use Web

Brent: Shadi has polished the document, asked COGA to look at some specific things. Have gotten some but expect more feedback from that group before we can publish. Editorial changes in document on this and mobile may require one last survey of approval.

Shadi: Thanks to Howard for updating links to current standards. While we wait for COGA take the time to re-read stories with an eye to the added references to mobile for relevance. See if it seems natural, if anything is jarring, etc to help expedite final review.

Brent: I will follow up with the initial COGA feedback.

<shawn> Shawn: COGA dealing with tough issues around 2.1

Topic: Introductions, Mitchell Evans joined EOWG

All: Introduce selves briefly

Shawn: Wanted to reiterate that we are welcoming to new folks and hope you will feel free to ask any questions. It is a strange and wonderful environment so let anyone know when/if you need help or support.

EOWG charter

Brent: We have extended the current charter in order to finish out the current deliverables, thank you Shawn for guiding us through that process. Chairs and staff have been working and Shawn will walk us through questions for the group.

Shawn: We have a proposed list compiled from the site redesign TF and EO discussions at the face to face meetings of last year and early 2017. There is a potential funding source to do specific work. We want to take the temperature of EO to see how we feel about doing more around Accessibility Statements, building on work we have previously done and providing some flexibility on how we proceed. One possibility is an accessibility statement generator. The question is do we want to do this work if funding is provided for an editor?
... building on work we did in the WCAG-EM intro, in the WCAG2 info about Conformance claims and a few other places. Note that in Developing Organizational Policies on Web Accessibility we say "consider providing a public accessibility statement that reflects your policy, goals, and achievements" but do not provide specific guidance on how to do this. This work could add or be complimentary to the Template for Accessibility Evaluation Reports and/or Planning and Managing Web Accessibility. It could also be made into a small generator as part of or in addition to the WCAG-EM Report Tool

<yatil> +1

Shadi: I see it to be an annotated template like the reporting template we have. Could be part of the Report generator or a stand alone generator.

Shawn: The work is proposed for later in 2018.

<Norah> +1

Denis: I would like to understand the priority in relation to what we have planned. What be our role?

Shadi: EOWG would review requirements and it would become part of the EOWG ongoing work.

<rjolly> +1

<Howard> I don't see any drawbacks unless someone else does.

Eric: Of course if you want to be more involved, supporting the editor, that would be encouraged and welcomed. It would be like the tutorials with ongoing input.

<Norah> +1

<Howard> +1 sounds like it fits within our scope.

<dboudreau> +1

<Caleb> +1

<Brent> +1

<shawn> +1

Brent: We have a list of several things we are considering for deliverables in the next charter. This is one of the items that Shadi knows could be funded. At this point we want EOWG to say if this is something that we would want to take into our fold.

Mitchell: From what I have seen in the practical world the questions commonly come from legal departments and whether companies should even have accessibility statements. The concern is not how to write it. Language is not the impediment, EOWG could be useful in providing the rationale.

Shadi: Not sure that providing the rationale would be a focus. Rather it would be how to write a statement and how to reference the proper sources when creating effective statements.

Mitchell: So more of what are the necessary components rather than the specific language to use? Seems that would be most valuable.

<MitchellEvan> +1

Norah: I think this would be an excellent resource. Rather than showing a variety of different statements in "the wild" and to be able to point to an authoritative guide from W3C would be valuable.

Shawn: Any objections or concerns?

RESOLUTION: EOWG supports the proposed work to develop guidance for crafting accessibility statements.

<krisanne> +1 - I think this is a good direction for eo

<shawn> https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects#2017_Charter_Work

Shawn: Current charter is extended into August 2017. Within the next couple of weeks, we must submit the next proposed charter.
... staff and Chairs have reviewed the work of the Web site redesign TF and the discussions of the previous face to face meetings and created a list of potential work.
... we ask you to review, look at the work proposed, see if there is anything on there that we don't want to do, and/or anything missing.

Denis: I see the Quick Tips are here, which is good. What I want to be recognized is the fact that we will break it into more granular parts.

Shawn: In talking about the Quick Tips, Denis referenced the ones that are still in draft and he and Robert have been working on those. Judy, you have too.

Judy: Yes, Denis. The 3 that were incomplete I have been looking at these and wanted to suggest a third on procurement rather than advocacy.

Shawn: So if you all can meet outside the meeting, try to get those done before this charter ends and see if we have more work on this for next charter.

Denis: Also, the accessibility Roles work is something I have continued to think about and I have met some folks who would like to work on it. My question is do we want to work on that in EOWG and what is the potential for IEs to help?

<shawn> pointer to past work https://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown

Shawn: What would be the deliverable?

<shawn> quick ref roles https://www.w3.org/WAI/WCAG20/quickref/?currentsidebar=%23col_customize

Denis: Much as we have the Quick Tips for Developers we would have similar tips for other roles. Allowing people to focus on the most relevant SCs for their own work. Follow the process through the entire product development life cycle. We have begun mapping SCs to various roles but nothing is fleshed out. I hear how often it is used in various companies. The people I met from Optum started with that and interviewed stakeholders and have developed the resource internally.

<shawn> Developing

<shawn> Interaction Design

<shawn> Content Creation

<shawn> Visual Design

<shawn> [Denis... "informal doc in CG kinda bothers me instead of formal doc from WG"]

Denis: I would like to rewrite in less formal language and provide practical support across the roles. It would be a useful way for people to break down and distribute across the enterprise. We continue to work on it in Slack and I would much prefer to do it here in EO.

Shawn: Can you send an actual project plan, what this would be so we can look at it?

Sharron: Can you do it on the wiki?

Denis: Yes do you have a template I can use?

Shawn: Yes

<shawn> sample requirements analysis https://www.w3.org/WAI/EO/wiki/Stage_1._Requirements

Shawn: I would say don't spend a lot of time, it is just a way for EO to see how to prioritize it with our next work.

Eric: What we know is that AC likes to see incubation work in Community Groups, so if instead of using Slack you can do the work in the Community Group wiki that would be encouraging to the AC.

<shadi> +1 to eric!

Denis: The other question was how to get these collaborators into EOWG as IEs?

Sharron: A great first step would be to get them started within the Community Group, contribute through that and GitHub, etc

Brent: Sounds like a good plan and

Howard: My suggestion previously was about a curriculum, I don't see anything like that in the charter. With this current grant we have, I can see a synergy. Is that to be considered?

Sharron: Can you do the project plan as well?

Howard: Sure, as long as I can describe a scope.

Sharron: The idea is to do a high level description of goals and final product and then as people consider, it will be further refined by EOWG based on group consensus and interest.

Judy: On the educational use of materials, I am not sure how much that is integrated into the charter work, but should be synchronized.

Shawn: OK great ideas. Anything else to be added, or anything on the list that should *not* be on the list? Your input is greatly appreciated today and on the coming survey.
... second part of our name is "Outreach" Have not been particularly active in outreach and want to address that. Many have not been comfortable doing outreach to an antiquated web site. So we are working hard to get the new site to a state of MVP and launch so that we can begin an outreach push. Questions or comments on that approach?
... Looking at the table, Outreach is posiitoned so that certain things are done before we even begin the outreach. Any initial thoughts about those?

<shawn> https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects#2017_Charter_Work

KrisAnne: Looking at the table, is this the order in which things will get done? Is this the priority?

Shawn: This is a rough draft, first pass at a timeline.

KrisAnne: I will be happy to help putting training together and think it would be part of the outreach.

Shawn: We have a resource that helps other people develop their own training. Your input would be valuable.
... Can we add you to the folks working on that?

KrisAnne: Yes absolutely
... I would like some of the older stuff to be fixed or removed before launching the outreach

<James> +1

KrisAnne: The whole web redesign has to be integrated with the materials update

<James> +1

KrisAnne: when doing library work, we used the term "weeding" This is needed on these resources so that pepole can get what they need when they need it.

Sharron: Reiterate that Resource Management of the training resource is formally assigned to Andrew. If you become part of that team, it will be very helpful.

KrisAnne: Yes I can do that

Robert: Will we develop presentations that we as EO participants can present at conferences?

Shawn: We wanted to provide guidance for people to develop their own presentations and kind of modular information that people could adapt within their own presentations.

<Brent> +1 to Robert

Shawn: An important thing to consider is the timeline -- and how long until we get MVP and can start outreach push. 3 items per quarter for example, what does that do to the timeline?

New project outlines from Judy

Brent: This is to follow up to the suggestions EO provided to Judy.

Judy: Thank you for the feedback everyone provided. There are links here to the changes, some have not been responded to and I will get to those soon.

<Brent> ARIA: https://www.w3.org/WAI/EO/wiki/Tutorial_Mockup_ARIA_Concepts

Judy: looking at the ARIA one first, there were concerns about the title for both this and the Mobile resource. It is now in flux so there may be inconsistencies.
... exploring the title "A developer's Introduction" rather than "Guide" which may indicate more comprehensive resource than actually provided.
... will ask a few questions and then put them in a survey.

<Brent> Mobile Overview: https://www.w3.org/WAI/EO/wiki/Tutorial_Mockup_Mobile_Overview

Judy: Want to address the mobile confusion that there is a separate standard for that. Want to use an approach that that WCAG absolutely applies and yet gives context for mobile. Provide guidance for where relevant resources are embedded in existing materials. One suggestion has been to integrate more mobile examples throughout the others rather than make an additional tutorial.

James: For the ARIA resource, suggest "An introduction to ARIA for developers" frontloading ARIA

<Brent> Accessible Media Tutorial Overview: https://www.w3.org/WAI/EO/wiki/Tutorial_Outline:_Accessible_Media

Judy: Captioning one was strongly suggested to make broader. We have expanded the outline that gives overview of conceptual and informational flow.
... interested in reactions on scope and names. A bit concerned that scope may be too broad given the time constraints for creating these.
... early feedback especially helpful.

Brent: Let's discuss the names of these resources. You have indicated that "Introduction" is preferred - any comments on the titles?

James: Think there are too many words in that title. A short title with the focus up front.

Judy: Front load topic

<shawn> ARIA Introduction for Developers

<Norah> +1 on Introduction rather than guide

Brent: Is the intention to follow a similar pattern for the mobile?

Judy: Yes, the less we have variation in titles, the less confusion we generate.

Brent: What do people think about the examples and what should be in the introduction?

James: Reading through the plan, it is not really a tutorial, it is an example of how to get the point about ARIA use. By the end. Want them to "get" ARIA and allow them to use their developer skills to apply it. As long as we make them aware of the consequences of using ARIA, having just one example throughout is great.

Norah: I think it would be useful to have more than one, at least two would allow me to understand how the principles might be applied in another situation.

Brent: And what about the conceptual approach?

Judy: Let's consider that question while thinking about the Mobile resource. I felt that at first it was hard to articulate how mobile is the same but different. Does this approach seem to be helpful for developers to understand that complex issue?
... what do people think about this approach?

<Norah> +1 approach looks helpful

All:No objections

Brent: For the captioning tutorial it has been suggested to change not just the title but also the content to broaden and include other aspects of media presentation on the web - any comments?

Norah: This is a better approach, it will have more appeal and be a more useful resource.

Brent: OK we will get some questions from you Judy and present them in the survey.

Face to Face meetings for 2017

Brent: Face to Face in Austin May 19 and 20 - Please let us know if you are coming, which days, and if you want to participate by phone.
... Also a face to face in California in November, get your dates set, make a reservation since hotel will sell out.

Policies

Brent: Have a couple of issues that need to be finalized - will be on the survey. As a point of information, Robert and Eric are working on the submission form.

WrapUp

Brent: Only survey this week will be the weekly survey. Thanks for all your feedback and the work you are doing. Thanks and look for the survey in Work for this Week.