Meeting minutes
<Rain> Draft desired outcomes based on the functional needs and user stories exercises
+present
<Rain> meeting agenda document is at https://
Set up scribe
Review the functional needs, user stories, and document reviews that were done during the pre-work
<Rain> my apologies, I'll be right back
<Rain> I hit the wrong button
<Rain> first order was to take a look at the functional needs section of the scratch document,
<Rain> so if you want to head there, I'll be back in a moment!
Rain: Will add/create functional needs in the scratchpad
Rain: per conversation with Sheri, add outcome of Safety from looping animation
Rain: Additionally, add outcome related to pseduo-motion/flashing safety
<AndySomers> physical or psychophysical
Rain: Functional Need added: User safety even with neurological sensitivity to motion
Rain: Functional Need added: Added Jedi
Rain: Functional Need added, Jedi FAST comments.
Rain: Sheri asked to add motion sickness directly as a specific point; will expand the list at this time.
<jeanne2> +1 to Rain's safety addition
Rain: Functional Need added, Be able to complete a critical flow without unintentional redirection (e.g. site redirection before submit of a task)
+1 as well
<AndySomers> dark patterns
<jedi> +1 to sheribyrne on removing higher level categorization for now
Sheri: Request to avoid high level categorization (for now) to allow better differentiation
Andrew: add Functional Needs related to harm as related their ability to do things effectively (compared to harm as an singular negative event)
Rain: As related to Andrew's comment; added visual fatigue
<Zakim> jeanne, you wanted to say that we should not be constrained by FAST
<AndySomers> Do we develop this as a harm category (general) as opposed to harm from motion
<AndySomers> +1 able to takebreak
Rain: Functional need, complete a critical flow without experiencing visual fatigue
<AndySomers> some people need motion
Sheri: Add motion personalization, be confident that motion personalization will be respected
Rain: Functional Need add: Some people will rely on motion
<AndySomers> haptics?
Rain: Q to Jeanne, this is limited to visual landscape?
Jeanne: Initially, that was mandate but there isn't a mandate and this should be moved as a new guideline
Rain: Haptics, such as pain from device vibration
Rain: Audio: such as disorientating spatial effects (doppler, left to right channel, sound like it's behind creating triggers, localizing sound)
Murray: Binaural audio could also be added under Audio
<jedi> +1 to Murray on Binaural audio, plus "dichotic listening"
Andy: Q to add General Harm category? (per parallels with other groups)
Rain: For now, we may need to stick to our more specific scope (more granular)
<jedi> +1 to AndySomers on involuntary movement reaction
<Zakim> jeanne, you wanted to talk about common vs unique user needs
Jeanne: Later in process, we want to identify common issues, and those that oppose or are inconsistent
<AndySomers> personalization is the holy grail of accessibility
<jeanne2> +1 as important to track topics that need personalization
<murray_moss> +1
<jedi> +1
+1
Sheri: Per 2.4.3, we should add auditory organizational memory (if including sound)
<Rain> ack?
<AndySomers> Auditory: I hear language in a musical way, it interferes with language
Rain: Under 2.4.3; internal cognitive mapping can be interfered with by motion; how can this be broken down into functional needs.
<AndySomers> motion does not change relative orientation and placement of objects
<AndySomers> or, motion does not change arrangements of itmems
Rain: Jedi recommendation, graphical memory
Rain: Add per Andy, Use without motion changing the arrangement or focus order
Rain: Example added to 2.4.4.1 Limited short term memory: use without having to remember something that goes away as a result of motin
Andy: Add under 2.4.7 Cogntivie and sensory intersection; use with the ability to only see something when it is still
Rain: All should review and feel comfortable to review the functional needs list; add any functional need that you might think would be missing.
+1
<jedi> +1
<murray_moss> +1
<AndySomers> +1
Rain: Will update text to plain language
<Rain> zakim: make minutes
<Rain> * thanks jeanne2
Draft desired outcomes based on the functional needs and user stories exercises
<Rain> We will be working on item 3 next week
<Rain> * aw, thank you jeanne2 !