- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 17 Oct 2019 13:02:40 +0000
- To: Scott Hollier <scott@hollier.info>, "Janina Sajka (janina@rednote.net)" <janina@rednote.net>, Accessible Platform Architectures Administration <public-apa-admin@w3.org>
+1 -----Original Message----- From: Scott Hollier <scott@hollier.info> Sent: Wednesday, October 16, 2019 7:27 PM To: Janina Sajka (janina@rednote.net) <janina@rednote.net>; Accessible Platform Architectures Administration <public-apa-admin@w3.org> Subject: RE: 48-Hour Call for Consensus (CfC): WebRTC Accessibility Considerations To Janina +1 from me. Scot. Dr Scott Hollier Digital Access Specialist Mobile: +61 (0)430 351 909 Web: https://nam01.safelinks.protection.outlook.com/?url=www.hollier.info&data=02%7C01%7Cjjwhite%40ets.org%7C24803adfaff74c2805af08d7529054c3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637068652179379472&sdata=z%2F4pwtMsElQMXSu2GkURvBfv1Ro0Zq7UHg8Mvdxxm30%3D&reserved=0 Technology for everyone Australian Access Awards 3 December 2019, Perth. Join us for the celebration. Keep up with digital access news by following @scotthollier on Twitter and subscribing to Scott's newsletter. -----Original Message----- From: Janina Sajka (janina@rednote.net) <janina@rednote.net> Sent: Wednesday, 16 October 2019 11:16 PM To: Accessible Platform Architectures Administration <public-apa-admin@w3.org> Subject: 48-Hour Call for Consensus (CfC): WebRTC Accessibility Considerations Colleagues: This is a Call for Consensus (CfC) to the Accessible Platform Architectures (APA) Working Group on a proposed Accessibility Considerations addendum to the WebRTC 1.0 specification: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2Fwebrtc%2F&data=02%7C01%7Cjjwhite%40ets.org%7C24803adfaff74c2805af08d7529054c3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637068652179379472&sdata=zXh4DUMFgSaDKb%2BZdAllZrhRWbOdBNb5Plmp9BmFDe8%3D&reserved=0 ***Begin Proposed Section ------------------ Accessibility considerations [New section, informative] The WebRTC 1.0 specification exposes an API to control protocols (defined within the IETF) necessary to establish real-time audio, video and data exchange. Real-time Text, defined in RFC 4103 on which people who are deaf or hard of hearing (among others) rely on for their communication needs, utilizes T.140 encapsulated in RTP to enable the transition from TDD/TTY devices to IP-based communications. Support for RFC 4103 is especially important as it is being established as the new and more reliable mechanism for text communications with Public Safety Access Points (PSAP).[1] Since Real-time Text requires the ability to send and receive data in near real time, it can be best supported via the WebRTC 1.0 data channel API. As defined by the IETF, the data channel protocol utilizes the SCTP/DTLS/UDP protocol stack, which supports both reliable and unreliable data channels. The IETF chose to standardize SCTP/DTLS/UDP over proposals for an RTP data channel which relied on SRTP key management and were focused on unreliable communications. Since the IETF chose a different approach than the RTP data channel as part of the WebRTC suite of protocols, as of the time of this publication there is no standardized way for the WebRTC APIs to directly support Real-time Text as defined at IETF and implemented in U.S. (FCC) regulations. The WebRTC working Group will evaluate whether the developing IETF protocols in this space warrant direct exposure in the browser APIs and is looking for input from the relevant user communities on this potential gap. Within the IETF MMUSIC WG, work is ongoing to enable Real-time text to be sent over the WebRTC data channel, allowing gateways to be deployed to translate between the SCTP data channel protocol and RFC 4103 Real-time text. This work, once completed, would enable a unified and interoperable approach for integrating real-time text in WebRTC user-agents (including browsers) - through a gateway or otherwise. MMUSIC-T140: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-holmberg-mmusic-t140-usage-data-channel&data=02%7C01%7Cjjwhite%40ets.org%7C24803adfaff74c2805af08d7529054c3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637068652179379472&sdata=6qdVePGcXaP0vOJiWdJUZeIeoqjMfkHz6jkEK8aq4ds%3D&reserved=0 At the time of this publication, gateways that enable effective RTT support in WebRTC clients can be developed e.g. through a custom WebRTC data channel. This is deemed sufficient until such time as future standardized gateways are enabled via IETF protocols such as the SCTP data channel protocol and RFC 4103 Real-time text. This will need to be defined at IETF in conjunction with related work in W3C groups to effectively and consistently standardise RTT support internationally. [1] https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ecfr.gov%2Fcgi-bin%2Ftext-idx%3FSID%3Dada7cebd65433a9e05c35426a2bc76b8%26mc%3Dtrue%26node%3Dpt47.3.67%26rgn%3Ddiv5&data=02%7C01%7Cjjwhite%40ets.org%7C24803adfaff74c2805af08d7529054c3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637068652179379472&sdata=JDNqdMLeVwDxhEs6hjA%2BIxRY9Cb64ys8Lpr747aMdGI%3D&reserved=0 ------------------ ***Action to Take*** This CfC is now open for objection, comment, as well as statements of support via email. Silence will be interpreted as support, though messages of support are certainly welcome. If you object to this proposed action, or have comments concerning this proposal, please respond by replying on list to this message no later than 23:59 (Midnight) Boston Time, Sunday 20 October. NOTE: This Call for Consensus is being conducted in accordance with the APA Decision Policy published at: https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Fdecision-policy&data=02%7C01%7Cjjwhite%40ets.org%7C24803adfaff74c2805af08d7529054c3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637068652179379472&sdata=PI%2FJ80h2qGZ6S3jkafqojEB3%2FoGgcmtDOLYLIccFGIU%3D&reserved=0 Thanks especially to our Research Questions Task Force (RQTF) for working with WebRTC to develop this addendum. Janina -- Janina Sajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup:https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org&data=02%7C01%7Cjjwhite%40ets.org%7C24803adfaff74c2805af08d7529054c3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637068652179379472&sdata=gHv2gmgr%2BVHr0ZI9vsqMl5FGZ6ouO3p1jCPSdJ2LByk%3D&reserved=0 The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectureshttps://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=02%7C01%7Cjjwhite%40ets.org%7C24803adfaff74c2805af08d7529054c3%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637068652179379472&sdata=XbvM5TcP0czRYa1I3EaxrGYA640XJGQiw7bNaWAFBoA%3D&reserved=0 ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Thursday, 17 October 2019 13:02:49 UTC