[rtcweb] RTC Accessibility User Requirements published - feedback request

Joshue O Connor <joconnor@w3.org> Mon, 23 March 2020 17:31 UTC

Return-Path: <joconnor@w3.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 80E363A044A for <rtcweb@ietfa.amsl.com>; 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-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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id fO9KvdPgLjH7 for <rtcweb@ietfa.amsl.com>; Mon, 23 Mar 2020 10:31:09 -0700 (PDT)
Received: from raoul.w3.org (raoul.w3.org []) (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 <rtcweb@ietf.org>; Mon, 23 Mar 2020 10:31:09 -0700 (PDT)
Received: from [] (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 <joconnor@w3.org>) id 1jGQuo-0002ID-IP for rtcweb@ietf.org; Mon, 23 Mar 2020 17:31:08 +0000
To: rtcweb@ietf.org
From: Joshue O Connor <joconnor@w3.org>
Organization: WAI/W3C
Message-ID: <f4b157a7-4dcb-3e16-c01c-d5bce0591dc0@w3.org>
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: <https://mailarchive.ietf.org/arch/msg/rtcweb/Y1Odc1uEuj-9SZJroO2lY8D5Dcg>
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 <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 17:34:07 -0000

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.



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)

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)

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:
If this is not feasible, send email to:
Please send comments by 21 April 2020.

Updates: In-progress updates to the document are available in the 
Editors' Draft at:

Share: We encourage you to share this information and include @w3c_wai, 
@w3c, #accessibility, #a11y, #RAUR, #RTC
Here's tweet you can use:

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)