These mockups explore how browsers and operating systems could help users remain aware of and stop playback-audio capture after permission is granted. They are illustrative rather than proposed final UI and draw on existing microphone, camera, and screen-sharing affordances in browsers.
Browser implementations vary. Current Microsoft Edge screen-sharing UI is one example that informed the concepts below:
If a browser tab is shared: the browser can identify sharing in both places. The captured tab can say which site is receiving it, while the capturing tab can identify the selected tab and provide a stop control.
If audio from an application or device is captured: a persistent browser-controlled sharing indicator could keep the capture visible and let the user stop it, even when another application is active.
Capturing browser tab
If audio from a tab, application, or device is captured, the capturing tab could identify the source and provide a stop control.
Captured browser tab
If a browser tab is the selected source, that tab could identify which site is receiving its audio and provide a stop control.
Another active browser tab
If Site A captures Site B while the user views Site C, the active tab could still identify the source and destination, provide sharing controls, and show the browser's playback-capture indicator.
Outside the browser
If a site captures system audio, a browser-owned floating control could remain visible when the user switches to another application.
Browser address bar
Extend Edge's microphone permission panel to show active playback-audio access and let the user manage future access.
This page is accessing audio playing on your device.
Possible OS integration
The OS could eventually expose playback capture similarly to microphone use, with a distinct icon for audio being captured.