Education and Outreach Working Group Teleconference -- 14 May 2019

MOOC

<shawn> scribe: Howard

<scribe> scribe: Howard

Shadi: W3C has collaboration with EdEx. W3Cedx.

High drop off rate for their MOOCs. Worked with them to make sure

accessibility is integrated.

One of highest requested topics from students was accessibility.

In response, developing MOOC based on curriculum in development at WAI.

Opportunity to put our own curriculum into practice but also provide

a free course open to anyone. Certification (optional) for a fee.

Want to make sure all materials are provided independently of edX.

Curriculum - what should be in a course and also speaker notes or you can go and

take the course. So that other entities can take the course resources and develop

their own course (perhaps in their own language).

Not an EO deliverable but Shadi would like to do in collaboration with EO for their feedback.

Looking at multiple trainers, at least a different one, perhaps two, per unit.

Purpose - this also shows different types of training styles.

Right now focused only on intro course. Not necessarily college students but any learner - could

be employees, managers from companies, etc.

Brent: will there be instructor interaction?

Shadi: all lectures will be pre-recorded, rotating start dates. Every week assignments are

released and students can ask questions of the trainers.

Ask trainers to check these during first run but after 2nd or 3rd run

they are not as present or not present on a regular basis.

Brent: What extent EO involved?

Shadi: Wasn't in charter but would like to see EO highly involved to the point

resources are available.

Bit of a separate project from curricula work. Not part of WAI guide.

Brent: coincides with previous work so interested in providing input.

<shawn> [ Shawn notes current charter says under Deliverables: "If projects are defined and editor resources are available, EOWG may also develop: ... Curriculum, training, or teaching material for trainers and/or self-study" ]

Would like to provide help around international standards for online courses, including accessibility.

Shadi: this could be helpful for WAI providing standards for building a course that meets

accessibility and other quality standards.

<shawn> ackme

Brent: also a set of standards for quality instruction. Brent will provide a link to this standard

in the wiki.

<shawn> https://www.w3.org/WAI/EO/wiki/WAI_Curricula#Deliverables

In the providing guidance section.

Shadi: may also provide a guidance section for students or managers looking to

direct their employees for training.

Plan for MOOC to be generic because it will be accessed by many

different sectors and audiences.

That's why guidance will be crucial for groups wanting to build or customize

their own training/courses./

Shawn: (to Brent) should we say that our course follows these standards?

Brent: standards help insure quality interactive course and instruction but may not want to

commit or say we're following all 58 or so standards.

Jenn: who does Shadi expect to have as resources (people) to work on

this project.

Shawn: our current EO charter says that if we have the resources, we can develop training and build course

components so it can be done within the group if we want and people resources are available.

Shadi: trainers will be developing their own materials/resources for the course but running it

by EO for feedback, but not necessarily an EO deliverable.

Shawn: thinks EO would like to provide feedback but not having to approve as per an EO

deliverable.

Shadi: would like feedback on selection criteria for trainers and presenters.

Top priorities - diversity - geographic, ethnic, gender, etc.

Shadi: other input on criteria?

<shawn> Howard: mix of people from academia, corporate, etc

Daniel: people with disabilities included as trainers.

<shawn> Howard: brainstorm - someone well known in the field

<shawn> might even want to ask someone really famous , e.g., marlee matlin -- who might do it for us as a non-profit -- low chance, but maybe worth an ask? (... oops, I meant for the other videos, not this topic)

Jenn: or someone like Jenn Lay Flurrie

<shawn> Jenny Lay-Flurrie

Brent: timeline?

Shadi: hope to have it launch at end of this year/ beginning of next year.
... based on completing details and components of the curriculum - aim for

September completion or near completion by September 2019.

Shadi: end product will be housed on EdX. But course materials will be

available separately on the WAI site.

Brent: How will curriculum be separate from the MOOC course?

Shadi: course materials will not be inside the core curriculum.

But perhaps a link to courses that implement or map to curriculum.

<shawn> Howard: Seems like want to link from the curriculm into the actual examples.

Brent: seems like there was a concern that we not create a course in

order not to prescriptive in the content of the course.

He's not necessarily concerned about this.

Shadi: introduction has such wide audiences that we want to provide room

for flavoring or flexibility to customize course.

Still hesitant to lock people in to our structure/scope.

Sam: interesting to see how sample modules are displayed/presented by WAI.

Brent: add "know your audience" to guidelines for course.

Sam: Remind trainers to ask "what do you know about your audience? Who are you training?"

<shawn> [ brainstorming potential trainers]

<Brent> Scribe: dmontalvo

<scribe> Scribe: Daniel

<shawn> scribenick: dmontalvo

<scribe> scribenick: dmontalvo

Instructional Videos

<shawn> material linked in agenda - https://www.w3.org/WAI/EO/wiki/EOWG_F2F_May_2019#Videos

Shadi: We had a survey, I know last week was very busy, we got some feedback

We talked about that a few weeks ago in a telecon. There were three videos proposed, then two more were added.

One of the interesting things was the rankings: Evaluation stood out very high, and then planning and managing, business case and accessibility statement. Then at the end we have conctacting organizations.

Subtopic: Evaluation

The original proposal was 3 videos.

There are now two proposals: one is to actually make the preliminary evaluation a more practical one and even lengthier one

Shawn: What I found by going through Easy Check is that some of the details are outdated but the concepts are the same. As PM you need to figure out the scope but as someone who's doing Easy Checks would be benefited by video training

Shadi: How many checks are there now?

Shawn: 10 to 12.
... There are aditional ones for WCAG 2.1
... for Color Contrast we would show an example maybe showing a specific tool but without identifying it

s/For Color/i.e: For Color

Sharron: but don't go explaning the steps detail by detail.

Shawn: for headings you can get an outline or you can get markup in the page.

Shadi: But you still need something to show the outline

Sharron: If there is differences between what we say and what they see then they would lose confidence.

<shawn> Shawn: strongl think need to update the resource

<Howard_> s/strong1 think/strongly think

Shawn: the concept still works regardless of the tool you use.

Lewis: We can mention the Eye dropper but there are now new tools as well.

<Jenn> Easy checks version? https://www.w3.org/WAI/test-evaluate/preliminary/

Lewis: the Easy Checks is a really good starting video to have because it has an impact.

Shadi: There is a combination of scripting and screen play. We worked on this for the Perspective Video.

Jenn: I understand that neutrality needs to be preserved, maybe mentioning hexadecimal values and CSS. For headings, maybe showing the HTML view or the Source code. There are ways to keep it neutral, focus on the components you are working with.

<shawn> Daniel: I mentioned adding some specific examples. Easy Checks seems important. Ideas: heading, contrast, keyboard navigation are 3 good ones.

Shadi: It was proposed that there will be a series of examples so that there is diversity. What Shawn is proposing now is to actually do the 10 or 12 bullets that are in the resource. Thoughts on this?

Sharron: I don't use videos very much. I care about them because I see interest from other people.

Shadi: If we get so much into detail we might have longevity-related issues. I would like to rise tthis as a question for the group.

<Zakim> shawn, you wanted to say screen clips https://www.w3.org/WAI/EO/wiki/Easy_Checks_Next_Gen

Lewis: 10 minutes might be too long for many people. Maybe we should start by having a 3-5 minutes introduction. There is difficulty of doing a how-to without specific tools.

Shawn: Maybe we could incorporate the videos clips into the resource itself. Maybe also have a very short overview video.

<Zakim> Brent, you wanted to say about chunking

Brent: Agree with Lewis and Shawn. An overall concept video about Easy Checks and how to use the video and then embed things into the resource would be good. A video for every check would get too long.

Shawn: We want the main concept videos professional and then have separate video clips of the tools doing it (so we can delete them when outdated).
... If we do this approach overview will become too short. After that we would have the 8 videos. As they're separated, we can just delete each piece when it becomes out-dated.

Howard: I think an overview makes sense as a short introduction, paying attention to the things you have to look at, not too technical.

<Zakim> shawn, you wanted to say existing tools then open source forspecifics

Shawn: When we worked on this we, we had criteria, e.g, freely available tools. May be this might become an example for organizations to take this resource and do their own implementation on how to do Easy Checks

Shadi: The intro video would be for a much broader audience. The second level videos would be for people who want to really follow the resource. And then we would have third level videos with instructions on how to actually check using a particular tool.
... I really like this proposal but we need to prioritize.
... We haven't decided the priorities yet but at least we have a plan. Introdduction of about two minutes, then second level videos (8-10 videos) 1 minute or less, and then the third level ones of specific tools simple screen recording maybe narration, hoping that we have all the resources, time, etc. Any other thoughts on this idea?

<Lewis> +1

<shawn> +1

<Jenn> +1

<Howard_> +1

<Brent> +1

<shawn> +1

Shadi: Right now in comprehensive evaluation we have a little bit of tools. The suggestion is to put it into a separated video.
... It would become a 1 minute or 1.5 minute video. The pro is that this will address many people's questions on whether there are tools for accessibility.

the con is that there is sensitiviy around tools and we need to be careful when taking these approach

Lewis: I like the idea

<shawn> Selecting Web Accessibility Evaluation Tools https://www.w3.org/WAI/test-evaluate/tools/selecting/

Howard: worry about taking the tools out of the comprehensive evaluation lessens the usefulness of it.

Shadi: According to my thoughts, the primary evaluation is for people who might have a quick look at it, and the comprehensive evaluation is for people who have to actually perform evaluations.

Sharron: Tooling is a commont question but might not be the most important one.
... I do think the tooling question should be separated.

Shawn: Proposal would be a separate video from tools but still mentioned in intro and comprehensive. Does everyone agree?

<shawn> +1

<Brent> +1

<Lewis> +1

<Howard_> +1

<Jenn> +1

<shawn> s/video for tools, and still mentioned in intro and comprehensive in context./

Shadi: We have suggestion for 5 videos with the evaluation expansion, we will have to do some prioritizing.
... Evaluation overview: how would you picture that? How would you imagine it visually??
... Could it be funny, formal, casual...?

Sharron: We need to avoid formality, we need to make people feel relaxed. Maybe a conversation, some iconography. It needs to be friendly, not sure about how funny it should be.
... Lightness of tone should be present.

<shawn> [ Shawn share with shadi a studio that is awesome with the animation / whiteboard approach ]

Brent: I like the idea of informal versus formal. I like the idea of the hand drawing some imagery and going from concept to concept like that. For me having a talking here might distract. If you have a person you only focus on the person.

Lewis: I agree, not as formal. I also agree on the suggested animation.

Brent: It is important to keep focus on the animations. Strike a balance between making it positive and something more informal.

<shawn> Shadi: wai-atar

<shawn> several people: naaaawwww

<Zakim> shawn, you wanted to say warm & fuzzy not formal

Brent: the whiteboard approach Lewis was talking about would work as well. I will share a video to show the style.

As they're talking, they have images supporting what they say.

They try to help people remember what has been covered.

There are many companies that use this approach, it is not animated characters but animated style

<Brent> Sample of animated style video... https://www.youtube.com/watch?v=BgULEFogRcM

<Brent> Sample of whiteboard animation style... https://www.youtube.com/watch?v=2y9GlmOPT2w

Shawn: I think all these series should have this style.

Lewis: If I had to choose one I would pick up the whiteboard.

Shadi: It is a good idea to have a concept for wihch you could write a course displayed in several devices

<Jenn> The whiteboard animation style is good - it focuses the whole screen on the content, concept and demonstration.

Shadi: Could we apply this same style to planning and managing?

Lewis: For the animation we could take a screenshot and this could serve the purpose if for whatever reason we cannot make a more elaborated video.

Shawn: Can we pull the 30 second segment that we have here on including people in evaluation and include this in the resource itself? Let's keep it in mind.

<Jenn> I completely agree with Brent that it would be powerful for a CEO type to deliver the message.

Brent: Just throwing an idea. With the Planning and Managing, it would be powerful to have someone acting as a CEO saying "It is important to think about accessibility... Here are the things we have implemented... here are some considerations... etc"

<Jenn> ... the message of planning and managing accessiblity

Jenn: I have incorporate this into my training, how these companies perform in accessibility. This should be an introduction to Planning and Managing.

<Jenn> +1 for using CEOs of a company (small, medium or large) - demonstrate they are invested in a11y and are driving the implementation of a policy, process change, training, execution

Brent: the experience of joining the Valuable 500 may help influence managerial teams

<Jenn> scribe: Jenn

continue

Instructional videos, continue

We talked about ideas on how to invision these videos and how the professional media producers can help. The default approach would be some form of animation / infographic. Then we went to Planning and Managing and Brent had this great idea - brainstorming, but basic idea is a testimonial approach that a11y needs to be part of the DNA of an org and its workflow, so to have a peer-level manager or CEO to speak about their experience (training, process)

Not just hypothetical ideas but rather, practical testimonials from real people.

Shawn: if we can't get real people, would we use actors?

Brent: My original thought was actors doing it, but because what CEOs would we get to do this? But also if it's about planning and managing and using that resource, if we were go after people, we would need those who are actually doing it.

Shadi: "join the crowd"

Sharron: Talking about how one dept might, but in a larger company, the answer to participate has been no.

Shadi: logistics can be a problem.

Shawn: If someone looks the part, acts like a CEO ...

Howard: I'm not sure.

Shadi: Could be a consultant that talks about their own experience. could be an actor portraying a manager, ceo, etc.
... we are talking about just the Planning and Managing Video only.

Shawn: Getting appropriate diversity so we are comfortable with the members, persons is important

Shadi: This would be the ideal (real people) and secondary, actors. Other ideas? thoughts?

Brent: Again, a dart on the wall... what about you got the head of [specific accessibility organizations] talking about their accessibility culture and policy? Talking about how they don't just work on a11y when there is a lawsuit.

Shadi and Sharron: this is great.

I agree and I think Siteimprove would be involved.

<Zakim> shawn, you wanted to ask if not specific people, then actor? and to say also business case video

Shawn: I had the same thoughts thinking about the Business Case video.

Brent: what if you got a number of CEOs from industry leaders in accessibility products and platforms to participate?

Shadi: If you think about promotional videos, what would work?

Howard: Another group - you could ask universities that have implemented a plan?

Shadi and Shawn: Yes.

Brent: We can't focus on large corporate company

Shadi: Diversity in industry sectors, not just people
... Ok. Let's move over to Business Case videos

Shawn: Had the idea initially for the business case. (I think if we could do it only one place or the other, it should be Business Case video.)

Howard: Agree, using some case studies that Sharron put together.

Shadi: Either film people for both. Bus case is the "why" and the Planning and Management is the "how"
... Just a question to toss out, the planning and managing or business case, do you see them as the same style or different in tone (quicker, catchier)?

Brent: Throwing pizza dough on the wall... You have the idea of the Business Case content being narrated, and then on the screen you show someone using an iPad with a large retailer logo on the screen with captions. So you show someone using accessible features or successfully using the products from the brand
... Remember the woman using a mobile on the street, or a guy taking off his glasses to listen to a screen reader. Successfully using the digital system with accessiblity included. The whole point of the business case is that you're improving the use of your product for more people, and maybe it's obvious they have a disability.

Shadi: It's a great idea. We were trying to pitch the business case in the video in 1-2 mins of a video. This is important - one of the comments: how much headline and how much content? So a11y is good for business. Excellent headline, catchy. But do we want to back it up, really going in and show how it improves usability.
... One approach: having a lengthier video (3-5 mins) to explain Organization A and their high-level advocate to talk about why they do a11y and why it's important for their customers.

Brent: So have a person use the product on an app on their phone as he is narrating
... This looks professional. It switches to the next person who will talk about their company.

Shadi: We could consider this - a more narrative view (3-5 mins with multiple speakers) or a shorter video with headlines and here is a resource on it

Brent: Showing that there is someone using their product (recognize the logo) in use by someone with disabilities. They gave us their case study, they were willing to talk about it, why not allow them to plug (Organization A)?

<Zakim> shawn, you wanted to say image of fewpeople then lots and to say this one short and to say maybe main video - then orgs can make their own testimonial(and maybe if they meet xyz

Shadi: Are we setting ourselves up for difficulty getting the organization involved? Even if the narrator introduces the CEO and they speak for 30 seconds... it's a bit of a lengthier video. We can still consider which direction we want to go in.

<shawn> ... for more people in more situations.

Shawn: A few things. I imagined having a company showing they have a number of people showing how many people are affected by web accessibility (instead of just one). Another thing - my gut feeling is that we want to keep the Business Case video kept shorter.
... Or, we could encourage other companies to create their own testimonials, and invite them to share their stories.

Sharron: Other people might get excited by other testimonials and want to contribute to post on their site, or even put it on their own.

Shawn: yes, put a case study or testimonial on their site, and have a criteria for sharing it on the W3C site.

Brent: I'm thinking of keeping the videos really short. If you have someone talking about their case study, the segment is only 3-4 seconds long -a demonstration of someone using a tablet with an accessible website with brand logo.
... Show the device, the website, and that they have a disability. Not what the organization did to make their product accessible, but the outcome / usability / result
... in order for someone to buy into a11y, they need to see how it impacts their company. Companies want to gain market share or profit from a product, and how they do that is show people using it. So for someone to buy into the business case for a11y and why you should be doing it, as a CEO (hearing about the business case and why) I would like to see /hear that it increased their market share and visibly show how that market is reached

Shadi: Do we need to see the logo, can't we just show someone with disabilities using a tablet?

Brent: It is to connect the company with the a11y. It's applied by a large, reputatable company. This is demonstrated in the video.

Shawn: Another idea is to have someone looking at two websites and trying to use one, and then using the other one because it's accessible. It may be too much, but in the brainstorm ... this also includes any industry - (academic as well as retail, corporate, etc)

Brent: It could be too much cognitive overload to watch what's happening and listening to what's being said

Shawn: The message could be quite short - "If you don't make your site accessible, a user will go to a company that has one"

Brent: Yes, that's a good example

Shadi: I think Brett's argument is that it's not just a theoretical environment ... that organizations are doing it, and we may want - in showing logos and brands - that this is being done ... and I want to be part of that "club"
... The idea that you're missing the boat

Brent: This is also a way of looking at other competitors and seeing what the big companies are doing.

Shadi: agree, it's a great thing.

Jenn: I agree as well. Powerful to showcase companies that are actively producing accessible sites and products.

Shadi: At the W3C, where we have done so much textual content, we are finally coming into the 21st century with videos.

Shawn: With the Business Case video, I still imagine graphics like an arrow going up to visualize.

Shadi: Yes, I think there will be animations

Sharron: Good angel, bad angel - as a business guy showing the pros and cons?

Brent, Shadi, Shawn, Jenn: I like that

Shadi: Do we want to look at Contacting Organizations?

Sharron: Yes, we could make it humourous and engaging - have the poor person who's answering the phone yelling at them because the site is accessible ... angry instead of calm. There are lots of opportunities for humour and showing people's experiences
... We want to remind people that there will be contact with staff

Daniel: I think there should be the two sides - showing the person complaining and the person who deals with that. I see an interaction between two persons talking together

Brent: There is a commercial showing two people talking on the phone about a product, but it's the same person - they are experiencing both sides. To Daniel's point - how to model an effective way to interact with someone if you are the complainant. How can you work collaboratively with the company?

Shadi: We either walk through how not to complain to someone, or we have a skit that shows it (a play, acting it out)

Lewis: I thought about how kids react to each other on the phone, and then how an adult reacts - calmly explaining the problem

<Zakim> shawn, you wanted to say underlying message/purpose

<Brent> Discover card commercial, costomer/support conversation... https://www.ispot.tv/ad/dFSG/discover-card-talking-tough-no-annual-fee

Shawn: We were talking about content and style but we went ahead with style. So for Contacting video, we should think carefully about whether we want to try to address the big issue or drive-by lawsuits. I am aware of advocates who are furious, and the approach they are taking (angry) is counterproductive to a11y. The resource of contacting organizations - what we want to say as the W3C is that lawsuits are the last resort.

Sharron: It's good to think about that because you're right. To kick-off the K12 session today, only a few in the room was worried about getting sued. I hadn't thought about how these things are related.

Shawn: If we decide that a primary goal is addressing this related issue, it will impact the script for the video fairly significantly

Sharron: Contacting Organizations video - could be a way of addressing the issues of lawsuits and structured negotiations as options.

Shadi: Not taking a position on lawsuits, but showing structured negotation as an option

Shawn: Accessibility Statements video - seems the least like a 'video'

Howard: It could be dry. How do you make it funny?

Shadi: We could stress it's simple and a way to engaging your customers.

Brent: It could be an animation with a few key bullet points as to why the statements are important

Shadi: Not nitty gritty details of programming, but an accessibility statement at a high-level and the benefits

Sharron: We can make Planning and Managing easily appealing visually with icons and most useful and least-used resource

Shawn: If the goal is to let people know we have a resource for Accessibility Statement, we could create a funny / funky one

Brent: We want to get people laughing about it. A humourous commercial goes viral - not what you should have in it, but why you should have one, but the video can be passed around

Howard: I think you can do it. Distance from the pyramids then close in on the entrance.... "the pyramids have an accessibility statement, what about you?"

Shadi: to wrap up, what I plan to do is to integrate what we've discussed today and then to contact and find the video producer, get estimates and thoughts. What if we implement it this way, that way, etc. some of the things we can balance - save resources by not doing one video or another and also save cost through animations. Look at resourcing. What cut-offs do we need to do.
... We have funding for this project.

<shawn> s/We were talking about content and style but we went ahead with style. So for Contacting video, we should think carefully about whether we want to try to address the big issue or drive-by lawsuits. I am aware of advocates who are furious, and the approach they are taking (angry) is counterproductive to a11y. The resource of contacting organizations - what we want to say as the W3C is that

<shawn> lawsuits are the last resort./We were talking about content and style but we went ahead with style. For Contacting video content, we should think carefully about whether we want to try to address the related issue [of people's approach to accessibility at a legal level]…

Shadi: Meanwhile, keep the thoughts coming.

Brent: I will share a resource video for the humourous tone/style that we want

<Sharron> Scribe: Sharron

Curricula, continued

<Brent> Intro module: https://w3c.github.io/wai-curricula/curricula/introduction/

Shadi: Using links on F2F page, we are lloking t the draft. We jumped to the 5th module since they had been ignored. The discussion was interesting since we seemed to devolve into differences in teaching styles. No one disagreed with any of the content or that it belonged there. But there was difference about how much time to spend, what would be the emphasis and how to deliver.
... Idea is not to get too hung up on specific wording but rather to look at how to clarify the messagin etc.

Brent: I agree content is right but may want to look at terminology and change the Getting Started to Applying and managing or something similar

Shadi: My reflections on the discussion is that espcially the intro module - because we only want one intro, not one for each audinece - we want it to be the most flexible in terms of timing, emphasis, etc.

Brent: One question - is there a reason why we should have timing stated at all?
... I know some people may wnat things to be time boxed but for most if we want to be flexible, why give durations?

Shadi: My research into standard curriculum develpment was that a time estimate is expected. One suggestion was to give various estimates based on audiences ot focus. So this is a different question and I think you sugested we come back to it later.

Howard: I like to include timing. It provides a range, parameters, and helps people set expectations.

Brent: Can we say timing depends on focus and audience?

Shadi: In the intro of the module, when the entire set of modules are introduced, we explain how to use it. Couldinclude timing.
... in this one, for exaple, at this time it is one long scary page. will eventually be five or so and can encourage customization.

Brent: And each might have a disclaimenr on the top of each module's intro page encouragin gthem to adapt and change timing based on focus and audience.

Shadi: Thanks, anything else on Unit 5?
... OK going back into Unit 4, will emphasize WCAG principles etc. Daniel has reworked the 8 bullets.

Daniel: yes I have combined them into 3 lessons, emphasizing role of standards, principles of accessibility, and then the first or most basic checks.

Brent: When looking at the learning outcomes, where does the bullet 4 fall in what you just described?

Daniel: Will belong and are related to both lessons 1 and 2.

Shadi: To remember that awareness is different from deep understanding.
... we want awareness of guidelines as a result of this lesson, and a way to approach but don't expect people to necessarily be able to successfully apply and test for conformance.
... again will depend on audience, the roles that are in attnendence, and what is the focus.
... Unit 3 is the Business case, let's look at the learning outcomes...

<Jenn> Agree with Brett - we need to ensure that web applications are also subject to WCAG. Also: responsive site experiences on mobile and tablet

Brent: A few people have brought up the incluion of web apps as we talk about these things.

Shadi: Yes but at this time it is beyond scope - not including ATMs etc.

Howard: Looking at busienss case learning outcomes, none actually mention busienss benefits.

Shadi: UNit 2 is closely related to how people with disabilities use the web.

<Jenn> The Business Case & Benefits within Unit 3 has three layers to answer the question of "why are we doing this?" 1) social aspect + human right 2) that 'disability' could include aging people, but also barriers to products, services and devices are caused to people, not because of people and 3) "Mainstreaming" design to me means inclusive web and product design is an innovation that is trending, becoming mainstream, the norm. Get on board.

<Jenn> s/ *board

<shawn> +1 to different approach

<Brent> Shadi: Considering moving the Stories of PWD into the first unit instead of the third unit.

<Jenn> +1 to adding user experiences to the introductory unit

Daniel: If people seem to agree to move these stories to the beginning of the modules, Unit 1.
... if we do that to move to the first unit, it should be the very first thing.

Shawn: Yes that is what I do - understand what people's experince is.

Jenn: I use a quote from a deaf friend - it is the environment or the web site design that is disabled, not the person.

Lewis: Under learning outcomes for Unit 1, you could add the intro to the user experince. It lends itself to be part of learning outcomes of Unit 1.

Shadi: It is powerful to show the person and while they encounter barriers explain what is happening.
... it is difficult however to put into lessons, easier to make into talking points.
... my issues is how to take what you have described into lessons or topics. If we call them topic points they are more easily woven together.

Sharron: +1 to keypoints

<shawn> agree that experienced trainers will customize. the issue is people who are not trainers and people who do not know accessibility well

Sharron: Thank you all for the effort, time and talent you have contributed, it was a great F2F - you are all so generous with your skill. It' great to be working with all of you.

trackbot, end meeting

- DRAFT -

Education and Outreach Working Group Teleconference

14 May 2019

Attendees

Contents

MOOC

Instructional Videos

continue

Instructional videos, continue

Curricula, continued

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output