CaptionPass
ProductConvertLearnPricingComplianceEnterpriseDocs
Sign inCreate accountDashboardConvert & fix free
CaptionPass

Professional caption delivery QA for editors and producers.

Product

  • Free caption converter
  • Fix captions
  • Pricing
  • What is CaptionPass?
  • API
  • Sign in
  • Dashboard
  • Compliance
  • Accessibility
  • Enterprise
  • Verify a receipt
  • About
  • Changelog

Learn

  • SRT vs VTT
  • YouTube caption upload issues
  • Why your captions are not showing
  • Fix overlapping subtitles
  • Educators
  • All guides →

Legal

  • info@captionpass.com
  • Privacy
  • Terms

© 2026 CaptionPass. Caption reliability layer for delivery.CaptionPass is in early access — features and limits may change. Spotted something off? Use Send feedback above.

Home/Learn/Caption rows of a VPAT

Last updated August 28, 2026 (UTC)

What goes in the caption rows of a VPAT

A VPAT — filled in, it becomes an Accessibility Conformance Report — asks, criterion by criterion, what your product supports. The caption rows are where video-heavy organisations stall, because the honest answer depends on evidence most teams do not have in a form they can cite.

The levels below are not a house style. They are what CaptionPass’s own report generator produces from evidence, and you can read one it made.

See a real conformance receipt — generated through the production engine on every page load, no account needed.

Verify a receipt you were sent — including one we hold no copy of.

What CaptionPass does about compliance — for a reader who arrived here having never heard of it.

Which rows are the caption rows

A VPAT covers the whole of the standard, but on a video library these are the rows a reviewer reads first — and the ones most often left blank.

Caption-related success criteria in a VPAT
CriterionWhat it requiresWhat a caption file can settle
1.2.2Captions (Prerecorded)Captions are provided for all prerecorded audio content in synchronized media.Partly checkedThe file can show this failing, but cannot show it passing. No findings means nothing detectable is wrong — not that the criterion is met.A caption file proves captions exist, and can show they start late or skip stretches of the programme. It cannot prove they cover all audio, because that comparison needs the audio.
1.2.4Captions (Live)Captions are provided for all live audio content in synchronized media.Not evaluatedNothing in a caption file can settle this. It is reported as not evaluated and is never marked passed.Live captioning is a property of the broadcast, not of a delivered file. Nothing in a sidecar can settle it.

Cited from W3C Web Content Accessibility Guidelines 2.1, Level AA (W3C Recommendation, 5 June 2018) — read the standard.

Which level the evidence actually supports

A row takes one of four levels: Supports, Partially Supports, Does Not Support, Not Applicable. The temptation is to write Supports whenever a scan came back clean. That is the single most common way a caption row becomes indefensible, because for most caption criteria a clean scan is not a proof — the file can show the criterion failing and cannot show it passing.

How evidence coverage and outcome determine the conformance level
What the evidence can settleOutcomeLevel
CheckedEvery asset passesSupports
Partly checkedEvery asset passesPartially Supports
CheckedSome assets failPartially Supports
CheckedEvery asset failsDoes Not Support
Not evaluatedAnyNot Evaluated

This table is computed by calling the same function that grades a CaptionPass conformance report, so it cannot describe a mapping the product does not apply.

Not Evaluated, not Not Applicable

When nothing you hold can settle a criterion, the row is Not Evaluated, with the reason — not Not Applicable. WCAG 1.2.4 is entirely applicable to an organisation that streams live; writing N/A there is exactly the unjustified row that gets a response thrown out.

Not Evaluated is not one of the four standard levels, and that is the point. It sits visibly outside the vendor’s own scoring, which is the honest place for it, and the remark says who has to answer the question instead.

Reviewers in higher education and government are trained to read blank caption rows and unexplained N/A as the place where vendors hide. A stated limitation reads as candour. A gap reads as evasion — and the reviewer decides which, not you.

Getting the evidence

The rows have to come from somewhere. A per-asset receipt records what one delivery was checked against; a conformance report rolls a library up into exactly the table above, failures included. If you are filling this in for a public body under a deadline, start from evidencing ADA Title II captions.

What this is not. A conformance receipt is evidence of what was checked, by which engine, against which version of which standard, and what it found. It is not a legal opinion, an audit, or a safe harbour. CaptionPass reads the caption file and never the audio, so anything that needs the audio — above all whether the captions match what was said — is reported as not evaluated rather than assumed.

Common questions

Which WCAG criteria are the caption rows in a VPAT?
For captions specifically: 1.2.2 Captions (Prerecorded) and 1.2.4 Captions (Live). A VPAT covers the whole of WCAG, but these are the rows a reviewer checks first on a video-heavy library, and the rows most often left blank.
What conformance level should a caption row say?
Supports, Partially Supports, Does Not Support, or Not Applicable. The level has to follow from evidence. A criterion that can only ever be disproved from the material you hold does not become Supports because nothing turned up — a clean scan is not a conformance proof, and Partially Supports with the limitation stated is the accurate row.
What do I put when the evidence cannot settle a criterion?
Not Evaluated, with the reason, rather than Not Applicable. WCAG 1.2.4 is entirely applicable to an organisation that streams live; writing N/A there is the unjustified row that gets a procurement response thrown out. Not Evaluated is visibly outside the vendor's own scoring, which is the honest place for it, and it says who has to answer the question instead.
Why are blank caption rows a problem?
Procurement teams in higher education and government are trained to read blank rows and unexplained Not Applicable on caption criteria as the place where vendors hide. A stated limitation reads as candour; a gap reads as evasion, and it is the reviewer who decides which.

Convert your captions free

Upload on CaptionPass, pick a delivery preset, and download upload-ready output with optional enhanced formatting — free tier, no account required.

Convert & fix free →

More guides

  • Free online caption converter — SRT, VTT, and delivery QAHow CaptionPass works as a free caption converter with upload-ready and enhanced exports, platform presets, and explainable fixes. Try the same presets on the homepage tool or Quick fix before you open a Pro project.
  • SRT to VTT converter guide — headers, timestamps, and pitfallsWhen to convert SRT to WebVTT, what breaks if you rename extensions, and how to validate before HTML5 or YouTube delivery. CaptionPass converts and validates both formats in the dashboard workbench and v1 API.
  • SRT vs VTT — when each format silently failsComma vs dot timestamps, WEBVTT headers, and where YouTube, TikTok, and HTML5 bite. Run either format through the homepage tool or POST /api/v1/process to see explainable fixes before delivery.
  • Caption file encoding — UTF-8, BOM, and garbled textWhy uploads show mojibake or blank cues: UTF-8 vs legacy encodings and quick fixes. CaptionPass ingest reports flag encoding issues in the workbench Checks tab and v1 processing errors.
  • Burned-in vs soft subtitles — what to deliver whenOpen captions burned into the picture vs separate SRT/VTT tracks — tradeoffs for editors and clients. Pro users can mux or burn-in via v1 render jobs after sidecar QA in the workbench.
  • Reading speed for captions — CPS, line length, and platformsCharacters per second, lines per cue, and where YouTube, TikTok, and HTML5 push back. Platform presets in the dashboard and v1 API apply the same CPS and line-length rules automatically.
  • YouTube caption upload issues — silent rejection and timingWhen Studio accepts a file but captions vanish: format, line length, drift, and how to validate before publish. Export with the YouTube preset from Deliver or v1 before you upload to Studio.
  • YouTube rejected my SRT — invalid file and Studio errorsWhen YouTube Studio blocks an SRT upload: encoding, index gaps, bad timestamps, and how to validate before you retry. Quick fix and the homepage tool surface the same diagnostics as a failed v1 run.
  • Caption timing drift after export from Premiere or DaVinciWhy captions slip after NLE export: frame rates, timecode starts, and how to normalize before YouTube or client delivery. Pro drift diff in the workbench compares revisions after you re-import from an NLE.
  • CaptionPass vs generic subtitle convertersFormat swap tools vs delivery QA: explainable fixes, platform presets, and when each approach fits your workflow. CaptionPass adds Checks, receipts, and handoff packs on top of one-shot homepage conversions.
  • CaptionPass vs Subtitle EditDesktop authoring vs delivery QA: when to use Subtitle Edit for editing and CaptionPass for platform-safe validation and API automation. Ship Subtitle Edit exports through the dashboard workbench or v1 API for final QA.
  • Caption QA API for CI/CD pipelinesAutomate SRT and VTT validation in GitHub Actions or your build pipeline with POST /api/v1/process and Bearer API keys. Keys and usage meters live under dashboard Automate alongside export webhooks.
  • TikTok subtitle format — short lines, CPS, and clean SRTVertical video reading speed, styling stripped on upload, and export settings that survive TikTok delivery. Use the social-shorts handoff profile or TikTok preset from Deliver before upload.
  • Why your captions are not showing — a triage guideHTML5, YouTube, and TikTok checks when subtitles vanish after upload. Cross-check workbench preflight and History receipts to confirm what CaptionPass actually exported.
  • Fix overlapping subtitlesWhat overlap means and why some players drop overlapping cues. CaptionPass flags overlapping_cues in Checks and can auto-fix via Fix again or v1 process.
  • TTML and DFXP — broadcast-style timed text on the webNamespaces, timing, styling stripped in practice, and when TTML is the right interchange vs SRT or WebVTT. Convert inbound TTML through v1 or the homepage tool when clients deliver broadcast sidecars.
  • CaptionPass JSON IR and the developer-json presetLossless-ish cue interchange for tooling: when to use JSON IR, version tag, and how it pairs with the HTTP API. Request the developer-json preset from POST /api/v1/process or export it from the workbench.
  • Timecode, frame rate, and caption syncWhy captions drift or jump: drop-frame vs non-drop, fractional frame rates, and export settings that survive upload. Pro drift panel and v1 diff help confirm sync after re-export from an NLE.
  • WCAG-minded captions — reading speed, sound tags, and burned-in contrastHow WCAG 1.2.x thinking maps to real files: CPS, line length, SDH-style cues, and contrast for open captions. Platform presets in the dashboard enforce readable CPS before you hand off to clients.
  • Educators & classrooms — CaptionPass for instructionPartner program for instructors: API keys, workspace pilots, Learn guides, and classroom-appropriate access. Students can start with the free homepage tool before moving to dashboard projects.
  • How to evidence ADA Title II captionsWhat the DOJ web rule requires for captions, what counts as evidence rather than an assurance, and what a per-asset conformance record contains. Deadlines are dated and cited, and the tense is computed so the page cannot describe a passed deadline as upcoming.
  • The FCC's four caption quality standardsAccuracy, synchronicity, completeness and placement under 47 CFR 79.1(j)(2) — what each requires, and precisely which of them a caption file can and cannot settle.
  • How to check captions against WCAG 2.1 AAWhich WCAG success criteria a caption file bears on, how to run a per-criterion check that names its own limits, and what a clean result does and does not establish.

Fix in CaptionPass

Free caption converter · Homepage tool · HTTP API (v1) · Pro workspace