– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

<julierawe> Link to TPAC site: https://www.w3.org/news-events/tpac/

<julierawe> Link to scheduling tab for COGA review of WCAG 3: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.uggxirp4slpc

COGA meetings: Quorum for June 29 and July 6?

julierawe - does anyone here know they cannot attend on either day?

Len can be here both days.

<julierawe> If you plan to attend on June 29, please +1. You can -1 one if you cannot attend on June 29

<Becca_Monteleone> +1 to both

<LenB> +1 to both

<tiffanyburtin> Trying for both

<Rachael> +1 to both

<julierawe> Looks like we may have enough for quorum so we will try to have the meetings on both days.

TPAC: October 26-30 in Dublin

julierawe still too early to register - but does anyone know if they are going to attend? Organizers are colelting meeting and topics right now and are needing to get some attendance info.

Len is planning on being there in person

<julierawe> https://www.w3.org/events/tpac/2026/tpac-2026/

<Becca_Monteleone> similar to Tiffany, our conference travel budget is pretty thin this year, so unlikely I would be able to travel in person

<julierawe> Better link to TPAC site: https://www.w3.org/news-events/tpac/2026/

COGA subgroups: Quorum for Tuesday’s Research call and Thursday’s COGA review of WCAG 3?

<Becca_Monteleone> I can make the research call tomorrow

I can make the research call and Thursday's call.

<julierawe> LenB: Traditionally it's been 3 or 4 of us on Tuesdays. Me, Eric, Lisa, and Abi.

<julierawe> LenB: I can reach out by email and see if they might be able to meet.

<julierawe> LenB: We were asked by Lisa to pick one paper and review it. I used AI to review 27 papers.

<julierawe> LenB: I used AI to remap around those issues. I think we should wait to share that suggesting remapping when Lisa can attend.

<julierawe> LenB: I also want to share some tensions between what we wrote and what the research is saying.

<julierawe> LenB: @rashmi please take a look at the trigger warnings paper.

<julierawe> LenB: There have been studies around trigger warnings for social media and blog posts. There does not seem to be a negative effect for those.

<julierawe> julierawe: Does your research top-up on trigger warnings affect the github issue we drafted about trigger warnings in WCAG 3?

<julierawe> Rashmi: I can attend tomorrow.

<tiffanyburtin> I cannot attend tomorrow

<julierawe> Becca_Monteleone: I can attend tomorrow

<julierawe> julierawe: I can attend tomorrow as well.

https://docs.google.com/document/d/1XWmikm5Ein5CQ02knEJ5iGzO1YJMilTMBJ_aLVCTzs0/edit?tab=t.rfkd7gpxr2qm

ACTION: item: The research subgroup will meet tomorrow to discuss Len's trigger warnings top-up. This will help us get ready to discuss with Lisa when she returns.

Research top off for Trigger Warnings

<julierawe> The research meeting is at 9am Boston time

julierawe I'll reach to John K and see if we're on track to talk Interactive Components.

ACTION: item: julierawe to email kirkwood to see if he is still available on June 25th for second discussion of Interactive Components. Will email the group to let everyone know if the June 25th meeting is still on.

Past meeting Eric pencilled himself in for images.

past meeting Len and Jennifer pairs on help and feedback. That section is now ready for review with the larger group.

ACTION: item: Julie and Len to reach out to Eric about whether it makes sense to start Images or to focus on a different section first

<julierawe> Notes from last week's COGA call: COGA review of WCAG 3: two draft issues that need more votes

<julierawe> User controls are currently missing in WCAG 3 to pause, stop, or hide all moving and scrolling content

<julierawe> --Votes added

<julierawe> --Group discussed that WCAG 3 does not seem to discuss proximity of user controls

<julierawe> --Rachael recommended creating a new GitHub issue that applies to all sections of WCAG 3 addressing co-location

<Rachael> +1 to summary

<julierawe> LenB: One other element: Pause, stop, hide should be respected in user settings. But the problem is once some of these things start playing, there is no pause, stop, hide.

julierawe The action item is we need to draft the new GitHub issue.
… we can talk amore about this on Thursday

ACTION: item: Get a volunteer to draft the new GitHub isse that Rachael recommended.

<julierawe> 5 seconds of motion and pseudo-motion should not be allowed.

<julierawe> Group discussed clarifying the wording—no pseudo-motion should be allowed, and 5 second of motion should not be allowed.

<julierawe> --Rachael said she thought no motion at all will be difficult, but this can be addressed through a core requirement that requires honoring motion settings and adjusting the note on Trigger warning available to any motion (vs. motion lasting more than 5 seconds).

Rachael it is going to be difficult for us to say that sites should have NO motion at all. There are mini-motions that happen that will be difficult to prevent.

julierawe maybe we should get more specific about what we mean when we say 'motion'
… sensitive to 'pretty impossible to get consensus on'. Maybe even defining not essential or other ways to define what we're counting and not counting as motion.

<Rashmi> check out https://www.1800flowers.com/ when keyboard focus reach to search button

tiffanyburtin wonder if we could rank the interactions from harmful to 'less harmful'. SOme of the some motions can cause nausea in some individuals.

julierawe wat are some of the big thing?

<Rachael> Example of micro-interactions https://www.nngroup.com/articles/microinteractions/ which I think would be the hard part to remove.

tiffanyburtin changing backgrounds, dynamic color changes for attention grabbing buttons, auto-playing videos, things that shift as you scroll down the page

Rachael I think defining motion could be helpful
… encouraging you all to do the work you see needs to be done. My comments about 'difficult' are to help you see the work you may have ahead.

<Jan> I won't be available July 6th.

<Jan> I should be available next week on the 29th.

Len's sleeper topic on something missing from Images

<julierawe> LenB: In Making Content Usable, we have several patterns about distractions in images. Those are missing from WCAG 3.

<julierawe> LenB: What's in WCAG 3 is written for low vision people, not people with cognitive disabilities.

<julierawe> LenB: Good thing to talk about on Thursday.

COGA subgroups: Quorum for Tuesday’s Research call and Thursday’s COGA review of WCAG 3?

Eric_hind it would be nice to know how is WCAG 3 work going in general

julierawe WCAG 3 is going to have an updated working draft; big change is that each provision will have user needs we think are being addressed. These user needs will be helpful for COGA to see written out to help us identify coverage and gaps.
… draft could be coming in July

Rachael we're striving to get more about the conformance model into the working draft, we well.

julierawe subgroups are doing work on provision refinement and streamlining. It would be helpful to get COGA feedback in soon so that subgroups can attempt to include our thoughts for the July version.

Eric_hind are the assertions going to be changed in any signicificant way?

julierawe we can assume that everything will be evolving. We're not doing wordsmithing right now as we focus on getting more changes into the draft. The assertion template may change since we're getting feedback about the 'filler' in them and we're trying to work on how to make them something organizations can strive to meet.
… we're looking into making the assertions more clear and concise - some have a lot of things stuffed in them.

Rachael I expect to see us focusing on assertions once we wrap this effort on conformance model

<Rachael> +1 to moving target both good thing and bad

julierawe just a note that when something looks like it is on the chopping block (like 'keyboard navigable responsive) it gets sahred widely. I'll keep an eye on these and share them here to make sure we have a chance to jump in on it.