Meeting minutes
WAO Curricula - Designer Module
<dmontalvo> https://
KrisAnne: You got the memo of our hope for timong on this - the survey is open and Daniel will introduce.
Daniel: We have the previous two modules published, the Designer Modules are now ready - we are a bit behind schedule and so are eager to get this one out and ready to get started on the next one - Austhors
<dmontalvo> https://
Daniel: this is the time to provide suggestions, not much more than discussion, questions, and thanks for all your consideraTION.
KrisAnne: Any questions or comments at this time? Next week is Thanksgiving I know it is a holiday but please do take the time to consider and comment.
Kevin: This is particularly challenging - consdierations for Designers - and I think this is really a fine resource and well done.
Daniel: Some background for the use of the word "define" - we use it to address many different methods, approaches, and situation. Could have used "apply" "use" "design" for graphic and felt that when it comes to interactions there is more of a need for definition and we used it related to decision making about things like iconography, focus placement, etc.
… there is also the aspect of communication and collaboration with other team members. We felt that "define" was a word that addressed all those aspects.
Shawn: With some of the things we write, we want to avoid repeition, but with something like a curricula it may not be so improtant.
Sharron: Sure, it may just be me so no need to spend more time on it.
KrisAnne: Anything else, other comments?
Daniel: Have been following up with people in the TFso if people don't have time, let me know.
Laura: I am traveling and won't be able to get this done by Tuesday
Daniel: Let's discuss in the planning meeting and thanks for that.
WCAG support docs redesign
<kevin> https://
<krisannekinney> https://
Results of survey: https://
KrisAnne: If anyone was unable to answer, feel free to discuss
Laura: Shawn bumped up the font size so I am OK now
Shawn: And you can update your survey to reflect that
Laura: I can accept this but it is still a bit small and am OK with this as a temporary fix but really strongly prefer the nav from the Report Tool
KrisAnne: Any other comments of questions
Kevin: I did not comment but think this is so much nicer, cleaner, very much improved. How some of those big text heavy docs might look in this format?
KrisAnne: Is there anything that people were looking for that they don't see here?
Shawn: Michael Cooper is waiting for resolution to code the new version. He has said that the nav box redesign is likely to be implemented this version and hover with scroll may need to wait.
KrisAnne: I am really excited for this redesign and how it will be received by the dev community.
Carlos: I was trying this out now and checking in on Safari and basically there are two nav componenets now - one labeled as nav (the box at the bottom)
<dmontalvo> I also noticed these two very similar items
Carlos: but then there is also the side box that supports this nav and also a TOC (happy to find that). When I have a narrow window ir look on mobile, those are presented in succession. So I get two exactly same nav tools in a row that allows me to do the same thing. Could be confusing.
KrisAnne: It will be at the top of the DOM when it is completely implemented.
Shawn: Other than that - if it is moved, does the rest of the design work for you?
Carlos: Yes but a wonder about the use of italic?
Shawn: Those are up for discussion
… and again it works really well if we have input for discretion for this iteration or next vs showstoppers for now.
Shawn: Can everyone go look at the survey now and get the backgroud and context?
Survey: https://
Kevin: It looks good!
KrisAnne: Will give eveyone a bit of time to read...
Shawn: I wanted to de-emphasize Guidelines Previous - Next. I thought about how to make it quieter.
Kevin: It is quiet here, no need to make it more so.
Shawn: I meant specifically that if I was looking at this I would want readable, etc to stand out. But maybe it's fine as is.
Carlos: I agree with you that those should be the ones to be emphasized and not sure that happens here.
KrisAnne: I really don't mind it the way it is, more visual styling seems unecessary. I will defer to those who use the documents on a regular basis.
KrisAnne: The subheadings do a lot so I'm not sure it needs more
KrisAnne: And if it will be modified in the future it is meant to match the Tools pages...
L: aura: It is different today than when I last looked correct?
Shawn: Yes, we modified since the survey opened
Laura: I am happy with the changes
Shawn: Shares screen with bolded words in teh nav
Laura: I would not bold those words
… we are doing something different under navigation than under page content
Carlos: I agree with Laura. I prefer when they share the same style
RESOLUTION: EOWG approves the current design of the prototype posted at https://
<MarkPalmer> +1
<krisannekinney> +1
<kevin> +1
<CarlosD> +1
Sharron: +1
<Leticia> +1
Daniel: +1
<Vicki> +1
<lkee> +1
<shawn> +1
List of Courses
Kris: Leticia will talk through the changes
Leticia: Thans everyone for the feedback. Most were minor changes but some were significant enough for discussion. (shares screen)
<krisannekinney> https://
Leticia: The use of the word "offer" made many uncomfortable so it was removed. We tried to use resource or solution where it made sense.
<Vicki> ready
Leticia: From what we noticed the names used in different contries for hybrid, etc and formats for source delivery. We gave a brief description for how we defined and used the terms and will be let you review them now.
<kevin> +1 to having a brief description
KrisAnne: It is useful to have it onscreen rather than an info button
Laura: Yes the short descriptions add a lot.
<dmontalvo> +1 for short descriptions
Leticia: In the Learning section we used terms that we found most commonly used and added a brief explanation and allowed them to choose more than one.
KrisAnne: The first two and the last two seem to be saying the same thing in a different way.
Sharrn: Estella submitted comments about the complexity and nuance of this characterization of learning type.
Kevin: It is not just the categories that are unclear - the term Learning itslef is unclear. Synchronous and asynchronous may be too complex for this purpose. We should try to simplify the language.
Leticia: We had detailed comment but from opposite directions so will need to continue to consdier.
Kevin: Just seems like insider language
<Zakim> shawn, you wanted to brainstorm "scheduled" ???
Shawn: What about scheduled and unscheduled training?
Kevin: Not entirely convinced - not sure.
<shawn> Unscheduled -- access when ever you want
<shawn> Scheduled...
Vicki: I tend to agree with Kevin that it is a bit of a tongue twister. Could the plain language version come first and put asynchronous in brackets.
Daniel: It is difficult here to choose the right term which may be right in one country and all wrong in another. I have seen the word "pace" used widely.
Carlos: Kevin made the point previously that the problem starts with the Learning title of the category. I am also struggling with the sameness of the self-paced/asynchronoous etc. if we change Learning to Activities, does that help? Scheduled and unscheduled activities?
<kevin> +0.5 to activities idea
<Zakim> shawn, you wanted to ask about combining the sections?
Shawn: Maybe to combine those? If it is online it could be either but in person will be scheduled
Kevin: Not necessarily
… what I come back to is - what are people filtering on and why?
… do you want a structured, scheduled course or are you more comfortable with access to the lectures and activities when you want them?
Shawn: We need to know what teh users will want to look for.
Carlos: I agree with Kevin - that is a great summary: How am I going to engage and When am I going to engage. People will want to know both.
Kevin: If that's what people with filter on, that what we can focus to answer those two questions.
… so how to engage - the format is pretty good but the When is where we are struggling.
Shawn: Do you ahve enough to take another pass or do you need more discussion?
Carlos: Let's just use scheduled and unscheduled now for discussion - are they exclusive or could they choose both?
Kevin: I think both would be possible and should be an option.
Shawn: Yes like my studies for the Masters
Leticia: Accessibility resources - Shawn provided a great list with links and we included other suggestions from Kevin. It is now called Accessibility support and has been expanded to be more comprehensive.
<kevin> This looks fantastic, love that resources are integrated into it!
Shawn: Great improvement. Many are already covered in Making Resources Accessible to All. We could link to supporting resources if we want to make the list shorter.
<Zakim> kevin, you wanted to respond to Shawn
<CarlosD> +1 to Kevin's arguments
Kevin: No we need to keep the list to make the expectations explicit - I really like this.
SteveLee: There is a cluster of items about media - should they be grouped together, thinking of the order of the list.
<Zakim> shawn, you wanted to put as sub points? and to
<Vicki> +1 shawn, grouping would be good
Shawn: The list is too long and could be grouped to be more readable.
Sharron: +1 to Shawn's point of moving the WCAG conformance to the top
<kevin> +1 for exploring grouping
KrisAnne: I understand the need for grouping but important to make clear that accessibility of a learning resource is important to consider before it is listed.
Kevin: There are aspects of that that might be useful but in some cases the support item is not relevant.
<Zakim> shawn, you wanted to brainstorm yes, no, not applicaable
Shawn: If someone will filter because it doesn't have media player accessibility and it turns out they don't use a media player it should be clear, so NA may be needed.
KrisAnne: You can meet content for WCAG but if the LMS does not support it, it is moot. LMS accessibility is another improtant factor.
Kevin: And can't use the term LMS since it may not be understood.
<shawn> "Unity" -> "Unit"
SteveLee: What does Unity mean?
KrisAnne: Typo, should be Unit
SteveLee: Learning hours is commonly used. Also Guided/self-guided in the UK
Shawn: Maybe the next step would be to do some user studies among a few people who make courses?
Leticia: We could pass it along while we work on the tech function.
Shawn: We can list it on W4TW so people can look at it, have course makers do a pass, get input that way.
Leticia: Would be great to get feedback while we work on taxonomy and making it work.
Shawn: Could get informal feedback or actually do screensharing and talk out loud observations - what might be psossible?
Carlos: Just to clarify your question - are you asking for us to provide participants or leadership?
Shawn: Leadership, but it could be just a quick session with the recording on.
Carlos: We can do that.
Sharron: Would it be helpful for us to provide some course providers who would be avaialble to do the study?
Wrap
KrisAnne: Please complete the survey on the Curriculum by the 30th
Shawn: It will be great if we can publish this in December so we want to get feedback in time to determine if it's possible this month.
KrisAnne: No meeting next Friday, Happy Thanksgiveing to all in the US.
Shawn: All are welcome to eat as much as possible on Thursday
KrisAnne: and sleep all day on Friday. Bye all and thanks