Meeting minutes
<lisa> please sign up for scirb list: https://
<lisa> Becca has jury duety, so stucture proposals may take that slot (thank you rain)
<lisa> close item 4
<lisa> close item 5
<lisa> next item
+EA
+present
<lisa> +present
Jump to general research - subgroups - new draft for t research pln
<lisa> https://
Need to move forward certain items such as issue papers and the new research agenda and where we want to store search terms.
<lisa> https://
Tiffany and E.A. to meet up to discuss timeline for symbols.
Mental health - lisa taking action for the group to move ahead.
Rain structure subgroup on track John K and Rain have set up a couple of approaches for layouts to be shared with task force soon - engineer will make prototypes in the following weeks and then gain feedback.
Internationalisation - setting up a call to discuss with APA and John Rochford to make sure happy with 5 languages selected so can move ahead - Rachael and Janina to be on call to touch base with Internationalisation group.
Lisa continued with request to go over collaboration with David Swallow and the other David as the liaison - need to be able to follow what we are doing and liaise
Lisa to make request for a new check element that is being worked on and funtional needs also pending.
<lisa> next item
Looking at storage of Coga database for sources and issue papers
Lisa made an extra column and secondary cells where there are more than a key pattern, objective or resource. So there is freedom to add additional information.
Recitation and key take away are required - this can be filled in by others than the original author.
The other database is the issue paper where web of things needs to be added and there are placeholders for the mental health papers.
The latter is in the action page so links have been cleaned up to show links that are being worked on at the moment.
Lisa asked Rain if she wanted to still manage this database but will help Becca is help is needed. Becca was not in the meeting.
Lisa is going to update the content as it acts as a tracking database
Lisa asked if anyone wanted to update any issue papers.
Justine offered to update an issue paper and Lisa added them to the database such as Web of things and Graded help
There are now 3 updates and 2 new ones - need to pick which ones are the most important and need an update.
<lisa> next item
Research guide is the next item
Now have a guide with layout in the Overview.
Lisa said we need to look at the way we are working on search terms - which ones we are using and where we are finding the information. This will help us find the gaps - also how we tweak our search terms in the literary analysis
Lisa asked where did we want to keep the search terms used an example is the list provided by mental health. Can be found in the document - in the appendix of the search plan
Another idea is that there is another document that just works for tracking the citations so instead of using the spreadsheet (database) the extra document could be used but it may be forgotten so Lisa feels it is better to have the terms in ones own document or the original document with an Appendix. The latter seems to work best - can be an indirect link before you put it in the database
<lisa> store search terms and datebases https://
<lisa> rerch plan apendix
<lisa> +1
Lisa's question is whether to store search terms - needs to be logged somewhere - preferably in the reseach plan appendix
+1
<JustineP> +1
Rain suggested that it would help to have a support page to tell people how to capture the information in the correct way and how to do the citations etc.
Lisa suggested that a short summary about 'what to do' would be a good idea
Rain felt that it would be good to have it in the Appendix and Lisa concurred with a three step type of help page
Rain suggested this would keep things consistent.
+1 to the idea of a help page to keep things consistent
Lisa mentioned that Eric would compose an issue paper on AI and then another on multiple impairments where co-occurring difficulties can affect the use of technologies. Behaviour control as another issue paper possibly part of the mental health group's work. Then we have the user research module which needs updating and may want to add a group and in particular one on general problems linked to a range of difficulties.
The question is whether we update the groups of disabilities whilst we are working on the issue papers? or pause and do the disability groups later?
Abbey would like to help with the updates for the disability groups.
Lisa suggested that each one could be a module so doing it in stages
<lisa> https://
Abbey will look through them all and see what she feels needs updating
This user research was done as a working draft in 2015
Rachael asked if this would be as a note or draft
<lisa> abby to review if we can update and publish a few modules in user reaserch
<lisa> +1
Lisa suggested that it would be updated and link to Content Usable and see what could be published as modules.
+1
<lisa> any objections?
<tburtin> +1
<abbey> +1
Justine has said she is also happy to update an issue paper
<lisa> next item
<lisa> next item
<lisa> close item 6
<lisa> next item
Re: scribing It helps me listen carefully
Rain discussed a new approach about how to structure 'Making Content Usable' wanted to stay with the model but based on user feedback there was an ABC testing not just AB testing.
Rain shared her screen as no link yet to share with attendees
Summary of contents was made up - Quick ref idea that was provided with the old WCAG guide to reach Success Criteria quickly. Then there is the collapse menu with show publications then intro to the document. Three content sections that are separate paper Section 1 of Who and Why
<julierawe> +1
<julierawe> ?
Section 1 to include personas. users needs etc then 2nd section what when and how - design principles etc. Final 3rd section is Evidence with references etc. This is followed by how to use the document
There would be tags use throughout the content so you can pay attention to particular parts of content - the tags would be guides such as roles of people. So if you are a product owner - there would be tags that link to that job and you would be guided to individual steps as a pathway through the document
There would be separate ways of going throug the document with other ways of exploring the document.
Lisa asked could we do this ... need to have a link so that this can be discussed with Roy and Lisa said she had some ideas but others may also have comments.
Lisa asked whether we are able to make this interface as a single document?
Need to share with Janina and Rachael and others to get feedback
Julie said that she really liked the idea but wondered if anyone would want to go to a long list of references rather than having the references attached to particular issues, patterns etc
Also wondered about the who and why and perhaps the evidence could be linked to who is using the document - the types of professionals.
Rain was grateful for the feedback and has taken on board the ideas and in particular the feasibility of making all these changes to the design.
Lisa felt that this idea could be made with a style sheet so that it can also be seen as a single document.
Rain wondered if it would worth trying with others even if not feasible with W3C
Rachael said she might ask Shawn Henry but Rain felt that it needs abit more work before asking others
Lisa felt that the idea really looked ready for discussion
<Rachael> Other people who would be interested in the conversation: EO Chairs, AG Chairs, Michael Gower
John K said that he will catch up with Rain later about what has been discussed
Next week time schedules will be back in synch -USA will have clocks going back 5th Nov.