Meeting minutes
<Jennie_Delisi> Apologies - will have to drop at 45 minutes after the hour and will miss next week
Introducing new member Tayef Farrar
<Jennie_Delisi> * Welcome Tayef!
tayef: senior experience designer at aetna health and located in NY USA.
<Abi> Welcome Tayef!!
@Eric and @Len are serving as COGA buddies to help new members orient
Holidays
julierawe: no call Thursday, December 25; no call Thursday, January 1
<Jennie_Delisi> I am working both Mondays
julierawe: should we have a call Monday December 22 or Monday December 29?
<Abi> I'm working both
<tayef> I am working both Mondays
<LenB> I'm not working Dec 29
<Eric_hind> I'm available
I am not working 29 Dec
julierawe: will confirm with Lisa to see if she can chair December 22
WCAG 3 subgroup participation survey - responses due December 15th
<julierawe> https://
<tayef> Yes, I'm familiar with AGWG and attended their first weekly meeting last Tue.
julierawe: WCAG 3 subgroups have been on pause recently. Survey sent out today to ask about interest in participating in AG subgroups.
julierawe: AG subgroups have changed recently, including "Text and Wording subgroup" which will include Plain Language, Text Appearance, and Text-to-Speech
julierawe: "single Sense and Contrast" subgroup, "Sign Language" subgroup, "conformance" subgroup are new (featured at end of survey as items 8, 9, and 10)
Jennie_Delisi: has been part of structure subgroup, but may be more helpful in conformance group - can only do one - does Julie/COGA have a preference?
julierawe: Rain has been active in layout and structure subgroup, so Jennie may be able to move to conformance for better COGA representation - will double check with Rain
Jennie_Delisi: if other COGA members can attend conformance meetings, that would be good, since Jennie will participate asynchronously
julierawe: survey responses due December 15
julierawe: LenB is one of leaders of text and wording subgroup, which has good COGA representation
WCAG 3 conformance discussion at tomorrow's AG meeting
julierawe: tomorrow's AG meeting (11 ET) will be discussing early draft of conformance model
julierawe: anyone is welcome to attend to learn more
johnkirkwood: text and wording subgroup had different name previously?
<LenB> it used to be "Text Appearance" and then "Plain language, Consistency, and Familiarity (Formerly titled “Simplified Written Content”)"
Thanks, LenB!
[Time-sensitive] COGA feedback on APA paper on CSS scroll-triggered animations
<julierawe> https://
Eric_Hind: coming from Accessibility Platforms Architecture (APA) group that does horizontal reviews - meets Wednesdays. Reviews W3C publications for accessibility issues and concerns
Eric_Hind: APA is very Github-oriented; COGA working on improving participation, since Github poses some participation barriers
<Eric_hind> https://
Eric_Hind: CSS team proposing animation-triggers and timeline-triggers rather than activation through Java Script. Requesting feedback on accessibility considerations.
<Eric_hind> https://
Eric_Hind: requesting feedback on 5.2 Timeline Triggers
Eric_Hind: time-sensitive - would like to have it reviewed for feedback ASAP
Eric_Hind: no hard deadline, but next few weeks
<Jennie_Delisi> Text to speech tools - interrupt reading? availability of animation to be read
<Jennie_Delisi> Visuals - ability to pause - will the pause stop hide be considered?
Jennie_Delisi: sound and dizziness issues need to be considered as well
Tiffanyburtin: vestibular and motion sensitive users - need for reduced motion options, even with pause-stop-hide options. Need choice in appearance
julierawe: does current draft have a no-motion browser-level preference?
Eric_Hind: will check, but doesn't believe so
Julierawe: can send a Google Doc to COGA to share thoughts
Eric_Hind: APA most concerned with 5.2 (timelines), but feedback on other areas welcome
LenB: browser-level reduced motion still often requires publisher to identify in CSS what that reduced motion state is - is that addressed or defined in the document?
Jennie_Delisi: what is considered the elements of an animation? Visual only? Visual with sound?
Eric_Hind: believe that is defined in other documentation
Jennie_Delisi: possible to add a glossary or link to those definitions in this document? For term "animation" specifically
<julierawe> https://
<Jennie_Delisi> * language like risk, harm...or potential risks and harm
julierawe: need for note that explains that if you don't include reduced motion options, there are consequences for users. Are there places in this draft that talk about user needs or why these options are important?
Eric_hind: don't believe so in the current draft
Jennie_Delisi: AG is thinking through possible future states - is that true for this as well? If so, need to consider audio, VR, etc
<Jennie_Delisi> * Have to drop. Talk to everyone in 2 weeks.
tiffanyburtin: re: choice in appearance; if user choice is available, choosing not to have extra motion, paralax shifting, etc., turning it off completely is an extremely useful option. If reduced motion is set at browser level, but the site doesn't listen, that still causes problems. Need user preference to turn off completely (e.g., turn off Java
Script, but need user to know if it's the Java script that's causing the animation)
julierawe: is the need for choice in appearance in addition to browser-level reduced motion?
tiffanyburtin: could be a separate option. Especially thinking through future technologies
julierawe: seems like there needs to be a section in document that emphasizes potential harm for users
julierawe: and future-proofing
Eric_hind: reiterate that current version does not address accessibility
tiffanyburtin: Not fully vetted/ read yet but cybersickness seems to be a new term in addition to vestibular: https://
julierawe: please supply feedback to Google Doc by December 19; Eric will deliver that feedback to APA
ACTION: item: Julie will share google doc for COGA members to add feedback by end-of-day December 18th
ACTION: item: Eric will be in charge github issues based on our feedback