Browser measurement method
Browser device tests: permissions, measurements, and results that are not certifications
Browser device tests are useful for checking what the current browser can observe after an explicit action. They are not calibrated laboratory instruments, identity checks, employment certificates, medical assessments, or anti-cheat systems.
On this page
Permission is an explicit boundary
A camera, microphone, or screen-capture route should request permission only after a person chooses the relevant action. The browser owns the permission prompt and may reveal different device capabilities depending on the operating system and privacy settings.
Aftermath keeps selected device media in the current browser workflow. The same privacy boundary does not extend to a separate application, browser extension, or service where a user later shares a recording.
The browser reports an observation, not a certification
A camera test can report negotiated resolution, frame rate, channels, sample rate, and a local digital level. A typing, click, or reaction test can report the events and timing that the browser received. Those are useful local observations with known scheduling and hardware limits.
They do not establish calibrated acoustic dB SPL, physical display latency, a person’s identity, clinical health, hardware condition, or fair-game status.
| Tool outcome | Reasonable use | Unreasonable claim |
|---|---|---|
| Camera/microphone facts | Check a local device/browser setup before a call or recording | Certified hardware performance or calibrated room noise |
| Screen recording | Create a local browser capture after choosing a source | Guaranteed system-audio behaviour on every platform |
| Typing/CPS/reaction result | Personal practice and consistent self-comparison | Employment, medical, anti-cheat, or competitive certification |
Keep the test conditions comparable
A score becomes more useful when the same browser, device, input method, duration, and visible-tab conditions are used. Comparing a phone touchscreen session with a desktop mechanical keyboard session can describe two experiences without establishing a meaningful ranking.
Hidden tabs and system interruption can change timing. A careful tool explains that limitation or invalidates the affected run rather than presenting a misleading number.
Use the result to decide a next action
A low microphone level can suggest checking a cable, input selection, browser permission, or conferencing application. A failed screen recording can suggest checking browser support. The tool result should guide troubleshooting, not close the investigation with a false diagnosis.
Use a local tool