Meeting minutes
<jasonjgw> chiar: jasonjgw
test
Collaboration Tools Accessibility User Requirements.
jason: some questions
first issue - made changes following meeting to editors draft
- section 1.4: impications of cognitive issues with collaborative envrionments, barriers to wide variety of AT users
Changes supported by Scott and Janina
- seciton 6.3
amendment to note clarifying change histories
made change to explain what is repsonsibility fo collaboration tool, and wht is responsibility of the user of the tool
referncing collaborative process in section 1.5
janina: good to acknowlede that humans are part of solution,
jason: if noticed other places fo rthis, shoudl add
- agreed to dicuss seciotn 9: requirements but not specific / catch-all seciton of dcument
too brad, except for example of keyboard conventions and compatibility with AT
i.e. revision tracking, comments already covered elsewhere
have recongised issue
Agreed that there were concerns on how to cover issues while at the same time be practical/useful
janina: maybe use practicable phrase?
jason: web applicaitons don't always follow desktop/windowing system, or app conventions that ocme with OS
issue with whether web apps should be more desktop-like or web-like when running in web browser
also if happen t have a good perfence system for UI, some oculd be handled
but dn't have ag ood mechanism on web but can be done on per-app basis
janina: articles coudl be referenced on to what articles address web app v desktop app interface
scott: I'm in a position to look at this
jason: great
janina: yes, want to document that there's reasoned arguments on both side, issues and barriers
jason: web devleoper dones't know what's familiar so they make choices
scott: will pull togethr a lit review
jason: could be standalone info in Seciton 9
then examples coudl be separate point
<janina> https://
test
jason: aside from intro, the rest of feedback is Seciton 9
janina: can join COGA call to look at editoral tweaks
happywit most edits, careful with WCAG gap reference wording
to keep neutral,
everyithng else Secitgon 9
as dicusse don design patterns web v desktlop app design
jasON; and supporting AT that support collaborative operaitons - revision, comment, etc
basically if COGA are happy wiht seciton 108, then that's a good place and now have steps on Seciton 9
jason: put nto place suggestions infomally agred,
then AT support as second point
and looking for exmaples of short series of process, windows tabs etc as applies to collaborative featuers
jason; can we get edits in before COGA call on Monday,
jason: will endeavour to update today
Draft note on Ethical Principles for Web Machine Learning.
janina: were in the early design phase of this doucment
now fnished its process, APA asked to sign off
would want RQTF to review first
scott: gropu review?
janina: let's all ready and dicuss next week on any issues
Immersive captions.
raja: final documentation is getting done, ready in one week
will meet with them today
janina: if you sent email to RQTF list and its ready to move to NOte track, we can tehn read it and review
after that it goes to APA wide review
jason: yes, as soon as the group is ready we'll review
raja: great. ALso hopiong ot get a final answer today, and afer that will email all
Miscellaneous updates and topics.
jason: interesting article publisehd by Linux weekly news
new dectralised tool - a bit like GitHub / GitLab, web interface that runs locally
so different collaborative tool