Re: COGA’s feedback on Collaboration Tools Accessibility User Requirements

Hi all,

As you may be aware, we are meeting with RQTF tomorrow to discuss COGA's feedback on Collaboration Tools Accessibility User Requirements (CTAUR).

The meeting is during RQTF's usual meeting slot at 9am Boston time.

It's been brought to my attention that not everyone will have access to the RQTF meeting page with details of how to join the meeting.

So, would you mind letting me know if you plan to attend the meeting? Then I'll send you the details privately.

Many thanks,

David
________________________________
From: Lisa Seeman <lisa1seeman@gmail.com>
Sent: Tuesday, March 19, 2024 11:50 AM
To: David Swallow <dswallow@tpgi.com>
Cc: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Subject: Re: COGA’s feedback on Collaboration Tools Accessibility User Requirements

CAUTION:EXTERNAL EMAIL SENDER!

As a small note, the latest draft is at  Collaboration Tools Accessibility User Requirements <https://w3c.github.io/ctaur/>

The content seems to have changed - section 9 is new. so it would be useful to read it over again before the meeting.

All the best
Lisa


On Mon, Feb 26, 2024 at 6:15 PM David Swallow <dswallow@tpgi.com<mailto:dswallow@tpgi.com>> wrote:
Hi everyone,

Over the last few months, I have been communicating COGA’s feedback on Collaboration Tools Accessibility User Requirements (CTAUR) to the Research Questions Task Force (RQTF) who created the document.

Although RQTF welcomed all feedback, and there has been a lot of discussion, they pushed back on quite a few issues due to them being out of scope. This is typically where:

  *
COGA’s feedback doesn’t pertain specifically to collaborative tools, but rather to software in general.
  *
RQTF felt a particular issue was already covered in CTAUR.
  *
RQTF felt a particular issue was about a very specific environment and not generalizable enough.
  *
An issue was explained from the perspective of a person with cognitive disabilities, but the document doesn’t explain it from the perspective of any other user group, so it would seem odd to mention them specifically.

Due to the number of issues rejected, it was felt that a meeting between COGA and RQTF would be useful, as this would allow members of COGA who feel strongly about a particular issue to make their case.

Unfortunately, because of how COGA gathered feedback in a Google Doc, some of the comments have become disconnected from the person who created them. So, it’s difficult to know who might want to attend a meeting. We know John, Jennie, and Lisa gave some of the feedback, but there will be others.

I've created a document which attempts to summarize COGA’s feedback on CTAUR to RQTF as well as RQTF’s response, to allow COGA members to decide on whether they would like to join the COGA-RQTF meeting. The first few issues have ‘additional response from COGA’ as we managed to discuss these issues.

Please have a look through the document, particularly at the issues that RQTF have rejected, and if you see something that you feel needs further discussion, let us know.


  *   COGA’s feedback on Collaboration Tools Accessibility User Requirements: https://docs.google.com/document/d/1CFJoA8DHst31mej6o2en49wXhoMMLVe15fUzQB-owk8/edit?usp=sharing



  *   For reference, COGA’s original feedback on CTAUR can be found here: https://docs.google.com/document/d/1CJhBYRI-zk2rl_mohHZ63xAGZxzpDMxhHhXT66bjFBI/edit?usp=sharing

  *   The latest version of CTAUR (which may have changed slightly since COGA provided feedback) can be found here: https://w3c.github.io/ctaur/


Any questions, let me know!


David Swallow
Principal UX Consultant


TPG Interactive
https://www.tpgi.com<https://www.tpgi.com/>


A Vispero Company
https://www.vispero.com<https://www.vispero.com/>


[Join us at CSUN 2024, Vispero Booth #503, March 18 -22; Anaheim, CA. Make every interaction inclusive and Usable. Check out our accessibility talks.]<https://www.tpgi.com/csun-2024-at-conference-tpgi-sessions/>

--

This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.