GratisAI accessibility · check caption cue reading rates against your own mark · local-first FREE TIER 1 Free Run Available
caption-rate triage · triage clipboard with three lanes

Check Caption Cue Reading Rates Against Your Own Mark

A caption can be perfectly timed by the tooling and still too fast to read. Divide characters by seconds per cue, hold the result next to your own pace mark, and the fast ones stop hiding in the timeline.

1 · Cue code | characters | seconds shown

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The caption-rate triage processes Cue code | characters | seconds shown locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: fast captions hid inside a comfortable file average. After: each cue carries its own characters-per-second, and the fastest one is on the record.

2 · Read the caption-rate triage

Reading-rate arithmetic on reader-supplied cue data only, not a conformance certificate or comprehension test. Review caption quality and any applicable standards with a qualified accessibility or captioning specialist.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the caption-rate triage

Characters are the visible caption text length for the cue — decide once whether you count spaces and trailing punctuation, and use that convention for every row. Seconds are the cue's on-screen duration as timed, not the gap to the next cue. If your source reports durations in frames, convert at the source frame rate before entry; the triage accepts seconds with up to six decimal places. The mark is your working threshold — values quoted by guidelines and broadcasters differ, and you supply the one your review is testing against. Reading rate is one axis of caption quality: line length, positioning, verbatim accuracy and audio significance remain outside this arithmetic.

Boundary and sources

Reading-rate arithmetic on reader-supplied cue data only, not a conformance certificate or comprehension test. Review caption quality and any applicable standards with a qualified accessibility or captioning specialist.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this caption-rate triage for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a caption-rate triage. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Cue code | characters | seconds shown; the setting is Reading-pace review mark (characters per second). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.