Meeting minutes
Setting up meeting, choosing scribe https://www.w3.org/WAI/EO/wiki/WAI_Curricula/WAI_Curricula_Task_Force_Meetings#Scribe_Rotation_List
Sequence for first module "User research and requirements https://deploy-preview-340--wai-curricula.netlify.app/curricula/designer-modules/user-research-and-requirements/
DM: collected different tasks in this area
… just concerned that working with people with disabilities comes at the end
… how can we address this issue?
HK: concerned about last bullet point?
DM: last topic
… does it convey involving in testing only?
CD: not seeing this concern
EO: agree with Carlos
SAZ: does first bullet need to be limited to "usability testing"?
… could also be involvement in the co-design process
… but just generally, are these designer tasks?
CD: agree with Shadi on expanding beyond just "usability testing"
… maybe also not put as first bullet point
… looks like module for UX designers
EO: miss terms like "user requirements" and "requirements gathering"
SAZ: other topics should also include aspects of involving people with disabilities
… for example for gathering requirements and researching users
… not just create personas and scenarios of them
… also need to include aspects of considering standards
… not everything needs to be researched from scratched
… standards provide a starting point
CD: agree with Shadi
GN: the latter bullets seem very general
… also apply to people without disabilities
… basic principles of usability and ethics
EO: agree, this is part of any research
… data protection laws also apply, confidentiality, ...
… protective of people with disabilities
… may have counter-effect of excluding them
DM: agree but some situations require particular attention
… including informed consent
EO: you have adapt to their communication
… for example, sign-language
… or easy-to-read instructions
CD: agree with Estella and Gerhard
… maybe focus just on these specifically relevant aspects
… also location, for example
… sometimes need to go to their homes/work environment
… rather than them coming to the lab
DM: so maybe integrate this last topic into the prior topics
… and in doing that reduce to the most essential parts
Is "Colors, Styles, and Animations" the best place to discuss 2.3.3 animation from interactions?https://deploy-preview-340--wai-curricula.netlify.app/curricula/designer-modules/colors-styles-and-animations/#topic-seizures-and-physical-reactions
DM: is this the right place to talk about seizures?
… seizures and physical reactions
CD: what about motion and animation not from interaction?
… everything else in this module is not interaction-driven
GN: I'm ok with this as-is
… these requirements are together in WCAG
EO: agree with both, not sure
SAZ: feel Animations is misplaced here but not sure where else
… there are other animations, such as carousels
… also the concept of "change of context"
… these all kind of relate to user interaction and animations
… but not necessarily seizures
CD: not sure misplaced here
… but agree with Shadi
… many more criteria from guideline 2.2
… kind of fall under Animations umbrella
DM: so need to broaden the scope for sure
… then can decide where it goes
EO: agree with Carlos and Shadi
… is Animations the correct term?
SAZ: where do we deal with the other types of animations, auto-playing audio, change of context, etc?
HK: moving content, like carousels, ads, etc.
… maybe focus on distractions? content that is distracting
Missing Examples of Visual Patterns
DM: refer to "distinguishable styles" but don't provide examples
… should we provide examples?
… or enough to say distinguishable styles
SAZ: don't think we should provide examples
… also didn't in the developer modules
CD: agree, out of scope
… courses should provide these specific examples
… not the curricula
EO: agree with Carlos and Shadi
… same approach like previous modules
SAZ: maybe make more specific but not as far as examples
… for example, that links should be distinguishable from the text around it
… or heading levels to be each distinctive
DM: so not provided the specific patterns but being more specific
… also the sign-posting to the coding aspects associated with this
HK: programmatic aspects seems out of scope of this part
… more about organization or structure
… for example, for "ensure headings are nested"
SAZ: agree, these seem more navigation and orientation
… rather than layout and spacing
HK: also should focus on the visuals
CD: partially agree
… layout may have particular meaning for designers
… yet they also need to mark-up the content
… not sure it needs to be moved
SAZ: maybe split?
… visual aspects of headings and hierarchy is one
… and working with developers to ensure coding is another
DM: good input but might not fully address concern from Howard
HK: maybe "Layout, Spacing, and Structure"
… visual cues, lists, headings, are for me layout
DM: will look into it
… but previously we wanted to move away from terms such as "structure"
… because too developer-oriented
EO: need to mention terms such as "responsive design"
… designers look for these types of terminology
DM: Gerhard mentioned that last time
… will look into it
Wrap-Up
DM: will integrate your feedback
… and work on other modules
… might not neet next week
… but might have a survey soon
… with all 7 modules proposed
… with just the learning outcomes
… to move things around etc.
<Daniel> S/ neet / meet /