Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ITU-T] 2.2 Routing and communication channel control #17

Open
RealJoshue108 opened this issue Dec 2, 2020 · 2 comments
Open

[ITU-T] 2.2 Routing and communication channel control #17

RealJoshue108 opened this issue Dec 2, 2020 · 2 comments
Assignees

Comments

@RealJoshue108
Copy link
Contributor

RealJoshue108 commented Dec 2, 2020

(Filed on behalf of Lidia Best - ITU-T)

• User Need 2: A blind user of both screen reader and braille output devices may need to manage audio and text output differently e.g. once they have accepted the call a user may wish to route notifications to a separate braille device while continuing the call on bluetooth headphones.
• REQ 2a: Provide or support a range of browser level audio output and routing options.
• REQ 2b: Allow controlled routing of alerts and other browser output to a braille device or other hardware.
• User Need 3: A deaf user needs to move parts of a live teleconference session (as separate streams) to one or more devices for greater control.
• REQ 3a: Allow the separate routing of video streams such as a sign language interpreter to a separate high resolution display.

New suggested requirement:

• Allow a separate stream for captioning for greater control

@RealJoshue108
Copy link
Contributor Author

It looks like we already meet this suggested requirement in RAUR https://www.w3.org/TR/raur/#routing-and-communication-channel-control

@RealJoshue108
Copy link
Contributor Author

Discussed on RQTF call https://www.w3.org/2021/01/20-rqtf-minutes.html

@ruoxiran ruoxiran transferred this issue from w3c/apa Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant