How we test our tools

Hardware Detective tests what a browser can observe. The project also includes automated checks that exercise those observations in controlled conditions. Neither kind of test replaces inspection of the actual device or a manufacturer’s diagnostic process.

Input and media checks

The repository includes checks for keyboard input and mouse behavior along with the screen tools. Separate checks cover controller state and camera or microphone interactions. Audio checks exercise speaker output behavior.

Controlled browser inputs make repeated software checks possible. They help identify whether a control responds and whether the page handles expected states. A simulated key press can’t establish the condition of a physical keyboard switch. A controlled camera stream can’t prove that a particular webcam has a sharp lens.

Page quality checks

The automated workflow includes accessibility and theme checks as well as layout and navigation checks. Content checks look for substantial overlap between guides. Link and structured-data checks help keep published pages connected and described consistently.

These browser checks are configured for Chromium in the automated workflow. We don’t claim a complete certification matrix for every operating system or browser. When reporting a problem include the browser version because the available device interfaces can differ.

Interpreting a result

A working microphone recording means the tested setup captured sound. It doesn’t prove that a meeting app selected the same input. A responsive controller in the browser doesn’t establish that every game supports its mapping.

A display test provides colors for a person to inspect. The page can’t observe physical pixels through the screen. Timing estimates also depend on how the browser schedules work. Our browser-test limitations guide explains these boundaries by tool.

What to send with a bug report

Use Contact and name the tool. Include the device model and connection method along with your browser and the action that produced the problem. Note whether the same symptom appears in another application.

Avoid sending private audio or video when a written description or a non-sensitive reproduction will do. The testing tools process their input on your device. The website also includes Google Analytics for page measurement so local device processing isn’t a promise of zero network activity during a visit.

Methodology reviewed on September 21, 2026. This date records the review of these methods rather than certification of any visitor’s hardware.