Meeting minutes
Relating what is taught to the users it affects https://github.com/w3c/wai-curricula/labels/Relating%20what%20is%20taught%20to%20the%20users%20it%20affects
Daniel: some comments noted bias towards screen readers
… how to address the different audiences each time
… in the context of coding
… have been making some adjustments
Daniel: in topic "Headings"
… split first learning outcome into two
… text-to-speech
… and visual landmarks
Howard: can see emphasis on screen readers in this context
… could have headings without the correct markup
David: agree, since this is focused on developers and markup
… may also be good to mention misuse of headings for visual presentations
… like marketing slogans
Estella: good to include other user groups
… often too focused on screen readers
Daniel: would need examples of assistive technologies that use markup of headings
Estella: more on the styling aspect
Carlos: agree with trying to make this as agnostic as possible
… but visual aspect pretty easy to understand
… can think of other uses
… to understand how the content is structured
… maybe motor strategies
<eoncins> +1 to Carlos
Daniel: aware of some browser extensions to browse by page regions
<sloandr> +1 to using "text to speech" over "screen reader" as a general default term, unless the issue is specifically relevant to screen readers
<Carlos> +1 to "text to speech"
Howard: search-engine optimization
<Howard> https://www.searchenginejournal.com/heading-tags-for-seo/341817/
Howard: best practice for SEO
Shadi: seems more business case
… related but not necessary
Howard: maybe footnote
Daniel: have examples of this in images
… mention SEO there
… could add it here too
Estella: agree with Howard, think it is very important
… important to mention as part of universal design principles
David: agree there will be SEO benefits to many of the coding aspects
… a little weary of this getting too much
… and potentially drawing away from the actual purpose
… if we can sign-post as secondary benefit
… but keep focus on the primary objective
… and make sure to not portrait accessibility as only worthwhile when there is a business benefit
Daniel: hearing that there will be some bias to text-to-speech
… and that it is good to expand
… but to be very careful to keep the focus
Carlos: agree with David's concerns
… not sure if need to be learning outcome
… need to check if some of this may be covered in the Introduction curriculum
Daniel: somehow covered in the Introduction curriculum
… but also had perspectives that some level of repetition could be useful
Shadi: agree with Estella about explaing purpose and context
… but also with David on maintaining focus
… maybe too much as learning outcome? maybe better teaching idea?
Estella: developers need to understand the audience and why they provide the code
Carlos: trying to put myself in the shoes of users of courses, the developers
… not sure if these should be learning outcomes
… maybe teaching ideas
… motivational aspects seems to be more for the Introduction curriculum
Shadi: maybe also switch first two teaching ideas to de-emphasize screen readers here?
Teaching Materials and Resources https://github.com/w3c/wai-curricula/labels/Defining%20the%20purpose%20of%20elements
Daniel: suggestion to add <picture> element, which I will be doing
… also suggestion to add CSS as competency
… and to only refer to specific Perspectives Videos needed
<Daniel> https://deploy-preview-232--wai-curricula.netlify.com/curricula/developing-accessible-content/
Daniel: however, disagree with removing long-desc
David: not sure what to do with elements not strongly used
… might be important to have a consistent approach throughout the curriculum
… can we use accessibility support matricies?
Shadi: agree need general approach for accessibility support
<sloandr> I'm thinking of sites like https://a11ysupport.io/ that might help inform discussions on whether and how to address certain elements where current and future support may be in question. It would help us form positions in deciding how to address these edge case situations.
Shadi: developers need to know when it is appropriate to select different techniques
Carlos: not strong on removing long-desc
… agree with David's proposal
Next meeting
Daniel: next meeting on 21 July
… there will be work for you to do in between
… also welcome to comment on the third agenda item we did not get to today
… or any of the other issues on GitHub
… thanks for your valuable input