# Independent answer check — Chrome camera or microphone on one site

The practice file `permission-diagnosis.csv` contains four fictional cases. Each case has a different first cause; the answer is not always “allow the site.”

| Case | First diagnosis | Expected check |
| --- | --- | --- |
| A | Per-site Microphone block | The exact chosen site's Microphone entry would read **Allow** only after the viewer deliberately authorizes that site; unrelated entries stay separate. |
| B | Wrong input device | Keep the site's permission state; choose the intended microphone and observe the site's own preview or meter. |
| C | Beyond site permission | Inspect the in-site mute control and operating-system access. An **Allow** label alone does not prove recorded audio. |
| D | Different hostname | Leave the working `meeting.example.com` entry alone; review the blocked `video.example.com` entry only if that is the intended site. |

Independent verification: compared each CSV clue against Google's Chrome Help at https://support.google.com/chrome/answer/2693767?hl=en on 12 October 2026. The help page separately documents per-site access, device selection, OS permission and mute checks. No physical device or real website was tested for these fictional rows, so the table describes a documented decision path, not an observed working call.