Meeting minutes
<dmontalvo> Date: July 28 2020
FYIs on proposals we have been working on
New layout for competencies to avoid repetition
<dmontalvo> Zakim: https://deploy-preview-238--wai-curricula.netlify.app/curricula/developing-accessible-content/structure-and-semantics/#competencies
<dmontalvo> -
DM: grouped competencies to avoid repetition
… and added expand/collapse to allow skipping
… thoughts on this?
GN: looks good
… like this version much more
EO: like this much more
… but were prerequisits removed?
DM: no, just linked to overview page
<dmontalvo> -
EO: better structured in this new version
<dmontalvo> -
Learning outcomes to sign-post cross references
DM: agreed we need to sign-post related requirements for other roles
… new proposal in topic "Section Headings"
[[describe complimentary requirements for authoring heading texts and designing visual styles for headings]]
… could have similar learning outcomes throughout as needed
… any thoughts on this approach?
<dmontalvo> [[describe complimentary requirements for authoring text alternatives of textual and complex images]]
CD: do you think "complimentary requirements" understood?
… or does it need some description?
HK: little confusing
… maybe example but may get too long
GN: agree confusing without example or such
SAZ: how could we address the issue differently?
EO: think one of the issues is the term "describe"
… would use a more specific verb
… maybe "identify" or "list"
CD: also wonder about the term "complimentary"
… maybe can be more explicit that these relate to other roles
… like "describe requirements for content authors that write headings and visual designers that style them"
GN: maybe "have an idea of how write and design headings"
DM: maybe "list"
… inline Bloom's Taxonomy
EO: also change from passive to active
DM: will take back this input
Broadening scope of Module 2
DM: now also include application menus
… was planning to have them in the widgets module
… but now have them here
… thoughts on this?
https://wai-curricula.netlify.app/curricula/developing-accessible-content/navigational-menus/
<dmontalvo> https://wai-curricula.netlify.app/curricula/developing-accessible-content/navigational-menus/
CD: concerned about complexity of this topic
… requires knowledge of WAI-ARIA
… is this something that students know?
DM: refer to some ARIA concepts in the prior module
… like headings and landmarks
… maybe need to add to the competencies
CD: agree
GN: not sure if application menus should be commonly used
… sometimes misused
… should add comment on that
DM: could be a learning outcome
… scoping application menus
… to clarify when to use and potential down-sides
… not interchangeable to use both types of menus
… explicitly for desktop-like applications
EO: replaced "single-level" and "multi-level"?
DM: not exactly, just organized content differently
HK: good thing is consistency with Tutorials
… easier cross-referencing
SAZ: was definitely not by intention
… started off from scratch to not get biased
… but went in circles and came back to Tutorials structure
… probably good indication for Tutorials!
… or subconcious bias
HK: good thing to have this consistency
CD: looks good
… agree with GN about adding caution note
DM: need to be much more clear about scope of application menus
… and explaining the difference to other menus
HK: maybe specifically add "not common"
… directly in the heading
SAZ: in the past such generic labelling had become limiting
… prefer to do in the learning outcomes
… teachers need to decide what they want to teach
CD: first learning outcome "identify situations where an application menu is appropriate"
… although not sure if that is a competency for developers
DM: "identify" does not mean they are solely responsible for it
… enough to have some degree of awareness
Closing
DM: would like to ask you to go through the two remaining agenda items
… where would you place "images of text" in the current organization?
… and other agenda item is on Module 6
… currently first topic is introduction to WAI-ARIA
… but that repeats the Intro curriculum
… suggest introducing concept of progressive enhancement instead
DM: not sure about meeting next week, will let you know
Introductions
GN: first project on accessible design in 1997
… did some lectures over the years
… look forward to this work on curricula
DM: thank you Gerhard!