The Two-Person IT Department’s Guide to Grounding the Webcam
By The bee2.io Engineering Team at bee2.io LLC

Imagine clicking a shop’s size guide and getting asked to turn on your webcam. For a second, you wonder how badly you’ve misunderstood pants. Then you remember the site has a support widget, a product demo, and a tag manager full of things installed by someone whose farewell cake you ate two summers ago.
If you’re the team responsible for that site, give yourself 45 minutes. Pick one person to trace where camera, microphone, or geolocation access is actually needed and one person to own the header change. If both people are you, congratulations on a fully staffed committee.
Spend 15 Minutes Finding Out Who Ordered a Microphone
Open a fresh browser profile and walk through the homepage, checkout or signup, and any page with a map, video call, or support widget. Actually click the buttons. A widget may wait until you open it before it asks for anything, like a dinner guest who brings up cryptocurrency only after the doors are locked. Write down the page, the action, and whether the request makes sense there.
Check DevTools for the widget’s script and any iframe it creates. The distinction matters. A third-party script loaded directly into your page runs in the page’s context and can call browser APIs with the same origin privileges as your own code. If you allow camera access for self, that script can attempt to request it too. A cross-origin iframe has its own origin, so you can give an embedded feature a narrower allowance. Think of a script tag as handing someone an apron and letting them work in your kitchen. The browser sees the apron.
Give Permissions-Policy One Boring Job
If none of those features belongs on a page, set this HTTP response header on the HTML document in staging. Your hosting configuration or reverse proxy is usually a good place to look. You need one header for all three features, which is the closest a browser has ever come to offering a family plan.
Permissions-Policy: camera=(), microphone=(), geolocation=()
Each empty list blocks that feature in the document and its descendant frames in browsers that enforce the directive. The blocked request fails before a user permission prompt appears. Where a policy permits a feature, the browser still applies its normal permission checks.
If you really host video appointments, keep the strict header on ordinary pages and scope the exception to the appointment page. For an embedded call, allow the provider’s exact origin in the relevant header directives and explicitly delegate the features on the iframe. For example, the camera directive could be camera=(self "https://calls.example"), paired with allow="camera https://calls.example" on the iframe. Apply the same pattern for the microphone if the call needs it. An iframe’s allow attribute can narrow the parent policy, and a parent’s empty list still wins. If the page runs vendor scripts directly, remember they share whatever you grant to self. Give the appointment page as few roommates as practical.
Test the Button Someone Gets Paid to Answer
Spend the last 15 minutes running two checks on staging. First, confirm the header appears on the actual document response in the Network panel. In the affected page or frame, run the relevant API from DevTools or trigger the widget and confirm access fails without a permission prompt. For camera and microphone, use navigator.mediaDevices.getUserMedia() with the relevant option set to true. For location, use navigator.geolocation.getCurrentPosition() with both success and error callbacks. Use HTTPS and a fresh profile so an old permission decision or an insecure context doesn’t muddy the result.
Second, run the legitimate workflow from start to finish in a browser your customers use. For a call, verify that the preview appears and someone on the other end can hear you say “testing,” the official anthem of software releases. If you serve customers across multiple browser engines, repeat both checks there. After deploy, confirm the header on the live document and repeat the click that mattered.
Start with whichever page has the most third-party widgets. Open its Network panel, reload, and check the document’s response headers for Permissions-Policy. Then click the widget you’d least expect to need a camera. You’ve got a concrete place to start, and the pants can wait.
Disclaimer: This article is for informational purposes only and does not constitute legal, professional, or compliance advice. SCOUTb2 is an automated scanning tool that helps identify common issues but does not guarantee full compliance with any standard or regulation.
Stop finding issues manually
SCOUTb2 scans your entire site for accessibility, performance, and SEO problems automatically.