TRV-2026-1105Certified recordPeer-reviewed

The impact of roadside advertising density on driver visual attention and safety in Kuwait: An AI-driven analysis of simulator and eye-tracking data

Objectives Driver distraction associated with roadside advertising remains a significant road safety concern, yet the precise physiological markers distinguishing stimulus-driven distraction from baseline driving are complex to isolate. This study quantified the impact of roadside advertising density on driver cognitive load and visual attention using a high-fidelity driving simulator and wearable eye-tracking technology. Methods A cohort of 60 licensed drivers navigated simulated environments under three contin…

Policy · The Trace — both readings · certified 2026-09-16 · v1 · article view · machine-readable

Current reading — gain

An ensemble of machine learning models analyzed 2.4 million physiological samples from simulator drives to classify driver cognitive states, with XGBoost identified as the most robust classifier.

Current reading — problem

High-density roadside advertising was associated with acute cognitive stress and autonomic visual rigidity marked by transient subconscious blink suppression in simulated driving.

What this doesn’t fix

Blink suppression finding was not significant in the global test and only emerged in spatially stratified analysis, limiting generalizability of that marker.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1105, v1: “The impact of roadside advertising density on driver visual attention and safety in Kuwait: An AI-driven analysis of simulator and eye-tracking data.” Truvace, 2026-09-16. /record/TRV-2026-1105 (accessed at citation time). sha256 6ea4f66d93f809f1…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv16ea4f66d93f8…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1105 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.