Meeting minutes
<lisa> scirbe+ Beca_Monteleonec
<lisa> scirbe+ Beca_Monteleone
<lisa> next item
Structure call upcoming on Thursday to start moving things over - 12 EST 20 March
<Charli> ? Has a meeting request been sent out for the Thursday meeting?
Lisa: Be sure to check time with time change.
Lisa: Please only attend Structure meeting if you are able to commit to helping update structure in the long-term (e.g. can attend multiple meetings)
Lisa: helping with structure would mean converting old version of Making Content Usable to new structure proposed by structure working group. First meeting scheduled so Rain and Frankie can attend - future meetings may happen at other times
Charli: would like to be involved with structure group
Rain: work conflict from 24 March to 7 May and so will not be able to attend meetings during that time. Will be at 20 March meeting. Will share document with Frankie and others with as much info as possible
Julierawe: Asking purpose of these planned meetings
Lisa: Actual implementation of new structure - working meetings to rewrite Making Content Usable
Lisa: Need to have some people from the structure subgroup there so that there is not duplication of conversations
Lisa: Do not need to know HTML or github to contribute - starting in Google Docs
<tiffanyburtin> When would the meetings be again
First call - 20 March, 12 ET
<tiffanyburtin> That is a great time for me. Will we receive calendar invites for this?
<lisa> If this is something you want to work on please fill out the attached table
<lisa> https://
Lisa: Spreadsheet is asking for general availability starting next week (24 March)
<EA> In the UK the clocks go forward 1 hour at 1am on the last Sunday in March
Lisa: Will need to update the times for England/Europe due to time change
Charli: Reminder to be attentive to COGA members' pronouns
Jeanne: Want to be involved in structure meetings
Jeanne: restructuring of Making Content Usable was presented at CSUN
<lisa> If this is something you want to work on please fill out the attached table
<lisa> https://
<Zakim> Rain, you wanted to say I can make only the first half of that
Lisa: Internationalization meeting 20 March at 11 ET
Lisa: Github Editor's call meeting 20 March at 9 ET
Lisa: Github Editor's call agenda on finishing drafts of issue papers
Becca_Monteleone: regrets for Editor's call this week
<lisa> next item
Lisa: community meeting notes feedback. From previous conversation, re: endless scroll. If making a new pattern, need more research on solutions
Lisa: multimodal communication - need issue paper
Lisa: Gesture interactions (mobile) - community group states that sole reliance on gestures is problematic
Rain: google recently did some research on this; we need to address this; not sure proposed solutions in the doc are sufficient
Rain: There are issues related to memory; building in affordances important.
Lisa: 4.2.5 may address this if we have explicit examples including gestures
Rain: May need to call attention to this specifically because people use Making Content Usable as a checklist
Lisa: Is there enough research to do a second pattern?
Rain: Need to connect with Kiki to verify
Rain: We know it's an issue, we just need to make sure that we have the research to give appropriate next steps
<Jennie_Delisi> 4 areas: know there is a gesture, get orientation/reminder, know how to turn it off, and
Lisa: proposal - see if we can find the research/ask the community group for the research
<Jennie_Delisi> 4 - ensure we are not duplicating WCAG
<lisa> and allow it to be off
<lisa> (5)
Jennie: WCAG 2.2 does address the ability to toggle off; new potential pattern should focus on the areas not addressed yet
<Rain> +1 to Jennie's point that some of this is already required in WCAG2
<EA> +1 agree - hard to find settings are a problem
Rain: Additional pattern to potential consider - the burying of supports in accessibility settings; people with cognitive disabilities are less likely to navigate the accessibility settings/menus
<Rain> +1 to new research, maybe an issue paper
Lisa: Important and much broader implications than just this issue
Lisa: Adding to suggestions doc for Making Content Usable
<EA> Look at the Lounge settings cog icon and then there is a questions mark - which one will be helpful?
EA: looking at the settings for IRC
… There are settings and a questio nmark
… But it is not just the content of the settings and where you try to find them
EA: As example, looking at settings for IRC has settings cog and question mark - not clear which one is going to help with accessibility settings.
… It can also be that the set of icons (like a cog) and help...can be confusing
* Sorry Becca!
* Thought it was EA scribing
* thanks Jennie!
Jennie_Delisi suggestions: 4 areas: know there is a gesture, get orientation/reminder, know how to turn it off, and ensure we are not duplicating WCAG
Lisa: Next community group item - intentional friction; e.g. when two similar adjacent actions have drastically different outcomes
Lisa: partially addressed by avoiding errors/making it easy to undo errors
Lisa: Some of this issue addressed by patterns under Objective 4
Lisa: propose to return to this item once the new structure for Making Content Usable has been completed and reviewed to see if it's been addressed adequately
<Becca_Monteleone> +1 to Lisa's suggestion
<EA> +1
<Rain> +1 to Lisa's suggestion, as well
Tiffany: agrees
<lisa> no one object
julierawe: is that part of the objective we'll be re-working?
Lisa: no; there is a list of items to review after our current sprints
Lisa: next item from community group is comparisons.
Lisa: supported decision-making paper mentions comparisons; Making Content Usable does discuss comparisons but does not mention problems of deceptive patterns
Lisa: propose 1) adding information to supporting decision making issue paper about deceptive patterns and 2) add deceptive patterns to where it is discussed in Making Content Usable; review both to ensure it's sufficient
<tiffanyburtin> Yes agree Lisa
<Rain> +1 agree
<Becca_Monteleone> +1 to reviewing both issue paper and Making Content Usable to include deceptive patterns re: comparisons