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

[RNIB] 4.15 Routing to second screens #25

Open
RealJoshue108 opened this issue Apr 6, 2020 · 7 comments
Open

[RNIB] 4.15 Routing to second screens #25

RealJoshue108 opened this issue Apr 6, 2020 · 7 comments
Assignees
Labels

Comments

@RealJoshue108
Copy link
Contributor

Filed on behalf of RNIB: Original comments sent to APA list

Regarding, 4.15 Routing to second screens-REQ 14a: Allow the user to route text output, alerts, environment sounds and audio to a braille or other devices, >>>as well as navigation and orientation data specified in User need 1<<<.

@RealJoshue108 RealJoshue108 self-assigned this Apr 6, 2020
@RealJoshue108
Copy link
Contributor Author

This is an interesting suggestion - I thought this is implicit in the requirement that navigation and orientation data is included - but it may benefit from being made more explicit. We will discuss in RQTF, thanks @Raisonali

@RealJoshue108
Copy link
Contributor Author

Suggested text after RQTF discussion:

REQ 14a: Allow the user to route text output, alerts, environment sounds and audio to a braille output or other second screen devices.

@RealJoshue108
Copy link
Contributor Author

Discussed on 27th May 2020 https://www.w3.org/2020/05/27-rqtf-minutes.html

@Raisonali
Copy link

Thanks @RealJoshue108 this works well

@RealJoshue108
Copy link
Contributor Author

Thanks @Raisonali

@RealJoshue108
Copy link
Contributor Author

@Raisonali I've updated the requirement in the second draft. It now reads

"REQ 14a: Allow the user to route text output, alerts, environment sounds and audio to a braille output or other second screen devices."

@Raisonali
Copy link

Great, thank you!

@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
Labels
Projects
None yet
Development

No branches or pull requests

2 participants