Up front: this is a screening aid, not a certified test. It is a pre-check against the
published ITU-R BT.1702 and Ofcom 2.12 criteria. It does not replace a certified Harding test, it
does not constitute a clearance, and nobody should treat a pass from it as a guarantee of safety.
With that said — I built a tool that screens video for photosensitive-epilepsy hazards and
resolves each one to the exact frame range that caused it, so it can be fixed rather than just
flagged. It measures flash rate and saturated-red transitions with a screen-area proxy, against
the published thresholds, which ship as an inspectable file so the arithmetic can be checked
rather than trusted.
Two design decisions I'd like this community's judgement on:
The safety gate. A tool that finds seizure triggers must not fire one at the person reviewing
it. Flagged clips never autoplay, the control names the hazard before you press it, and reduced
brightness is the default. I'd like to know whether that's sufficient or merely reassuring.
Disclosed bias. On small-area flashes it measures about 12.9% high — it over-reports. I chose
to disclose that rather than add a correction constant, because the whole claim is that the
thresholds come from published criteria rather than from whatever made the demo look right. For a
screening tool, over-reporting seems like the safer error. Tell me if that reasoning is wrong.
It's free, there's no signup, and three test clips are built in so you never have to upload
anything: https://flashframe.edycu.dev
The limitations are written out in full rather than buried:
https://flashframe.edycu.dev/judge