Touchscreen Test

Check touch coordinates and verify that touches are detected.

🔒 Local-first◉ Modern browser recommended.

☝

Touchscreen TestTouchscreen

Local-first

Ready

Mode

Cover the test zone with your finger. Untested cells are not dead zones.

Browser gestures can intercept input. Only the test zone prevents scrolling. Esc exits fullscreen.

Active: 0 · Maximum observed: 0 · Tested cells: 0 · Possible unexpected touches: 0

I tried the highlighted areas again.

Coverage—

Tested cells—

Untested cells—

Browser-reported maxTouchPoints—

Events—

X—

Y—

Pointer cancellations—

Lost pointer capture—

Timing gaps—

Broken paths—

Tracking interruptions—

Average CSS-pixel offset—

Maximum CSS-pixel offset—

Offset consistency—

Mean line deviation—

Maximum line deviation—

Coordinates and distances are CSS pixels in this zone, not physical pixels or millimetres. Aiming error is not a sensor fault.

Edges and corners

Possible unexpected touches

Method and limitations

Coverage counts cells containing observed finger samples; gaps are not interpolated. Confirmation records your repeat attempt and only suggests a possible unresponsive area.

A move gap over 100 ms breaks the drawn path. Pauses, scheduling and browser gestures can cause gaps or cancellations; this is not a hardware diagnosis.

Tap offset is Euclidean distance from the shown target; consistency is standard deviation. Line deviation is perpendicular distance from the fixed reference line. Results include aiming and motion.

Pen values are browser API values. Missing or constant pressure, tilt or size does not establish hardware failure. Touch fallback has no pen telemetry.

Unexpected touches count new browser contacts during hands-off observation. Synthetic events are excluded. This cannot prove a ghost-touch hardware fault.

How it works

Use the interactive panel above and watch the live measurements. Results depend on events and capabilities exposed by your browser.

Runs in your browser

Core tests are processed locally in your browser. Camera and microphone streams are not intentionally uploaded by Testvexa.

FAQ

Does this test upload my input?

Core interaction is processed in your browser. Testvexa does not intentionally upload camera or microphone streams.

Can browser limitations affect the result?

Yes. Browsers expose different hardware APIs, so unsupported access is not the same as faulty hardware.