Meeting minutes
<lisa_> regrets, EA RAIN
Collaboration Tool Accessibility Feedback <https://docs.google.com/document/d/1odt2eWGeJT06S2xdW2H3ymTHOTa0QWkscNSEphNI1og/edit#heading=h.wik9fsv1osxs > next steps
<Becca_Monteleone> Lisa: New members - reach out to Lisa for orientation calls if you need one.
<Becca_Monteleone> Jan: Please invite Jan to next orientation meeting in order to develop a "cheat sheet" for new COGA members.
<Becca_Monteleone> Lisa: we could also add this info as a page on our Wiki once complete
<Becca_Monteleone> Lisa: collaboration tool accessibility feedback given at the end of last year, noting that more work was needed. Jennie was editing the document
<Becca_Monteleone> John: Shawn and John tried to collaborate on a document but ran into licensing issues and other problems that made it impossible. Good anecdote for collaboration tool feedback.
<Becca_Monteleone> Lisa: APA research questions group is making a document on accessibility of collaboration tools (e.g. Github, Google Docs, Microsoft suite). They gave COGA 1 month to add comments last year. APA did not have time to address comments last year, so added a note with summary of COGA comments
<Becca_Monteleone> David: Did we get any feedback from APA re: issues with sharing our feedback?
<Becca_Monteleone> Lisa: Janina wanted every issue as a separate link, but compromised on a single Github issue with a link to the Google docs
<Becca_Monteleone> Lisa: APA has not looked at our extensive feedback yet. Two ways to give feedback: 1) give each issue as a separate issue in Github, or 2) copy their document into Google doc, add our comments, and then they have to reply to each comment in Google
<Becca_Monteleone> Lisa: first question - do we have everything that we need? I think we need new next steps. First, can members review it again to see if any notes are missing?
<Becca_Monteleone> Lisa: Next question - should we put it in Github or Google?
<Becca_Monteleone> Lisa: Third - we need someone to edit our comments to make them understandable to APA
<Becca_Monteleone> Lisa: Can John and Shawn capture the issues they encountered with the collaborative doc?
<Becca_Monteleone> John: John and Shawn will work on doing this.
<Becca_Monteleone> Lisa: Does any else have a strong preference for Google v. Github?
<Becca_Monteleone> David: David can be the person who transfers between Google docs and Github
<Becca_Monteleone> Lisa: Is that something that you can do quickly?
<Becca_Monteleone> David: will need to think about timeline he can work on.
<Becca_Monteleone> Lisa: Recommends a COGA call to go through the document together
<Becca_Monteleone> Lisa: Call should include Shawn, John, David, Jennie, and Lisa
<Becca_Monteleone> Eric: Also interested in joining call
<lisa> next item
tpac
<Becca_Monteleone> Lisa: TPAC scheduled for sept 11-sept 15 in Seville, Spain
<Becca_Monteleone> Lisa: Travel may be complicated. There is not a direct flight from most places to Seville. Would likely involve taking a train from Madrid.
<Becca_Monteleone> Lisa: provisional schedule - group meetings Monday and Tuesday. Tech plenary on Wednesday. group meetings Thursday and Friday
<Becca_Monteleone> Lisa: Need to leave before Friday. COGA could meet on Monday + Tuesday and Lisa could meet virtually once she leaves. This year hoping for a stronger in-person presence from COGA
<Becca_Monteleone> Lisa: do people want to have a face-to-face in Seville?
<Becca_Monteleone> John: Do we know if AG or APA or EO have schedules for TPAC yet?
<Jan_> I will not be able to attend TPAC because I will still be in the middle of my front end dev program.
<Becca_Monteleone> Lisa: not yet. Guessing that APA will be meeting. And guessing it will be closer to the beginning of the week because of the Friday conflict with Jewish new year
<Becca_Monteleone> John: unlikely to be able to attend, but does not know yet.
<Becca_Monteleone> Lisa: Even if COGA does not meet, anyone is able to attend other meetings
<lisa> next item
<Becca_Monteleone> Lisa: FAST is a document started by Michael Cooper about functional needs for accessibility
<Becca_Monteleone> Lisa: Includes functional need and user needs
<Becca_Monteleone> Lisa: First draft re: COGA needed substantial edits. COGA worked to create "buckets" of categories related to COGA.
<Becca_Monteleone> Lisa: Made a strong recommendation that co-morbidity needs to be accounted for. E.g. people with motor issues may also have COGA issues. Functional needs solutions often assume only one need
<Becca_Monteleone> Lisa: E.g. screenreaders like JAWS may be very difficult/impossible to use for some people with intellectual disabilities who also are blind
<Becca_Monteleone> Lisa: COGA feedback did not get fully integrated into FAST.
<Becca_Monteleone> Lisa: Now starting FAST task force. Task force should have COGA representation
<Becca_Monteleone> John: Interested, but does not want to overextend
<Jan_> If it starts meeting after the middle of November, I could possibly join, but my time is going to be very limited from May 8 - mid November.
<lisa> next item
<Becca_Monteleone> Lisa: Thursday is test plan and strategy subgroup
<Becca_Monteleone> Lisa: Mental health subgroup has updated action items.
<Becca_Monteleone> Lisa: Aiming to have 2 issue papers publish-ready and adding a new persona
<Becca_Monteleone> Lisa: No meeting next week.
<Becca_Monteleone> Becca: Will have publish-ready paper drafts for April 17 for review
<Becca_Monteleone> Lisa: We have many issues on Github. Can someone go through and tag them correctly?
<lisa> next item
<lisa> close item 5