GratisAI accessibility · measure concurrent caption time once, not once for every cue pair · local-first FREE TIER 1 Free Run Available
cue-concurrency strip · paper ticker strip

Measure Concurrent Caption Time Once, Not Once for Every Cue Pair

Stacked captions can overlap in pairs without creating that much distinct overlapping time. Sweep the timeline, count each overloaded second once, and keep cue participation separate from the union.

1 · Cue code | start seconds | end seconds

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: This cue-concurrency strip calculates in the tab from Cue code | start seconds | end seconds. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.

Perspective: Before: pairwise overlaps inflated the apparent problem time. After: overloaded timeline union, peak count and per-cue participation are distinct, checkable quantities.

2 · Read the cue-concurrency strip

Timing-union review only: no caption-content check, playback test or WCAG compliance verdict. Inspect actual media and cue layout with a qualified caption professional or accessibility specialist before treating a marked span as a barrier.

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 cue-concurrency strip

This is a timing review of supplied cue intervals, not a media player or accessibility certification. Multiple simultaneous cues may be intentional for speakers, positioning or a caption format. The budget is your review convention, not a WCAG threshold. Enter seconds on one consistent timeline, with starts included and ends excluded. Up to six decimals are converted to integer microseconds before comparison, avoiding floating-point phantom overlaps. No caption text, audio, screen position, subtitle file or speaker identity is collected. Review the actual content and playback with users and an accessibility specialist before interpreting a marked interval as a barrier.

Boundary and sources

Timing-union review only: no caption-content check, playback test or WCAG compliance verdict. Inspect actual media and cue layout with a qualified caption professional or accessibility specialist before treating a marked span as a barrier.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this cue-concurrency strip 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 cue-concurrency strip. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Cue code | start seconds | end seconds; the setting is Allowed simultaneous cues in this review model. 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.