Meeting minutes
Janina, we're giving you time.
Collaboration Tools Accessibility User Requirements.
jason: changes to document made to resolve open issues
changes merged directly
janina: happy with changes
reviisons re being worked on by Janina
janina: discussed with COGA about points considered out of scope,
woudl be good to discuss with COGA on our decision and clarify with COGA
jasoN: how long for reviiosns?
janina: aiming for next meeting
jason: good to circle back to references/citations in recent literature
to head towards working draft
janina: would be good to put out working draft earlier so we have an updated draft ot work from goin forward,
also need glossary
jasons: we do definte in document, do we need glossary?
janina: yes, cna use exisitng definitons for glossary
jason: lhow about makng all changes in response to comments, then send out working draft - not just a heartbeat draft, a call for review with reasonable review time
then in parallel add citations, discuss COGA comments
janina: would prefer wait for referencs, citations before a major 'lat call'
jason: let's get working draft in place and then work out what else we can do in parallel once htat's in place
subtopoic+ issue 18, 19, 20 and 21
in requirement 14c at end of notificaiotn and messages
<DavidSwallow> User Need X: As a user with an executive function impairment who struggles with too much content, I need support to focus on the key content.
already discussed by Jason and Scott on GitHub
<DavidSwallow> REQ Xa: I need ability to mark for myself which items need you to follow up on. Notifications sometimes get marked "read" but do not have a way for you to remember to come back to them. You may need to review them multiple times to be sure you understand, and to complete the task. Further allow Users a view of just the items they need to follow up on, both from notifications, and any additional they identify.
and possibility of AI covering it
<DavidSwallow> REQ Xb: Provide a mode of operation for a separate viewing mechanism. Example: different window. This can better support readability, and maintain focus in the main document.
<DavidSwallow> REQ Xc: Ensure that users can choose how the notifications are delivered, such as through personalization and extensions.
jason: i thik the first one does relate to issue tracking
perhaps proviing some kind of labelling feature in UI for comments in issue tracking, potentially private to the user
janina: more software design
jason: any thoughts o response?
janina: first one is covered,
it's i there
Scott: agreed
jason: for labelling, some discussion good for this one
jason: yes, person with disability may not want labelling visible to everyone
janina: woudl be good to hear more from COA perspective on this
janina: let's defer that one
subtopic+ issue 22
<DavidSwallow> Add section about needing a wayfinding/orientation space within a collaboration tool This helps users: • Know where within the tool they are to complete certain tasks. • The names and locations available within the tool used for a specific group. Example: if there are multiple document libraries within a collaboration space, this makes finding the one related to a project difficult to find. • Review a summary of current work histo[CUT]
jason: quite general
janina: 'you are here' feature?
scott: WCAG 2.2 has consistent and finable help, woudl that cover this?
jason: if there's someting rleated to issue tracking/project maangement
but don't tihnk there are collaborative features not already covered, seems more general to wide variety of applicaitons and possibly out of scope unless ther'es something related to issue tracking
scott: agree, not specific to collaboraiton tools
jason: yes, focusing on collaboraiton aspect of tool, not every aspect of tool
jason: agreed, issues best addressed in gidance elsewhere
janian: flagged reelvance to WCAG
subtopic+ issue 23
<DavidSwallow> Add section about improving participation of all members. Examples include: • Identify when group members are not participating in conversations and decisions. o They may not be able to use one or more of the methods. o They may not know the conversations and decision making opportunities are taking place. o Silence is not necessarily an indicator of agreement.
jason: social usage advice rather than software design advice
outside of scope
janina: agreed
can say someting general about needs in colaborative envrionment from a non-technical perspective
jason: great proposal
could be framed that a successful collaboraiton needs technolog used appropriately
introductoy section, deliniating scope of document
while remiding good designed software system is not enough
janina: accepting comment and adding intro on appropriate facilitation by collaboraiton teams
janina to write, jason to review
scott: just a concern that sometimes people are jumping in and out of collaboraiton toosl,
not always pepole bieng left otu, may be many reasons
raja: sometimes paper adn pen may be more functional,
lookng at user communication is more mportant
janina: basically accepting, will explain a little differently
jason: and people need to be reminded that technoogy is still important
david: three comments left for next time