– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

Len TPAC feedback

<julierawe> LenB TPAC was really interesting. It focused a lot on WCAG 3.0

<julierawe> LenB We talked a lot about how to talk to legislative bodies about WCAG 3 conformance models.

<julierawe> LenB Same themes as we've talked a lot at COGA calls, but more intense.

<julierawe> LenB: Shadi as usual had all of the best challenging questions.

<julierawe> LenB: Meeting notes are available somewhere. We'll look for them and share them out.

<julierawe> LenB: On Wednesday, there were a lot of breakout sessions.

<julierawe> LenB: The HTML working group wants to introduce an HTML <amount> element.

<julierawe> LenB: In our plain language subgroup, we've been wondering how to handle things like Roman numerals, dates, etc.

<julierawe> LenB: I wanted to talk with the HTML group about this.

<Lisa> link?

<kirkwood> interesting! can you put link in?

<julierawe> LenB read the description for this breakout session.

https://www.w3.org/events/meetings/126c9a01-9cbb-47d2-a5c9-7cc17dde0b58/

<kirkwood> great!

<julierawe> LenB: If you think about one thousand, it's 1,000 in the US and 1.000 in Europe

<julierawe> LenB: Could browsers handle a lot of the work of that interpretation?

<julierawe> LenB: Browser could tell if you're viewing from the US so you'd see it in the context that makes the most sense to you.

<julierawe> LenB: Mozilla has already written this up.

<julierawe> LenB: The link I shared for the breakout session includes a link to Mozilla's writeup.

<julierawe> LenB: The <data> tag has something similar to present data in different languages.

<julierawe> LenB: We don't want to convert currencies.

<julierawe> LenB: There's so much more to unpack.

<julierawe> LenB: Could we do this for dates?

<julierawe> LenB: Months come first in some cultures and day comes first in some cultures.

<julierawe> LenB: The HTML group really likes the idea of focusing on amounts first.

<julierawe> LenB: It might be good for some COGA members to get in touch with the HTML group to help move this work forward.

<julierawe> LenB: The next step is to make a proposal for the spec.

<julierawe> LenB: So this is the perfect time for COGA to think about this.

<julierawe> Lisa: Thank you, Len. I think we need to have a conversation with them and give them some use cases. Who do we communicate with?

<julierawe> LenB: I would reach out to Tantek and Eemeli, who are listed on the breakout session link I shared.

<julierawe> Lisa: Maybe we should also reach out to Matthew and Janina.

<julierawe> Lisa: As APA chairs, they do coordination with other groups. We should be careful to loop them in.

<julierawe> Lisa: We'll bring up with them at our coordination call tomorrow.

<julierawe> LenB: There is a separate but related object proposal that apparently addresses similar use cases.

<julierawe> Eemeli Aro and Tantek Celik shared the HTML call

<julierawe> kirkwood: Was there any representation of numbering that were different to you than anything you've seen discussed before?

<julierawe> LenB: No, we were really focused on amounts

<julierawe> Charli: I was jumping immediately to a use case. This is exciting. My use case involves medical testing and looking up what the different units meant.

<julierawe> Charli: Nanograms versus milligrams versus micrograms

<julierawe> Charli: I'm not a mathematician but I generally understand numbers

<julierawe> julierawe: Any other conversations related to COGA?

<julierawe> LenB: Nothing outside of AGWG.

<julierawe> LenB: Big topics such as future of W3C, future of AI, etc.

<julierawe> Lisa: There's a lot of follow-up we can do with these initiatives.

<kirkwood> with that, do you think there should hvae been better COGA representation there?

<julierawe> Lisa asked Len to put together a list of initiatives we should follow up with based on TPAC conversations.

<kirkwood> (no criticism) ! ;)

<julierawe> LenB: You're triggering memories of Makoto-san submitting a request abou Ruby. We spent an hour digging into concerns about line height issues.

<julierawe> LenB: Ruby is a model inside HTML and certain languages that use characters such as Japanese. Above the characters can appear a phonetic or colloquial secondary text.

<julierawe> LenB: In some scenarios, that can actually be more confusing because you have two sets of text representing the same thing.

<julierawe> LenB: Everybody agreed it's important to keep talking about this.

<Lisa> including when it doesnt support accessibility

<julierawe> kirkwood: This is fantastic. I am remembering times I have been at TPAC before.

<julierawe> kirkwood: Did you feel that COGA was underrepresented?

<Jennie_Delisi> +1 to John, and wish we had ongoing representation, not just during TPAC. But agree we need to keep scoped to what we can do

<julierawe> LenB: The first few days were very focused on AGWG. I felt COGA as being underpresented on the Wednesday that was full of breakout sessions.

<julierawe> LenB: From a representation perspective, I didn

<julierawe> LenB: I didn't find a single room where people weren't trying to close some sort of gap, including neurodivergence even if COGA members weren't there

<Zakim> Rachael, you wanted to say you could coordinate applications for the diversity funding

<Lisa> https://knowbility.org/programs/john-slatin-accessu-2026

<julierawe> Reminder that AG will be attend AccessU instead of CSUN this year

<Rachael> TPAC inclusion fund https://www.w3.org/get-involved/tpac-inclusion-fund/

<julierawe> LenB: Where can we find the minutes from TPAC?

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

Whether/how to include exceptions in V2 of Making Content Usable

<julierawe> https://docs.google.com/document/d/1uAVRkNIgd3XlUIGQ6Gq-ZOcnwsFvIM9UJ1dNyHq8NSQ/edit?pli=1&tab=t.ht1sood1wqs8

<Lisa> rachal should/can coga meet at access u

the question is - is it too disruptive to have an exception on a V2 pattern
… Pros - cluster relevant inforomation together. Con - moakes overall guidance more cluttered / harder to read

<kirkwood> of couse the example that would be an exception. it still would not be usable. i like the one page idea!

<kirkwood> it would highlight how legislation can be considered.

<kirkwood> fq+

Lisa: we also don't want to look like WCAG and we're trying to take a different approach to making content usble. With WCAG being referenced by legislating bodies ties it to being very precise to make it work for laws. Every scenario has to be considered and written for.
… we had previously taken our exceptions out becuase we were writing guidance for progammers and assuming they are trying their best.
… We've written some of our things as "if it helps ... do this, if it doesn't ehlp don't it". We're focused on guidance that makes sites better. But we understood that people writing a Masters Thesis with a template won't be able to follow all of our guidance.
… The question is do we want to change our approach and start including exceptions.
… The question is do we want to change our approach and start including exceptions?
… It might be useful for WCAG 3, but it is not a requirement, yet.
… OPTION 1 - we keep doing it the same way.

OPTION 2 - we write an exception page

OPTION 3 - we start writing it to olook more like WCAG

<kirkwood> if so the exception name should be very very clear. afraid you could “drive a truck through them” if not done properly

<Jennie_Delisi> Rachael - this is a note, correct? Do we have a definition of note?

Rachael - not an anser, but a perspective. A lot of this will be translated to 3.0 in some form. So, someone will need to consider the scenarios. But, there is benefit in having the same content on two formats.

<julierawe> +1 to kirkwood comments

kirkwood - This question could help us figure out how to write things better. If we had a page of scenarios it would help us group things and see where things are effective or where we can focus.

<Lisa> OPTION 1 - we keep doing it the same way.

<Lisa> OPTION 2 - we write an exception page

<Lisa> OPTION 3 - we start writing it to olook more like WCAG

Lisa - keeping things simple to read could help people apply our content to their scenarios. Option 2 might be the best because it would help us with 3.0.

Jenni - this is a note, correct? Do we have a definition of note?

<Zakim> Rachael, you wanted to try to answer

Rachael - a recommendation is a formal document that goes forward through a rigorous process to become a spec or even be used in a law. a note is a more informal document that goes through an internal process and is considered informative. A note is a specific format and can be changed more easily.

<julierawe> OPTION 1 - we keep doing it the same way.

<julierawe> 11:52 <Lisa> OPTION 2 - we write an exception page

<julierawe> 11:52 <Lisa> OPTION 3 - we start writing it to olook more like WCAG

Jennie_Delisi - does that mean an audience coming to a note would understand how to read the document. Would they appraoch a note with the same expectation as the spec?

<Lisa> 1 or 2

Rachael - yes.

<julierawe> 2

<Eric_hind> Option 2

2

<Jennie_Delisi> 2 or 3

<Rachael> 2

<Gareth> 2

<kirkwood> 2

<Jan> 2

<Charli> 1 or 2

<Lisa> any objection to 2

<Lisa> or need more time

<Lisa> or a wiki page

kirkwood This scares me - it seems like something that will be referenced a lot. It has to be really well-written.

<Lisa> at least to start with

<kirkwood> i think i’d have to see the list, seems scary to put it out

Rachael - if you created a list of exception would it be its own published document or would you make it part of WCAG 3?

julierawe - mmm, feels like a timing thing. We'll have to think about it.