Routing to second screens

[mikecrabb]

General Description

A deaf-blind user communicating via a RTC application in XR may have sophisticated 'routing' requirements for various inputs and outputs.

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

• https://www.w3.org/TR/xaur/#user-needs-definition

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

[bruce-usab]

As noted on call 6/8: This was put into traditional captioning category as the ability to route captions to a second screen is something that would be expected outside of an XR setting.

[bruce-usab]

Per call 6/15, we are trying to distinguish this requirement from #113 as it is a little simpler. This requirement may or might not include routing captions to a different app (e.g., using Discord for chat while gaming, rather than using in-game chat).

Since this requirement applies to dynamic braille displays, the term screen should be not be taken literally.