Moderate evidence
Published recordPolicyProblem Space
More
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 record
- TRV-2026-1105raw data (JSON)
- Version
- v3Revised
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- a194cc7cd41d…check it
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…
The problem
In a Kuwait simulator study of 60 drivers, dense roadside ads raised cognitive load, shown by pupil size changes, though blink suppression was not significant overall (P=0.12).</br>
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.
Sources
1 on file- Traffic Injury Preventiondoi:10.1080/15389588.2026.2729620
Cite this record
v3Truvace Impact Record TRV-2026-1105, v3: “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-11-04. /record/TRV-2026-1105 (accessed on the day you copy it). sha256 a194cc7cd41d5e81…
Change history
3 versionsEvery change made to this record since it was first published, and why.
Editorial pass: sharper headline; gain/problem restated as concrete outcomes.
Direction audit: the gain line stated no AI consequence and was removed.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-1105 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace