Meeting minutes
<Lisa> disabilities? " in our documents? (If time). See issues document at https://
<lisa> presesent+
<lisa> Am I in the right room?
<lisa> next item
Eric_Hind: Eric will scribe
<lisa> next item
<lisa> close item 1
<lisa> next item
Lisa: We have automatic calendar invite as well as my normal updates - should we merge the agenda from Lisa's email into the W3C COGA invite? Are there other things we want in the W3C COGA invite?
julierawe: Is the W3C invite zoom link completely open to anyone?
Lisa: Currently this invite is sent to normal COGA invitees - not to the list.
julierawe: Current way done by Lisa seems easy and easier.
Lisa: We will continue to use the W3C style invite.
Lisa: W3C calendar (after login) for COGA has all the same invites as well as Editors call, mental health call, subgroup fall. These should pop up in your calendar. All these meetings should be present/listed. Organizers can go here to edit the meeting; content, invitee list, etc. Just make sure to save some changes per meeting, not for all
meetings.
Rain: This seems reasonable and workable.
<lisa> next item
Lisa: Just to confirm, one invite will be sent in the future (the w3c automatic invite).
Lisa: Organizing feedback related to content of Making Content document - where to save it? Actions document, Comments document, Github issue tracking 2024 document (new section, feedback from other sources like Community groups, Structure studies, I18n).
Rain: For the most part, yes, this makes sense but will want to keep some actionable elements in the Making Content document.
<lisa> next item
Lisa: Resolved to ping folks about given issue while things continue
Lisa: We currently have a very long name "Making Content Usable for People with Cognitive and Learning Disabilities". Rain has brought up shorter main heading and longer secondary subhead.
<Rain> Proposal based on what came out of the studies and did well in the studies: "Cognitive accessibility guidance: making content usable for people with cognitive, learning, and developmental disabilities and differences"
Lisa: Cognitive impairment definitions may be impactful to the proposals.
<lisa> change the name to cognative accessebility guidence, with a subheading of making content useable to ....(list)
<lisa> +1
<DavidSwallow> +1
<JeanneEC> +1
<Eric_hind> +1
<Frankie> Suggested wording for subheading: Making content that accommodates cognitive, learning, developmental and mental health differences and disabilities
Lisa: This vote is about Rain's proposed main title heading with a subheading related to a list that is to be determined
<lisa> we dont have final wording for the subheading
<tiffanyburtin> +1 with rewriting the sub heading
<julierawe> +1 for Rain's suggested main title. More discussion needed about what comes after the colon.
<Frankie> +1 to main heading “Cognitive Accessibility Guidance” and have suggested subheading wording
Rain: FYI, this proposal is based on many conversations (Feedback)
<julierawe> +1 to David's comment
DavidSwallow: Feel that Making Content Usable (current) isn't as pointed (to the point) as our proposal.
<lisa> next item
Lisa: Questions have been brought up on specific disabilities - although they are mentioned in the opening paragraph.
<lisa> Suggested wording for subheading: Making content that accommodates cognitive, learning, developmental and mental health differences and disabilities
Frankie: added some suggested wording in IRC
Lisa: We will be using 'main' or 'go to' phrases throughout the document - "Cognitive and Learning disabilities" is our current go-to. This has some cultural dependency and may not mean quite the same thing to different jurisdictions.
Lisa: The term 'disability' was used a lot because of mandates of inclusion of people with disabilities (like ADA).
<julierawe> Another suggestion for subheading: Removing barriers for people with developmental, learning, mental health, and other kinds of cognitive differences and disabilities
<julierawe> Suggestion for replacing "cognitive and learning disabilities" in the document: "cognitive differences and disabilities"
Lisa: We should open things up to alternatives... see IRC
julierawe: "Cognitive differences and Disabilities" is proposed.
julierawe: Propose to have a subheading that is short, followed by a list of COGA focus areas
Lisa: "COGA disabilities" which pops up a long list?
Frankie: Step further back, since the wording changes based on accommodation. Look at less judgemental language (such as memory impairment, focus challenges).
<lisa> franki can you work on: Support adaptation and personalization.
<lisa> People with cognitive and learning disabilities often use add-ons or extensions as assistive technology. Sometimes, extra support requires minimal effort from the user via personalization that allows the user to select preferred options from a set of alternatives. Support personalization when you can. Do not disable add-ons and extensions!
<lisa> Sometimes users can receive extra support through personalization.
<lisa> See also:user needs,design patterns, mappings to scenarios,and user testing for objective 8.
<lisa> Test with real users!
<lisa> Involve people with cognitive and learning disabilities in the research, design, and development process. They’re the experts in what works for them. This includes involving people with cognitive and learning disabilities in:
<lisa> focus groups.
<lisa> usability tests, and
<lisa> the design and research team.
<lisa> See also:working with users with cognitive and learning disabilitiesand section 5.
<lisa> https://
<lisa> https://
Lisa: Frankie, can you do an off line review and provide feedback based on this conversation.
Frankie: Yes, can do.
Rain: The community groups have given us a lot of feedback, some contradicting. They are going to meet to give feedback on patterns for now - once we have a revision, they may be able to provide a better sense of feedback on something more concrete.
Rain: We are shifting new patterns in and will have opportunities to implement new and better language related to this discussion.
Lisa: ask is to add your phrasing to the Github issues tracking November 2024 "Suggestions" section. Give advantage, disadvantage and feedback in appropriate table columns.
julierawe: For the folks not on the call - could we send out a 'homework' email around giving their input and review.
<julierawe> I have to jump to another meeting—thanks, everyone!
Frankie: Will follow to Lisa's email.