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

Routing and Communication Channel Control #113

Closed
2 of 11 tasks
mikecrabb opened this issue Jun 8, 2020 · 2 comments
Closed
2 of 11 tasks

Routing and Communication Channel Control #113

mikecrabb opened this issue Jun 8, 2020 · 2 comments

Comments

@mikecrabb
Copy link
Contributor

General Description

Users of immersive augmented environments need to be able to route and configure their audio inputs and outputs to multiple devices. In that many users can choose to turn of images and use only text if they choose, or modify or zoom an interface, users should able to route inputs and outputs to where they choose in formats that they need. It is arguable that being able to customise audio routing preferences is the same.

Notes

This may have deeper architectural requirements such as access to browser plumbing.

Associated Documentation

Based on:

Functional Performance

Please see EN 301 549 for descriptions of functional performance areas.

  • Usage without vision
  • Usage with limited vision
  • Usage without perception of colour
  • Usage without hearing
  • Usage with limited hearing
  • Usage without vocal capability
  • Usage with limited manipulation or strength
  • Usage with limited reach
  • Minimize photosensitive seizure triggers
  • Usage with limited cognition
  • Privacy
@mikecrabb mikecrabb added User Need Subgroup: XR - Captions Directly related to XR SubGroup labels Jun 8, 2020
@mikecrabb mikecrabb added this to Incoming in XR 1st Guideline Development - User Needs via automation Jun 8, 2020
@mikecrabb
Copy link
Contributor Author

Second screen (not only screens, can include braille devices)

@mikecrabb mikecrabb moved this from Incoming to Relevant for Traditional Captioning in XR 1st Guideline Development - User Needs Jun 15, 2020
@mikecrabb mikecrabb moved this from Relevant for Traditional Captioning to Relevant for Traditional but XR Requires additional thought in XR 1st Guideline Development - User Needs Jun 15, 2020
@bruce-usab
Copy link
Contributor

bruce-usab commented Jun 15, 2020

Per call 6/15, this requirement is deeper than second screen #129, as it is more involved for XR and plumbing (see note above in top card).

This requirement includes routing captions to a different app (e.g., using Discord for chat while gaming, rather than using in-game chat).

One possible more exotic example is XR captioning displaying to Library or Theater VR space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Subgroup: XR - Captions Directly related to XR SubGroup
Projects
No open projects
XR 1st Guideline Development - User N...
Relevant for Traditional but XR Requi...
Development

No branches or pull requests

3 participants