Test methods and editorial policy
Denerim's web tools make the signals reaching your browser visible or audible. They help you understand the conditions in which a problem appears. One successful test does not establish that a device will work correctly in every application or at all times.
What do the tools check?
| Tool | Observation | Not measured |
|---|---|---|
| Keyboard / mouse | Key, button and scroll events received by the browser | Electrical latency, actual USB polling rate or a definitive switch fault |
| Microphone / camera | Audio and video from the permitted device | Calibrated sound pressure or laboratory sensor quality |
| Speaker | Your channel feedback on generated test audio | Room acoustics or an automatic speaker quality score |
| Monitor | Defects you visually identify on solid colors | Automatic pixel diagnosis, color accuracy or panel repair |
| Gamepad | Buttons, axes and trigger values reported by the browser | Identical mapping for every model or game-specific dead zones |
Make the check repeatable
- Select the intended device. Disconnect other devices of the same type where practical; confirm the default camera or microphone.
- Complete the checks on the relevant page. Testing only a left click, for example, does not test every mouse input.
- Repeat a suspicious result, changing one condition at a time: port, cable, browser or device.
- If the issue repeats across environments, share your observations with the manufacturer's support team. Do not treat the result as a service report.
Automatic summaries and your observations
Some tools summarize detected input or threshold checks. For example, mouse events less than 80 milliseconds apart may be flagged as suspicious; deliberate fast clicking can produce the same flag. It is a reason to check again, not a definitive fault diagnosis. Monitor and speaker results also depend on your visual or listening feedback.
Permissions and test recordings
Camera and microphone tests request browser permission. Previews, snapshots and microphone test recordings are processed in your browser; these tools do not include a step that uploads this media to Denerim's server. Downloaded files remain on your device. This does not mean the website processes no technical data: server logs, preference storage and analytics you permit are described separately in the privacy policy.
A limited history of recently completed tests may be stored locally in this browser. You can remove it by clearing the site's browser data.
Product content and corrections
Specifications, user reviews, sample recordings and editorial evaluations are different types of information. A specification or user opinion should not be treated as an independent laboratory result. The headphones and volume you use to listen to a simulation also affect the experience.
Denerim's developer, Emirhan Bıçakçı, is responsible for the site's content. When reporting an inaccuracy, include the page address, the relevant passage and a verifiable source if available. For test issues, the browser, device and steps to reproduce help with investigation.
Technical references
- MDN: getUserMedia — camera and microphone access
- MDN: Gamepad API — controller input in browsers