– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

+present

<lisa> next item

<lisa> https://www.w3.org/WAI/GL/task-forces/coga/wiki/Scribe_list

<lisa> next item

Lisa requested "Please could people help with scribing if they have a moment to sign up".

<lisa> close item 4

<lisa> next item

Rashmi would like a subgroup meeting this week

Sructure subgroup meeting same time as this meeting

<lisa> next item

Next two weeks there will be no meetings for coga - holiday break

Discussion on mental health - open questions

Julie requested if Clear language could have some more meetings. Rachel will be meeting in an hour about the feedback timeline

Julie will be sending around calendar invitations for Clear Language activity

<lisa> https://docs.google.com/document/d/1K4tI9SV4lsDXzCdaEAXExeL3f061__Sy06lfGV9mLvY/edit

Link to the mental health proposal

<lisa> Proposal 1 : Add sentence or paragraph for fine motor skills Add a paragraph or pattern explain comorbidity and problems for with High-demand For good fine-motor skills, eye hand coordination and rapid information processing. Alternatively we can make this a pattern Where: Moving controls and Clearly Identify Controls and Their Use (Pattern) and a general statement Text suggestion : People]with mental health and cognitive disability also ma[CUT]

Rashmi will share her screen

Main document for the subgroup

The document has 4 proposals and tables - research about existing background to support Content Usable.

There are a few ideas that can be added to Content Usable such as fine motor controls and this fits with co-occurring factors such as small buttons that fit with some mental health issues, cognitive impairment as well as motor problems

Lisa added the problems of hand / eye coordination and visual difficulties,cognitive decline...

Lisa asked how do we deal with things that come together when there are neurological difficulties but something like fine motor skills could mean this needs to be added to all of WCAG - so suggested that a comment should be added to sections and one example includes tiny moving object controls

So should there be a separate pattern or just add these statements to other sections?

<lisa> option 1: add text to the 2 patterns as suggested

<lisa> option 2 : new pattern for fine moter and eye hand coodination

<lisa> option : 3 : discuss or other

Jan asked how much complexity would Option 1 cause when working through the patterns

Lisa showed how short pieces of text could be added as often the topic has been mentioned but just needs emphasing

<lisa> 1

<Eric_hind_> 1

<abbey> 1

<tburtin> 1

<Jan_> +1 for option 1

<Rashmi> 1

<Jennie> 1

Jennie said that by adding to the existing pattern it would allow those who have cognitive impairments would see it in the patterns as fitting their other difficulties

+1 for option 1

<lisa> Proposal 2 : Add sentence or paragraph for Limiting the Topics/Subjects covered per page Minimize the number of topics a page covers .Minimize the number of different subjects an application addresses Page contents should be organized using minimal independent topic areas.Try to group all the hyperlinks for a given topic together in one area of a screen.The diversity of topics covered, and the complexity of their designs likely caused significant imp[CUT]

Rashmi - next discussion was about limiting topics on apps to make it easier to find topics -

<julierawe> Ha, thanks, Jennie

Jennie mentioned how developers consider what they write is under their control but when it comes to items that are injected into a site are seen as separate and so not in their control th

Need to consider the issue of how we deal with content that is pulled in and how we can deal with this aspects

<Jennie> *Thanks for clarifying, Rashmi!

Rashmi confirmed that this pattern is about content controlled by the developer

Lisa wants to put the content that is pulled in should be added as a separate suggestion

<lisa> option 1: add text / bult point to the 2 patterns as suggested

Option 1 add text and bullet points to the patterns that are already suggested

<lisa> (may involve name change

<lisa> option 2 : new pattern for fine moter and eye hand coodination

<lisa> option 2 : new pattern for this

<lisa> one topic per page

+1 for Option 1

<lisa> +1

<Jan_> +1 to option 1

<Eric_hind_> +1

<Rashmi> 1

<Jennie> 1

<tburtin> +1

<lisa> next item

Lisa showing her screen about the AGWG Training - they are happy to support us.

There are likely to be tighter timelines for commenting on issues on Github. There should not be comments on the old verionon

version

Rachael has added that there will be a 'coga' label and items are merged into a staged queue

There will be well titled comments - that may have links - issue may go back but do not always have to have comments

Things do not always have to be commented on.

Lisa still feels that there may be times that those with cognitive impairments may not be able to work on it all can have supporte t

<Zakim> lisa, you wanted to say testing and support calls?

Testing will also be an important time to give support as so much happens at that time

Rachel is concerned about the complexity of setting up notifications

Rachel showed her screen with an example of an issue that is then linked to a google doc t.

<Jennie> *Thank you for clarifying, Rachel!

The tag for 'coga' would allow people to just engage with those comments that are relevant

The chair of the groups would be able to create summaries and so would not have to scrill through all the comments

Jan asked if the training was recorded

<Rachael> https://github.com/w3c/wcag3/pulls?q=is%3Apr+is%3Aopen+label%3Acoga

<Zakim> Rachael, you wanted to ask about timing of engagement

The link above is for the coga information on Github

<Rachael> training: https://www.w3.org/WAI/GL/wiki/Onboarding_for_working_in_Github

The content from the taining is available on the link above

<Jennie> *Thank you for the video snippets, Rachael - those will be really helpful!

<Jennie> *Apologies, have to drop

Thank you Rachael for all that work on the training

Julie asked if the spint team does not have a coga person available - how do we keep up with other items on AGWG

Lisa suggested it might also help to have training for AGWG on aspects of coga difficulties

Rachael mentioned that the draft will be discusse at TPAC - the process will be phased with exploratory options - Coga does not have to be in each meeting just engaged with each stage so many points and chances for discussions.

<Rachael> https://www.w3.org/2002/09/wbs/35422/tpac-2023/

TPAC will mainly with virtual - link to participation survey.

Lisa asked what is on this week's agenda

<Rachael> Thumbs up this github: w3c/wcag3#9 (comment)

Clear Language in the next few hours...

<Rachael> https://docs.google.com/document/d/1inXby8ML3xFJRJBXtPbisbqvGE2gACixbEmqlG7mAYA/edit#heading=h.qtwegsl6du2c