Extreme Reach
audio description,
in plain language.

Short answer: Extreme Reach does not require audio description on commercial uploads. AD is an optional service XR offers, billed as an add-on, and AD audio rides on dedicated channels of the master (channels 3–4 in the stereo-plus-AD layout). Captions are required — CEA-608 embedded is the floor; sidecar SCC is accepted with a per-spot merge fee. WebVTT and TTML are not broadcast-delivery formats at XR.

Extreme Reach (XR) is the largest US ad-delivery vendor by market share. The company combined the legacy Extreme Reach business with Adstream in 2021 and now operates as XR Extreme Reach at xr.global. DG Systems was folded into XR in 2014. Most of an agency's intuition about "what the delivery vendor requires" comes from XR's published specs, even when the ad is going through CTS, Yangaroo, or another vendor.

Does Extreme Reach require audio description on commercials?

No. XR's own help-center article on audio description states it directly: "While some broadcasters are mandated to air a certain number of hours of primetime or children's programming with Audio Description, there is no such requirement for commercials." AD is an optional service XR sells, billed as an additional fee, with extended turnaround when it is added.

When a brand does add AD to a spot, XR's North America Broadcast Specs lay out two audio layouts: a stereo+AD layout with channels 1–2 carrying program audio and channels 3–4 carrying AD (left/right), and a 5.1+stereo+AD layout with AD audio on channels 9–10. AD is delivered as embedded audio channels on the master, not as a separate sidecar file. The same channel layout convention applies to the SAP transmission path most broadcasters use to air AD — with a known conflict: a station can carry SAP-Spanish or SAP-AD on a given spot, but not both.

XR also flags an enforcement reality worth knowing: fewer than 100 US broadcasters as of 2024 can actually air commercials with an AD track. Most stations are not equipped on the playout side to route a commercial AD audio stream. So even when AD is included, in most markets it will not reach a viewer's set.

What caption formats does XR actually require?

Embedded CEA-608 is the floor. CEA-708 is derived from 608 automatically by XR's pipeline. Sidecar SCC files are accepted but carry a per-spot merge fee when XR has to combine sidecar captions into the master. Sidecar SRT is accepted on a similar basis.

Two formats XR does not list as broadcast-delivery formats: WebVTT and TTML. Those are digital / streaming formats. Sending a VTT file for a broadcast spot is a workflow error that XR's QC will catch and bounce back.

Container constraints worth knowing. MOV containers only support CEA-608 captions. MXF OP1a supports both 608 and 708. Caption-bearing masters must be 23.98, 29.97, or 59.94 fps; other frame rates will not pass XR's caption-validation step.

What about Comcast Technology Solutions, Yangaroo, and other vendors?

Comcast Technology Solutions (CTS) supports embedded CEA-608 (SD/HD) and CEA-708 (HD) in MPEG and QuickTime containers. CTS explicitly does not support SAP/VDS audio description for short-form ads under 5 minutes. If you ship a spot to CTS with an AD track, CTS will not pass it through.

Yangaroo requires CEA-608 / DTV-608 on broadcast deliveries and offers captioning, subtitling, and audio description as production services. Their published note: "closed-captioning is not required by law in the United States for commercial content so is optional." In practice, Yangaroo's broadcaster integrations require captions on commercial inserts because the receiving network's traffic department requires them — not because Yangaroo does.

DG Systems is defunct. The company was acquired by Extreme Reach in 2014 and fully merged. If a brief still references DG, it is referring to a 12-year-old pipeline that has run under XR since 2014. WideOrbit operates ad order and traffic management rather than the file-delivery layer — do not treat WideOrbit as an XR/CTS peer for caption delivery.

If AD isn't required, why do brands still order it?

Three reasons. Brand procurement contracts at most large advertisers cite WCAG 2.1 Level AA conformance, which includes criterion 1.2.5 requiring AD on prerecorded synchronized media that lives on the brand's own properties. Agency QA pipelines flag spots without AD as non-compliant by default. And broadcasters that can air AD (the under-100 stations XR references) increasingly note it favorably in ad-acceptance reviews.

The cost-benefit math gets odd. A brand pays XR an additional fee to add AD to a spot most stations cannot physically air. The audience that will actually hear the AD track on broadcast is small, because the apparatus rule at 47 CFR § 79.105 requires devices to decode the secondary audio stream but the rule does not require stations to carry AD on commercials. Most consumer TVs can route the secondary stream; most station playout systems cannot get it there.

Where AD on a commercial does reliably reach an audience: on the brand's website (the WCAG 1.2.5 case), in agency-aggregated CTV apps that carry alternate-audio tracks, and in any over-the-top distribution the brand controls. The broadcast leg of the media plan is the part where AD often does not land, despite the cost.

Does the FCC's 2026 AD expansion change this for commercials?

No. The FCC's audio description rule expansion to DMAs 111–120 on 1 January 2026 (and the continued 10-DMA-per-year expansion through 2035) applies to programming on top-four-network affiliates — not to commercials. Commercials remain outside the scope of 47 CFR § 79.3 entirely.

What the expansion does change is the volume of described programming on air. The top-4 affiliates in 120 markets now have to air 87.5 hours of described programming per quarter. A brand running spots inside that described programming may face pressure from the network's ad-acceptance department to provide AD on the spots that air during described content. That pressure is per-network policy, not FCC rule.

What does a compliant XR delivery package actually contain?

The required floor: a master ProRes 422 HQ video file (or accepted equivalent) at the broadcaster's frame rate (23.98 / 29.97 / 59.94), with embedded CEA-608 captions on Line 21 (SD) or DTV-608 captions (HD), audio loudness target −24 LKFS per ATSC A/85, and metadata fully populated.

Optional add-ons billed separately: an AD audio track on channels 3–4 (with the stereo+AD layout), Spanish SAP track (mutually exclusive with AD), sidecar SCC file (with merge fee), and any platform-specific deliverables for CTV pass-through. The mixed master with AD blended is a separate file from the master without AD — some broadcasters want each.

AD is a value-add purchase, not a vendor gate. Captions are the actual gate. Build the spec sheet that way. — The Slate, reading across XR, CTS, and Yangaroo specs

Three things to verify before the next delivery

1. Confirm captions are embedded, not sidecar. Most XR delivery problems are caption problems, not picture problems. Open the final master in a tool that can read CEA-608 (Telestream Switch, Adobe Premiere, MediaInfo). If you see captions, the master will pass XR's caption-validation step. If not, the sidecar SCC will trigger XR's per-spot merge fee.
2. If AD is part of the deal, verify the audio layout against the broadcaster's spec. XR uses channels 3–4 for AD in the stereo+AD layout. Some broadcasters want the layout matrixed differently. Confirm before the master is rendered; re-rendering an audio layout after the fact wastes a day.
3. Match the caption file format to the destination, not the source. SCC sidecar for XR broadcast handoff. WebVTT for the brand's own CTV trafficking through programmatic. TTML for premium streaming pass-through. Same captions, three formats. Author once, export the three.

Editor's note. Prepared by The Slate, Editorial. Published 11 May 2026. Reflects XR's published help-center documentation on caption and audio description requirements, Comcast Technology Solutions' published ad delivery format specifications, Yangaroo's published broadcast requirements, and FCC rules at 47 CFR §§ 79.1, 79.3, 79.105 current as of writing. Not legal advice. Vendor specs change — confirm with the vendor's current published spec before delivery.