14:07:25 <RRSAgent> RRSAgent has joined #coga
14:07:29 <RRSAgent> logging to https://www.w3.org/2025/04/07-coga-irc
14:07:29 <Zakim> RRSAgent, make logs Public
14:07:30 <Zakim> Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference
14:08:02 <Lisa> agenda+
14:08:05 <Lisa> agenda?
14:08:12 <Lisa> clear agenda
14:08:20 <Lisa> agenda+ meetings this week
14:09:22 <Lisa> agenda+  replace the phrase cognitive and learning disabilities and mental health impairments. see  -email at https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2025Apr/0009.html and - the issue  discribed at
14:09:22 <Lisa>  https://docs.google.com/document/d/1FkyRIP3CAuZ-JAazUOAUI64TYCrEfOkKSeBg94mMOkg/edit?resourcekey=0-HM4QyycKbkfCwWAXzIymrw&tab=t.0#heading=h.r0jc39bbtz1i
14:09:56 <Lisa> agenda+  feedback. what feedback do we have to review. See Review coga community feed back at COGA Community Meeting Notes https://docs.google.com/document/d/1VsHS-oQDR7XY87E91sd-zqYaq8DCH9Ppwf9YeqCNcks/edit?tab=t.aohwqsygorkh
14:11:50 <Lisa> q?
14:50:19 <Lisa> Lisa has joined #coga
14:50:24 <Lisa> agenda?
14:52:16 <Lisa> present+
14:52:30 <Lisa> RRSAgent, publish minutes
14:52:32 <RRSAgent> I have made the request to generate https://www.w3.org/2025/04/07-coga-minutes.html Lisa
14:53:04 <tiffanyburtin> tiffanyburtin has joined #coga
14:53:08 <tiffanyburtin> present+
15:01:50 <JeanneEC> JeanneEC has joined #coga
15:01:58 <JeanneEC> present+
15:02:03 <AngelaYoung> AngelaYoung has joined #COGA
15:02:20 <EA> EA has joined #coga
15:02:29 <Jennie> Jennie has joined #coga
15:02:38 <Jennie> present+
15:02:39 <EA> +present
15:02:43 <AngelaYoung> present+
15:04:08 <Becca_Monteleone> Becca_Monteleone has joined #coga
15:04:15 <Becca_Monteleone> present+
15:06:43 <Lisa> next item
15:08:10 <EA> Meetings this week - Tuesday an hour earlier than coga meeting... call for editing the patterns as per the new structure. Meeting re-occurs during April please join if you can make most of the meetings.
15:08:39 <EA> Mental Health and GitHub call for editing this week on Thursday and Internationalisation.
15:09:09 <EA> Any other updates to share.
15:09:10 <Lisa> Q?
15:09:13 <Lisa> next item
15:10:16 <EA> Aiming to close decision on the title that is being used for Content Usable.  The difficulty for learning disabilities is that it means different things in some countries
15:10:35 <EA> Title needs to be easy to understand and shorter.
15:10:46 <Lisa> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2025Apr/0009.html
15:11:39 <EA> Lisa's proposal can be seen in the web link above.  The name is important - Cognitive Accessibility Guidance
15:12:32 <EA> There will be a subtitle ... "Making content usable for people with  cognitive,  intellectual,
15:12:32 <EA> developmental, learning and specific learning disabilities,
15:12:32 <EA> neurodivergence and mental health impairments and temporary
15:12:32 <EA> impairments that affect cognitive function. ...  (We can agree on the
15:12:33 <EA> full subtitle later - let us just agree on the direction )"
15:13:09 <EA> There is an explanation in the introduction - needs to be in the abstract and the main document.
15:15:12 <EA> The second bit is about where we use the term cognitive accessibility - sometimes it does not work in all situations so in other places there may be a need to include 'our user group' rather than detailing each of the user types
15:15:18 <julierawe> julierawe has joined #coga
15:15:21 <julierawe> present+
15:15:26 <julierawe> q+
15:15:45 <Lisa> ack next
15:16:09 <Lisa> Our user groups
15:16:52 <EA> Julie appreciated the brevity of 'our user groups' but wonders if we are giving up some SEO value - may lose some search value when not using labels for different disabilities and difficulties.
15:17:41 <julierawe> "users with disabilities that impact cognitive accessibility"
15:17:47 <EA> Lisa felt that being discoverable may have to come from the descriptions as it is more important to keep things easy to understand.
15:17:48 <Jennie> q+
15:18:03 <Lisa> Our user groups
15:19:17 <EA> Jennie felt that there could be an an additional strategy about what does support search engine optimisation and then then look at what will support searching.  The abstract could contain some of the words needed that fit with the way WAI structure the back end for this
15:19:39 <Jennie> julierawe - maybe I misunderstood your point? If so, please clarify.
15:20:09 <julierawe> q+
15:20:28 <Lisa> ack next
15:20:36 <Lisa> ack next
15:20:51 <EA> Lisa has concerns about the length of some of the ideas that include longer phrases with the words that might explain cognitive disability.
15:21:40 <Jennie> q+ to see if I understand Julie's use case
15:22:39 <Lisa> ack next
15:22:40 <Zakim> Jennie, you wanted to see if I understand Julie's use case
15:22:48 <EA> It is hard to keep the phrases short and easy to understand.
15:23:35 <Lisa> Q+
15:24:23 <EA> Jennie asked if it was about the search issues that could arise when trying to find key words they know related to cpga within the document
15:24:25 <EA> coga
15:24:38 <tiffanyburtin> q+
15:25:05 <Lisa> ack next
15:25:47 <Lisa> ack next
15:25:58 <EA> Lisa said we may have to depend on editor's discretion - add extra sentences to provide clarification.
15:27:08 <Lisa> aprove the titile?
15:27:08 <Lisa> 1: The title is cognitive accessibility guidance
15:27:08 <Lisa> 2: We have a sub title along the lines of  (direct being approved only) :
15:27:08 <Lisa> Making content usable for people with  cognitive,  intellectual,
15:27:09 <Lisa> developmental, learning and specific learning disabilities,
15:27:09 <Lisa> neurodivergence and mental health impairments and temporary
15:27:09 <Lisa> impairments that affect cognitive function. ...  (We can agree on the
15:27:11 <Lisa> full subtitle later - let us just agree on the direction )
15:27:13 <EA> Tiffany suggested keeping the words we value highly in the beginning and then the shorter terms can be used later and not necessarily affect search engines
15:27:38 <EA> Angelo Young  left earlier
15:28:11 <Lisa> +1
15:28:17 <EA> Lisa went over what is already suggested and wants a vote
15:28:17 <julierawe> +1
15:28:19 <Becca_Monteleone> +1
15:28:24 <JeanneEC> +1
15:28:27 <Jennie> +1
15:28:31 <EA> +1
15:28:32 <tiffanyburtin> +1
15:28:46 <Lisa> We explain who is included in both the abstract and the introduction
15:28:56 <julierawe> [We are voting on title of "Cognitive Accessibility Guidance" and a subtitle "Making content usable for people with [long list]
15:29:20 <EA> Thank Julie
15:29:38 <Lisa> reolution . We replace the phrase people with learning and cognitive
15:29:38 <Lisa> disabilities in the document so that the intent is not changed, but it
15:29:38 <Lisa> is easier to read and follow. This would involve  using different
15:29:38 <Lisa> phrases depending on what fits. Included phrases are:
15:29:39 <Lisa>    - The phrase "cognitive accessibility"* where it fits -
15:29:39 <Lisa> *with a pop up glossary item with what the phrase means and  a full
15:29:39 <Lisa> list of who is included
15:29:40 <Lisa>    - The phrase " Our user groups" - also with a pop up explaining who
15:29:40 <Lisa> is included
15:30:09 <Lisa> -sometimes an extra sentence may be added such as: users with disabilities that impact cognitive accessibility
15:30:51 <Lisa> and sometimes use that sentce where it is helpful and eaiser to understand
15:31:50 <EA> This means we are leaving it to the editors' discretion - the above are some examples
15:32:10 <Jennie> q+
15:32:26 <Lisa> ack next
15:33:10 <EA> Jennie suggested this could include a caveat - a certain amount of feedback could be gathered from larger chunks of information.
15:33:37 <EA> Asking is it clear who is included
15:33:58 <Lisa> resolution for wording chenges in the document?
15:34:00 <Lisa> +1
15:34:05 <EA> +1
15:34:06 <JeanneEC> +1
15:34:08 <tiffanyburtin> +1
15:34:09 <Jennie> +1
15:34:16 <Becca_Monteleone> +1
15:34:16 <julierawe> q+
15:34:26 <Lisa> ack next
15:35:26 <EA> Julie suggested using metadata when discussing 'our user groups' to overcome the lack of detail
15:36:27 <Jennie> q+
15:36:56 <Lisa> ack next
15:37:46 <Lisa> Q+
15:37:48 <EA> Jennie explained the difference between the machine finding content versus people seeing things in a document that help with search
15:38:55 <EA> Keyword strategy on the backend to help with the search funtionality
15:39:20 <tiffanyburtin> q+
15:39:27 <Lisa> ammended resolution to include keywords with all diffrent disabilites and spelling
15:39:37 <Lisa> ack next
15:39:40 <Lisa> ack next
15:40:01 <julierawe> +1
15:40:19 <EA> Tiffany mentioned similar help could be provided with tool tips
15:40:57 <EA> Lisa mentioned that at the moment we have the definitions that include all the alternatives to certain disabilities - include in the glossary.
15:41:33 <EA> The resolutions could be added to the style guide.
15:41:46 <Lisa> next item
15:42:02 <EA> Lisa would like to send this to the list for a last chance to change these ideas
15:43:11 <EA> Looking at feedback from community groups
15:43:28 <Lisa> https://docs.google.com/document/d/1FkyRIP3CAuZ-JAazUOAUI64TYCrEfOkKSeBg94mMOkg/edit?resourcekey=0-HM4QyycKbkfCwWAXzIymrw&tab=t.0#heading=h.wyaggdwvjazi
15:44:42 <Lisa> https://docs.google.com/document/d/1VsHS-oQDR7XY87E91sd-zqYaq8DCH9Ppwf9YeqCNcks/edit?tab=t.aohwqsygorkh
15:47:55 <EA> Looking at the comments and quotes - regarding issues around resizing windows and what is missed - ensure information does not disappear with new layout
15:48:51 <julierawe> q+
15:49:05 <Lisa> ack next
15:49:08 <EA> The resolution on the watch makes it unreadable
15:50:03 <EA> You may have to linearise more of the content
15:52:09 <EA> Julie asked if we can ask the person who commented on this issue what is the actual problem
15:52:38 <EA> Tiffany suggested that zoom-in may be having an impact
15:54:48 <EA> May also depend on the size of screen and width and height differences.
15:55:44 <EA> +1 to asking for more information
15:55:51 <julierawe> q+
15:55:57 <Lisa> ack next
15:56:20 <EA> Useful to see an example of the challenges being described
15:56:35 <julierawe> q+
15:56:49 <tiffanyburtin> Agree with Julierawe that we could use a description of the example.
15:57:11 <Lisa> ack next
15:58:25 <Lisa> RRSAgent, publish minutes
15:58:27 <RRSAgent> I have made the request to generate https://www.w3.org/2025/04/07-coga-minutes.html Lisa
15:58:33 <julierawe> Thank you, Lisa and EA!