Inspect the supplied file
Parse SRT indices and timestamp blocks or the declared WebVTT subset. Recoverable diagnostics point to source lines without changing the file.
Review SRT format and timing checksBrowser-based subtitle QA preflight
Check an SRT or WebVTT file before delivery
Inspect timing, structure, reading speed, line limits, and adjacent duplicates under a visible rule profile. Review cue-level findings and create a local CSV or self-contained HTML report.
Preflight summarylocal
Synthetic sample · General readability v1.0
9 findings to review
2 errors · 7 warnings · cue-level explanations
CUE_OVERLAP · CPS_ABOVE_PROFILE_MAX
No universal pass score is calculated.
SRT and WebVTTChecks run in your browserCue-level findingsCSV and HTML exportsNot certification
See the issues before the handoff
Review readable evidence
Each deterministic finding records a stable ID, cue location, severity, observed value, threshold, unit, profile, and explanation.
Understand subtitle CPS and WPMExport a reviewable report
Download CSV for sorting or a self-contained HTML report for review. Generated reports include the profile snapshot and limitations.
Inspect report fieldsUse the profile your workflow requires
The accepted General readability v1.0 profile keeps its name, version, source, review date, thresholds, and user-modified state visible beside results. You can edit numeric thresholds and reset them. Any edit makes existing results stale until checks run again.
Defaults are a transparent starting point, not an official or universal standard. Client, platform, language, audience, and program requirements may differ.
Turn findings into a reviewable report
Reports include safe input metadata without an original device path, generation time, a complete profile snapshot, summary counts, parser diagnostics, every finding, browser-local disclosure, and non-certification language. Subtitle text remains in browser memory unless you intentionally include subtitle-derived findings in a local export.
Know what file-only checks cannot verify
Technical/readability preflight only — not certification or a substitute for media review.
The checker does not compare subtitles with audio or video and cannot verify accuracy, completeness, speaker identification, meaningful sounds, visual placement, accessibility or legal conformance, or client/platform acceptance.
Planned options for repeat workflows
The current concept is a free browser-local checker. Pro and Team are planned hypotheses only. There is no account, checkout, cloud history, hosted sharing, batch queue, or payment flow.
Questions about planned options can be sent to xma5@my.hpu.edu. Email does not create an account, purchase, or recorded waitlist.
Frequently asked questions
Are subtitle files uploaded?
In the implemented default workflow, parsing, checks, and report generation run in the browser. Subtitle contents are not intentionally sent to an application server.
Does a clean report prove accessibility compliance?
No. A file-only technical/readability preflight cannot verify the source media or grant certification.
Which formats are supported?
The MVP supports SRT plus a declared WebVTT subset through file selection or pasted text.
Can I change the limits?
Yes. Numeric thresholds are editable and resettable, and the report records whether the profile was modified.