Introductions

Participants introduce selves. Vivienne brought two guests: Nayef Alawahdi and Muhammad Saleem from Kuwait. Muhammad works for GreenTech and Nayef for CITRA (a state regulator) Muhammed: Major problem is in the Mid-East there is little awareness, need to know more about W3C, looking for more speakers to invite, awareness increasing, and more participation in W3C.

Vivienne: GreenTech and W3C are collaborating to translate into Arabic WCAG and other WAI docs

Tutorial Update

Eric: Created around one and half years ago. They are in transitional layout. Web developer resources, easy way to approach the topic, exposed to best practices and code examples.
... have received feedback, bugs, editorial, request for new tutorials.

Vivienne: Is there a list of the new ones that are planned?

Eric: There is a wish list, nothing has been prioritized.
... many requests for new topics, and these are among the most often accessed materials. Challenges around editorial language, approach, still need to consider quantity of content.
... Next steps include adding new method for example display
... add WCAG 2.1 SCs
... narrow scope of new tutorials
... prioritize

Brent: Of the next steps, which are the ones that *you* would do and which need EO input?

Amanda: Scoping, prioritization will require group input.

Eric: When we receive input from lists, email, or even social media, I log and collect it in the GitHub. Others should feel free to do the same so we keep track and have a good idea of what the community wants and allow group input for priorities.
... also need to determine how detailed we want examples to be. Must maintain a consistent approach.

Amanda: I prefer the high level approach. If there is so much detail it is a time sink. Rather have high level info in the tutorials and more topics than to have very detailed info on fewer.

Shadi: And making sure that people understand there is a certain level of pre-requisites. (Must know HTML for example)

Stephane: "Make sure your developer kit allows you to do... this and such" rather than tease out detail of each one.

Amanda: Do we need a disclaimer?

Eric:any input on new tutorials, please let me know either through email, twitter or github issues

Sharron: we need to determine if it's current or future work

Brent: we have the tutorials in Current Work, we should make sure it includes the next steps and we can prioritize

Shadi: The 2.1 addition will ripple back through current work

Brent: As you add to current work, please try to add accountability - will Eric do the item or will you need group input?

Stephane: May we consider extending the review period?
... you put things out on Friday and only have a few days to respond. I almost always need more time.

Shadi: People like longer review times in order to have a heads up to schedule time.
... resource editors must plan ahead to give the notice to the group and let them know what is coming down the pipeline.

WAI-Guide Project Introduction

Shadi: New EC Funded grant to Authoritative Implementation Guidance and International Cooperation to Support Training, Awareness...and lots more.
... focus on three main areas 1. Implementation and training guidance 2. Accelerate Support for Accessible Authoring 3. Identify Gaps in Accessibility Standardization

<yatil> WAI-GUIDE: https://www.w3.org/WAI/about/projects/wai-guide/

Shadi: for the first item, a major task is to revise and expand Techniques and Understanding documents. A UI and information architecture task.
... modify the presentation, add content.

KrisAnne: This is something that is inconsistent, some are well constructed, others not so much

Vivienne: And Failures missing in many.

Shadi: First priority is to update and streamline the way they are presented, the information architecture. Mainly this will be within the AG. Will likely need input and coordination with EO.
... also funded to expand the content, but looking at accessibility in immersive environments, webVR, WoT, need to be addressed technically
... will be coordinated across WGs including Silver, AG, EO, APA.
... mostly under AG with input from other groups as needed. APA=Accessible Platform Architecture
... next two areas will be more familiar to EO, videos along the lines of Perspectives video. Will brainstorm on that this afternoon. It is a three year project, so we want to be sure we get the momentum going.
... these will be the foundation for the curriculum development, training resources
... we have the WAI training resource suite, will be updated, role based, etc. There are so many accessibility training courses out there but have a lot of variation in accuracy and harmonization is needed. So we want to provide authoritative, flexible building blocks that can be modified and used in various contexts.
... a use case is in a University setting where a computer science professor may want to include but not have the expertise. Another is to base certifications on these materials so they have the same content.

Vivienne: Are you looking at IAAP certifications?

Shadi: Yes we are speaking with them.
... it needs to be scalable, translatable, flexible enough to successfully place in different contexts.
... build the core building blocks before any courses are created.

KrisAnne: I would like to see authoritative, reliable resources that give our developers something to actually rely on.

Amanda: Will we provide a W3C tick that validates that the pillars have been included?

Shadi: Expect to refer back to the foundational resources maintained by WAI so that we control the quality and current relevance. Curricula will be a packaging of existing WAI resources.
... much of the second task will fall to EO. Since Authoring Tools WG was closed, it is uncertain where we will do the third area of work. Some of it will be outreach to authoring tool community. One task will be to reach out and re-engage the community at conference and events.
... could fit under broader task of outreach of EO
... Develop industry specific tooling guidance is another task. ATAG as it is now, is very broad. From educational materials to social media, threshold of support is very different. Understanding of how and why these differences exist and how to navigate among what the purpose is and what accessibility provision is appropriate.
... helping people understand what they need to provide within their own sector and provide specific guidance. May be good to do in EO and could include or relate to the AccessLearn project.
... Finally in this area, we are looking to develop, in the same way we provide the guidance to Evaluation Tools, we would (in year 2 or so) provide guidance for Authoring Tools. Would develop its own taxonomy and approach.

(...discussion...)

Stephane: There are pain points here for reliability and maintenance.

Shadi: We have learned a bit about how to address those issues with the Evaluation Tools list. May want to develop a common approach.

Vivienne: Seems like a major challenge is keeping things current. Need people to provide reliable information and check links, etc.

Shadi: Have had good experience with volunteers.
... Finally one of the parts of this project is to identify gaps, keep an eye on emerging tech, and harmonization of standards.

Vivienne: I will send the Kuwait Framework around to anyone who wants to see it.

Shadi: In my view we need to sharpen the way that user needs are communicated to other WGs. That may be a good task for EO.
... 3 job openings

[Coffee Break]

Web Accessibility Curricula

<shadi> https://www.w3.org/WAI/teach-advocate/accessibility-training/

Shadi: We need to have thought this through and be ready to hit the ground running. I think the existing Web Accessibility Training Suite may be the basis for the curriculum work.

<yatil> https://www.w3.org/WAI/teach-advocate/accessibility-training/

<yatil> https://www.w3.org/WAI/teach-advocate/accessibility-training/topics/

Shadi: reviews the existing training module outlines. This basic approach is likely to be what we are looking for. As it is now, they are thematically grouped.

Sharron: When Andrew created the training resources framework and I supported it, we recognized that we did not have all the detail needed to build out a full course. It was more of a framework and approach to help trainers think about what they might want to include for presentation, courses or different length and depth.
... we made outlines for some topics and links to the resources that were completed. We have many more educational resources now, and can fill in some gaps and identify others. Can be useful to provide a response to people who say - we want to teach about accessibility, what do we teach?

Shadi: Will hire a curriculum specialist to review the existing material, build a modularized set of lessons, and balance between materials that are too specific vs those that may be too loosely defined, vague.
... also must consider, what are trying to teach people? If the role is developer, do we have to teach them HTML? To what degree must we include the empathy, human rights aspect and so forth? What level of understanding do we expect them to show up with?

Amanda: What about different levels - beginner, intermediate?

Vivienne: Pre-reading is another option.

Shadi: The point is we will need to define entry level and exit level. Will be an on-going discussion.

Stephane: agree, it's not the point of the curriculum to teach basic language stuff - links are there for this purpose

Eric: Must differentiate between what we need to teach the teachers and what we want them to teach others. Will need an intro to Accessibility that is a cornerstone to raise awareness.
... another thing is the fact that we have the resources that can support a basic curriculum. What parts of tutorials, EasyChecks, etc can be integrated?

Vivienne: What is the starting point? Do they have HTML? CSS? Must understand basic structure stuff to know where to insert accessibility.

<yatil> [An introduction of HTML and CSS for Web Accessibility - Vivienne] - sounds very interesting :-)

Shadi: One of the key discussions will be definition of scope - both to teach the teachers and what to expect them to communicate to students.

Stephane: The same teacher may read through and leave out certain parts based on teaching of developers vs designers.

Shadi: Yes, and in the ongoing A11y Matrix work, we have looked at 4 areas - Design Roles, Development Roles, Testing Roles, Management Roles - all with various content to learn.

Vivienne: If you want to include accessibility within a college course in the computer science department you can assume HTML competence.

Shadi: As an idea, we have a complementary option to make a video for how to use the resource, how to put the modules together.

Sylvie: We had the presentation notes to presenters that explained what to say, provision of guidance for how to use.

Shadi: Yes but this will be packaged in these four roles, some portable across, some even more flexible on how to mix, match, combine to use the entire resource. Making outlines, and the video guide.

Eric: What do you see the final deliverable to be?

Shadi: Something similar to the existing framework, the core part will be a collection of topics mapped to roles.
... a definition of entry points and what the exit looks like as well. Outlines of workshops, presentations, how to combine resources and an overview of how to use.
... I do not see as much the provision of slide decks and actual training materials .

Vivienne: I see the organization of the structure in terms of sticky notes where we cover the wall with modules that we have, how they relate to the different roles, what the gaps are, how to address the gaps.

Shadi: Yes, the first role will be the most difficult to organize and those that follow will benefit from the effort.

Eric: We must be transparent when we do not fill the gap for specific topics.

KrisAnne: And invite the community to fill the gap by contributing their own expertise.

Shadi: Need clear criteria for linking out however, do not want to just do so arbitrarily.

Sharron: Maybe the model of the Evaluation Tools list?

Shadi: Yes and the connection to the A11y Roles Matrix is a useful thing to consider as well.

Amanda: Need to look at these roles with some degree of granularity - their tasks are so very different.

Shadi: Yes I grant you the difference with content creators, but what else may need to be granular?

MaryJo: It depends on the size of the project. There are some projects where all designer roles listed - user research, UX design, Visual design, content - all have separate roles, little crossover. Other smaller projects have one person doing all roles.

Brent: There may be a reason for some crossover if nothing else simply to communicate well.

Shadi: If we agree on the need for granularity, do we have WAI resources to meet that need? If we do not, if we remain high level, is the general approach of no value at all?

Vivienne: Maybe do a pick and choose like Lynda.com

Brent: Maybe part of the follow-up for the group working on the roles, they will help define what resources will help with various granular levels.

Stephane: And the teacher will be able to determine what resources (which modules) will be of most relevance to thier role.

Eric: General design modules for "design" and specialized ones for the more granular roles will give teachers, trainers, and students the most flexibility.

[Lunch Break]

Meet with ARIA

Eric: Meant to coordinate beteen the two groups since we both have educational resources and sync up examples - will do quick round of introductions.

<shawn> And THANKS to Knowbility for Fellowship of Eric!

Matt: Background on what Authoring practices does and what our goals are to align. Since ARIA became a standard, it has yet to include normative standards for AT. Inconsistancies resulted in how aria is expressed in browsers and AT. Want ARIA to be as reliably, robustly implemented across devices. First was to revise APG and update authoring proactices with examples of ways to use, intent, etc.
... one important thing is that there is more than one way to correctly implement.However there should be canonical methods that always work.
... step 1, let's get this series out there. Have 29 roles, some 60 examples. feel pretty close to having a robust set of examples of all ARIA widget roles, 37 of 48 states and propoerties used within the examples.
... have put in place some regression testing for most of the examples. We are at a point where the examples can be regarded as, if not perfect, at least reliable. Always welcome community feedback. New repository is ARIA-AT - now empty but will build the framework, methodologies, to assess each pattern and indicate performance in various browser/AT combos. Want to develop vendor neutral way to measure and report. The goal there is to get consistant, robust way to render across all these.
... will expand to mobile and more AT over time. We have had examples getting more visibility and then noticing difference between our examples and how it is presented in tutorials.
... want to get aligned and maybe even have tutorials be able to build the examples in the ARIA resource.

Eric: One of the first steps is to come up with a system that works for both groups to set tutorials. Currently the tutorials do not aspire to be the be all and end all of providing solutions. When things are given in the ARIA practices guide, the tutorial will put it in context of the holistic view - where ARIA guide is focused, tutorials are more generalized along with design considerations, etc.

Michel: Do you feel the APG examples are badly designed - or?

Eric: Not at all, only that they have different purposes.

Matt: As we look at plans for the coming year, may be ways to look at issues backlogs and see where they overlap. Carousel for example?
... next year our goals will be to finish off the guidance covering everything from placeholders to aria describedby, etc.
... bottom line is to do some comparison of open issues and coordinate work.

Brent: Keep tabs on upcoming work, ideas around tutorials, and sync up to take advantage of shared effort.

Matt: Plan our APG work through milestones, Release 3 is December of this year
... could structure June release, #4 (planning in January) to include EO goals as well.

Sharron: What are EO goals?

Eric: If we have common points of guidance, we can (first half of year) look at where we are, what we have, is it synced up to APG, if not get aligned. then in the 2nd half of the year, we could get clarity from APG about their roadmap and see how EO can contribute.

Matt: may be some issues in the Guide where rather than try to explain something, send them off the WAI tutorial. Want it to be a very consumable resource for those who write code.

Shadi: If your audience is broad, how well is the current fromat (spec style) serving that audience? As an integrated, cross linked format might it serve the audience more effectively?

James: Interested in exploring that.

Michel: There is wide interest in having the document in a more easily consumable format.

Matt: I want to finish by the end of next year have APG 1.1
... complete and then when we have this comprehensive resource finished, maybe in spring of 2020 look at changing the format.

James: Content is good, the editorial change could be relatively easy to do.

Shadi: But would caution against underestimating. There is an AG effort, beginning in January 2019 to re-format the Techniques and Understanding documents for WCAG. That would may be replicable, while content remains completely owned by ARIA-AG

Eric: Yes we see AG not happy with having support docs in TR and as we re-format may be easily used as a template, stepping stones to more easily used material.

Matt: Yes we have old examples, buggy code, floating around in TR space. Less than ideal.

Eric: Using the WAI website, each section is a GitHub project, could be linked up automatically

Matt: and as we build the published resource, our links can be maintained as we publish.

Eric: Also could look at EO guidance that we have to identify gaps and need for clarification about when to use which document, which guidance resource. If you see gaps on our side that need revision.

Matt: For the next step, shall we schedule a planning meeting to look at which items need review, how to approach, how to coordinate.

Sharron: In January?

<shawn> EOWG Planning meetings: Wednesdays 9:00E. EOWG meetings alternating Fridays @ 8:30amET and Thursdays @ 6:00pmET (Friday morning Asia-Pacific)

<scribe> ACTION: EricE to set date with Matt to meet in January.

<trackbot> Created ACTION-389 - Set date with matt to meet in january. [on Eric Eggert - due 2018-10-29].

Industry-specific guidance

<shawn> Shawn: broader that WAI-Guide

Shawn: AccessLearn Community Group, focused on accessibly of online learning. Been working for a couple of years about materials they would like to see added to EO materials in support of their goals.
... they - David Sloan and Mary Zeigler - believe it would be useful for EO. As well,the digital publishing will have similar requests.
... may be related to WAI-Guide
... basically EO has considered providing industry specific guidance. For example online learning, digital publishing and WAI Guide is considering the same for authoring tools.

Shadi: We want to provide guidance for how WAI resources support these various industries. Do we want a portal, a set of resources, etc?

Shawn: We could review the requirements of AccessLearn and see if this is how we want to approach these different industry sectors.

<shawn> Accessible Online Learning Resources - Requirements Analysis https://github.com/w3c/wai-eo-online-learning/wiki/Requirements-Analysis

Brent: The proposal is to broaden what we had thought to provide Accesslearn into a portal that sends users down a specific pathway based on their interest.

Shawn: Not one portal with various pathways but three different portals.

Shadi: More of a landing page than a portal

<shawn> +1 for not "portal" by something more like "landing page"

Shadi: the idea is how to package so that someone has a clear set of resources that are relevant to them and the task they are seeking to accomplish.

Amanda: Does AccessLearn have these resources?

Shawn: No not yet, they have polled their community and identified what they need. We have suggested that they provide the overview in the language that will make sense to their industry and then point them to specific resources that will then make sense to them in context.

Stephane: this resonates well with what we were saying this morning with profile-specific entry and information.

<shawn> Accessible Online Learning Resources - Requirements Analysis https://github.com/w3c/wai-eo-online-learning/wiki/Requirements-Analysis

Sharron: The use cases are super helpful to help understand their goals.

<shawn> ACTION: Shawn or others request Portal Page -> Landing Page in https://github.com/w3c/wai-eo-online-learning/wiki/Requirements-Analysis

<trackbot> Created ACTION-390 - Or others request portal page -> landing page in https://github.com/w3c/wai-eo-online-learning/wiki/requirements-analysis [on Shawn Henry - due 2018-10-29].

Brent: Creating these different landing pages would mean we would create requirements to match each industry sector. Are we at a place to ask the group if we want to do this? We know we will move forward with the AccessLearn since they have done the background, Community Group work, yes?

Shawn: I think we are now bringing this to EO for approval specifically for the AccessLearn project.
... do we want to do that now?

Eric: For me, it looks like those are applications of things we already have. The physics diagram is similar to the financial graph description in the tutorials.
... need to make sure we have common guidance that can be applied more generally.

Sharron: Or that AccessLearn is able to create examples that are missing.

<Stephane> Yeah but maybe we don't talk in a lingua that can be understood by teaching people - maybe their original need was: how to speak in the language of the target audience, i.e. Learning community?

Shadi: There has to be some context provided before you link to an example that is not specific enough. Set them up that even though this is financial data making the graph, if given context the physics teacher can extrapolate.

<Stephane> Sharron: We have to find what we already have and build some context around it, which is what the CG is willing to create.

Eric: Yes we can bridge that gap with putting them in context.

KrisAnne: Seems like they are asking us to take all the great information we have and make it easier for them to find.

Brent: Another aspect was to fill in gaps of info that we don't yet have.

KrisAnne: Can we find harmony so that they can exisit together.
... want to avoid being disjointed or too much work.

Brent: We keep talking about how to provide guidance to specific sectors but the project you spoke about this morning Shadi is not meant to be a page called "WAI-Guide" is it?

Shadi: We do have an aspect of it that is specific guidance for the authoring tool industry.
... what we are speaking of now is meant to explain a broad spectrum of WAI resources through a specific lens - like online learning
... this morning we spoke about specific authoring tools guidance

Shawn: We do have a roles section and this could fit there. Do we envision that there are two, possibly three, sectors. If this is the limit, it could fit into the roles section. If we brainstorm and come up with 20, it could be problematic.

Sharron: And I like to work with them, since they have done all we asked them to do in terms of building a Community Group, use cases, requirements, etc

<Stephane> +1 for adding it into the roles section

<shawn> cross-linked!

Amanda: Do we even have the resources to meet these requirements? Online learning would provide very different resources than accessibility training and advocacy.

Eric: Having a resource like that is something that we can trust to our content providers, editors to make it work and it seems very useful to me.

<shawn> [ Shawn thinks they would be lead editor ]

<shawn> [ +1 Sharron also have to have someone in EOWG to help ]

Shawn: There is another part to this. For the most part they wanted the landing page and also had a few suggestions of things to add to our resources. There are four specific things.

Vicki: Are we in danger of being so repetitive - to provide existing content again?
... good to provide specific inofrmation to online learning tools. Rather than also recapping the same old intro information.

KrisAnne: New lipstick, same pig.

Amanda: But there are things that crossover - general accessibility, transcripts. The key is to talk their language on the landing page, set the tone and prepare them for the fact they will find examples that apply to them in another context.
... like the idea, I think we should have a specific landing page and we do need to create materials that are focused and relevant to that audience.

<shawn> [ although we already have one user story on online learning (I think) -- they're asking for several more ]

Brent: We have consensus in the group in this room but should open out to entire group?

<Stephane> https://www.w3.org/WAI/people-use-web/user-stories/#classroomstudent

Shawn: The question will be do we move forward with their proposal and what questions, comments, changes do we have for them.

<Stephane> https://www.w3.org/WAI/people-use-web/user-stories/#onlinestudent sorry

Eric: Again, we should start small and focused and then consider how to maintain and update. Give editors latitude for how/when to expand.

Stephane: Several questions about whether to change and add use cases, build another page, what pages for other resources, how to put in content editor stream, etc

<shawn> well, actually you did! ;)

<shawn> Shawn: +1 to stephane. We need to think about the additions to other resources. e..g, we potentially have multiple additional stories covering diffrent areas: onlinelelearning, digiPub, mobile...

<shawn> yes please

Video-based resources

Shadi: What can we do to move accessibility forward? What would you like to see, to have, a video based resource? Some ideas - Perspective videos were to make accessibility more tangible, understandable. Others could be digging deeper into a tutorial or something, how to use WAI resources, how to get around, find what you need.
... a short video based demo of the BAD, how to use as a teacher, as a student, as a tester, as a tutorial on its own.
... easy to base an hour long lecture on the BAD

KrisAnne: I have shown the difference between a good and badly coded website on screen reader. Or use a pool noodle to let people see what its like looking with magnification?

Shadi: Since we can build resources, it does not have to be just a talking head, it can be actual tangible training that someone can watch and learn from.

<shawn> [ Shawn is biased, and agrees that low vision issues lend themselves to videos to explain! e.g., reflow ]

<shawn> +1 for Easy Checks screencasts for many of the "To check..." sections. <https://www.w3.org/WAI/EO/wiki/Easy_Checks_Next_Gen>

Chris: One of the biggest we still have is awareness in general, if we can use a video to highlight that.

MaryJo: Agree also EasyChacks

Amanda: Step by step through easychecks

Chris: So many are not at the point to talk about tools since they don't even begin to comprehend the problem. Too often, it is a systemic problem that people have no idea that it exists.

Brent: Showing the tools that people use, like my brother in law.
... a tech company and yet has such a lack of knowledge does not even know there is a screen reader. Maybe jsut videos showing those.

Sharron: Lots of those out there.

Stephane: Show a person not able to use, doing the work, then can use it well.

MaryJo: Designers get the idea that accessibility is so hard. But when you think about while you are planning, testing, coding, testing, etc. have finally gotten most of our designers to "get" it.

Stephane: When I do a survey for good examples, they are hard to find.

Shadi: Regardless of video or not, it is hard to do at W3C to say - gallery of accessible web sites. Very difficult to make statements that are not vendor neutral.

Stephane: Basic examples in the video could be useful.

Eric:What about "EasyChecks the Video Course," Base instruction on Accessibility Principles with step by step developer guidance, Need as well to add WCAG 2.1 to tutorials.

Shawn: BAD update has pending open issues, not yet resolved.

<Stephane> "EasyChecks the Video Course" I love the title :)

Eric: Do we want to create our own bookmarklets for EasyChecks?

<Stephane> Note on bookmarklets: more and more problematic as CORS security is being rolled out - we'd have to move towards web extensions along the way (possible maintenance overhead)

Eric: also general accessibility principles rather than SC level guidance. Helps developers keep the bigger picture in mind. Must have a look at what we produce: have good content and have content that people are searching for. I think they are searching for courses.

Amanda: It goes to the point that Chris was making. I always must explain what it is to be an accessibility consultant. I need a way to explain in 30 seconds or less. Easily point them to something that is quick, clever, and easy to digest. Quick, short, easy to understand.

KrisAnne: Can we gear it to the Business case - look, our SEO improved, we gained market share, we avoided legal risk.

Brent: Get clips from the people who provided the BizCase studies and put it on video, audio.

Amanda: Great way to scream from the rooftops.

<Chris> https://www.youtube.com/watch?v=Gv1aDEFlXq8

<Zakim> yatil, you wanted to say googles videos

Eric: I can imagine a short video that is flashy and tells the business case and then links to the narrative version.

Vicki: I like 5 reasons why to be accessible (bizcase); the cross disability awareness; tutorials

Sharron: How to use the WAI site

Vicki: May not be useful, who would use it?

Amanda: Could play up the roles to point people in the right direction.

<shawn> [ sounds like a recurring high-level issue is the life-time / outdatedness of videos ]

Shadi: Maybe role based, customization, the explainers,

<shawn> +1 for video of how to use the quickref

<Stephane> +1

Brent: Some complex resources like the policies or quick ref could be useful to have a way to show how to use.

Brent: a bit about inclusive user testing. Some could benefit from a short video at the top, how to use it.

Stephane: I am a visual designer, never knew it was for me, what I learned.

Amanda: Have some highlights of specific aspects that could be of great importance.

Eric: Google has short 15 minute accessibility casts that go into specific topics like audits, focus management, etc.
... stepping back from our resources and talking about principles may be better than how to navigate or use specific resources.
... things on the WAI site you didn't know were there, highlight some of the more obscure items, etc.

KrisAnne: Not how to use the policies page but instead what it is for and the fact that it exists at all.
... need to market ourselves, come back to WAI for support for your practice. Love to see a video on retro-fitting vs baking accessibility in.

Stephane: +1 on "marketing ourselves": I didn't know there were that many great resources before joining EO

Chris: Might be more appropriate for the outreach discussion. We don't have a Twitter account do we?

Sharron: We do.

<shawn> https://twitter.com/w3c_wai

Chris: How often do we use it? Need more where we go to people with our stuff rather than expecting them to come to us.

Eric: Could do 10 second clips of the perspective videos.

<steve> https://twitter.com/w3c_wai

<shawn> youtube channel https://www.youtube.com/channel/UCU6ljj3m1fglIPjSjs2DpRA (850 subscribers)

Chris: There is no Twitter account referenced on the web page.
... maybe should be on the agenda each week, a standing discussion each meeting.

Brent: What is our standard procedure for tweeting?

Amanda: What are the constraints? restrictions?

Eric: We cannot endorse, must stay vendor neutral. May be able to retweet someone else's announcements.

<shawn> +1 to Shadi that the basic limitation is resources

Amanda: need an internal policy before we can mount a campaign.

<Stephane> +1 we'd risk losing relevance: I follow w3c_wai for w3c wai info not other retweets

Shawn: A big thing to be aware of is signal to noise ratio. Recently was an announcement list that says you can only get announcements rather than all the IG conversations (noise). Would like to keep it that way.

Chris: We are in no danger of crossing that threshold

Sharron: +1

<shawn> Shawn: +1 that we can do much more tweeting without getting too noisy

Stephane: You lose relevance when you relay information about others rather than your own information.

Shadi: We talk about videos, I wonder if we are trying to use video to solve a broader problem.
... I heard three categories, 1. making accessibility more understandable; 2. more technical detail like how to use BAD or easychecks, role specific videos; 3. help with the WAI site, even specific complex resources

MaryJo: There is another aspect of people just being unaware of our work, WAI work in general, maybe some ads?

KrisAnne: Not a bad idea

<Stephane> Ad as viral communication? re: BBC4's "We're the supehumans"

Brent: To bring the awareness from outside the existing community.

Shawn: In addition to or instead of ad in places like Business Week Kris Anne mentioned, what about getting more coverage through articles that mention accessibility & our resources.

Amanda: Have used that strategy, an article based on event that provides exposure without paying for an ad.
... might take more resources than social media

Eric: I always get accessibility articles on the web. Many times they mention resources but not the ones from WAI. I try to reply by pointing people to our stuff.

Shawn: can add as an outreach task for all of us.
... We have had outreach on our wishlist, could pump up the star power.
... as the EOWG

Brent: What about WAI talks like TED talks. Someone with a disability or someone who works in accessibility as a developer or a product lead, etc?

Shadi: I like that idea of interviews, show people and their stories.

Eric: Our website, our work is pretty faceless. No humans, no images, no dedicated passionate advocates. We could also add interviews of EOWG members and share the incredible energy I see in this room.

Eric: Business case is the first document in our resources that I like to read over and over again, including my own. It is human, it has a voice that is good to review, it speaks to me.

Sharron: We must continue to give our documents a human voice.

KrisAnne: We have to.

Eric: We can show a video of Sharron explaining how it was done.

Brent: We could also interview someone who told us the resource is great, and why it's great for them.

Brent: One of the powerful things of the perspective videos was the professionalism

Eric: True but production value is not as important as content and tone.

Shadi: Through WAI Guide, I would like us to think of these videos separately from outreach or the use of video in outreach, I encourage us to think about the video in and of itself. In addressing gaps in accessibility practice.
... like the perspectives are based on other resources, but it is its own purpose in moving our practice further. Think of it as a self-supporting resource rather than as outreach support.

Brent: Are there categories that we must steer away from?

Shadi: Yes we could not justify advertisements. But what a great opportunity to do something significant.
... people whose lives were impacted, think about what the message would be.

KrisAnne: At CSUN short videos about people who do accessibility or who are affected by it, use human stories to make the case for why it is important.

Amanda: And the point of making it international is really important. People want resources they can relate to.

<Stephane> +1 on the international stuff, translated subtitles were a very good first step

MaryJo: A day in the life of people with disabilities trying to acheive all the things that people do online.

Sharron: +1

KrisAnne: what about TED-WAI talks?

Stephane: It is now transformed into entertainment rather than education.

Eric: Meetups and small events are a good ice breakers for bringing people to WCAG, I've found.

<Stephane> ...Go to events and mention EO, it's a thing.

Amanda:I wouldn't speak to an Australian audience as I do an American audience. I just saw it in Kuwait, cultures are so different...If we're all carrying that banner, we can show it a bit more and relay ti to groups that can then relate to the activity.

Shadi: We have the opportunity to do 4 resources. I see 1. People stories, 2. something related to business case, 3. someting technical, like tutorials and talking to developers, 4. [coming]

KrisAnne:I see people who want to teach it but have never taught it so it's hard to grasp the idea of teaching it, so we can show people in their class to help other teachers understand how they can do it.

Brent:We can also do small things, like screenshot videos etc.

Shadi:Somebody is working on extreacting shots from the videos to speak more to people and reach out more...I can reuse a lot of the perspective videos to create introductions. It took a bit to prepare but the filming is not that long, it was story-boarded.

Brent: Yes, there are so many images in this video that we can clip into the site.

Eric: Getting a visual language takes time, and we are doing our first baby steps with graphics and icons. At some point we will find a way to design things that is fitting.

<Stephane> Brent: We should make a WAI sticker.

<Stephane> [ Sharron debriefing from today and showing tomorrow's agenda ]