Meeting minutes
RAUR and XAUR update on the CfC.
<joconnor> JS: There are two CFCs
<joconnor> Most have voted on only one
<joconnor> We have one per document
<jasonjgw> Janina notes there are two CfCs - one for each document, to be responded to separately.
<joconnor> Not too late for vote - open till Friday
js: Notes most people haven't voted on both CfCs, only one. Should have made that more obvious, but it's not too late!
<SteveNoble> FYI - I am being pulled into another meeting that begins at 9:30 Eastern
<jasonjgw> CfCs are open until midnight Boston time on Friday.
Media synchronization research.
<joconnor> JW: still working on...
<joconnor> Great contribs from Steve
<joconnor> SN: The part that is slowing me down is Sign Language Interp
<joconnor> I've reached out to a deaf colleague and gotten feedback
<joconnor> As well as intros to other related work by my colleague which is relevant
<joconnor> Am learning a lot
<joconnor> <gives overview on time lag and interp errors>
<joconnor> Some delay and latency is good - into to interp effectively
<joconnor> It can help reduce error
<joconnor> Difficult in live meetings
<joconnor> Am writing up findings
<joconnor> am getting there
<joconnor> JS: Sounds good
<joconnor> If we can make a recommendation on this - this will be helpful
<joconnor> SN: Gotta drop
<joconnor> JW: Thanks for your good work on this
<joconnor> <various lols >
<joconnor> JW: Mentioned Grammar variances
<joconnor> SN: Discusses latency variance
<joconnor> JW: Thanks Steve
Making Content Usable for People with Cognitive and Learning Disabilities update.
<joconnor> JW: There is a CFC coming soon
<joconnor> JS: I dont know where this ended up - seems like close but not sure
<joconnor> JS: Expecting outreach
<joconnor> JW: Be aware it is coming, and please do review
<joconnor> JS: It is a big doc
<joconnor> JS: It would be better if structure improved
<joconnor> Others have similar suggestions to me
<joconnor> JW: I've also reviewed and +1 to Janina
<joconnor> Dividing it up, or a clearer outline of structure and relationships would be good
<joconnor> Still time to review
Accessibility of natural language interfaces.
<joconnor> JW: Work is progressing
<joconnor> Ref to latest text is in agenda...
<joconnor> I've added some cognitive a11y reqs to the draft...
<joconnor> John P made some good comments on reorg of input and output reqs
<joconnor> JW: There are cognitive issues added
jo: Have merged Jason's changes into main
jo: let's focus on main in our work now
<joconnor> JW: There is a lot to cover, and it would be useful to give time for review and comment on the draft
<joconnor> That covers issues so far.
<joconnor> JS: Sounds good - we want a FPWD
<joconnor> So we need to have substance in there.
<joconnor> JW: Yes, its a way off, but if we give it some attention we can then make that step
<joconnor> We can also insert editors notes
<joconnor> JOC: Logging issues in GitHUb is also a good.
<joconnor> With the NAUR label
<joconnor> JS: We have heard suggestions for edits
<joconnor> branches and PRs etc, also file GH issue.
<joconnor> JS: Anyone here OK, with filing issues?
<joconnor> JB: I can log issues but not PRs.
<joconnor> John and Jason would be up for some demo/training of how to do that.
<joconnor> JB: We should be doing this all the time.
<joconnor> JS: That ability of working with the code - is really helpful - but you need a comfortable way of doing it.
<joconnor> JP: I've issues of getting GH on my work machine.
<joconnor> JOC: You can use your browser
<joconnor> JS: There are lots of options, and also a11y probs with some
<joconnor> <distinguishes Git from GH>
<joconnor> JW: John do you want to create issues based on that?
<joconnor> JP: I can
<joconnor> <discusses branches and commits etc>
<joconnor> JS: Offering helpful alternatives is useful
<joconnor> So branching allows this.
<joconnor> <disusssion of editing setups>
<joconnor> and workflow...
<joconnor> JS: getting to the right repo can be a problem
<joconnor> But good for issue
<joconnor> JOC: I like using issues for tracking
<joconnor> JS: Using markdown is good
<joconnor> JW: Markdown also supported in comments area
<joconnor> JS: Branching tuts?
<joconnor> JW: You'd like to do that?
<joconnor> JS: Yes
<joconnor> <discussion of editors>
<joconnor> JS: Anyone want to focus on areas or just review?
<joconnor> SH: Regarding GitHub etc doesn' work well with my screen mag set up
<joconnor> Any tuts for visual a11y would be helpful
<joconnor> JW: We could discuss outside the meeting - when looking at branches and changes
<joconnor> +1 to using text editor bash etc
<joconnor> JB: We do need to better explain how our tools work
<joconnor> JW: We can work on various issues
Miscellaneous updates and topics relevant to Task Force work.
<joconnor> JOC: I like the idea of getting review of sections of the NAUR
<joconnor> JS: Scott is working on a11y of remote meetings etc
<joconnor> JS: We also have an a11y concern - came from Jeanne, about transcripts
<joconnor> May prevent access
<joconnor> JB: There is a default that can be overriden
<joconnor> JS: So we can do this?
<joconnor> JB: There could be a provision for this.
<joconnor> JS: I'll have a look and be up to speed
<joconnor> JB: If there is a problem let me know