FCC 47 CFR § 11.35(d) — compliance required by September 29, 2026
Station Compliance

Station Compliance›Field Notes

Television

Closed captioning: the obligation that runs on equipment you just secured

Two separate obligations run through the same box. You are already scheduled to be in front of it before September 29, which makes this the cheapest audit available.

By Mark Shannon ·

Captioning is usually filed mentally under accessibility, which is correct but incomplete. For the next month it is also a program chain security question, because the device that inserts captions into your transmission is equipment the FCC now requires you to secure.

That overlap is worth using. You are going to be walking the plant before September 29 anyway.

Where the two rules meet

§ 11.35(d) applies to EAS equipment, STL equipment, and any remotely managed equipment that routes, processes, or inserts content into the transmission of your programming.

A captioning encoder inserts content into the transmission. That is its function. So it needs, by September 29:

Meanwhile § 79.1 governs what that same device is producing, and § 79.2 governs what happens during an emergency. Same box, three rules.

The § 79.1 quality standards, briefly

The captioning rules are not satisfied by captions merely existing. § 79.1 sets quality standards covering:

Placement is the one where emergency operations and captioning collide directly, and it is worth thinking about before the night it matters.

Your EAS crawl appears at the top of the screen because § 11.51(d) says it must be at the top or somewhere it does not interfere with other visual messages. Captions default to the bottom for the same reason. If your crawl and your captions have ever fought for the same real estate during severe weather, that is a placement problem in both rulebooks at once, and it is discoverable in advance rather than at 2am.

What actually breaks

In small and mid-market television the recurring failures are not editorial. They are plumbing:

The encoder passes through captions it never receives. A network feed arrives without captions, or with captions the encoder cannot parse, and nothing downstream notices because the encoder is doing what it was told.

Local content is uncaptioned. Syndicated and network programming arrives captioned. The locally produced segment, the sponsored insert, the emergency cut-in — those depend on your own workflow, and the workflow has gaps.

The pass-through dies silently. A firmware update, a router change, a format change upstream, and captions stop. On a monitor wall nobody has captions enabled, so nothing looks wrong.

Nobody monitors it. This is the same structural problem as the secondary audio stream: the failure is invisible to everyone in the building and visible only to viewers who cannot report it in a way that reaches engineering quickly.

The audit, folded into the security walk

You are already going to be in front of this equipment. Add these:

  1. Turn captions on and actually watch. Ten minutes across a network programme, a local segment, and a break. Not a decoder readout — captions as a viewer sees them.
  2. Check placement against your crawl. Trigger a test crawl and confirm the two do not overlap or obscure each other.
  3. Check the secondary audio path while you are there. § 79.2(b)(2)(ii) requires emergency information shown outside a newscast to be spoken on the secondary audio stream, preceded by a tone, in full at least twice. The detail is here.
  4. Now do the § 11.35(d) part on the same box. Default password? Second interface with separate or no authentication? Reachable from outside the building? Firmware revision recorded?
  5. Write down what you found. Nothing gets filed for the security rule — the record is for whoever inherits the plant.

Why bundling them is the right call

Compliance work at a small station fails for one reason above all others: it is a task with no daily symptom, owned by nobody in particular, competing against work that breaks visibly.

The September 29 deadline is the rarest thing in that environment — a hard date that forces someone into the rack with a checklist. Everything you can honestly attach to that trip gets done. Everything you defer to a quieter month does not, because the quieter month does not arrive.

Captioning, emergency audio and program chain security all live in the same three or four devices. One walk, three rulebooks.

The TV scope guide lists what § 11.35(d) covers in a television plant, and the crawl inserter article covers the device most stations have not counted.

Who wrote this

Mark Shannon has spent 43 years in broadcasting. He is the owner and program director of Power88.FM, and builds Cartwright — the traffic, CRM and billing software small-market stations run day to day. Like most people at a station this size, he does his own rack work: STL, codecs, automation, transmitter remote control. That is where these rules stop being paperwork and start being a Saturday afternoon. More about who writes this.

The kit is the version you can work from

Everything on this site is free to read. The Program Chain Compliance Kit is the implementation version — the device-by-device reference, the network patterns for a one-rack station, and the worksheets that leave a paper trail behind the work.

See the kit — $149

Get told when the FCC moves

The rules on this site change without warning — a deadline gets waived, a filing window opens, a Public Notice lands on a Friday. Leave an address and you get an email when something changes that affects a small station. Nothing else, and one click to leave.

Free. No pitch. Your address is not sold or shared. One click to leave.