– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

<julierawe> Google doc with amount use cases: https://docs.google.com/document/d/1osxm57PcCyIwWKAPqVSu8djzrMDTSlxNSC8YsmitUTE/edit?tab=t.0

ACTION: item: Julie will ask Roy about the "This meeting is being transcribed" notice.

Scheduling for the next few weeks

julierawe With the holidays coming up, wondering if we'll have quorum on upcoming meetings.
… anyone on vacation on the 2nd?

<kirkwood> -1

<Jennifer> +1

<LenB> +1

<julierawe> +1 if you can attend April 2nd COGA review of WCAG 3 meeting, -1 if you can't attend, 0 if you're not sure

<Becca_Monteleone> -1

<julierawe> -1

<Jan> 0

<julierawe> Lisa -1

<julierawe> Tiffany is a maybe, won't know until the night before

<julierawe> Officially canceling the W3C calendar invite for April 2nd

julierawe We'll cancel officially, but anyone can still huddle up and keep working if desired.
… we'll see if Monday, April 6th we can have quorum

<julierawe> For Monday, April 6th, +1 if you can attend the task force meeting, -1 if you can't attend, 0 if you're not sure

<LenB> -1

<Jan> +1

<tiffanyburtin> 0

<kirkwood> -1

<julierawe> Jennifer +1

<julierawe> Becca is a maybe

<julierawe> 0

<Becca_Monteleone> 0

ACTION: item: Julie will ask Lisa what her preference is for Monday, April 6th

julierawe We'll ask Lisa what her preference is and then make a decision later about Monday, April 6th.
… now we want to check in Thursday, April 9th.

<kirkwood> +1 4/9

<Becca_Monteleone> +1

<tiffanyburtin> 0

<julierawe> For April 9th COGA review of WCAG 3, +1 if you can attend the Thursday meeting, -1 if you can't, 0 if you're not sure

<Jan> 0

0

<Jennifer> +1

<Jennifer> (I can attend starting at 8am PT)

ACTION: item: Talk with Lisa and let the group know where we land on April 9th

Reminder for W3C Breakouts Day

julierawe Sent an explanation and a calendar intvite out to the group. The Calendar invite was sent via Julie's work email to help people make sure you get just the COGA presentation meeting on your calendar uniquely enough to appear with the othe W3C invites.
… we will be going through the presentation during COGA research session on Tuesday.

<julierawe> LenB is asking John if he wants to partner on getting those slides ready

John K and Len will get together through email and collaborate on slides.

<Becca_Monteleone> I

<Becca_Monteleone> I'll be ther!

ACTION: item: Julie will remind presenters to attend Tuesday research subgroup call so we can practice the presentation.

julierawe We'll be presenting a deck for the first half ot fhte W3C call and then opening it up for discussion. Since the audience will be bigger than COGA TF it'll be a great opportunity to get some feedback.
… there are a bunch of other breakout sessions for this mini-TPAC. There are 4 time slots for all the break sessions. I sent an email as did Lisa. If you have issues getting into these sessions, please let us know.

Revisiting the <amount> use cases

<julierawe> https://docs.google.com/document/d/1osxm57PcCyIwWKAPqVSu8djzrMDTSlxNSC8YsmitUTE/edit?tab=t.0

<julierawe> LenB: Based on what we did last week with WCAG 3, I can use AI to get a first pass on amount use cases

<Jan> That was ALL Len - I provided very minor copy/paste work :-)

<julierawe> LenB: Jan created a master list of all of our user needs.

<julierawe> LenB: There were some things Lisa was talking about that aren't written up yet as a single-item user need.

<julierawe> LenB: So we'll need to figure out how to approach those.

<julierawe> LenB: But for the single-item user needs, Jan compiled a list of 206 user needs.

<julierawe> LenB: I can use Clause to look at those user needs and see how they relate to <amount> tag.

<julierawe> LenB: The three parts are research modules + Making Content Usable + Google's Omnibar which is represented in the explainer that APA's <amount> team is looking at.

<julierawe> LenB: We could look at those search engines to see how they could be helpful.

ACTION: item: LenB to use AI to do first pass.

ACTION: item: LenB and Lisa to huddle and look at the analysis before the task force discusses.

<Jan> Spreadsheet: https://docs.google.com/spreadsheets/d/19l6VWmRj0tQWAOkOOFBGVjWGdY7WnD7CKXFwDZX7gXo/edit?usp=sharing

<julierawe> LenB: Jan was a good sounding board and confirmer

<julierawe> LenB: When we look at COGA's review process tab in the google doc, there is a description of what things to look at.

<julierawe> LenB: It calls for looking at Content Usable, the research modules, and a list of cognitive needs that John Kirkwood shared.

<julierawe> LenB: Then reviewers are supposed to look at Julie's presentation on how WCAG 3 is organized.

<julierawe> LenB: The big thing about the functional needs is that is breaks things into categories, like "executive functioning."

<julierawe> LenB: The good thing about that is that it is already recognized in our big list of COGA user needs.

<julierawe> LenB: We already consider so much of the cognitive functional needs in Content Usable.

<julierawe> LenB: We copied all of the objectives and the appendix into the master list.

<julierawe> LenB: Jan and I looked at what is a description versus a user need.

<julierawe> LenB: The color coding helps with things like mapping where a description cleanly maps to back to the intro.

<julierawe> LenB: We decided to make the intros their own reference point.

<julierawe> LenB: The "intro" is the first paragraph in a user story, before the bulleted list.

<julierawe> LenB: We added a parenthetical that makes clear exactly where the user need or intro comes from, such as which section of a research module or which section of Making Content Usable.

<julierawe> LenB: We pulled everything into a master list.

<julierawe> LenB: For the appendix in Content Usable, we pulled in the intros, but the rest of the tables present things to do rather than how to meet user needs.

<julierawe> LenB: We took the master list of 206 user needs and asked AI to group them into themes

<julierawe> LenB: Claude came back with 12 themes

<julierawe> Link for user themes:

<Jan> User Need Themes Document: https://docs.google.com/document/d/1dIx9tEnG4xVPfUhacHpTeBrXVFJL6YYLK5si41oI4AY/edit?usp=sharing

<julierawe> Tracker spreadsheet is titled "Review Tracking WCAG 3 - W3C Editor's Draft 04 March 2026": https://docs.google.com/spreadsheets/d/19l6VWmRj0tQWAOkOOFBGVjWGdY7WnD7CKXFwDZX7gXo/edit?gid=989059939#gid=989059939

<Jan> Here is the folder with links to all of the documents Len and I worked on last week. This folder is "WCAG 3 COGA Feedback" and it's located in the COGA Taskforce Shared Drive: https://drive.google.com/drive/folders/1nPxnxFdZq3Zz4xFRGCujY0pOAf53cx7e?usp=drive_link

<julierawe> LenB: Helpful to look at what Claude flagged and to also look at the User Themes so we can think about what Claude might have missed.

<julierawe> LenB: As a team, we can call out what seems to be missing from our own user needs list — we can add to our user needs list and help prioritize our work for later in 2026.

<julierawe> LenB: I did a raw binary "is it covered or not" and then do is it partly met.

<julierawe> LenB: Claude limitations is that I don't know all of the user needs that have been discussed over the years.

<julierawe> LenB: Another limitation is that WCAG 3 is focused on testing whether a user need is met.

<julierawe> LenB: Doing this next bit as humans is going to be really helpful.

<julierawe> LenB: At the bottom of the google doc is a tab called "AI Assessment of User Need Coverage"

<julierawe> Link to that "AI assessment" tab: https://docs.google.com/document/d/1jLkvaCNxpk1xJ-yuyTWciizRe3GkGWPc-3yu6ZJLIqg/edit?pli=1&tab=t.fan0staxn8ap#heading=h.urhpdk27cgh3

<tiffanyburtin> Can we add tags such as "User Need" or "Testing" and others to identify for us and future AI summarizing?

<julierawe> LenB: The tab includes a note that the prompt on its own may not provide as powerful results as it did for Len because I have already been in conversation with Claude about these user needs.

<julierawe> julierawe: Assertions are in WCAG 3 to address things that can't be tested

<julierawe> LenB: WCAG 3 has a big focus on testing. It's a big difference between the COGA resources and WCAG 3.

<julierawe> LenB: My prompt told Claude not to ignore assertions in WCAG 3.

<julierawe> tiffanyburtin: We could use tags to help Claude quantify some of the items so it takes less work of human brains

<julierawe> LenB

<julierawe> tiffanyburtin: If we put a tag on certain things, so I know where these things are physically

<julierawe> LenB: It does have that kind of tagging, to a point.

<julierawe> Column L in the tracker spreadsheet will link to the draft github issue. It will be easier for a lot of COGA members to add comments or wordsmithing suggestions if we do the draft github issues in a google doc rather than in tracker spreadsheet.

<julierawe> Jan: We probably should include instructions in bracket to help people jump back and forth between the spreadsheet and the draft github issues.

ACTION: item: Julie will ask Eric and Lisa about which github issues can be ready to review at this Thursday's meeting.