Meeting minutes
<EA> +present
next item
<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.
<EA> Mental Health and GitHub call for editing this week on Thursday and Internationalisation.
<EA> Any other updates to share.
next item
<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
<EA> Title needs to be easy to understand and shorter.
https://
<EA> Lisa's proposal can be seen in the web link above. The name is important - Cognitive Accessibility Guidance
<EA> There will be a subtitle ... "Making content usable for people with cognitive, intellectual,
<EA> developmental, learning and specific learning disabilities,
<EA> neurodivergence and mental health impairments and temporary
<EA> impairments that affect cognitive function. ... (We can agree on the
<EA> full subtitle later - let us just agree on the direction )"
<EA> There is an explanation in the introduction - needs to be in the abstract and the main document.
<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
Our user groups
<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.
<julierawe> "users with disabilities that impact cognitive accessibility"
<EA> Lisa felt that being discoverable may have to come from the descriptions as it is more important to keep things easy to understand.
Our user groups
<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
<Jennie> julierawe - maybe I misunderstood your point? If so, please clarify.
<EA> Lisa has concerns about the length of some of the ideas that include longer phrases with the words that might explain cognitive disability.
<Zakim> Jennie, you wanted to see if I understand Julie's use case
<EA> It is hard to keep the phrases short and easy to understand.
<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
<EA> coga
<EA> Lisa said we may have to depend on editor's discretion - add extra sentences to provide clarification.
aprove the titile?
1: The title is cognitive accessibility guidance
2: We have a sub title along the lines of (direct being approved only) :
Making content usable for people with cognitive, intellectual,
developmental, learning and specific learning disabilities,
neurodivergence and mental health impairments and temporary
impairments that affect cognitive function. ... (We can agree on the
full subtitle later - let us just agree on the direction )
<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
<EA> Angelo Young left earlier
<Lisa> +1
<EA> Lisa went over what is already suggested and wants a vote
<julierawe> +1
<Becca_Monteleone> +1
<JeanneEC> +1
<Jennie> +1
<EA> +1
<tiffanyburtin> +1
We explain who is included in both the abstract and the introduction
<julierawe> [We are voting on title of "Cognitive Accessibility Guidance" and a subtitle "Making content usable for people with [long list]
<EA> Thank Julie
reolution . We replace the phrase people with learning and cognitive
disabilities in the document so that the intent is not changed, but it
is easier to read and follow. This would involve using different
phrases depending on what fits. Included phrases are:
- The phrase "cognitive accessibility"* where it fits -
*with a pop up glossary item with what the phrase means and a full
list of who is included
- The phrase " Our user groups" - also with a pop up explaining who
is included
-sometimes an extra sentence may be added such as: users with disabilities that impact cognitive accessibility
and sometimes use that sentce where it is helpful and eaiser to understand
<EA> This means we are leaving it to the editors' discretion - the above are some examples
<EA> Jennie suggested this could include a caveat - a certain amount of feedback could be gathered from larger chunks of information.
<EA> Asking is it clear who is included
resolution for wording chenges in the document?
<Lisa> +1
<EA> +1
<JeanneEC> +1
<tiffanyburtin> +1
<Jennie> +1
<Becca_Monteleone> +1
<EA> Julie suggested using metadata when discussing 'our user groups' to overcome the lack of detail
<EA> Jennie explained the difference between the machine finding content versus people seeing things in a document that help with search
<EA> Keyword strategy on the backend to help with the search funtionality
ammended resolution to include keywords with all diffrent disabilites and spelling
<julierawe> +1
<EA> Tiffany mentioned similar help could be provided with tool tips
<EA> Lisa mentioned that at the moment we have the definitions that include all the alternatives to certain disabilities - include in the glossary.
<EA> The resolutions could be added to the style guide.
next item
<EA> Lisa would like to send this to the list for a last chance to change these ideas
<EA> Looking at feedback from community groups
<EA> Looking at the comments and quotes - regarding issues around resizing windows and what is missed - ensure information does not disappear with new layout
<EA> The resolution on the watch makes it unreadable
<EA> You may have to linearise more of the content
<EA> Julie asked if we can ask the person who commented on this issue what is the actual problem
<EA> Tiffany suggested that zoom-in may be having an impact
<EA> May also depend on the size of screen and width and height differences.
<EA> +1 to asking for more information
<EA> Useful to see an example of the challenges being described
<tiffanyburtin> Agree with Julierawe that we could use a description of the example.