the pointer accelerated and slowed on its way to each control
Check id pointer-approach-speed-profile
What an ordinary browser yields
Step speed varying by more than 15% of its own mean on every measured approach. N/A on touch and when no approach carried enough movement (severity: warn).
What a detector infers
A pointer moved by an arm leaves rest, accelerates, and brakes into its target, so the distance covered between consecutive samples rises and falls across the journey. A loop advancing a fixed distance per tick holds one speed from start to stop. The row measures the coefficient of variation of step speed within each approach - the spread of those step lengths relative to their own mean - which needs no reference table and no population, only the visitor's own movement compared against itself. CALIBRATED AGAINST RECORDED HUMANS RATHER THAN AGAINST INTUITION, using a database of trajectories captured from real people (Vinyzu/cursory) morphed onto 300 endpoint pairs across distances from 40 to 900 pixels. Step-speed CV: quietest human 0.396, 5th percentile 0.704, median 1.123. Naive interpolation: 0.029, every path. That is a factor of fourteen with nothing in between, and the threshold sits at 0.15 - five times above interpolation and more than twice below the quietest human. THE ROW THAT WAS DROPPED IS THE INTERESTING RESULT. Path curvature looks like the obvious signal, since an arm rotates around joints, and it does not work: the same recorded humans have a median path/straight ratio of 1.016 and a minimum of 1.0028, so a threshold loose enough to catch interpolation at exactly 1.0 flags most real people - measured, 165 of 300 - and one of the gate's own steps is a slider drag, which travels in a straight line by design. The ratio is still reported as context and decides nothing. A PROPERLY EASED SYNTHETIC PATH PASSES, at 0.334, and that is correct rather than a miss: a wrapper that eases its movement is producing the varying speed a hand produces. This row asks whether the pointer accelerated, not who was holding it.
How to resolve it
Vary the step size across a programmatic move - ease out of the start and into the target rather than stepping uniformly. Easing alone is enough to pass; the threshold has a wide margin on both sides deliberately.
Nearby checks in Automation surface
- keys were held down for a measurable moment
key-press-dwell-durationThe keyboard twin of the press-dwell row, and it is deliberately separate because the two fail independently - which SeleniumBase 4.51.5… - movement while a button was down reported the button as down
pointer-buttons-during-dragMouseEvent.buttons is a bitfield of which buttons are currently held, derived by the browser from the physical button state rather than from… - dragging the slider moved it through the values it crossed
slider-drag-value-progressionA range slider is the only common control that has to be DRAGGED to be used as intended, which makes it the only one that produces a stream… - clicks landed on different points, not the same one repeatedly
pointer-landing-dispersionAiming is imprecise. A hand lands somewhere inside a control and the spread shows up within two or three clicks; a driver resolves the… - the pointer travelled to each control it pressed
pointer-approach-per-targetThe gate asks for four separate acts in four separate places - three markers, a text field, a slider and a dropdown - and a pointer has to… - no automation pointer-flash artifact is present
pointer-flash-keyframe-artifactThe only row on this page that works by recognising a specific string, which needs justifying because a name table is exactly what this… - pageXOffset/pageYOffset match their scrollX/scrollY aliases
scroll-alias-coherencewindow.pageXOffset is not a second scroll position, it is a legacy alias of window.scrollX — the specification defines them as the same… - a focused child frame implies its parent document is focused
document-focus-vs-realmdocument.hasFocus() is true when the document OR any of its descendants holds focus, which makes it hierarchical rather than local: a…
Clearcote is a browser built for fingerprint coherence
It is a Chromium fork, maintained by the same people who wrote this reference. It ships as a compiled browser rather than as a stealth script injected into someone else's — which is a description of how it is built, and is not an argument about how it behaves on this check.
This audit takes no position on how Clearcote scores on Automation surface checks, on this one, or anywhere else. It has no baseline corpus of other people's fingerprints to rank you against and no vendor scoreboard — nearly every check is self-referential, asking one browser the same question through two independent APIs and reporting whether both answers can be true at once. It runs identically on any browser, including ours. Run it on yours and read the result yourself.
See the other checks in Automation surface — the family pointer-approach-speed-profile belongs to.