Skip to main content

FCC Closed Captioning Display Settings Requirements: What Changes in August 2026 and How to Prepare

· 16 min read
Recap Innovations
AI-Powered Video Accessibility Solutions

Starting August 17, 2026, the FCC requires manufacturers of covered apparatus and multichannel video programming distributors (MVPDs) to make closed captioning display settings "readily accessible" to individuals who are deaf and hard of hearing. The rule, codified at 47 CFR 79.103(e), defines "readily accessible" through four specific factors and applies to a broad range of devices, from televisions and set-top boxes to smartphones, tablets, and computers.

This guide covers the full scope of the requirement: what the regulation says, who must comply, what display settings must be supported, how the FCC will evaluate compliance, and what organizations that produce or distribute video content should do before the deadline.

Regulatory background​

The FCC's closed captioning display settings rule implements Section 203 of the Twenty-First Century Communications and Video Accessibility Act of 2010 (CVAA). The CVAA directed the FCC to ensure that people with disabilities have access to video programming on modern devices, expanding on earlier requirements from the Television Decoder Circuitry Act of 1990.

The FCC adopted the Third Report and Order (FCC 24-79) at its July 18, 2024 Open Meeting. The rule was published in the Federal Register on August 15, 2024 (89 FR 66282), and it became effective on September 16, 2024.

However, actual compliance with the "readily accessible" requirement was deferred until the Office of Management and Budget (OMB) completed its review of information collection requirements under the Paperwork Reduction Act. On January 15, 2025, the FCC Media Bureau issued Public Notice DA 25-48, announcing that compliance is required no later than August 17, 2026.

Who must comply​

The rule applies to two categories of entities.

Manufacturers of covered apparatus​

"Covered apparatus" means any digital device designed to receive or play back video programming transmitted simultaneously with sound, manufactured in or imported for use in the United States. This includes:

  • Television receivers (smart TVs, standard TVs)
  • Set-top boxes and converter boxes
  • Smartphones and tablets
  • Personal computers and laptops
  • DVD and Blu-ray players that render or pass through captions
  • Streaming media devices (Roku, Apple TV, Fire TV, Chromecast)
  • Software video players that manufacturers install on devices before or after sale

Devices with screens 13 inches or larger must comply if technically feasible. Devices with screens smaller than 13 inches must comply if "achievable," defined as possible with reasonable effort or expense.

Multichannel video programming distributors (MVPDs)​

MVPDs include cable operators, satellite providers, and other distributors that make video programming available to subscribers. The requirement applies to:

  • Navigation devices (set-top boxes) provided by the MVPD to subscribers
  • The MVPD's own video programming applications hosted on third-party devices

What is not covered​

The rule explicitly excludes:

  • Third-party applications: Apps that are not preinstalled by the device manufacturer or provided by the MVPD are not subject to the requirement. A consumer-installed streaming app on a smart TV, for example, is not the manufacturer's responsibility under this rule.
  • Display-only monitors: Screens with no playback capability are exempt.
  • Professional or commercial equipment not typically used by the public.
  • Devices manufactured before August 17, 2026: The rule places no restrictions on importing, shipping, or selling apparatus manufactured before the compliance date.

The compliance obligation for the "readily accessible" requirement applies specifically to devices using "next generation operating systems deployed after August 17, 2026," per 47 CFR 79.103(e)(2).

The "readily accessible" standard: four factors​

The FCC evaluates whether closed captioning display settings are "readily accessible" based on four factors defined in 47 CFR 79.103(e)(1).

1. Proximity​

Caption display settings must be available in one area of the device or application settings, accessed via a means "reasonably comparable to a button, key, or icon." Users should not need to navigate through excessive menus to reach caption customization options.

In practice, this means settings should be reachable within a small number of taps or clicks from the main settings screen or from within the video player itself.

2. Discoverability​

Users must be able to easily find the caption display settings. The regulation goes further than simply requiring clear labels. Manufacturers and MVPDs must:

  • Conduct usability testing to determine if caption display settings can be easily found, working with consumers and disability groups as part of the testing process
  • Make good faith efforts to correct problems identified during consumer testing
  • Train customer-facing employees on how to advise customers about caption display settings

This is one of the more operationally significant requirements. It is not enough to ship the feature; organizations must test whether real users, including people with disabilities, can actually find and use it.

3. Previewability​

Viewers must be able to preview the appearance of closed captions on programming on their screen while changing display settings. This allows users to see how adjustments to font, size, color, opacity, and other attributes will look in context before committing to the change.

A static preview image does not fully satisfy this factor. The regulation specifies previewing "on programming on their screen," indicating that the preview should reflect actual or representative content.

4. Consistency and persistence​

Caption display preferences must remain stable across sessions and content. The regulation includes specific technical requirements for how settings are shared between devices and applications:

  • MVPDs providing navigation devices must expose closed caption display settings via an API or similar method that over-the-top application providers can use. The API must enable the app to use the device-level settings for its own content if it chooses, and the MVPD must notify application developers about this API through any reasonable means.
  • MVPDs providing their own app on third-party devices must use the operating system-level closed caption settings of the apparatus when the application launches.
  • Manufacturers must ensure their apparatus makes closed caption settings available to applications via an API or similar method.

This factor ensures that a user who sets their preferred caption appearance on their TV or operating system does not lose those preferences when they open an app, switch content, or resume viewing later.

What must be customizable: the ten display capabilities​

Beyond the "readily accessible" requirement in paragraph (e), 47 CFR 79.103(c) specifies the caption display capabilities that all covered apparatus must implement. These are the settings that must be made readily accessible under the new rule.

1. Presentation modes​

Apparatus must support three caption display modes: pop-on (text appears all at once), roll-up (text scrolls up as new text appears), and paint-on (each letter or word appears as it arrives).

2. Character color​

Users must be able to override the authored caption text color and select from a palette of at least 8 colors: white, black, red, green, blue, yellow, magenta, and cyan. The full 64-color palette defined in CEA-708 must be supported for display.

3. Character opacity​

Users must be able to vary the opacity of caption text, selecting between at least opaque and semi-transparent options.

4. Character size​

Users must be able to adjust caption text size across a range from 50% to 200% of the default size.

5. Fonts​

Apparatus must support the eight font styles required by CEA-708 and 47 CFR 79.102(k):

  1. Monospaced serif (similar to Courier)
  2. Proportionally spaced serif (similar to Times New Roman)
  3. Monospaced sans serif (similar to Helvetica Monospaced)
  4. Proportionally spaced sans serif (similar to Arial or Helvetica)
  5. Casual (similar to Dom or Impress)
  6. Cursive (similar to Coronet or Marigold)
  7. Small capitals
  8. Default (system default font)

Users must be able to assign fonts included on their device as the default for each of these eight styles.

6. Caption background color and opacity​

Users must be able to override the authored background color and select from at least 8 colors (white, black, red, green, blue, yellow, magenta, and cyan). Opacity options must include at least opaque, semi-transparent, and transparent.

7. Character edge attributes​

Users must be able to select character edge styles including: no edge attribute, raised edges, depressed edges, uniform edges, and drop shadow edges.

8. Caption window color and opacity​

Users must be able to override the authored window color and select from at least 8 colors. Opacity options must include opaque, semi-transparent, and transparent. (The caption "window" is the region surrounding the caption text, distinct from the immediate text background.)

9. Language selection​

Apparatus must support selection between caption tracks in different languages when multiple tracks are present, and must support "easy reader" (simplified or reduced) captions when available.

10. Preview and setting retention​

Users must be able to preview default and custom caption settings, and the apparatus must retain those settings as the default configuration until the user changes them. This directly supports the "previewability" and "persistence" factors.

What this means for video platforms and content providers​

The "readily accessible" requirement is directed at device manufacturers and MVPDs, not at content creators or web-based video platforms per se. However, the rule has significant downstream implications.

Video platform vendors​

If you build or operate a video platform used by educational institutions, government agencies, or enterprises, your customers are increasingly evaluating caption display customization as a procurement criterion. Platforms that support user-adjustable caption display, preview, and persistence align with the direction the FCC is setting for the industry.

Questions to ask:

  • Does your player support user-customizable caption font, size, color, background, opacity, and edge attributes?
  • Do user preferences persist across sessions?
  • Can users preview caption appearance changes before applying them?
  • Does your platform expose caption settings via an API that host applications can consume?

Content creators and accessibility teams​

The rule reinforces the importance of delivering captions in formats that support downstream customization. Caption formats that carry styling metadata, such as WebVTT, TTML/DFXP, and SMPTE-TT, enable players to apply user preferences. Simpler formats like SRT carry only timing and text, limiting what a player can customize.

When evaluating captioning workflows, prioritize:

  • Generating captions in WebVTT or TTML format for maximum downstream compatibility
  • Ensuring caption output includes timing, speaker identification, and proper segmentation
  • Testing that captions display correctly when user customization is applied in the player

Procurement and RFPs​

For higher education institutions, government agencies, and enterprises purchasing video accessibility services, the FCC rule provides a concrete framework for evaluating vendors. Include the following in RFPs:

  • Support for user-customizable caption display (font, size, color, background, opacity, edge attributes)
  • Caption preview functionality
  • Persistence of user caption preferences across sessions
  • Caption output in formats compatible with FCC-ready players (WebVTT, TTML/DFXP, SCC)
  • Integration with your existing video platforms (LMS, media management, streaming)

Relationship to WCAG, ADA Title II, and Section 508​

The FCC caption display rules operate in a separate regulatory lane from web accessibility requirements, but they converge on the same goal: making captions usable.

RequirementScopeCaption obligation
FCC CVAA / 47 CFR 79.103Device manufacturers, MVPDsCaption display settings must be readily accessible; apparatus must support user customization of font, size, color, opacity, background, edge, and window attributes
WCAG 2.1 Level AA (SC 1.2.2)Web content (enforced via ADA Title II for government, Section 508 for federal)Captions must be provided for prerecorded audio content in synchronized media; must be accurate, synchronized, and complete
ADA Title IIState and local government web content and mobile appsAll video content must meet WCAG 2.1 Level AA, including captioning requirements
Section 508Federal agency ICTElectronic content must be accessible; references WCAG 2.0 Level AA (with updated standards referencing 2.1)

WCAG does not mandate user customization of caption display. The FCC rule does, but only for covered apparatus and MVPDs. Together, these frameworks ensure that captions are both provided (WCAG/ADA) and usable in a way that accommodates individual visual needs (FCC/CVAA).

For organizations subject to both, such as a state university using a video platform on devices that are also covered apparatus, both sets of requirements apply independently.

Frequently asked questions​

When exactly does the "readily accessible" requirement take effect?​

August 17, 2026, per FCC Public Notice DA 25-48, issued January 15, 2025. The compliance date applies to devices using next generation operating systems deployed after that date.

Does this rule apply to web-based video players?​

The rule applies to "covered apparatus," which includes computers, smartphones, and tablets, and to software video players that manufacturers install on those devices. A web-based video player accessed through a browser on a covered device may fall within scope depending on how it is distributed. Video platform vendors used by educational institutions and government agencies are increasingly implementing user-customizable caption display to align with FCC expectations, even where direct legal applicability is debatable.

Does this affect how we produce captions?​

Not directly. The rule governs how devices and applications display captions, not how they are authored. However, the requirement amplifies the importance of delivering captions in formats (WebVTT, TTML/DFXP, SMPTE-TT) that support styling and customization. Captions delivered in plain SRT format work for basic display but offer limited support for the customization options the rule requires devices to provide.

What about third-party apps?​

Third-party applications, whether preinstalled or consumer-installed, are explicitly excluded from the "readily accessible" requirement under 47 CFR 79.103(e). However, the consistency and persistence factor requires manufacturers and MVPDs to expose caption settings via an API that third-party apps can optionally use. This creates an incentive for app developers to consume device-level settings even though they are not required to.

What is the penalty for non-compliance?​

The FCC can take enforcement action against manufacturers and MVPDs that fail to meet the "readily accessible" standard after the compliance date. Consumers and advocacy organizations can also file complaints. Covered entities should anticipate increased scrutiny from disability advocacy groups as the deadline approaches.

Does the rule require specific caption file formats?​

No. The rule specifies display capabilities, not authoring formats. However, it includes a safe harbor provision: apparatus implementing SMPTE ST 2052-1:2010 (Timed Text format) for the ten required functionalities are deemed in compliance with the display requirements.

How Recap Innovations supports FCC-compatible captioning​

Recap delivers captions in multiple formats that support downstream customization on FCC-compliant devices and players:

  • WebVTT: The standard format for web video, supported by all modern browsers and players. WebVTT captions carry timing, text, and optional positioning and styling metadata that players can use or override based on user preferences.
  • TTML/DFXP: Used by broadcast, streaming, and enterprise video platforms. TTML supports rich styling, positioning, and region definitions that enable user customization.
  • SRT: Simple timing and text format, widely supported. Suitable for platforms where advanced styling is handled by the player.
  • SCC: Used in broadcast workflows where CEA-608/708 caption encoding is required.

Our accessible video player supports caption display customization options that align with the FCC's four factors:

  • Proximity: Caption settings are accessible directly from the player controls
  • Discoverability: Customization options are clearly labeled with intuitive controls
  • Previewability: Changes to font, size, color, contrast, and background are visible immediately on the video
  • Persistence: User caption preferences are retained across videos and sessions

For organizations that produce video content for distribution across devices subject to the FCC rule, Recap ensures your captions are delivered in formats that support the full range of user customization options those devices must provide.

Timeline and next steps​

DateEvent
October 8, 2010CVAA signed into law
July 18, 2024FCC adopts Third Report and Order (FCC 24-79)
August 15, 2024Rule published in the Federal Register (89 FR 66282)
September 16, 2024Rule becomes effective
January 10, 2025OMB approves information collection requirements
January 15, 2025FCC Media Bureau announces compliance date (DA 25-48)
August 17, 2026Compliance required for covered apparatus and MVPDs

What to do now​

  1. Audit your video ecosystem. Identify which devices, platforms, and players your organization uses to deliver video content. Determine whether they qualify as covered apparatus.
  2. Evaluate your video platform's caption display capabilities. Ask your vendor whether their player supports user-customizable caption font, size, color, opacity, background, edge attributes, and whether preferences persist across sessions.
  3. Review your caption file formats. Ensure your captioning workflow produces output in formats (WebVTT, TTML/DFXP) that support downstream customization by FCC-compliant devices.
  4. Update procurement language. Include FCC caption display customization requirements in RFPs for video platforms, captioning services, and accessibility tools.
  5. Monitor for updates. Check the FCC Display of Closed Captioning on Equipment page for any changes to the compliance timeline or guidance.

References​

  1. Twenty-First Century Communications and Video Accessibility Act of 2010 (CVAA), U.S. Congress
  2. 47 CFR 79.103 - Closed caption decoder and display requirements for apparatus, Electronic Code of Federal Regulations
  3. Third Report and Order (FCC 24-79), Federal Communications Commission, July 18, 2024
  4. Federal Register publication (89 FR 66282), August 15, 2024
  5. Media Bureau Public Notice DA 25-48: Compliance Date Announcement, January 15, 2025
  6. FCC Display of Closed Captioning on Equipment, Federal Communications Commission

Contact us:

This article is provided for informational purposes and does not constitute legal advice. Organizations should consult with legal counsel regarding specific FCC compliance requirements. All regulatory citations reference the text of 47 CFR 79.103 as amended through 90 FR 10042 (February 21, 2025).