From joconnor@w3.org Mon Mar 23 10:31:11 2020 Return-Path: X-Original-To: rtcweb@ietfa.amsl.com Delivered-To: rtcweb@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80E363A044A for ; Mon, 23 Mar 2020 10:31:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fO9KvdPgLjH7 for ; Mon, 23 Mar 2020 10:31:09 -0700 (PDT) Received: from raoul.w3.org (raoul.w3.org [128.30.52.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF7CC3A0404 for ; Mon, 23 Mar 2020 10:31:09 -0700 (PDT) Received: from [79.171.75.117] (helo=InterAccesss-MacBook-Pro.local) by raoul.w3.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jGQuo-0002ID-IP for rtcweb@ietf.org; Mon, 23 Mar 2020 17:31:08 +0000 To: rtcweb@ietf.org From: Joshue O Connor Organization: WAI/W3C Message-ID: Date: Mon, 23 Mar 2020 17:31:13 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------A1107B94A34D92E96FD7AC85" Content-Language: en-GB Archived-At: Subject: [rtcweb] RTC Accessibility User Requirements published - feedback request X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2020 17:34:07 -0000 This is a multi-part message in MIME format. --------------A1107B94A34D92E96FD7AC85 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi all, I work as an Emerging Web Technology specialist at W3C/WAI, with a special interest in accessibility. I'd like to share the recent announcement of the publication of our new 'RTC Accessibility User Requirements' document. See below and please do forward to any other interested parties and if you have feedback we'd love to hear it. Thanks Josh Dear WAI Interest Group, WAI’s Research Questions Task Force (RQTF) and Accessible Platform Architectures (APA) Working Group invite you to comment on the First Public Working Draft of a W3C Working Group Note:     RTC Accessibility User Requirements (RAUR) https://www.w3.org/TR/RAUR/ RAUR outlines user needs, requirements, and scenarios for real-time communication (RTC) to be accessible to people with disabilities. Accessible telecommunication technology is increasingly important for people who are working remotely and relying on RTC for daily needs. The purpose of this document is to inform the development of specifications and underlying architecture at W3C and beyond. Some of the requirements apply at the system or platform level, and some are authoring requirements. For more information, see:     RTC Accessibility User Requirements – Call for Review (blog post) https://www.w3.org/blog/2020/03/rtc-accessibility-user-requirements-call-for-review/ Review and Comments: We particularly would like input on any user needs or requirements that are missing from this draft. To comment, please open a new issue in the APA GitHub repository, and add the “RAUR” label: https://github.com/w3c/apa/issues/new If this is not feasible, send email to: public-apa@w3.org Please send comments by 21 April 2020. Updates: In-progress updates to the document are available in the Editors' Draft at: http://w3c.github.io/apa/raur/ Share: We encourage you to share this information and include @w3c_wai, @w3c, #accessibility, #a11y, #RAUR, #RTC Here's tweet you can use: https://twitter.com/w3c_wai/status/1240672981225033728 Regards, Janina Sajka, APA Working Group Chair Jason White, Research Questions Task Force Facilitator Joshue O Connor, W3C Emerging Web Technology Specialist Michael Cooper, W3C Staff Contact for APA Working Group Shawn Lawton Henry, W3C WAI Accessibility Outreach -- Emerging Web Technology Specialist/Accessibility (WAI/W3C) --------------A1107B94A34D92E96FD7AC85 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi all,

I work as an Emerging Web Technology specialist at W3C/WAI, with a special interest in accessibility. I'd like to share the recent announcement of the publication of our new 'RTC Accessibility User Requirements' document. See below and please do forward to any other interested parties and if you have feedback we'd love to hear it.

Thanks

Josh

Dear WAI Interest Group,

WAI’s Research Questions Task Force (RQTF) and Accessible Platform Architectures (APA) Working Group invite you to comment on the First Public Working Draft of a W3C Working Group Note:
    RTC Accessibility User Requirements (RAUR)
https://www.w3.org/TR/RAUR/

RAUR outlines user needs, requirements, and scenarios for real-time communication (RTC) to be accessible to people with disabilities. Accessible telecommunication technology is increasingly important for people who are working remotely and relying on RTC for daily needs. The purpose of this document is to inform the development of specifications and underlying architecture at W3C and beyond. Some of the requirements apply at the system or platform level, and some are authoring requirements.

For more information, see:
    RTC Accessibility User Requirements – Call for Review (blog post)
https://www.w3.org/blog/2020/03/rtc-accessibility-user-requirements-call-for-review/

Review and Comments: We particularly would like input on any user needs or requirements that are missing from this draft. To comment, please open a new issue in the APA GitHub repository, and add the “RAUR” label:
https://github.com/w3c/apa/issues/new
If this is not feasible, send email to:
public-apa@w3.org
Please send comments by 21 April 2020.

Updates: In-progress updates to the document are available in the Editors' Draft at:
http://w3c.github.io/apa/raur/

Share: We encourage you to share this information and include @w3c_wai, @w3c, #accessibility, #a11y, #RAUR, #RTC
Here's tweet you can use:
https://twitter.com/w3c_wai/status/1240672981225033728

Regards,
Janina Sajka, APA Working Group Chair
Jason White, Research Questions Task Force Facilitator
Joshue O Connor, W3C Emerging Web Technology Specialist
Michael Cooper, W3C Staff Contact for APA Working Group
Shawn Lawton Henry, W3C WAI Accessibility Outreach 
-- 
Emerging Web Technology Specialist/Accessibility (WAI/W3C)
--------------A1107B94A34D92E96FD7AC85--