Cognitive and Learning Disabilities Accessibility Task Force Teleconference

08 July 2021


AbiJ, cweidner, Fazio, Jennie, johnkirkwood, JohnRochford, JustineP, Rain, stevelee

Meeting minutes

<LisaSeemanKest> close item 5

<LisaSeemanKest> close item 6

Updates, actions and tracking requests with other groups: https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Actions

Lisa: Mental health subgroup wrapping up lit review (target end of July)
… APA review, do we have feedback from Josh?

Rain: They have feedback that they needed from us, made progress with personalization.

Lisa: Jenni, Rain deadline next week for image subgroup
… Clear words subgroup will meet later today.

actions equests https://www.w3.org/WAI/GL/task-forces/coga/wiki/Actions_Requests

Rain: Francis will join at the beginning of the clear words meeting to demo his project SilverWriter

Lisa: EO has a number of documents that will be released next week. Those docs would benefit from COGA input. Any volunteers to review and discuss with this group so that we can provide feedback?

Rain: EO expects to send docs by July 16 and they will need feedback returned by July 26 (although we can tell them if additional time will be needed).

Lisa: We will need people to read docs, send feedback to the list, and discuss in a COGA meeting.
… Anyone interested?

John K: I'm interested. Can we use Google docs?

Lisa: Yes.
… Working with Silver: As each subgroup considers moving user stories into Silver guidance template, we will need to collect references/links. Should we begin as Google docs and transfer to Wiki page? Need to gather research, testable statements, etc.
… If we know that certain issues will be raised, we should be able to refer people to references/documentation.

<Jennie> +1 - would be great to have a place to collect and review

Lisa: Everyone okay with this approach?


<johnkirkwood> +1

<Rain> +1

<AbiJ> +1

Jennie: From reading different research topics, some of our terminology might differ from the research terms. Can we create a list of keywords?

Lisa: Yes. Let's add a list of tags/keywords to the top of the doc.
… Any volunteers to create Google doc template?

accessible authentification

Rain: I can create the template unless we have another volunteer.

Lisa: APA actions are done. Silver actions are in progress. Pronunciation APA might need follow up. Also will look at two AG comments.

visible controls https://github.com/w3c/wcag/issues/1877

visible controls https://github.com/w3c/wcag/issues/1877

new comunities

visible controls https://github.com/w3c/wcag/issues/1888

accessible authetification

Lisa: We proposed to look at 4 open issues from AG in a subgroup. Does that sound like the right path forward?

John R: Are issues unresolved?

Lisa: Some issues seem to have been reopened.

Rain: We spent a fair amount of time during last 2 meetings to prepare a response for issues related to accessible authentication (password toggle, user uploaded pictures).
… Challenge is that we have varying, strong needs for the SC. Each time COGA has responded, new issues are raised in response to our feedback. Abi has raised good points related to security policies.
… We might need to form a subgroup to examine the issues thoroughly.

John R: That has been going on for a long time and is typical for new, upcoming SCs. I think its important for people to understand that COGA has appropriate expertise.
… Alastair has responded to Abi. I thought discussion was going well because no one has re-opened issues.

Rain: After last call, I sent an email asking for consensus from COGA and additional issues were raised in response.
… We still don't have consensus from COGA.

John R: Is that because not enough people responded or due to -1's?

Rain: Due to -1's.

Abi: I am actively involved with organizations that have significant security requirements related to accessible authentication.
… It seemed that the response was broadening scope of SC, specifically related to password fields, which could cause organizations to claim exceptions around the SC.

Lisa: I didn't think that being able to view your password solved the problem. Didn't seem enough from my perspective. We will still have issues with lengthy username/password combinations.
… I would downgrade that to an advisory technique.

John R: Yes, that will be in the Understanding doc rather than directly in the SC text.

Jennie: Could we look at graduated response as it relates to Silver's conformance model?

<LisaSeemanKest> https://www.w3.org/TR/WCAG22/#accessible-authentication

Lisa: We proposed to look at 4 open issues from AG in a subgroup. Does that sound like the right path forward??

Ignore the last, copy/paste issue

John R: Abi, should we have a conversation and bring our thoughts back to COGA?

Abi: Yes, I can discuss from my own perspective what a cognitive function test is.

Lisa: Does that sound okay, John? To form a small group discussion with Abi, John, Alastair (John K and Lisa volunteered). This is a big issue that needs to be addressed.
… Anyone available to coordinate the time/date of the call?
… John R, do you want to send a list of possible times?

Abi: Happy to take the action.

visible controls https://github.com/w3c/wcag/issues/1877

<JohnRochford> I too must go.

<johnkirkwood> I would say, yes

Lisa: To summarize, issue is related to obscure content in Understanding doc. Anyone up-to-date on this thread?

John K: I've been on top of that thread. Clear instructions seem to resolve issue.

<LisaSeemanKest> we think clear instuction on how to reach the control, that are on the page is enough

Jennie: I'd add "before the control" to the text.

<LisaSeemanKest> we think clear instuction on how to reach the control, that are on the page before the control is enough

+1 Jennie
… Does reading order get forced by the language that has been selected?
… If information is on the left of the control, would it switch?

Lisa: Yes, if properly encoded.

Jennie: Okay with "adjacent" in that case.

John K: Agree.

<LisaSeemanKest> +1

<johnkirkwood> +1


<LisaSeemanKest> we think clear instuction on how to reach the control, that are on the page before or agasent to the control is enough

<Jennie> +1

Lisa: Any objections?

<LisaSeemanKest> ack j

new comunities

<LisaSeemanKest> topic issue https://github.com/w3c/wcag/issues/1888

issue https://github.com/w3c/wcag/issues/1888

Lisa: This issue is also related to visible controls. If you have an icon or visual indicator such as a down arrow, that will indicate that controls are visible by clicking in that area.

<LisaSeemanKest> coga feels that a single control such as an arrow(and text or personlization sematics for more ?) will indicate that contols are availible by clicking here. The full toolbar can be visible on clicking the "more icon"

Jennie: Seems like a great idea to have a toggle to expose additional controls/options menu. Are you comfortable using "right click" function with relevant instructions placed before the area?

<johnkirkwood> clear insturcutions on how to reveal controls ?

Lisa: If we have clear instructions located before the control, that's okay with me. We can explicitly call for clear instructions before the control in the text.

<Rain> +1 to "clear instructions to reveal controls"

<LisaSeemanKest> coga feels that a single control or togel such as an arrow (and text or personlization semantics for more ?) will indicate that controls are available by clicking here. The full toolbar can be visible on clicking the "more icon". clear instructions on how to reveal controls before or agec on the

John K: What about "clear instructions to reveal controls"? That would address the concern about having too many controls appearing on-screen.

Jennie: What about a "more" option visible on-screen without relevant instruction?

<johnkirkwood> “provide clear instruction on how to reveal hidden controls”

Lisa: That relates to common controls and personalization.

Jennie: I think we will be asked how that can be measured. I'd define "clear".

<LisaSeemanKest> coga feels that it need clear how to reveal hiden controls.

<LisaSeemanKest> clear: can be "more" icon with text or personlization sematice

<LisaSeemanKest> clear instructions on how to reveal controls before or agecnt to the controls

Lisa: Please +1 or comment on pasted/proposed response

<Jennie> more icon or other toggle familiar with users?

<LisaSeemanKest> +1

Jennie: Could we add "or other toggle familiar with users"?

Lisa: Yes.

<Jennie> +1 with that change

<Rain> +1 with that change

<LisaSeemanKest> clear: can be "more" icon or other toggle familiar with users" with text or personlization sematices,


<LisaSeemanKest> justien is happy with this

<LisaSeemanKest> clear: can be an icon or toggle familiar with users" with text or personlization sematices,

John K: Okay with me (last version Lisa pasted)

<Rain> +1

John K: Verifying that we have "adjacent" included?

Lisa: Yes. Any objections?

inclusive groups

<johnkirkwood> in agreement

<Jennie> I can participate in reviewing by document, but cannot add more meetings at this time.

Lisa: Moving clear words into plain language for Silver...I want to ensure that we have enough COGA participants involved in re-writing. Anyone interested in assisting?

Chris: I am in that subgroup.

Lisa: Did I miss you on the list of invitees?

Chris: I'm on the list.

<johnkirkwood> where is it located?

Lisa: We wanted to have different user groups review Content Usable and provide feedback if anything was missing. The group started to draft an email and created a tracking spreadsheet, then stopped.

Jennie: Same question as John K., as I know of a group that might be interested but would need to have an orientation session.
… I can handle the walkthrough for the group, and they might have valuable feedback.

Lisa: That works.

Jennie: If you add link, I'll contact them to see if they are interested.

<LisaSeemanKest> https://docs.google.com/spreadsheets/d/1RPD4pRLngZslj-KsRBlxknECCe0q1cDIx1eo0XyFGks/edit#gid=0

David: I received feedback from someone that was trying to teach people with developmental disabilities do user testing. They found the document difficult to understand.

Lisa: We need to capture that feedback, I'm also hearing that they would like a document covering how to do user testing.

David: Feedback was received from someone without a cognitive disability, not an expert in accessibility. Found it even more difficult to try to teach people with cognitive disabilities to do user testing.

Lisa: That's important feedback that should either be submitted as an issue or sent to the list.

<LisaSeemanKest> https://docs.google.com/document/d/1DoohB2-tREjXx7PF6sCi3jLt6OrjE1ciAb0Dcb7FgyU/edit

Lisa: Regarding recruiting, we need feedback on whether or not the patterns were helpful.
… Or if we've missed specific user needs. Maybe we should create a video...

Jennie: I wonder if we should involve outreach group.

Lisa: Assigning to Kris Anne.

<Rain> I'm going to drop as well to get the Silver Help meeting started

<Jennie> Have a good week everyone!

Lisa: Let's revisit in two weeks.

Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).


Succeeded: s/EA/Abi

Succeeded: s/seems/seem

Maybe present: Abi, Chris, David, Lisa