Meeting minutes
Collaboration Tools Accessibility User Requirements.
jason: changes we're going ot make
Janina had beginnings of additional requirement for Seciton 9
janian: evolved on CGOA
Scott: identified references relevant to the use of desktop and Web-based UI conventions.
scot: following up on actio form two weeks ago, ciruclated references to list
focused on UI deskltp v web optimised in look and feel of collaborative tools
janina: so expecting a better understanding of section 9 - wh to what degree soudl a web app borrow from conventions
jason: great. so how ot progress?
david: had COGA meeting, agreed on outstnaidng issues
list created
janina: issues were primarily from Seciton 9 in preovus dicussion
david: general comments:
first comment: glossary of icons and symbols
janina: happy to add a glosary, requesting COGA to provide
if COGA provides text, will reate glossary
scott: can we have a timeframe for COGA to respond?
janina: yes, ahve requested in reference to April /May
david: commetns about reference to non-normative guidance
janina: has already been changed two weeks ago, issue addressed
<DavidSwallow> "improving accessibility for people with cognitive and learning disabilities is addressed in [coga-usable]."
janna: agreed
david: rest referers to difficulty finding items inteh document
janina: agreed Seciton 9 could expand issues not covered, will look at specific suggestions
janina regarding symobls: need to be careful as there's no spec yet
AAC currently in CR coudl be referenced once its published
jason: coudl put a note to the CR/under devleopment
janina: lets reference developing AAC guidance
in terms of where it goes, some confusion between 10a and 19a by COGA, will look to confirm
david: some concern that icons and symbols were being conflated
janina: resolved by pointing to the work on symbols
david: next issue of using plain languag enames, e.g. using chat instead of IRC
coudl vendor specific go into the glossary
janina; yes
jason: don't think IRC is in the document
janina: let's get specifics
jason: reviisng Seciotn 9 coudl cover that
david: feedback on optional user interface dicussion
jason: suggestion is collaborative enviroments shouldn't be forced ot use its interface, API could use with own tool which has accessibility advantages, e.g. familiarity
go as additional Section 9 requirement
janina: yes, provide an API
jason: doens't remove need to make their own UI accessible, but does provide additonal options
david: avoid and correct mistakes needed
scott: in WCAG 3.3 so important to all web content including collaboraiton tools, not unique here
jason: see if WCAG reference fits but agreed it's not unique here
david: attention control guidance
janina: too general
shoudl be specificlaly content usable,
Privacy Principles.
jason: does it adequately address privay isue?
jjanina: would like to see a more general privacy statemetn from W3C that can be adopted rather than everone having thier own
jason: EU has good process
janina: good to keep reading
jason: on accessibility, concerns mianly what can be inferred by interaction of user
not about disclosure, but inference that can be drawn
Immersive captions.
no report/URI yet
APA will suport progress to FPWD
raja: has been completed, ready to go forward
janina: can start reading it?
raja: yes
jason: read it fairly recently, seems reasonble
formal changes needed
raja: let me know if need anything
janina: need ot thik about how to promote it for wide review
Miscellaneous updates and topics.
janina: IRC lounge tool
<janina> https://
can log issues
scott: seems more stable this time but was an issue with dropouts last time
janina: conrast issues are present
scott: did have these issues last itme, looks liek some improvemetns