Meeting minutes
Requirements for designers and authors to convey page structure and semantics
DM: want to go over the sign-posting approach
<dmontalvo> Module 1, topic 1, learning outcomes, last two bullets
DM: had issue with word "complimentary"
… does this example of rewrite work better?
HK: agree with how this is written
… however, not a WCAG requirement
… i'm fine if that's OK
SAZ: good point, need to be careful not to imply requirement
DM: yes, can look at this aspect
HK: wondering about the term "distinctive" as opposed to "key"
DM: will look at that but considered "key" in the past
HK: maybe "principle" or "relevant"
https://www.w3.org/WAI/tips/writing/#use-headings-to-convey-meaning-and-structure
SAZ: either use examples closer to actual requirements, or add some qualifier
… for example "list requirements and good practices ..."
… would run by Shawn and the planning team, maybe EOWG is interested and has time to chime in
<dmontalvo> Module 1, topic 2, learning outcomes, last bullet
DM: worried here about relation to "HTML elements"
… content authors don't really use HTML code
SAZ: maybe reword to move away from "mark up" and be less cody
… something like "use the correct type of structures, such as lists and paragraphs, to convey the intended meaning" or such
HK: don't feel so strongly about "mark up" but agree overall with that suggestion
… or "explain that these lists are identified as 'ol' or 'ul'"
SAZ: think that may be too techy for some authors?
HK: agree, maybe specifically say "numbered lists" and "unordered lists"
DM: yes, differentiating these types of lists makes sense
<dmontalvo> Module 1, topic 4, learning outcomes, last bullet
DM: thoughts on this one?
https://www.w3.org/WAI/tips/designing/#create-designs-for-different-viewport-sizes
SAZ: maybe just one example rather than both?
… could try to use viewport example from Design Tips?
HK: agree, this seems too much
… would be good to simplify
Requirements for designers and authors to write menu item texts and to style menus
<dmontalvo> Module 2, topic 2, learning outcomes, last 2 bullets
<dmontalvo> Module 2, topic 2, learning outcomes, last 2 bullets
SAZ: topic title jumps out at me
… not really about styling
… maybe more about behavior or states?
HK: third bullet seems vague
… how would I convey the states of a menu
… but don't have specific suggestion
https://www.w3.org/WAI/tips/designing/#provide-clear-and-consistent-navigation-options
https://www.w3.org/WAI/tips/writing/#make-link-text-meaningful
SAZ: agree with Howard's concern on third bullet
… seems more designer-related
… suggest to drop and also switch latter two bullet items
DM: developers need to code the different styles
SAZ: good point but in this case needs to be clearer and more direct
<dmontalvo> https://www.w3.org/WAI/curricula/
SAZ: maybe even bump up listing requirements for designers
… then next bullet could be along the lines of "code styles provided by designer" or such
https://deploy-preview-238--wai-curricula.netlify.app/curricula/developing-accessible-content/
https://www.w3.org/WAI/tips/developing/#associate-a-label-with-every-form-control
https://www.w3.org/WAI/tips/writing/#provide-informative-unique-page-titles
HK: "list requirements" could be misunderstood the developers provide requirements for authors or designers
… a little ambiguous
SAZ: good point, maybe need to adjust sentence structure?
… using another verb might not help along
Wrap-Up
DM: will be sending out a survey on modules 4, 5, and 6
… these have not been reviewed yet
… and optionally also modules 3, 2, and 1 if you can get to it
… probably no meeting next week but will notify the list