CTAUR updates from COGA - some commentary

To the RQTF

Following up on my action item, here's the COGA content from the Google Doc and a bit of commentary from me. The only thing I would ask is that if I'm understanding the document correctly, the COGA comments are identified in blue text which in my high contrast colour theme I couldn't pick up, so one of my colleagues has kindly copied it out for me to review and compare with the source.  Going forward we may need to consider how feedback can be provided that isnt' reliant on colour coding or perhaps it is okay and it was just me.

Regardless, here's what I understand to be the COGA feedback and I've marked my comments with 'S.H.:' below after each COGA point. On a whole I'd like to acknowledge how valuable this contribution is and lots of exciting ideas here.



  *   Coga Suggested User Need    As a user with a cognitive or learning disability and who likes to browse on the Web, I need the structure to make sense to me, so that I find what I am looking for, without looking in the wrong place.

S.H.: agreed


  *   Coga Suggested  REQ (Requirement ) Allow the user to determine the storage location of the collaboration space.

S.H.: agree in principle but may be difficult with multiple users


  *   Coga Suggested  REQ (Requirement ) Allow search through a page, whole document, a group of documents (such as a project or directory)

S.H.: agreed if multiple documents are part of the collaboration


  *   Allow the user to structure the collaboration space.

S.H.: agree in princpe but all uses would have to agree?


  *   Coga Suggested User Need   As a slow reader I need short summary for long pieces of content or an option for an easy to understand language<https://www.w3.org/TR/coga-usable/#dfn-easy-to-understand-language> version.

S.H.: with ChatGPT this is quite achievable to have an automated AI summary. This could expand far beyond collaboration tools and there's potential for any web page to have an auto-generated summary in something resembling plain language. Thinking there would need to be some safeguards to make sure the provision of this doesn't interfere with the source document.


  *   Coga Suggested  REQ (Requirement ) Provide  summaries of changes. Examples: list of comments and revisions they made (for use in meetings, for example). Also, items marked resolved: these can be difficult to track, understand how/why they were resolved.(From CTAUR with COGA

S.H.: agreed


  *   Comments - Drafting Space December 2022.)
  *   Coga Suggested User Need  :  As a user with an executive function impairment who struggles with too much content, I need support to focus on the key content.

S.H.: Would need to have some process as to what the key content is: difficult when anyone can contribute to a document to know what that is


  *   From CTAUR with COGA Comments - Drafting Space December 2022.
  *   Coga Suggested REQ (Requirement  : 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.(from CTAUR with COGA Comments - Drafting Space December 2022.)

S.H.: agreed


  *   Coga Suggested REQ (Requirement   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. From CTAUR with COGA Comments - Drafting Space December 2022.)

S.H.: agreed in principle but how it differs from the main view would need fleshing out


  *   Coga Suggested REQ (Requirement  Ensure that users can choose how the notifications are delivered, such as through personalization and extensions.

S.H.: agreed: this could e an extension of how you can export documents so some additional info may be needed.


General COGA Feedback (not for a specific section)

  *   Add section about needing a wayfinding/orientation space within a collaboration tool. This helps users:

S.H: would WCG 2.2 Help SC cover this?


     *   Know where within the tool they are to complete certain tasks.

S.H.: I think this is discussed already


     *   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.

S.H.: I don't quite follow this one.


     *   Review a summary of current work history on a project

S.H.: agreed. A simplified presentation of just changes would help a lot of disability groups



     *   Upcoming important deadlines and tasks should also be available and easily found.


     *   This place needs to be:
        *   Persistent
        *   "One source of truth"
S.H.: Given the organic nature of collaboration tools I'm not sure how easy it would be to do this unless it's a specific project management collaboration tool like Monday


  *
  *   Add section about improving participation of all members. Examples include:
     *   Identify when group members are not participating in conversations and decisions.
        *   They may not be able to use one or more of the methods.
        *   They may not know the conversations and decision making opportunities are taking place.
        *   Silence is not necessarily an indicator of agreement.

S.H.: I like the idea but not sure what mechanism could make it happen.



Dr Scott Hollier
CEO & Co-founder
[Centre for Accessibility Australia logo]<https://www.accessibility.org.au/>
Centre For Accessibility Australia Ltd.
Phone: +61 (0)430 351 909
Email: scott.hollier@accessibility.org.au<mailto:scott.hollier@accessibility.org.au>
Address: Suite 5, Belmont Hub, 213 Wright Street, Cloverdale WA 6105

accessibility.org.au<https://www.accessibility.org.au/>
Subscribe to our newsletter<http://eepurl.com/drA-ib>
[Instagram icon]<https://www.instagram.com/centreforaccessibility/> [Facebook icon] <https://www.facebook.com/centreforaccessibility>  [Twitter icon] <https://twitter.com/centrefora11y>  [LinkedIn icon] <https://www.linkedin.com/company/centreforaccessibility/>

CFA Australia respectfully acknowledges the Traditional Owners of Country across Australia and pay our respects to Elders past, present and emerging