Meeting minutes
Announcement
Brent: We have added a co-chair and it is Kris Anne Kinney had been invited to join as a 3rd co-chair. We will be needing more project management since Shadi has left. Know that we needed more of that kind of project mamangement Kris Anne has agreed to join.
Kris Anne: I am excited and pleased to accept, looking forward to it.
<Vicki> Congrats!
<kevin> Fantastic news!
<estella> Great news!! Congrats Kris Anne :)
<Vicki> Well said, Kevin
Kevin: I think these chairs do a great job, and it will be great to have KrisAnne joining since there is a huge amount of work going on now and you two manage it well.
<estella> +1 to Kevin!
Brent: Thank you Kevin
<Jade> +1!
WAI Curricula Designer Modules
<dmontalvo> https://
<dmontalvo> These modules have been organized to facilitate teaching designers and developers together. If you are teaching in other environments, feel free to change
<dmontalvo> the structure so that it fits your audience needs.
Brent: Daniel has been working with the TF and hoping to bring it for review toward the end of the month. Daniel?
Daniel: We have been looking at specifics now, honing into the details and would like to speak with the group about them before the thorough review.
Sharron: Commend you for processing these substantial comments
Daniel: Yes the group has b=provided a lot of excellent feedback and the resources is improved. First this for discussion:
Teaching Designers and Developers Together
<dmontalvo> https://
<dmontalvo> These modules have been organized to facilitate teaching designers and developers together. If you are teaching in other environments, feel free to change
<dmontalvo> the structure so that it fits your audience needs.
Daniel: That is the lead paragraph and there is a link to the intro paragraph since this was not in the module when you reviewed it last month. It will mostly be used in a context in which designers and developers will be in the same class. So the question is do we need this or does the content explain itself?
… does this seem useful for instructors or just redundant? There is another place where we speak about combining
<dmontalvo> https://
Daniel: What are people's thoughts on this?
Kevin: I think the highlight within the overview says all that needs to be said. People will use this however they wish. Unless this is addressing a specific issue that was raised but I don't think it adds anything necessary.
Sharron: +1
Kevin: These are distinct module set to your credit so I don't think these last two sentences are required.
<Vicki> +1 Kevin
Jade: I agree they are redundant unless you want to talk about how they two sets of modules work togehter. Otherwise, not much point to this information.
… it might be worth considering that once the modules are established, we can provide more guidance about combining modules based on user feedback.
Daniel: Good point, can expand based on how it used.
KrisAnne: My thought is the same as Jade, more guidance about how to use the modules together based on the composition of your student roles. Maybe on the overall intro a note about how the modules can be used together.
Estella: During the design of the modules, we find so much overlap that we felt the need to address. It may not be clear enough and the background may be helpful to instructors.
Daniel: I am hearing that this sentence is not useful but there may be some need to address teaching students in different roles. I am not sure we will work this out soonish, but may have a look at in the future.
… so will remove this and look to introduce specifics in the future.
Clarifying Scope for orientation cues
<dmontalvo> https://
Daniel: We discussed this at a previous meeting. There was a request for greater explanation of the presentation of visual cues and programmatic elements like landmarks
<dmontalvo> -- learning outcomes for topic, last bullet.
<dmontalvo> "use text cues to supplement information provided through vision only, for example available dates in a calendar marked with a background color" changed
<dmontalvo> to
Daniel: We ended up including more language and it was changed to include more context and advises to define methods.
… these are the proposed changes and would require changes to teaching Ideas the section below.
… wanted to be sure I got it rgiht before making the change.
<Jade> I think the edited version reads much better
<Jade> +1
Kevin: Yes, I think it covers what it needs to and people will be able to use the example.
<Vicki> +1
<krisannekinney> +1
<brentb> +1 to update
<estella> +1
Sharron: +1
Daniel: Sounds good, thanks, I will now make a pass at the Teaching Ideas
Brent: Have we added a new teaching Idea?
Daniel: No, you may be thinking of our discusssion of the Form Elements Teaching Ideas
<dmontalvo> https://
Is Target Size Flexible?
<dmontalvo> -- learning outcomes for topic, last bullet.
<dmontalvo> "use text cues to supplement information provided through vision only, for example available dates in a calendar marked with a background color" changed
<dmontalvo> to
<dmontalvo> "define methods help users perceive and understand orientation cues, for example using text, color, and icons to convey the status of tasks in a project"
<dmontalvo> https://
Daniel: This comment was made a while ago.
Daniel: Even though this is a AAA requirement, it does not really point to flexibility in the actual WCAG requirement. I am a bit confused about how to present this. We need some sort of mention during the design phase and not sure what to do with this?
… is there a risk in presenting this only in the interaction moddule and not in the design modules?
Brent: Are we looking at the rewording or the original wording as it was commented on?
Kevin: I think the original wording was what I commented on. The new wording works well within the context of visual design and seems to make good sense now in the new context.
… I think the only other placewhere it might come in is the Form elements where we would need to discuss target size more than flexibility.
Daniel: I am torn about forms and interaction modules and how target size and flex fits in those. When we discuss scrolling, scaling, zooming etc.
Daniel: Thanks all, I will keep this wording here under the Visual Design Module, flexible design. I will make some specific references to target size and also references within interaction design
<Vicki> +1
Relationship between keyboard and other input methods
<dmontalvo> https://
Daniel: This is the module on interaction design and the section on keyboard insterations. There is also Geatures and Motion. We don't have other interaction modes, for example Voice. Wanted to be clear that robust keyboard interaction support faciliatates other kinds of interactions as well.
… so I added a section about how keyboard support is helpful for other interaction modes as well. What does the group think about how this is phrased?
Jade: You used the word "benefits" other types of interaction rather than "favors" them. Benefits is a better word imo
<kevin_> +1 to changing from favours to benefits
Daniel: I was not sure if benefits would be patronizing.
Brent: Suggest to move the point about how keyboard support is useful for other interactions to a later place in the list. Not the first.
<kevin_> +1 to repositioning learning outcome slightly lower down the list
<Jade> +1
<CarlosD> +1
Daniel: I was trying to broaden the audience. My rationale was to show the larger number of users impacted. But I see your point, I will move it.
Daniel: I am hearing it is a useful point but should be lower in the list of point sequence.
<estella> +1
<Vicki_> +1
<krisannekinney> +1
Daniel: thanks everyone for this input. Will go back and make these changes and adjustments needed to other sections. My intention is to have this done by the end of November and ready for thorough review. Any other comments before I get to work on this?
Work for this week/Wrap
Brent: We have a DragonFly review of the WAI Course List open until Nov 11. If you want to save, go ahead and anser a few questions and "Submit" to save what you ahve answered and you can come back and finish another time.
Carlos: Thanks to everyone in advance for their reviews.
Brent: Thanks to Carlos and Leticia for the editor interactions and the very clear maangment of input and commnets. We may/may not meet next week and will announce on Wednesday or Thursday about the meeting next week.
Michelle: Next week will be my first week scribing. I will be speaking at WebFlow hosting their NoCode conference and I will be emphasizing accessibility.
<Michele> Webflow No Code Conference: https://
Brent: Accessing Higher Ground is next week
<Michele> (Hilarious that Sharron scribed my scribe comment. LOL!)
Carlos: Next Wednesday is Shape the Future Research Symposium, register by Sunday.
… Jade will moderate on session and estella will lead one on education.
<CarlosD> https://
<CarlosD> https://
Carlos: Will not join next week will be giving a talk at a german organziation on accessible CMS
Brent: OK thanks all for a good meeting, watch the W4TW and for an announcement about next meetings. Appreciate all, and welcome KrisAnne to leadership.