– DRAFT –
Accessibility Education and Outreach Working Group (EOWG) Teleconference

Curricula first page

<brentb> https://wai-curricula.netlify.app/curricula/

<krisannekinney> Daniel: Working on the first page of the resource, pass to tighten it up. Thank you Shawn for helping. Changed some titles, added bullet to the tips section.

<krisannekinney> Daniel: Does anyone have reactions to the new structure? What are we missing? What needs to be polished? Quick thoughts?

<brentb> https://wai-curricula.netlify.app/curricula/

<krisannekinney> Breant: Like how clean it is, and the approach. The 4 distinct sections are very important. Its very clear.

<krisannekinney> Shawn: do we want a stronger word than Tips?

<krisannekinney> Daniel: we're not really getting into the details of how they should do it.

<krisannekinney> Daniel: something else may communicate that we have more to offer than what's in the tips. we will talk about the Titles, so we could discuss that as we go through. How can we improve what we are communicating.

<Daniel> https://github.com/w3c/wai-curricula/issues/316

<krisannekinney> Daniel: Focus on the first section. There is an issue for that 316

<krisannekinney> Daniel: The section is called Overview - what its it about, what it contains, advice on how to use it, use this to compare and select different courses. Provide situations and scenarios you can use it.

<krisannekinney> Daniel: Primary audience : someone who needs to create courses or add accessibility into their course. secondary audience: someone who is auditing these classes.

<krisannekinney> Daniel: want a title to let them know how to use the resource.

<krisannekinney> Brent: hearing you explain it, i heard the word Purpose. What is the purpose of the resource? provides the purpose of who could use this.

<Laura> +1 to Purpose

<MarkPalmer> +1 to purpose

<shawn> brainstorms:

<shawn> Using this Curricula

<shawn> Using this Resource

<krisannekinney> Howard: Does it have to be purpose of the resource - thinking about page contents of that section.

<krisannekinney> Shawn : Is purpose user focused enough?

<krisannekinney> Howard: also thinking Use of Resource

<krisannekinney> Brent: Thinking similar Purpose of Resource, but other titles are one word. Purpose means the reason why something was created or why something exists.

<krisannekinney> Shawn: but that's why we created - why should they use it?

<krisannekinney> Daniel: what about Uses?

<brentb> "Curricula Uses"

<shawn> KRisAnne: Curricula Users

<krisannekinney> Kris Anne : The bullet points are the people that will use it.

<krisannekinney> Daniel: hesitant to do that because we may ahve many more, its not JUST these users.

<krisannekinney> Howard: I like Curricula Users, more about what the purpose of it is. Encompasses the uses.

<krisannekinney> Howard: Corretion Curricula Uses

<krisannekinney> Daniel: We're proposing that this is how it can be used, but not all the ways to use it.

<MarkPalmer> +1 to Curricula Uses

<krisannekinney> Shadi: I like Curricula Uses but it will depend on if we want to look at other titles, and what the other titles are. See how the other titles come together. Do we go with Uses of this Curricula

<krisannekinney> Laura: Thinking Uses for this Resource - that's more general.

<krisannekinney> Shawn: I don't object to any of that. Using this Resource or Using this Curricula is clearer. And the other titles don't have to have Curricula.

<krisannekinney> Daniel: without implying we're going to show you how to do these thing, there is room for working on the titles.

<Howard> I like "using this curricula"

<krisannekinney> Daniel: Uses or Using this Resource work

<krisannekinney> Shawn: English hat on, its not a problem - they don't have to have the same structure.

<krisannekinney> Kris Anne: Pointed out Howard's Using this Curricula - and my point that I like using Curricula over Resource - we use resource a lot in all of our resources.

<krisannekinney> Daniel: Addressing the audience that woudl be looking for Curricula, but not using the word curriculum because some may not use that term.

<krisannekinney> Shawn: I support that - you've done a good job of simplifying it. Having Curricula in the first H2 is good to reinforce what it is.

<krisannekinney> Daniel : Using this Curricula as the title of this section?

<shawn> +1

<krisannekinney> +1

<Howard> +1

<Laura> +1

<brentb> +1

<bwbealer_> +1

<shadi> +1

<MarkPalmer> +1

<krisannekinney> Daniel : that's good, we are in agreement with it. Let's move to the Tips title. I think the other titles work, Contents and Structure and Terminology. But we can discuss if anyone thinks they don't work.

<Howard> I'm fine with 'contents.'

<MarkPalmer> Me too

<Laura> +1 to contents

<Howard> And with 'Structure & Terminology'

<brentb> +1 to "Contents" and Structure and Terminology"

<krisannekinney> +1 to both titles

<shawn> +1 to "Contents" and"Structure and Terminology"

<bwbealer_> +1 to both

<krisannekinney> Daniel: lets go to the last title to Tips

<krisannekinney> Daniel: We want to communicate to instructors different tips or pieces of advice for their teaching. Maybe "teaching tips" or "tips for teaching"

<krisannekinney> Shawn: they are all about accessibility, not tips on teaching. Maybe something like Ensuring Effective Approach

<krisannekinney> Kris Anne: what would make an instructor stop and really look at these?

<krisannekinney> Laura : Strategies - Strategies for Teaching

<brentb> What about "Best Practices"

<krisannekinney> Daniel: Trying to relate this to accessibility - "Strategies about Communicating Accessibility"

<krisannekinney> Shadi: I like the Tips idea - Tips for Inclusive Teaching, Tips for Successful Teaching,

<MarkPalmer> I like Best Practice. I also considered "Recommended approach"

<krisannekinney> Shawn: Tips for Communicating Accessibility.

<krisannekinney> Barry : More like Guidance and Tips

<shawn> Guidacne for Addressing Accessibility

<shawn> Guidance for Approaching Accessibility Teaching

<krisannekinney> Kris Anne : Accessibility Guidance and Tips

<shawn> Tips for Approaching Accessibility

<shawn> Tips for Accessibility Teaching

<krisannekinney> Shadi : I like the simplicity of Tips. The other words are getting heavy. Tips for Awesome Teaching?

<shawn> Tips for Accessible Teaching

<shawn> [ Shawn brought it up, yet fine leaving it just Tips ]

<shadi> +1 Tips for Accessible Teaching

<krisannekinney> Daniel: Accessibility should not be in isolation. Maybe Good Practice Tips - this is actually good practice we are recommending.

<Zakim> shawn, you wanted to say what I typed

<Howard> "Good practices" or "recommended practices"?

<bwbealer_> Best Practices and Tips?

<krisannekinney> Shawn: the big point is that I'm find with just Tips, but I've put my other ideas into IRC.

<krisannekinney> Daniel: We should try to make the effort, but would Tips stop us from moving forward?

<krisannekinney> Brent: earlier I put in Best Practices - professional procedures - but led me to Effective. What about Effective Tips for Teaching.

<brentb> Effective Tips for Teaching

<krisannekinney> Daniel: Yeah, that's a good point.

<krisannekinney> Howard: Like suggestion Best Practices and Tips or incorporating Teaching Best Practices and Tips

<krisannekinney> Daniel : Teaching Tips and Best Practices.

<krisannekinney> Daniel : the audience we are addressing already knows Best Practices, its pretty general.

<krisannekinney> Brent: when you're teaching, to be effective, try these things. What are the most effective things we can tell people to do. You came up with the very best things you coudl think of.

<krisannekinney> Brent: here are best practices to make your teaching more effective.

<Zakim> shawn, you wanted to say essential, really

<krisannekinney> Shawn: I don't feel strongly about any of it. But I think this is more than Best Practices. This is important stuff - you really have to do this an do it right. its the essence of accessibility.

<krisannekinney> Shawn: if someone isn't doing this - they're missing the point.

<Laura> +1 to Shawn's comments

<krisannekinney> +1 to Shawn's comment

<Howard> How about just the phrase "Inclusion & accessibility"

<krisannekinney> Howard : Inclusion and Accessibility.

<krisannekinney> Shawn : Getting it Right

<shadi> Essential Teaching Tips

<krisannekinney> Daniel : essential Elements or essential tips

<shawn> Essential Elements for Teaching Accessibility

<krisannekinney> Shawn: Essential Elements for teaching accessibility

<shadi> Teaching Essentials

<krisannekinney> Laura: I agree with Shawn. I think Tips makes it sound optional and the content doesn't feel optional. Essential Elements for Teaching Accessibility sounds more like what it is.

<krisannekinney> Daniel: when we talk about accessiblity, its not just about communicating or teaching, but we need to relate it to the resource too. The idea that these are essential things you need to do.

<brentb> "Essential Implementation"

<krisannekinney> Shawn : these are the things that broadly apply to everything.

<brentb> "Essentials for Teaching Accessibility"

<bwbealer_> Essential Best Practices for Teaching Accessibility

<shawn> Principles for Teaching Accessibility

<krisannekinney> Shadi : i like that since you ruined Tips for me.

<Laura> +1 to Principles...

<krisannekinney> +1 to Principles

<krisannekinney> Daniel : I like this, but when people see Principles, will they relate that back to the principles of WCAG - is that a risk? That we will describe them?

<krisannekinney> Shawn: in this context i think its ok to use Principles

<Howard> +1 to "essentials for Teaching Accessibility" but will go with consensus

<krisannekinney> Barry: Essential Best Practices for Teaching Accessibility - not mandatory, but its essential.

<krisannekinney> Barry: Its about what will catch the attention of the audience.

<krisannekinney> Howard : Essentials for Teaching Accessibility better than Principles.

<krisannekinney> Howard: Principles sounds more encompassing. That's why I like essentials better.

<krisannekinney> Howard: We want to make the page contents easy to scan.

<shawn> KrisAnne: Liked Principles at first -- but we don't teach these points in detail.

<shawn> Shadi/Shawn: We do link to more on each point

<krisannekinney> Daniel: we have the links, but the curricula itself doesn't go into detail about how to these points. See the danger of raising the expectations that we'll teach them, not just give them this overview.

<krisannekinney> Shadi : different approach. Hearing Essentials or Principles of Teaching Accessibility.

<krisannekinney> Shadi: Shoudl we send that back to Daniel and let him make the decision.

<krisannekinney> Daniel : I would go for Essentials - to avoid any confusion. Essentials for Teaching Accessibility.

<krisannekinney> Daniel: Do we think this is ready? Survey to approval to publish is open for the Developer modules. There will be another for the overview page. So we need to make sure we're doign this right.

<krisannekinney> Daniel : Approval to publish for this page as well - do we need another pass at the overview page?

<krisannekinney> Daniel : approval to publish in the coming weeks?

<krisannekinney> +1

<Howard> +1 to publish

<Laura> +1

<bwbealer_> +1

<MarkPalmer> +1

<brentb> +1

<shadi> +1

<shawn> +1 to publish (after copy edit pass)

<krisannekinney> Group is ready to put the overview page to publish after one more copy edit for language.

<krisannekinney> Shawn: I think this page is in shape and i agree that its tight and clean and focused and important. Kudos!

<krisannekinney> Daniel: Thank you all, your input has improved this.

Curricula Next Development

<krisannekinney> Brent: Team is ready to move to the next piece of curricula to work on. I think they discussed what would be next. Can you explain that to the group?

<krisannekinney> Daniel: Designers Curricula - writing and efficiency - having things fresh on our minds after finishing the developers. Cross posting references to take advantage of the work we've done.

<krisannekinney> Daniel: Two left - Designers and Content Authors

<krisannekinney> Brent : Any objections or comments to that?

<Howard> +1

<krisannekinney> +1

<shawn> +1

<krisannekinney> Everyone OK to move to designer curricula next?

<krisannekinney> +1

<Howard> +1 to designer curricula next

<bwbealer_> +1

<shadi> +1

<brentb> +1

<shawn> +1 to designer next

<Laura> +1

<krisannekinney> Brent : Looks like we are good with that. Move forward with the designer curricula.

<krisannekinney> Brent : Maybe end of next week - survey to publish the Overview Page?

<krisannekinney> Daniel: Need to let the task force know the changes, and then we will get the survey together.

<Howard> Nice work Daniel!

<krisannekinney> Brent: Thank you Daniel, and please pass that to the working group too.

Perspectives Videos

<shawn> https://www.w3.org/WAI/perspective-videos/

<krisannekinney> Shawn: Issues with the headings - small points, but I didn't want to make decisions myself.

<krisannekinney> Shawn: H1 and then a sentence and then the H2 Perspectives Videos. I think the world refers to them as the Perspectives Videos.

<krisannekinney> Shawn: shoudl we add Web Accessibility Perspectives Videos to the title?

<krisannekinney> Shawn: If you look at a sub pages of new resources, we add the original page title as a sub under the page titles. So we'd add Perspectives Videos under the page titles, e.g Video Captions.

<krisannekinney> Shawn : put the parent resource name under the page title for all the Perspectives Videos.

<krisannekinney> Laura: is the tag line part of the H1 and just a different style or is it a different tag?

<krisannekinney> Daniel adn Shadi : its part of the H1

<krisannekinney> Laura : i like the longer version in search results you get more information.

<krisannekinney> Shawn : loger version in the H1 of the parent page.

<Zakim> Daniel, you wanted to mention multi-level resources

<krisannekinney> Daniel : when we have multi level resources we'd have a parent and a grandfather. WAI should decide if we point to both or just the one prior?

<bwbealer_> +1 to adding "video"

<shadi> +1 to both

<Daniel> +1 to proposals

<bwbealer_> +1 to both

<MarkPalmer> +1 to both. Adding video to main page would be in line with URL, headings on the page etc

<Laura> +1 to both

<Howard> +1 to both

<brentb> +1

<krisannekinney> Shawn : Proposal : add Video to the main page. And to the sub pages add main title "Web Accessibility Perspetives Videos"

<krisannekinney> +1 to both

Outreach

<krisannekinney> Shawn: Brainstorming

<shawn> https://www.w3.org/WAI/EO/wiki/Promoting_Media_Resource#Ideas_for_additional_promotion

<krisannekinney> Shawn : we updated the media resources - new first page, making it work better for our target scenario.

<krisannekinney> Shawn : Ideas on how to reach the virtual conference presenter target audience.

<krisannekinney> Shawn : Next audience is the conference hosts

<krisannekinney> Barry : concerted effort to post on the conference website. Or contact conference organizers these resources.

<krisannekinney> Shawn : if we reach out in a positive way its Targeted Outreach.

<krisannekinney> Shawn : if that's something you want to help with - that would be great.

<krisannekinney> Shawn : If you know of a conference and send a super friendly email with the resources to help them make conference accessible. Make sure you list it to the Promoting Media Resource page listed above.

<krisannekinney> Barry : any way we should target the software vendors that provide the online events.

<krisannekinney> Shawn : it would be great if we could do that.

<krisannekinney> Barry : narrow it down to the online event companies so they can help people create accessible events. Should be a best practice to have accessible online events.

<krisannekinney> Barry : I can take the action to find out what companies are out there.

<krisannekinney> Shawn : you do get into whether their platform is accessible. Is the online conference software accessible.

<krisannekinney> Barry : I don't mind doing the outreach part.

<krisannekinney> Howard: reaching the audience ... there are listserv's that deal just with meeting planners. Been a lot of discussion in those listserv's. ACM puts on a lot of conferences. Give the resources to the people that curate listserves

<krisannekinney> Shawn : Could you send those leads to Barry.

<krisannekinney> Howard : yes

<shawn> https://www.w3.org/WAI/EO/wiki/Promoting_Media_Resource

<krisannekinney> Kris Anne : Can we have a crafted email to send out to different companies?

<krisannekinney> Shawn: the updates we have target the home video maker. new updates need to focus on the conference organizers.

Work for this Week

<krisannekinney> Shawn: Next step is that we have pending ideas for adding points to the resources so we can expand our outreach on making these resources widely used.

<krisannekinney> Shawn : Outreach for WCAG 3 - point to the intro page

<brentb> WAI - Web Accessibility Initiative

<krisannekinney> Shawn: Input on Images in our tweets

<krisannekinney> Shawn : now that we have our 6 icon image set we wanted to update the graphic we used for social media posts.

<krisannekinney> Shawn : any initial reactions to the images she showed?

<krisannekinney> Laura : I like the simple W3C in the middle - icons across the top in yellow. The others feel misaligned and busy

<Howard> +1 to Laura

<krisannekinney> Laura : this one feels more polished

<krisannekinney> Brent: Agree with Laura - I like the yellow icons, my eye is drawn to the white of the text.

<krisannekinney> Brent : Social_2 the icons look skewed. Or switch the icons to match better. I don't see a need to repeat the icons.

<krisannekinney> Mark : social _1 is the one I like. only concern i have is that I think the C in the W3C gets lost. Wonder if the background color could change how you see it.

<krisannekinney> Barry : social _1 cleaner version, like it the best. Generally on social media the left and right get cut off so the centered logo is good for social media.

<krisannekinney> Barry : What other social media platforms do we use?

<krisannekinney> Shawn : Just twitter. No Facebook or official Linked in.

<krisannekinney> Barry : I would recommend LinkedIn.

<brentb> acl shadi

<krisannekinney> Shadi: I like Social _2 and _3

<krisannekinney> Shadi : the reasons I like it is because I feel that the logo is smaller. On 1 the logo is the center. In 2 or 3 the resource name gets the focus. I like that the icons are bigger and the icons represent what WCAG is about.

<krisannekinney> Shadi : the 2nd and 3rd emphasized the right things - and the setup of the logo is similar to the website so the recognition will be there.

<krisannekinney> Shawn : i like the logo in 2 and the colors have grown on me. I like that the resource is so prominent.

<krisannekinney> Shawn: on image 1, i like the icons in a row. I don't like that WAI is not in version 1.

<krisannekinney> Shawn: Maybe if we put the icons at the bottom, and the WAI in the top right and the resource name in middle.

<krisannekinney> Howard: I like what you suggested Shawn - could we incorporate the two tone color - makes it visually interesting i like the two different colors.

<brentb> Kris Anne: I too like the two-tone colors. In the ones with the two-tone as a slash, I don't like it as much.

<Howard> Doesn't matter either way.

<Laura> Ok with all icons together.

<krisannekinney> Shawn: Do we like the initial 5 icons or all 6? the single body was supposed to be only used when we needed one icon.

<Howard> Need to jump off. Bye everyone.

<krisannekinney> Shadi : I am glad the icons are being used. I think its good to use the body.

<krisannekinney> Kris Anne : that person represents the All.