Public announcements for CTAUR

To the RQTF

I've created content for the public announcements below. Would it be possible for someone to put the below on GitHub? I've got the hang of editing content on GitHub but starting things still takes me quite a bit of time so if someone can help with this bit it'd be great.

A few notes:

  *   I've endeavoured to mirror the announcements as close to our other RQTF announcements as possible
  *   I've tried to summarise the abstract a bit of the e-mail and webpage announcements
  *   In the template it says that only create a blog post if absolutely necessary, so have left it for now but happy to do one if needed
  *   I've also changed our call for feedback to be in a similar way to our discussions at TPAC: made it two distinct choices of GitHub and email, but specified in email that feedback needs to be itemised
  *   Apologies for any strange formatting in the text

Announcement info for GitHub follows:


Collaboration Tools Accessibility User Requirements announcement


  *   Expected date: November 2022
  *   Contact(s) for Shawn to get info: Jason White jason@jasonjgw.net<mailto:jason@jasonjgw.net>; Scott Hollier scott.hollier@accessibility.org.au<mailto:scott.hollier@accessibility.org.au>; 'Janina Sajka' janina@rednote.net<mailto:janina@rednote.net>
  *
  *   Draft document:  https://raw.githack.com/w3c/ctaur/FPWD-2022/index.html
  *
  *   Related pages that need updating: (such as Overview page)
Any notes for us working on the announcements, such as important points to get across: this is a first public working draft and acknowledges that more literature is needed, seeking wider input as it is currently weighted towards experiences of vision-related disabilities.

  *   @@
Status of announcements below: draft not ready for review
Review of announcements below:

  *   @@ OKed by [name] on [date]

Doc Abstract & Status -

Abstract:

This document outlines various accessibility-related user needs, requirements and scenarios for collaboration tools. The tools of interest are distinguished by their support for one or more specific collaborative features. These features include real-time editing of content by multiple authors, the use of comments or annotations, and revision control. A Web-based text editor or word processor offering all of these features would be a central example of such a collaboration tool.

The accessibility-related user needs and corresponding requirements described in this document may be implemented in the collaboration tool itself, or elsewhere, for example in an assistive technology such as a screen reader. The scope of the discussion is not limited to problems that can be solved in the design or implementation of the collaboration tool. Instead, a holistic approach is taken that gives foremost priority to the user's perspective, leading to the identification of solutions that may be implemented by different components of the software involved in performing a collaborative task.

Although the user needs and associated requirements identified in this document are not normative accessibility guidance, they may influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are relevant to software developers who contribute to any of these aspects of the collaborative experience

Status:
First Public Working Draft

WAI E-mail -
FOR REVIEW:


Dear WAI Interest Group,



W3C WAI invites you to comment on the First Public Working Draft of the Note:

            Collaboration Tools Accessibility User Requirements at <link>



Background: The purpose of this Note is to outline various accessibility-related user needs, requirements and scenarios for collaboration tools.



Functions of collaborative tools include real-time editing of content by multiple authors, the use of comments or annotations, and revision control. Examples of collaborative tools include a Web-based text editor or word processor offering these functions.



The accessibility-related user needs and corresponding requirements

may be implemented in the collaboration tool itself, or elsewhere, for example in an assistive technology such as a screen reader.



The solutions identified in this Note are intended to influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are relevant to software developers who contribute to any of these aspects of the collaborative experience



For in-progress updates to the document, see the Editors' Draft at:

            https://raw.githack.com/w3c/ctaur/FPWD-2022/index.html



To comment, please use one of the following:

  *   By GitHub:  please open a new issue in the APA GitHub repository:

            https://github.com/w3c/apa/issues/new Please add the label CTAUR. Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue.

  *   By email: , Please send comments in e-mail to:

            public-apa@w3.org<mailto:public-apa@w3.org>. Ensure that your comments are itemised into single issues.



Please send comments by  Date 2022*.



Thank you in advance for your comments.



Regards,

Scott Hollier, Co-Chair, Research Questions Task Force

for:

Janina Sajka, APA Working Group Co-Chair Becky Gibson, APA Working Group Co-Chair Jason White, Research Questions Task Force Facilitator Scott Hollier, Research Questions Task Force Facilitator Michael Cooper, W3C Staff Contact for APA Working Group


WAI News:
FOR REVIEW: Collaboration Tool Accessibility user Requirements First Public Working Draft

The Accessible Platform Architectures (APA) Research Questions Task Force (RQTF) welcomes feedback on the First Public Working Draft of the Collaboration  Tool Accessibility User Requirements.


The purpose of this Note is to outline various accessibility-related user needs, requirements and scenarios for collaboration tools.



Functions of collaborative tools include  real-time editing of content by multiple authors, the use of comments or annotations, and revision control. Examples of collaborative tools include a Web-based text editor or word processor offering these functions.



The accessibility-related user needs and corresponding requirements

may be implemented in the collaboration tool itself, or elsewhere, for example in an assistive technology such as a screen reader.



The solutions identified in this Note are intended to influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are relevant to software developers who contribute to any of these aspects of the collaborative experience



For in-progress updates to the document, see the Editors' Draft at: https://raw.githack.com/w3c/ctaur/FPWD-2022/index.html



To comment, please use one of the following methods:

  *   By GitHub:  please open a new issue in the APA GitHub repository: https://github.com/w3c/apa/issues/new Please add the label CTAUR. Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue.
  *   By email: , Please send comments in e-mail to public-apa@w3.org<mailto:public-apa@w3.org>. Ensure that your comments are itemised into single issues.



Please send comments by  Date 2022*.




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: 92 Adelaide Street, Fremantle WA 6160

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