<scribe> Meeting: COGA Review of WCAG 3
Scheduling link: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uggxirp4slpc#heading=h.xvuinihmbhgv
Link to co-location/proximity issue: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.xhbqn69zszr5#heading=h.snl8q7g6agvy
Link to updated motion issue: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.7btf7qjplo1i#heading=h.ug544rrtrwde
Link to Help and Feedback issues: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uubdkgkddw8k#heading=h.duq826e1a3p
Link to co-location/proximity issue: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.xhbqn69zszr5#heading=h.snl8q7g6agvy
Group shortened the first sentence and added new first paragraph.
Jennifer asked about grouping related items, such as labels, so that this applies to non-sighted users as well.
julierawe noted the draft already mentions that many WCAG 3 provisions specify programmatic association but leave out what would help sighted users.
Group removed 2 examples from the controls examples
Group removed them because current wording may be controversial and we don't want to distract from the larger issue this draft is raising.
Group removed a keyboard user need.
Group shortened the keyboard section so it simply notes that WCAG 3 already has a "Keyboard effort comparable" provision.
In More Details, group added 'to the point where users may abandon the process or task."
Group voted.
Jennifer reviewed the table at the top of the tab.
Jennifer folded the sensory characteristics into a different issue.
Jennifer updated the status.
Group reviewed sensory characteristics: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uubdkgkddw8k#heading=h.e7lg9gvz14cu
Group aligned and voted on this issue.
Group discussed "Support available": https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uubdkgkddw8k#heading=h.8b7qvjymowao
Group aligned and voted.
Group discussed "Feedback mechanism available": https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uubdkgkddw8k#heading=h.90jdv0hcb5da
Group aligned and voted.
Group discussed burden on memory, especially with voice user interfaces: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uubdkgkddw8k#heading=h.rhjlfc148kcp
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Rashmi, kirkwood, lseeman, julierawe, LenB, Jennifer Present: Rashmi, kirkwood, lseeman, julierawe, LenB, Jennifer No ScribeNick specified. Guessing ScribeNick: julierawe Inferring Scribes: julierawe WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]