<Brent> Scribe: Sharron
trackbot, start meeting
<trackbot> Meeting: Education and Outreach Working Group Teleconference
<trackbot> Date: 26 July 2019
<shawn> AHG survey results https://www.w3.org/2002/09/wbs/35532/EO-2019-F2F-Input/results#xahg19
<estella> I just got the information that in 2020 we will held the TVX conference "https://www.i2cat.net/i2cat-host-acm-tvx-2020/" as a proposal for a conference in Europe
<scribe> Chair: Brent
<scribe> Scribe: Sharron
<shadi> estella looks interesting! particularly for APA WG
Shadi: Shadi we have outlines, am
in discussion with video production companies. Soon will have
drafts of the scripts for these short pieces and there is an
issue for group consideration.
... there are several moving parts and so as yet is let
specific until I get some input to help set direction. The
amount of videos - 5 to intro eval resources, and then 10 sub
videos for the EasyChecks, less than a minute each.
... so even though 15-20 minutes of total time, it requires
more budget to make a number of small pieces than we had
anticipated. Options:
<yatil> Agenda link for reference: https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#26_July_Agenda
Shadi: we could explore doing the
top 5 as animations (and there are many levels of animation to
consider)
... the other 10 could be in another style, wha tis called
"screencasts" that show the process by capturing the browser
display. It could bring down the price a bit but would result
in two different styles.
<yatil> +1 screencasts for EasyChecks sounds right for me
Shadi: another option is to use a
person speaking about the topic and then very simple
illustrations would appear. That would lower the cost and make
the style consistent among all.
... or we could reduce the number of videos altogether.
... another option would be to go forward as planned, spend a
largr proportion of the budget on the eval resources and have
less for future projects.
<Laura> +1
<estella> +1 screencasts for EasyChecks
<Vicki> Option 1 sounds good with screencasts for Easychecks
Brent: The idea of the screencasts is the best, most effective way to tell the story in any case. A quick view intro of how to do the check.
<estella> +1 to Brent comments
Laura: I support that as well.
<Lewis> +1 to screencast on easy checks
KrisAnne: I like the idea of screen casts as well over animations
<Howard> +1 for screencasts from EasyChecks
Shadi: Great, this does help me.
If you know anyone who does this. It is funded by a European
sponsor so it must be someone who works internationally.
... this is what I need, survey with the scripts will be coming
soon.
<Vicki> Shadi in hollywood
Brent: Thanks Shadi for this good work and providing the options.
<shawn> https://wai-media-guide.netlify.com/design-develop/media/
<shawn> historu of updates https://www.w3.org/WAI/EO/wiki/Accessible_Media_Resource#History
Shawn: Thanks for those who have provided review. Aware that there is a history of updates linked here in teh minutes. People look at different times, those who checked early may want to review what has changed more recently. Will keep updating as significant changes are made.
<shawn> for EOWG comment https://github.com/w3c/wai-media-guide/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+EOWG+comment%22
Shawn: There have been many
issues that we can resolve as editors but need a few more
comments on some of them
... please review and add to these as you have input and
interest. Will discuss
<shawn> https://github.com/w3c/wai-media-guide/issues/81
<shawn> example https://wai-media-guide.netlify.com/design-develop/media/planning/#--video-checklists
Shawn: It is issue #81. Wanted to differentiate, but depending on how people percive they may expect ti to be clickable.
<shadi> +1 to laura
Laura: Curious about having the check box being not clickable has potetnial for confusing people
Sharron: +1
<estella> +1
<estella> Having both might be distracting
Shawn: (without editor hat) I agree that if the really look like a check box it would be a problem but the color and presentaiton makes it not look that way to me.
Laura: You could fill them in, to
be solid and bit smaller.
... like a square bullet
<Zakim> dmontalvo, you wanted to say do we want to functionally implement filters on that page? If no, I would use plain bullets.
<Howard> +1 to square bullet
Daniel: Looking at the functional aspect, do we want to use filters here? If not, just use plain bullets. As a screen reader user, I have no issues with how it is now.
<Vicki> +1 to bullets
Vicki: You have the problem of looking very like checkboxes and learned behavior realted to it.
Shadi: You have so many great icons and graphics on a WAI page, so letting this one go should not be too bad Maybe use an arrow or something.
<Brent> How do people feel about a checkmark or tick? Instead of an open box
Estella: Agree with Shadi, great that you have been able to integrate so many visual aspects. But having both checkboxes and bullets si quite confuisng.
<yatil> BTW, this would be our normal second level bullet: https://dsc.cloud/yatil/Screenshot-2019-07-26-at-15.05.43
Shawn: If we just replaced the checkboxes with bullets as in the above paragraph there wuld not be enough distinction, is that what you are saying?
Estella: yes
Shawn: Encourage people to look throogh the request for examples and share them. I will keep you posted on any other changes.
<shawn> Terminology - Audio Description / Video Description / Described Video https://github.com/w3c/wai-media-guide/issues/75
Shawn: more FYIs, places whare
the changes are documented for your review
... terminology
... can skim that section to see if you ahve quetions but
mostly just to get in sync on the background.
... questions or comments?
Laura: Is there a distinction between audio description and video description?
Shawn: They are interchangable, they mean the same thing
Estella: There are instances of live description which are not for recorded media, audio description was used for that.
<shawn> There are also live descriptions of visual information - way before videos..
<shawn> Level of detail to include and links to outside resources: https://github.com/w3c/wai-media-guide/issues/30
Shawn: Updated issue #30 with
real check boxes
... Also spoke about images, don't have the revisions yet, hope
to have it by next time.
Brent: Thans Shawn, any
addiitonal questions or comments on this topic?
... thanks for all the work on that really looking good.
Brent: We have spoken about this several times at F2F meetings and in meetings. We have a couple of things that could be reached out about:
<shawn> quick ref https://www.w3.org/WAI/EO/wiki/Promoting_Quick_Ref#July_draft_tweet
Shawn: The first one is the QuickRef, welcome your input on the tweet and support for the outreach.
<Vicki> +1 on tweet
<Lewis> +1
<shadi> +1 laura
<estella> +1 Laura
Laura: The full title is long in the tweet, can it be shortened?
<yatil> [ Take a look at the updated Web Content Accessibility Guidelines (WCAG) Quick Reference, a way to tailor the WCAG 2 success criteria to your specific project. Please Retweet! #a11y #wcag]
Howard: Would be better to say what teh updates are
Shawn: Many have been unaware of it entirely so may not need to get into detail
<yatil> [ The Web Content Accessibility Guidelines (WCAG) Quick Reference, a way to tailor the WCAG 2 success criteria to your specific project, has been updated to include the latest techniques. It is also loads quicker now and features improved scrolling. Please Retweet! #a11y #wcag ]
Eric: A few conceptual changes to interface, some performance changes so it may not be useful to get in the weeds of these specific changes
<Brent> I like it except "loads". to much slang
<estella> I like it better
Shawn: I like this approach, does anyone have thoughts about the fact that people did not even know about it a t all.
<Vicki> tut tut @yatil... you have to tell your friends
Laura: I agree with Brent in IRC, but would leave out the reference to loading since it talks about a past problem.
Howard: 2.1 is a nice hook would think it could be included and if you want less text in the tweet could have a link to more detail about what the changes were.
<shawn> outreach on translations https://www.w3.org/WAI/EO/wiki/Promoting_WAI_Translations#July_draft_tweet
Shawn: Outreach on translation is
here
... the goal is to get people who know those languages to share
those tweets.
<Vicki> Impressive
Shawn: Would like to be shared
among Spanish organziations that serve people with disabilities
etc.
... Spanish is the first language for which we have enough
translated resources and navigation to think about doing
serious outreach.
<Laura> +1 I like it.
Shawn: Any further comments or
questions?
... thanks all.
Brent: We will be sending out the final text and ask for your support in getting out the word.
Brent: We will be adding this resource and Hidde is the editor. We discussed in the planning meeting now have a requirements doc.
<Brent> https://github.com/w3c/wai-authoring-tools/wiki/Requirements-Analysis:-Authoring-Tools-List
<Vicki> https://github.com/w3c/wai-authoring-tools/wiki/Requirements-Analysis:-Authoring-Tools-List
Shadi: We have a list of eval tools and we made an attempt several years ago to do the same with authoring tools. We found two challenges - which filters can we use (ATAG? too complex? Simpler?) and how to keep the list maintained.
Brent: You can follow along as we
review the requirements doc and next week we will discuss in
more detail.
... want to be sure we define clearly and specifically enought
to avoid scope creep and don't leave out essential
elements.
Shadi: We want to stay vendor neutral while encouraging authoring tool makers to meet requirements. Will have a disclaimer "The info is provided by the vendor, not WAI" and are considering the broad array of tools that might be perceived as an authofring tool. The way we ask questions can skew the outcomes. Want to be sure we have the right kind of clarifications as we collect info about specific
products.
Brent: And there may be risks we
are not aware of.
... what are your high level reactions? And you will have time
for more considered response as you review during the week.
Please make the time to do that.
Shadi: The evaluation tools list
resource needs updating and Eric has shared the code so they
are aligned and will be more integrated into the style of the
current website.
... any reactions to the new reaource?
Estella: How do you want us to provide the information?
Brent: Will add to work for this
week and ask everyone to review and keep notes for a meeting
next week.
... following the meeting, we will post a weekly survey and
invite comments there.
<shadi> Hidde de Vries <hidde@w3.org>
Shadi: Right now we have no specific questions but are asking for high level conceptual feedback. You can use GitHub if you wish to post comments as issues. Also will be, as Brent said, a follw-up survey, and can send direct feedback to Hidde. This is a good time to provide input.Will eventually have mockups but for now it is conceptual.
Estella: This seems a very technical resource and process. I do not have the technical background so I want to be sure I understand how you want comments.
Brent: There is a current survey open, will want that completed by Tuesday. Another one for 2020 face to face meetings
<Vicki> Brent: please add a European destination to the survey. There are already several options on the F2F page.
Brent: will be updates to W4TW and appreciate your attention and active participation.
Laura: Wanted to let Shadi know that we are doing a presentation and will use Shadi's video to introduce higher management to the issue.
<shadi> great to hear!
Laura: I watched it again this morning and it hits all the right notes, happy to be able to use it.
<estella> +1 to Vicky
Vicki: Can we add a European F2F meeting?
Brent: Are you saying add a destination and a date?
<yatil> ICCHP 2020 is happening, too
Shadi: And Estella added a suggestion, and it is always good to know the organizers.
<shadi> +1 estella
Estella: And the conference itself may be of interest as well.
<Vicki> Sold
<Vicki> There is always time for a siesta
<shadi> +1 vicki
Brent: Sounds good, any other new
business?
... thanks for sharing the way you are using the resources.
Laura: Putting the slides together, I happened on the video and decided it was a great encapsulation of what I wanted to say.
<Vicki> Bon weekend!
Brent: Thanks all, have a good weekend.
trackbot, end meeting
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s|Agenda link for reference: https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#Upcoming_Teleconferences#26_July_Agenda|| Succeeded: s|Agenda link for reference: https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#26_July_Agenda|| Succeeded: s/si/is/ Succeeded: s/.terminaology/terminology/ Succeeded: s/quetions/questions/ Succeeded: s/information/information - way before videos./ Succeeded: s/chack/check/ Succeeded: s/Spansih/Spanish/ Succeeded: s/new/current/ Succeeded: s/Eric will share the code/Eric has shared the code/ Default Present: Vicki, Brent, Lewis, Sharron, Shadi, Eric, Howard, Laura, Daniel, Estella, Shawn Present: Vicki Brent Lewis Sharron Shadi Eric Howard Laura Daniel Estella Shawn Regrets: Amanda Denis Sylvie Vicki Andrew Found Scribe: Sharron Inferring ScribeNick: Sharron Found Scribe: Sharron Inferring ScribeNick: Sharron Found Date: 26 Jul 2019 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]