Meeting minutes
Putting the keyword at the beginning of the heading. Wouldn't it be going beyond WCAG requirements?
<dmontalvo> https://wai-curricula.netlify.app/curricula/developing-accessible-content/page-structure/
DM: suggestion of "putting keywords at beginning of headings"
… but is that going beyond WCAG requirements?
HK: valid point, so fine with it
Shadi: I would expect this more for content authors.
… IF we start diverging from the context, that could be worrying for these curricula
HK: agree
EO: agree, also on going beyond WCAG where it fits well
… leave it to editors' discretion
DM: thanks, seems more for the content authors document
EO: add as best practice?
DM: could consider for "Teaching Ideas"
… but maybe not appropriate for developers
Shadi: My concern is that we may start deviating, if we add this one, why we should not add the other?
Changing topic title. "Contextual Information of Pages" -> "Meta information about a page".
DM: suggestion to change title of topic
… from "Contextual Information" to "Meta Information"
… wonder if "Meta Information" is broader than we want?
… tried to have narrower view on the specific aspects needed for orientation and navigation
HK: don't feel strongly but did not understand "Contextual"
Shadi: Howard is a native speaker, so we need to take this seriously. Meta is also a bit jargony, though technically more accurate.
HK: yes, "Meta" is a little jargony
Shadi: Changing my mind
SAZ: maybe OK to use for developers?
… technically more accurate
EO: "Contextual Information" worked well for me
… maybe also more from humanistic sciences
SAZ: good points
… maybe pick one approach for now
… and raise it with larger group to confirm if no-one raises it
Action: Daniel to choose approach, and mark it for confirmation by larger group
Including link to tutorials in "Competencies > Knowledge of" section.
DM: suggestion to add links to tutorials from competences
SAZ: how would that work?
DM: for example, where "knowledge of", link to tutorials
OC: expect more or less from the students and instructors?
DM: level of knowledge is different
OC: confuses me
… maybe needs more differentiation
HK: in a sense we are teaching them about this
… not sure how much is covered in earlier parts of the curricula
SAZ: like these ideas
… think ARIA should drop for students
… this is what they learn here
… link to HTML5 spec sections for students
… and link to Tutorials for instructors
… also change from "experience with" to "applied expertise in" for instructors
EO: would also add qualifiers like "basic knowledge" and "advanced knowledge", to help differentiate and emphasize aspects
DM: might be good to differentiate level of knowledge
… so hearing that both descriptions are too similar
… will try to add more
EO: yes, differentiate expected level of "knowledge" more clearly
Action: Daniel to better differentiate different expertise needed for students vs instructors
EO: also "experience with" seems ambiguous
… what type of experience
DM: trying to differentiate sections
SAZ: what terms would work here?
… maybe "Applied Expertise"?
EO: could work
HK: agree with EO
… what does experience mean?
… worked with somebody?
DM: maybe use "Basic knowledge of ..." for students and "Applied expertise in ..." for instructors
Suggestion for students to try out a screen reader or a screen reader emulator.
DM: suggestion for students to try out assistive technologies
… concerned that this could get confusing
… sometimes bad experience if not guided well
… but see the point, and we could add something
DM: took an attempt in this Pull Request
… need to change "use" to "try out" or such
… also added a note
SAZ: agree with this
… 1. could also use "explore" instead of "try out" but definitely not "use"
… 2. note seems far away, maybe needs to be closer?
… 3. note seems focused on screen readers only but should apply to most assistive technologies
DM: note applies to multiple points, so maybe best to leave there and not repeat?
SAZ: works for me
Combining topic "Regions" > Teaching ideas > Bullets 4, 5, and 6 together.
DM: suggestion to combine bullets 4, 5, and 6 of "Teaching Ideas"
HK: think examples of header, footer, and main content really all part of the same page
… lots of real-estate dedicated to these
… we also combine ARIA landmarks
EO: don't feel strongly either way
SAZ: agree with HK
… not really compelling to show different headers and footers
… maybe different types of page layouts
… and explain the functionality of the different page regions in these layouts
DM: sounds good
DM: will update this, and put next modules on a survey