– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

Happy New Year - just getting my fingers warmed up! It is freezing here! Welcome to 2026!

<Lisa> https://docs.google.com/document/d/15HtPkkYx1CIl6bAwP2nsSZKhqTVbqcuMDRz5RmtmvXg/edit?tab=t.p64c5smxfdrc for orention

Link to orientation notes

<Lisa> next item

Each month we start with going over action items - screen shared by Lisa

Plan with topics being worked on and subgroups

<kirkwood> (sorry c ould you put the link in again?-irc issues my bad)

Making Content Usable v2 - two main topics and Welcome Tayef

Also Jen - lisa offering times for meeting up

<Lisa> https://docs.google.com/spreadsheets/d/1Ou0f7XCc5nRLhZD462OP5DA-NHqql2YSC8__lncIuxQ/edit?gid=1626073744#gid=1626073744

Actions document link

Content Accessibility guidlines... first working draft for next version - Julie to update and next 6 months plan...

Julie felt that in the next 6 months - introduction and first three patterns reformated for public feedback. - need to discuss as a group the introduction. Concensus may take time but 6 months seems reasonable.

Need to work on a new title of Content Usable, need to work on a few sections in the introduction area.

Jen is working with Rain on the introduction sections.

Jen mentioned that there were not any new sections but will check with Rain as she is on holiday

Julie has an update from Rain and discussed the coding - Rain to provide template and is concerned that she cannot do the coding. Julie is asking if any others can help with the coding of the architecture.

Lisa asked what was meant by the architecture... take from a Google doc to Github and Lisa has offered to carry out the tasks

Lisa and Julie to work out what is needed to complete the task

Lisa will ensure that the document is accessible inc, accordians etc

Lisa also asked about the icons that work with the outline and for the folders that open etc.

Lisa asked who is doing the graphic design elements

Julie was not sure if there were new items that would be needed that is not already in the next draft of WCAG 3

Julie felt there may be a need to look at the next working draft and Lisa suggested a list was made to check what is missing so action items can be sent out so different people can help out with the tasks.

John suggested that it would be good to do this as a Google doc to show where things are and keep track of the work so people are aware what is needed.

Items can be pulled out so that the current items that are worked on are at the top of the document and others can be found via other tabs etc

John suggested you might even need an accordian sub-group... Lisa uses a pre-made accordian

<julierawe> Two notes to clarify the transcript: (1) Rain said she cannot do the coding for the new template in GitHub. Lisa volunteered to do the coding. (2) The next working draft of WCAG 3 will include icons to open and close accordion drawers. We can review those icons and see if they will work for the next version of Making Content Usable.

Lisa confirmed that the sub-groups could deal witch some of the item discussed at the beginning of each month

Eric mentioned the Github issues about the old document. Lisa mentioned these questions be dealt with by the guidance sub-group on a Thursday.

Detailed issues

these would be dealt with by the Guidance group but broader issues are for the Monday group

These would come as agenda items

Research sub-group 9EST on a Thursday

CFC reached for four issue papers - research modules - sent to APA and AG for comments and now they are Call for Consensus (CFC)

<Lisa> https://docs.google.com/document/d/187NtfTTIs_gpq6gL4zcKqLcNs2qyValFRpoGKrvZt6U/edit?tab=t.0

The link above is for making comments

<kirkwood> can we have a title for the CFC email sent out?

AG CFC's email went out on Thurs 17th Dec so no one has responded to date.... now need to reply to Rachael with a +1

Rachael added that having a +1 is helpful but if no rejections the draft should pass CFC

<LenB> title: Call for Consensus (CfC) closes 7 January 2026: Publish FPWD of COGA Research Modules Note

Thanks Len

Two days away from no having any objections which means that if there are no issues the document can be published

If there are no strong objections it can go forward

Replies are not being seen on the email so everybody is checking...

During all those that emailed saw repies so the problem appears to be resolved

Proposal for changes due to the issues will be dealt with on a Thursday meeting

<Rachael> Here is a direct link to the CFC email if anyone needs it: https://lists.w3.org/Archives/Public/w3c-wai-gl/2025OctDec/0145.html

Working with AG updates

Rachael mentioned that one of the last reviews will be taking place and the Guidelines with be ongoing WCAG 3 next update coming up - with a few reviews by subgroups and then Coga will need to review more of a full review of the document - looking for gaps where coga needs to be involved.

Julie - the WCAG 3 next working draft will include more about the requirements for a web and/or app - requirements per assertion - now included will be the tests that might be done - so people can see how items are tested - so requirements are based on a feedback - so went from development back down to exploratory where more needed to be done and

also there has been some consolidation.

<Rachael> minutes clarification: one of the last reviews before the next update

Subgroups will be involved in further refining so timescales have yet to be set

Len asked when the sub-groups start up again

Rachael suggested that invitations will be sent out in the coming week

Discussions around changes of members to the various subgroups and timings

New for WCAG 3 subgroups meetings should start showing up on official W3C calendars - placeholders may need to be updated.

These subgroups are in addition to the coga ones

Conformance subroup is just for 8 weeks and may be over subscribed. There will be more subgroups for specfic topics

Discussion around lost calendar dates on W3C official calendar but it appears some groups appear to have been lost of the list of meetings.

Lisa to look out for coga subgroup invites.

APA news?

David felt he had no news having been away

Eric Accessible Platforms Group (APA) one of our parent group

Len - TPAC feedback will be represent in the January version of feedback

Lisa and Julie to talk to Janine and Matt about timelines - APA acts liaison between sub groups and so next step to work on use cases o HTML - the Matt and Janine will liaise

Looking at making content understandable by a local user - TPAC presentation - then make use cases about those with cognitive disabilities to see what supports these types of users - Len will make the link to the presentations and the patterns etc so all the information is made available in one area.

Lisa suggested then there is another call to see if anyone else wishes to contribute to the use cases. Then bring it back this group for review.

<julierawe> Links: TPAC's HTML <amount> meeting page has more background: https://www.w3.org/events/meetings/126c9a01-9cbb-47d2-a5c9-7cc17dde0b58/

The initial document would act as roadmap with suggested timescale

Link to the HTML map

<julierawe> Mozilla's initial write-up: https://github.com/mozilla/explainers/blob/main/amount.md

<julierawe> Minutes from the TPAC session about <amount> tag: https://www.w3.org/2025/11/12-amount-element-minutes.html

<Lisa> next item

'Helping people participate in the group' next item

<Lisa> next item

<Lisa> close item 2

<Lisa> next item

Julie wanted to make sure that Jen was aware of the new Coga buddy sytem - Eric and John to act as mentors.

Buddy system - sorry not mentors.

A way to orient to the way the coga teams work - looking at the big picture.

Lisa asked if there was a need for more agenda time on the participation needs please send a note to Lisa