Real-time communication accessibility - working group interdependencies

One of our agenda for the meeting tomorrow is to identify dependencies among working groups relevant to the real-time accessibility needs documented in the draft at
https://www.w3.org/WAI/APA/wiki/Accessible_RTC_Use_Cases


Here are my notes, based on a reading of the draft.

WCAG/Silver is relevant to whichever of these requirements should be expected to be implemented in an accessible real-time communication application.

“Incoming Calls”: who is working on browser or operating system-level notifications delivered by Web applications? Are they subject to Web standards?

“Accessible Call Set up”: possibly WebRTC, possibly instead the signaling protocol used by the application to create/modify calls.

“Audio routing and multi-channel”: Audio Community Group? Anyone else?

“Dynamic Audio Description Values”: Web Audio Community Group again? Anyone else?

“Audio-subtitling/spoken subtitles”: already supported by standards (but may require additional AT support)?

“Communications Control of Alternate Content”: Web Audio Community Group, who would handle the video component, and is it already possible?

“Text communication data channel”: probably APA or ARIA, requiring implementation in screen readers. My understanding is that Unicode braille entered directly into ARIA live regions can already be used with some screen readers, so that the spoken output is different from the braille.

“Control relative volume and panning position for multiple audio”: Web Audio Community Group?

“Quality synchronization and playback”: WebRTC, possibly IETF as well.

“Simultaneous voice, text & signing”: signaling protocols, possibly WebRTC (W3C or IETF)?

“Support for Real Time Text”: WebRTC (W3C or IETF).

Video relay services/remote interpretation: Signaling protocols or WebRTC itself? I expect this can be accomplished already, if the application is appropriately designed. Is more standardization needed?

“Distinguishing sent and received text”: possibly WCAG/Silver, but it isn’t obvious that any underlying technology change is needed.

“Warning and recovery of lost data”: WebRTC (W3C/IETF)? What support exists already?

“Call status data and polling”: signaling protocols? Already supported?

“Bandwidth for audio”: applications, and implementers of audio codecs?

“Bandwidth for video”: the same for video codecs, I assume.

“Quality of video resolution and frame rate”: the same as the previous item?

“Personalised symbol sets for users with cognitive disabilities”: APA, implementations?

“Live transcription and captioning”: signaling protocols?



________________________________

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.

________________________________