Translations

<shawn> https://deploy-preview-125--wai-website.netlify.com/videos/standards-and-benefits/

Brent: Shawn has done excellent work in laying the foundation so we can invite people to actually do the translations. The framework is built and we will get real world feedback after deployment and soft launch.

Shawn: Kudos as well to Eric who has done extensive web site back end work. We are excited about the design of the UI and meeting user needs. With various input from people who do and who use tranlations. I don't really want to walk through it. Would rather that you click around and see if it is intuitive about how it works and what you understand without guidance.

Brent: We want to take a moment to click around from the link Shawn provided to see how things work for you.

Eric: This is basically how the website will launch. We do not have a lot of translations but here are the ones completed so far. Several of the French translations, thanks to Stephane.

Shawn: and Sylvie has helped as well

Shadi: I love it - the ability to hide, the clarity. It's great.

<Laura> +1

Shawn: The issue with Arabic is to test out the display of left to right languages and then will be added that as well.

Laura: The 'all translations' link at the top seems a bit much and can be confusing. Where there is so much already going on the nav, that link takes you away from what you may actually be looking for

Shawn: Look at a different page to see how it works. Do we maybe not want the 'all translations' on pages where we do not have a lot?

Laura: Even then, it is distracting. It may be too much. The 'all translations' link should probably live somewhare else.

Shawn: In the top bar there is a skip content, stays on page. Translations goes to a new page. In our research, the links to translations in placed top right. We are following common practice.
... also use of common translation icon.
... On pages where we already have them it may add confusion about if it is just for this page.
... thanks for that good observation.

Sylvie: Next to skip and color change. Reading in braille, the color change and translations are not separated, seems like the same thing. And they are sometimes working and sometimes not. When I look at the French page, some things in navigation are translated and there is a repeated ARIA tag.

Shawn: It is on one line and there is a visual separator.

Eric: It is a different list element in the code

Sylvie: Not identified in Braille output
... in nav there are elemetns sometimes in French sometimes in English

Eric: English titles in nav elements indicates there is no translation
... aria current means that is where you are in the page.

Sylvie: There are several of those tags, I cannot be in several places at one time. May be too much aria, a bit confusing/

Shawn: Would love to get input. Considering doing a soft launch, let translators see their stuff live, but not to a big announcement. Let it sit a bit, do a big announcement after we get a bit of feedback.Ideas about that?

Laura: That is a good plan, I would do the same.

Sharron: +1

<Brent> +1 for soft launch

<yatil> +1

Shawn: But what if others start tweeting about it or sharing it and we have not yet announced it - awkward?

Laura: At the LOC we have done similar, did a beta with volunteers. There was a bit of chatter previous to our announcement but it was not a problem.

Eric: If a natural buzz occurs it should be fine and positive. Would be more of a problem if we made an announcment with very few translations. If people discover it, it's a good thing.

Shawn: There is alot of automation that Eric built in, thanks again for all that work. We are hoping to get it done by CSUN. Thanks all!

WAI curricula

Brent: Introduced in Lyon, there has been progress in the planning and we will have some work to do at CSUN later this month.

ShadI: We had an initial discussion at TPAC

<shadi> https://www.w3.org/WAI/EO/wiki/index.php?title=WAI_Curricula_(WAI-Guide)

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

Shadi: This is the requirements documentation to help the group understand our goals. The ingredients will be brought together to build a course, but not the course itself. What would be given to an instructor. Similar goals to the previously published Developing Web Accessibility Presentations and Training.
... categorizations of how to present and train. This was an outline rather than provision of content. Now want to go deeper than the high level treatment previously provided but do not want to constrain the teaching methodology. Want the resources to be geared toward formal education but very flexible for different kinds of teaching approaches or course focus.
... want to provide assessment materials, methodologies, default curricula for differnt roles that allows a skilled instructor to build their own MOOC or something. Will allow modular mixing of content blocks. Creating a big umbella.
... you will find learning objectives, suggested targeted roles (possibly aligned to ARRM), will remain in general roles, not get too granular in dev roles.
... deliverables will likely be a multi-page resources, might be a dynamic widget. It is as yet undefined, will depend on designer. Another deliverable will be something like content blocks, modules, learning units. Another resource will be the guidance for trainers. How to make presentations accessible for everyone, for example. Want to show different aspects for different roles - e.g., pointy brackets or not
... often things will overlap which is fine. We want to be looking at things from different perspectives - e.g., designers vs. developer
... for some roles maybe make sense to have multiple levels. It is still open whether we want levels and how many. Intro will be available for F2F. For today, do you any questions or comments -- so you can review in detail - the Requirements Analysis and the draft outline for Intro. Prepare for discussion at F2F. *everything* is up for discussion at this point.
...Not only for the roles, but maybe also based on industry, e.g., banking vs. social media.I would request that the group review both in detail -- both the Requirements Analysis and Intro Outline. esp if not going to be at F2F, please send your thoughts and input ahead of time. (and way - GitHub, wiki, e-mail, fax :-)

Shadi: Hoping that the outcome of the F2f will be agreement on framework and structure

Brent: One thing we can do is put this on W4TW to review and comment. Is there a repository to submit comment?

<shadi> https://github.com/w3c/wai-curricula

Shadi: May be too early for pull requests but certainly can raise issues and make comments. At this time will likely to be high level discussion.

KrisAnne: Looking at list of roles, is it a good idea to put specific training around procurement - really agree with that - but also think it will be useful to add soemthing around Human Resource systems. People wonder why their workforce is not diverse when they have barriers to the very process of applying.

Shadi: Great idea and please add that thought to the GitHub

<Brent> +1 to HR (for systems and documentation)

Shadi: Like for example procurement, is that a multi week course or instead an unit within a larger course?

Kris Anne: Yes a targeted module makes more sense.

<Norah> +1 to Laura and Krisanne

Laura: Great to be aligned with the ARRM work. As a developer in a large organization, we so need resources we can offer to collegues who are not developers. Resources that define their responsibilities and provide guidance. As a developer I think of course we should go first. But we can't do the job alone and it will be so valuable to have specific guidance for other roles

Shadi: And we have so many existing resources that we can point to. Design of the framework will be the first challenge.

Brent: I like the idea of keeping an open mind toward flexibility. Not thinking that we will define the content for each and every role but instead create useful blocks and let instructional context determine what is appropriate for each role.

Shadi: There is everything from C level folks who don't want detail - only numbers; to project managers who may not need as many tech details; to HR people who may need general info and specific basics for inclusion to the full requirements for devs and designers - like the Toolkit approach.

<krisannekinney> just excited for all of it!!!!

Shadi: any other comments or questions?
... look forward to your comments, remember I am thick skinned so don't hold back.

F2F Agenda

<Brent> https://www.w3.org/WAI/EO/wiki/EOWG_F2F_March_2019

Brent: Details on the wiki. Please update your availability if it has changed, let us know if you want to join any part by phone. Quick review:

<shawn> [ note that we are not ordering phone connection at the hotel (although might be able to use webex) ]

Brent: these are plans, never set in stone, happy to make changes if you have input. ...implement WCAG 2.1 updates, look at EZ Checks, Silver update, -and then will -> break into groups for 1.)Plain language for Silver and 2.) Policies work
... hoping that UnDoc team will help with the plain language work with Silver.
... Tuesday will dig deeper into the WAI Curriculum project that Shadi just outlined; ARRM work; Outreach planning
... that is the overview, anything else overlooked or additions needed, any other questions?
... another agenda item is to review materials prior to meeting and you will find the materials listed and linked. May be adding to that so please check in from time to time.

Shawn: Overall task is to integrate new SCs from 2.1 into EOWG resources. Task will be to go through the other resources to determine what needs to be added. Some resources (like easy checks and getting started) are not meant to be comprehensive. Will be tasked with looking at the docs, deciding what needs to be added, what not, pose and answer questions, consider how to proceed.

Howard: I am interested in the curriculum, I am supposed to create another (advanced) course for CU. If there is a collaboration possible, I would like to explore it.

Brent: If is something that you want in the agenda, meet with the planning team.
... Let's see what makes sense in the context of what we are focused on at the f2f and next week we are talking to Denis as well about ARRM.

Shadi: Let's you and I talk first Howard and then bring to the Chairs

Brent: The time from 8 am to 9 am CT is open
... It will be US Daylight Savings time during CSUN and not in Europe yet
... check your clocks and watches

Kris Anne: Do we have a place, a room to meet?

<shawn> Thanks to Pearson for hosting/sponsoring again. And thanks to Knowbility for previous hosting/sponsoring EOWG F2Fs.

Brent: Three groups will meet at the same time - AG, Silver TF, and EOWG - at the conference hotel. Plan is to break at the same time.

Shadi: Before we close out the f2f discussion, another topic at Lyon was the development of more video based resources. We brainstormed in Lyon and maybe we can create an open survey with some of the previously offered ideas as well as an open field for people to post new ideas.

Brent: I remember the brainstorming and that it got out of scope very quickly. If you captured any of those, we could certainly put them in survey and invite new ideas as well.
... little video clips at the top of each resource.
... thoughts?

Sharron: We have time at the end Tuesday. Seems to fit well with Outreach.and good idea to post a survey with previous ideas and collect new ones in advance.

Shadi: Maybe discuss how to integrate into the curriculum as well.

Brent: Great we will look for your draft survey and add it to the outreach and curriculum discussion

Wrap-Up

Sharron:Becky, Laura, and I are working on QuickRef tags and it will be finalized Wednesday morning. I will miss the planning meeting

<shawn> [ Shawn: woo-hoo ! ! ! ]

Brent: UnDoc work is moving forward as well - will send the first 3 final recs from our group to AG today.

<yatil> Availability Survey: https://www.w3.org/2002/09/wbs/35532/availability/

Brent: add attendence to that survey and link to preview of F2F prep, there will be surveys this week, may get a lot thrown your way before CSUN face to Face meeting. We will ask for additional review of curricula and additions to GitHub.

Brent: There will be a lot coming at you this week, thanks for your attention and help.
... we have been communicating with Andrew who has stepped up to shepherd the policies work and Shawn recruited Lainey to help - will move that forward at the F2F. Deepest appreciation and thanks to Andrew for stepping up - and to Robert and MaryJo for bringing it along this far. Robert will do a hand off to Andrew at CSUN. Thank you all for your contributions and support!