– DRAFT –
Cognitive and Learning Disabilities Accessibility Task Force Teleconference

<Lisa> https://docs.google.com/spreadsheets/d/1eKNrofGubnpQE6mO-vxmI-1MW5nA2LDj0LxebREPRGA/edit?resourcekey=&gid=1686096268#gid=1686096268) note citations should also be in the database

<Lisa> - A review of what we are working on and arrears we can help (publications and subgroups)

<Lisa> - what we are doing include - reminder for the call. action page, once a month review actions. should these things change?

<Lisa> - what problems are you having?

<Lisa> - tips, tricks and brainstorm solutions

+present

<Lisa> hi EA

Numbering may be different compared to the Zakim entries

TPAC to start and then main discussion about participation with coga - thinking about terms etc and not necessarily going over items we already have but if changes are needed then we can go over them and then brainstorming the ideas. Followed by going over the action page and finally possibly touch base on issue papers and citations - how these

will be done.

<julierawe> Lisa, can you share your screen?

Charli questioned whether there was a mention of how hard it was to contribute.

<Lisa> next item

TPAC next up...

TPAC asked the task force what we want to discuss at TPAC

ADAPT Aria - summary tag or topic tag mentioned.

Also at TPAC may include discussion of issue papers

Triggers would also be a good subject for discussing with ADAPT - proposals about types of triggers - still need solutions

Julie asked about specific meetings with APA and the other one about breakout topics.

Lisa clarified that they were not talking about break outs

review issue papers with APA or via AG group - ADAPT do more on cross meeting.

<julierawe> Clarification: APA asked last week if there are specific topics we want to discuss at meetings with APA at TPAC.

<julierawe> APA meeting topics Lisa suggested: (1) Adapt and/or ARIA: We have a paper coming out on adjustable trigger warning. It may also be useful to have semantics to identify summaries of documents, key points, and key sentences. (2) Issue papers: conversational interfaces, indoor navigation, safety online (including data driven algorithms and social

<julierawe> media) and supported decision making online. (3) New format of cognitive accessibility guidance.

Julie mentioned ' new format'

Lisa wondered if they would be interested in the new format but also mentioned internationalisation.... may be an update

TPAC will be in November 14-15

<Lisa> in japan!

Julie mentioned that AG and Coga had a meeting about internationalisation

Lisa mentioned that it could be a three way discussion APA / AG and coga -

<julierawe> Minutes clarification: AG, Coga, and Internationalization (i18n task force) had a meeting.

Thank you Julie

<kirkwood> +1 to 3 way meeting APA AG & Inmternationalization

Jennie - need to consider schedules when setting up TPAC meetings

Julie wondered if it would help to have an APA meeting prior to TPAC due to the scheduling with time zones

<kirkwood> pre TPAC meeting +1 w/ APA

<kirkwood> -1

Lisa asked if anyone is likely to come to Japan

<Jennie_Delisi> -1

<julierawe> -1

<EA> -1

<Charli> -1

<LenB> -1

<Lisa> next item

Nest item - how we can help people participate in coga activities

<Lisa> next item

Starting with what is being worked on at the moment - next version of the Content Usable document - getting working template completed and big issues such as the name and internationalisaton. Now working on issue papers - from draft and then into GitHub. Publication process can take a couple of months. Looked at the subgroups.

Lisa went on show where there are links to other work.

Once a month go over 'Action items' but may need to revisit this idea as people may miss the start of the month meeting.

<Lisa> next item

Charli mentioned that it can be hard to learn what the big picture is and some of the problem can be the acronyms or the way items are discussed such as patterns and format etc

Finding information can be hard due to the formatting which may be affected by the mail app that is used.

<EA> +1 to format changes that occur in different mail apps

May need to have all the links for all the relevant resources in one place.

<Jan> +1 to the calendar being a problem - it's not intuitive.

<EA> +1 to doing it our own way

<LenB> +1 to doing it my own way, and I've found I need to re-check every few weeks

Yes thank you for the reminders with the links in the email so there is not need to go elsewhere

Julie suggested providing more context as to the links to whom we belong to as a task force

<julierawe> +1 to Charli's comment about needing more context/high-level overview of what COGA is doing and why.

Len also said getting quick answers to his needs - how to send questions that will be answered without having to wait for ages.

<LenB> +1 to having to do a dance with google docs. My company doesn't allow access to them on work laptops.

One problem that affects some people is the problem of not being able to use Google docs in a work place or other apps. So having so many different apps that are being used can cause issues.

Different work flows and various environments need to be sorted in the best possible way to make it easier to access items

<kirkwood> Microsoft and Google workflow issues are a problem. agreed

<kirkwood> and github

David felt that the complexities do cause problems - the topics need research and investigation and it is not easy to resolve some of the deep topics discussed makes it hard and takes too much time.

<julierawe> LenB Please remind me when to shift from discussing challenges to discussing solutions that I have an idea to help with getting email responses.

Do the size of the tasks cause issues - bite sized topics but can make it harder to get things back to the bigger picture. The areas to discuss are so large that it can be hard to find people who can cover all aspects.

Lisa suggested we may need to revisit this idea again in a couple of weeks.

<Lisa> next item

ACTION: https://docs.google.com/document/d/15HtPkkYx1CIl6bAwP2nsSZKhqTVbqcuMDRz5RmtmvXg/edit?tab=t.0#heading=h.p5pma1o6s97e

Charli will review the document

Lisa went through all the elements in the Action document - included item about GitHub and IRC support.

Lisa asked if adding more definitions for the terms that are used in Content Usable might be helpful

<Lisa> Charli added github and irc and all these things

<Lisa> EA, images and mind map

<Charli> EA - a mindmap or flow chart or something would be super helpful!

Hard to achieve graphical representation of the content of Content Usable but it would need constant updating. It would hard work.

<EA> +1 to Julie and Lisa about time needed for a mindmap -

email subject lines need to be precise - tailored to topic

Julie suggested they need to grab people's attention - Len agreed

suggestion that there should be guidelines on better subject lines in emails

<Charli> Yes to definitions

<EA> +1

<Jennie_Delisi> Thank you to those sharing challenges participating.

<Jennie_Delisi> I appreciate the conversation by all.

<EA> +1 thanks also

<DavidSwallow> +1

<LenB> +1 and thanks

<julierawe> Lisa Can you include a deadline for adding to the google doc?