the browser cannot access a camera, microphone, location, notification, or other permission-gated feature
A permission failure can block perfectly healthy hardware. DeviceOK separates browser permission from whether the device exists and produces a usable signal.
Do not jump to the most invasive fix
Do not reinstall hardware drivers before checking the site/browser and operating-system privacy controls.
Retest the same condition
After permission is granted, rerun the relevant live test and confirm the device produces the expected signal/output.
Rule out the simple causes
- 1
Run DeviceOK's permission check and note the exact state.
- 2
Open the site's permission controls from the address bar and allow only the feature you are trying to use.
- 3
Check the operating system's privacy settings if browser permission is allowed but access still fails.
Work through the problem in order
- 1
Test the relevant component directly in DeviceOK after changing permission.
- 2
If DeviceOK now works but the original app does not, inspect that app's own device selection and permissions.
- 3
If the permission immediately resets or is managed, check browser profiles, parental controls, enterprise policy, or OS privacy restrictions.
If the matching DeviceOK test succeeds, prioritize the affected app, browser policy, operating-system setting, or configuration before assuming complete hardware failure.
If the same capability also fails in DeviceOK and another trusted diagnostic path, broaden the investigation to connection, operating-system/device state, official driver or firmware support, and finally hardware.