WCAG-EM Report Tool

<yatil> WCAG-EM Report Tool

Brent: Overview of tool and purpose
... did usability testing at AccessU earlier in the year
... some issues addressed, other still on hold... new prototype available. Not everyone has had time to consider Wilco's updates - therefore those survey questions will be extended into next week
... Wilco and Shadi are hoping to be finished with updates in mid-December. The question then becomes whether to - release then or wait?
... One opinion is that it is not a good time to release due to holidays, so prefer to make announcement in early January. Others are eager to publish updates ASAP

David: have used the tool at client request
... and found some fundamental challenges in using it
... we could offer feedback

Sharron: yes please do - maybe to Wilco in private (and EO-Editors for the record) thanks for that suggestion, Andrew

<yatil> -> wai-eo-editors@w3.org

Brent: will be good to get feedback from actual users
... thank you David
... any other comments?
... Wilco will try and be on Dec 4th call to discuss updates

Brent: Translations - looking for assistance to translate into non-EN languages
... initially from within EO, or to wider WAI-IG. Please look through your networks for potential people to reach out to for this purpose.

Quickref Update

Eric: public review is open - some feedback is coming in

<yatil> https://github.com/w3c/wai-wcag-quickref/issues?q=milestone%3A%22Before+PR%22+is%3Aclosed

Eric: I have already made a few minor changes - header height and some small visual changes
... better button naming

<yatil> https://github.com/w3c/wai-wcag-quickref/issues/new

Eric: It is now open for public review and of course EO is still welcome to contribute until Dec 2

Brent: please all look over and make appropriate comment
... any other comments today?
... Thank you Eric of the work

Showcase Examples with Video

Brent: Our task force has been creating stories and video describing how accesisble features make sites and services much more usable and will bring updates and Qs to EO
... we hope to be finished by the end of end Q1 2016
... currently seeking a production company to create story boards
... eight have been contacted and asked for samples that match what we're trying to achieve - 4-5 responses received
... asking is larger EO was interested in helping to assess the production companies and the submitted sample videos
... if anyone is interested, contact Shadi directly
... TF meets every Monday - on Nov 30, others welcome for consideration of submissions
... any questions?

Andrew: will EO members be able to review and comment / provide feedback on the story boards?

<shadi> [[yes - for sure]]

<shadi> [[here is a preview of the the first script http://w3c.github.io/wai-showcase-examples/script1.html]]

<shadi> [[once it is more complete, EO will be invited to review]]

Brent: storyboards will have sketches and scripts that we will be able to provide feedback on

Brent: there comes a point where the production company effectively takes control as they move into production
... hope there will be a point where EO can comment before production starts

<shadi> [[production company will only film what EO says it should film]]

<Vicki> correct link: http://w3c.github.io/wai-showcase-examples/script1.html (closing bracket was too much)

Brent: any more comment?

Planning Activity Icons

<kevin> https://www.w3.org/2002/09/wbs/35532/EOWG13Nov2015/results#xq4

Kevin: survey results re activity icons
... explored the idea of including icons for the activites - mocked-up some pages with icons for review
... general response was that they added too much clutter

Kevin: anyone pushing to support icons?

<davidberman> ok

Brent: lets take a few minutes to refresh what was proposed and the responses

<davidberman> done

<Vicki> done

<SusanHewitt> done

<Sharron> done

<yatil> done

Kevin: open for discussion

David: seems they are decorative rather than definitive - probably too many

<Vicki> +1 Andrew, top level

Andrew: think we should keep top level, but second level gets distracting

<SusanHewitt> +q

Brent: likes top level, but next level has less meaning

<kevin> http://w3c.github.io/wai-dynamic-planning/icons/initiate/get_familiar.html

<Sharron> agree with Brent that lower level icons distract from top category icons

Brent: when looking at the link provided, on the 'get familiar' page the mortar board icon does help tie short name with page title

Kevin: still need to address short names issues

Kevin: and more questions?
... no - propose we don't pursue icons for the activities

RESOLUTION: we will use icons for top categories, but not for activities

<James> +1

<Vicki> +1

<SusanHewitt> +1

<Brent> +1

+1

Planning Resource name

kevin: let's look at resource name

<kevin> https://www.w3.org/2002/09/wbs/35532/EOWG13Nov2015/results#xq2

Kevin: pulled out and presented starting options in survey

<Sharron> I liked the "Blueprint" idea that Susan proposed

<yatil> Categories in the agenda

Kevin: presented survey offerings in Agenda by interpreted clarity of suggestions

<inserted> [[Reading Break:]]

# Clear options

Planning for (Web) Accessibility +

(Web) Accessibility Planning +

Planning and Managing Accessibility +

(Web) Accessibility Planning Guide

# Less clear options

Organizational Accessibility Activities

Accessibility Planning Procedure

Accessibility Blueprint

Addressing Accessibility Toolkit/Toolkit for Addressing Accessibility

# Didn't make the cut

Accessibility Practices

Accessibility Infuser

The Road Less Travelled

Create a Plan for Web Accessibility

How to Plan for Web Accessibility

Accessibility Strategy/Strategic Planning for Web(Digital?) A11y --

<davidberman> done

Brent: focusing on agenda summary - let's look at options

Kevin: didn't include all (late) suggestions

David: like the inclusion of "web" and also "strategic"
... prefer "plan" to "planning" as we actually offer a 'plan'

<SusanHewitt> pointer...

<SusanHewitt> it's a guide as to how make a plan

Kevin: is it actually a plan, or just a pointer?

Vivki: likes planning as it's a whole process

David: yes - probably correct

Brent: we're offering an approach to planning, not a plan per-se

<shadi> +1

<Brent> I vote for NOT using the word "Web"

<davidberman> so I have been convinced that "Plan" is not right.

Andrew: quite happy to drop 'web' as it applies to more boarder digital accessibility

<SusanHewitt> good point shadi

Shadi: does 'web' help with SEO?

Eric: With the wealth of content on the pages, I don't think web makes a major difference for search engines, especially with more personalized search results.

Kevin: suggests a ranking survey Q for this week and we can vote
... can reconsider having 'web' in title when we're clearer about top choice(s)

<Vicki> good point shadi. i think we shouldn't overlook it. keep it on the burner as suggested by andrew

Kevin: will include first 4 from agenda and a few other later offerings

<Vicki> no problem: you're doing well kevin

<SusanHewitt> Kevin, can you briefly explain why the middle four are less clear?

Kevin: not sure about James' suggestion - might be to precise/prescriptive

James: happy if not included in vote

Kevin: will include a suggestion with "strategic"

Brent: thanks for going over all that and explaining the sorting and next steps

Planning - Introducing Initiate content

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

Kevin: introducing as it will be on the next survey to review content
... overview page and sub-pages
... will have to take a clean-up pass once we settle on final page titles
... please comment via github, or via survey or via email

Brent: any questions at this stage?
... will see survey Qs this week on Planning resource

Getting Started Tips

Kevin: Seeking approval to publish recent changes made. While they ahve been incorporated, the changes have not yet published
... will put together a separate survey when all changes are complete
... changes will be detailed in the survey
... prototype will include all changes. any questions at this stage?

<davidberman> no immediatequestions from me on that

<Vicki> clear

Work for this Week and Survey

Brent: lots in prep for this week's survey
... WCAG-EM Report Tool
... Planning resource name
... Planning - initiate pages
... getting started tips
... and a reminder re Quikref that is out for public review
... and contact Shadi if you'd like to review the Showcase material
... still deciding if we'll meet next week - 50:50 at this stage

Brent: anything else to raise this week?

<davidberman> I don't have anything to announce or bring up.

Eric: EO can comment on Quickref during public comment period, but will also get a chance to review the comments and make additional comment

Brent: yes, EO gets another pass
... Ok - that's it for this week
... thanks for all your input today (and in the surveys)