- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jul 2023 08:25:16 +0000
- To: public-webrtc-logs@w3.org
I think my main argument[0] for retaining this value is that, as currently defined, it is potentially useful for accessibility-conscious applications. I suspect[1] that people using screen readers find it challenging when the active window on the screen changes. The reader needs to announce this, read out the new fields available, etc. * When such a user is on Chrome-on-Windows, they might prefer to keep the capturing application focused, because that's what they last interacted with and had read out to them. * When such a user is on Safari-on-macOS, I imagine[2] the macOS media-picker performs some read-out that makes the user feel like the new window is in focus. When such users configure the Web app for a11y, the app might wish to request divergent behavior depending on the platform, and this might be a good way to achieve it. --- [0] The others arguments mostly being about having to check how much havoc this would wreak on existing applications before committing to a deprecation. [1] Let's pull someone more experienced in these matters to verify. [2] Am I wrong? -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/271#issuecomment-1621278093 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 July 2023 08:25:17 UTC