Some environments recognize a controller only after you press a button while this page is visible.
Connect a controller and press a button
Use USB or Bluetooth, then interact with the controller to make it available to the test.
Inspect connected gamepad buttons, analog values, stick axes, mapping, and connection state.
Repeat the same check and compare the result with behavior you can directly observe. For a microphone, speak at several normal levels and watch whether the waveform responds without staying flat or constantly clipping. For a camera, inspect focus, exposure, resolution, and motion. For keys, buttons, channels, pixels, or refresh rate, test the complete range rather than one successful input. Permissions, connections, operating system settings, adapters, background load, and hardware conditions can affect a reading, so use specialist diagnostics when the result will guide a repair or purchase.
The information available to a test depends on the operating system, connected hardware, selected input or output, granted permissions, display configuration, and features exposed by the current environment. A camera can report a nominal resolution while delivering a different mode, and a refresh-rate estimate can vary when frames are delayed by background activity. Audio behavior can change with enhancements, balance settings, wireless codecs, and volume controls. A missing value means that detail was not available to the test, not automatic proof that the device is broken.
No. These checks help reveal common input, output, pixel, connection, and timing problems, but they cannot prove that every component works perfectly under every condition. Intermittent faults, driver issues, cable problems, thermal behavior, electrical noise, damaged ports, and failures that appear only in a specific application may require operating system tools, another known-good device, or professional diagnosis. Use the result to narrow the problem, then reproduce it with another connection, application, or machine before deciding that hardware must be replaced.
Confirm that the device is physically connected, powered when required, and selected as the active input. Allow the requested microphone or camera permission, then check operating system privacy controls for the site and input category. Close calling, recording, streaming, or conferencing apps that may already be using the device. Disconnect and reconnect an external device, try another port when appropriate, and restart the test. If several microphones or cameras exist, verify the selected one by changing a visible or audible condition instead of relying only on its displayed name.
Use stable, repeatable conditions. Run the same test more than once, change only one variable at a time, and record what you can actually see or hear. For refresh rate, keep the page visible and reduce demanding background work. For audio, start at a safe low volume and keep the same output path when comparing channels or frequencies. For screens, clean the panel and inspect multiple solid colors from a normal distance. For controllers and keyboards, test every control, then watch for stuck or drifting values after releasing it.
The test displays buttons and axes exposed through the standard gamepad interface. Vendor software, platform-specific features, motion sensors, touch surfaces, adaptive triggers, audio, macros, and wireless status may not be available. Small resting axis values can reflect normal dead-zone behavior rather than a fault. Test every control through its full range, repeat after reconnecting, and verify calibration, mapping, and drift in the target game or system settings.