Meeting minutes
<lisa> -What goes into our reviews
<lisa> -What do we have a future issue paper
<lisa> -What do we ask for more consensus and research
<lisa> -What goes into our reviews
<lisa> -What do we have a future issue paper
<lisa> -What do we ask for more consensus and research
<lisa> Changing the phrase cognative and learning disabilities. see
<lisa> https://
<lisa> next item
<lisa> next item
<lisa> close item 1
<lisa> next item
No updates for the structure group. Tiffany apologies for not being able to contribute in the way she wanted.
Planning for next week - 2 meetings one with Rain and Julie and Github html side - the order of things so things do not get overwritten.
Rain said she may be able to meet but very booked -
Lisa wants to be able to move an item - with people working on something in one day
Rain asked if it was possible to do it in the subgroup time plus one hour
Lisa suggested may need to do two sessions.... around the editors' call.
Object one in Google doc and then week after another meeting.
Rain subgroup time good and the hour before on Thursday.
Lisa does not want to start the work without Rain as she is the expert on the new template
Need to have people moving one objective to the new Google doc. Need to start with Rain on Thurday and then carry on the following week
The other call was to do with HTML GitHub conversion with Julie, Rain Lisa et al - new folder and new branch for new version and then starting moving things
Then can see the general look and feel - the introduction and flow through...
Lisa asking if there is an extra hour in the diaries for the editor's call - an hour before this coga call on a Monday
Times are clashing - trying to plan events. Rain suggested the following week - Thursday 6th March? Prep work can be done before the actual meeting suggested by Frankie.
Rain feels that the shell could be put in place and this Thursday those who can attend clear where the editing happens so it is ready for a larger group. This is just on the Google doc.
Lisa agreed and the following week will result in the GitHub work. Frankie will hopefully attend the meetings tomorrow. Support the making of the branch and new folder and how things are moved over.
Lisa hopes a sample conversion can be completed. May need another meeting as well due to the difficulties that can arise with files etc
Then when anyone who feels convident with using GitHub can continue to work on it all. There still needs to be a conversation about other sections beyond the introduction.
Frankie also wanted to know about this aspect - investing time - what should she do.
Lisa suggested 2 hours with Rain and then an hour before coga next week with Julie, Frankie and possibly Rain if time allows
Lisa suggested changing the agenda to discuss what is going to be in the first working draft
what is in next Working Draft
This is going to be the equivalent of an abstract - the intro and what will follow - then folded out from content you have links to the old structure so people can see how it works together - All the objectives will be there ...
Rain said the first priority is getting Objective 1 into a way that it will be written - there will be notes that show the flow through - editor's notes.
Items that still need to be written will have placeholders
This process will allow people to see what has been discussed - the structure is in place and you can follow through to pattern 1 for instance. Changes can be made without concerns about language or other issues.
Frankie asked what the flow of the work will be - what goes into the editors' draft
Lisa clarified that this will be an HTML web document in GitHub
Changes to the syntax and punctuation can still occur in the Google doc version.
Next week will be in Google docs working on it all with a small group - working on the text happens there and once acceptable it will be transferred to GitHub
Frankie suggested that setting up Google docs with the new template woud be work she could complete this week.
Rain and Frankie confirmed their working time on the task
<lisa> next item
Eric confirmed that he is working on both APA and would also like to go over some process pieces. Eric was also willing to work on the way the transfer to GitHub works
<lisa> What goes into our reviews
<lisa> What do we have a future issue paper
<lisa> What do we ask for more consensus and research
Lisa has suggested there may need to be some triaging for the community work
Need to review a few topics that were not handled in the way we may not have been happy with in the past. Thinking about making some reviews or setting up an issue paper - samples of potential challenges and solutions - add to review or make more of it such as more research then it can become an issue paper. Also ask for more research to see what
the community wanted.
It is possible to make more tables with more queries or we could say we don't agree with some of the concerns raised. There needs to be strong concensus for requirements and if prioritised there needs to be a good look at what has been said... such as endless content feed - such as happens in some social media settings. Some suggestions can then
be used e.g. add a stop watch type of strategy to remind someone they were still on the platform and needed to know how long they had been there - time of day changes - some indication.
Not felt just to be related to social media - also happens with gaming so need to look out for more on this subject.
Rain felt the response should be one of agreement but we do not have the resources to do the research - could be ask the community if we do not have the capacity to look at the subject.
Frankie mentioned that Rachael had a form that can be used for research - Lisa wants to what the forms are like
Frankie explained that the forms are used for WCAG 3 and will find the link
Lisa agreed more research is definitely needed -
Rain mentioned that this particular topic of spending excessive time on something when executive functional challenges are in place this can be a real problem but need to find strategies.
Lisa also mentioned that usual strategies may not work and Rain suggested this could be part of the research
<Rain> +1 to EA's suggestion of "strategies" instead of "solutions"
<Frankie> +1 to "strategies"
<Jennie_Delisi> +1 to EA - strategies implies may work for you, but you may need another option
Lisa confirmed that you can identify the risks and effectiveness of strategies - so we tell people to look into them.
Accept this problem as an issue - time spent hooked into something without realising how long being taken up by the subject.
Frankie and Rain agree this is work that needs exploring further
The next one is Mulitmodal communication that needs research... text needs to be more easy to follow, what happens when images are removed, screen reader issues around icons and other controls - hero images etc. May need to filter out images - but these tools may also remove the alt text - Improve the structure and provenance of multimodal
communication - offer a review.
The new structure of all the documents could change some of this last set of comments so may need to pause of these issues... Re-read the comments after we have got the whole document in place
Rain said these comments were hard and when we do the review we can give guidance on what is needed and what not to do but hard to address all the points. Rain gave some expamples how it is possible to get the screen reader to read in different ways such as reading without images or without links etc... can be used when you have particular needs
and very much depends on what is wanted at the time. Can't expect developers or designers to offer all these creative things for everyone all the time. May need to get the Assistive Technology to do part of the job.
We may need to get better at discussing the way AT can come into aspects of making items accessible in adaptive ways that suit personalisation as well as customisation.
<Jennie_Delisi> Apologies - have to drop. Have a good week
<lisa> proposal for issue paper and possible review
Rain said multimodal communication comments could become an issue paper