Nonprofit Video Accessibility: When You Need Captions, Transcripts, and Audio Description

This article is for informational and educational purposes only and does not constitute legal advice.

Video accessibility should be part of the script and publishing plan, not a repair job after a video is posted. For most nonprofit videos with meaningful speech or sound, the practical default is accurate, synchronized captions. If people need visual information to understand the message or act on it, the production also needs a way to communicate that information without relying on sight alone.

The right approach depends on the media format and the information it contains. It also matters whether your organization serves the public, delivers an online service for a state or local government, or receives financial assistance from the U.S. Department of Health and Human Services (HHS).

Understand the three accessibility tools

Captions are synchronized text that conveys spoken words and meaningful sounds. Good captions are timed to the media, are accurate, and identify speakers when that context matters. A doorbell, applause, or an off-camera speaker may be meaningful enough to include. Captions are different from translated subtitles: translation alone does not communicate the original spoken content and relevant sounds as accessibility captions do.

A transcript is a separate text version of the content. It can make the spoken material easy to review, search, or read without playing the media. A descriptive transcript can also include relevant visual events. W3C notes that transcripts are particularly important for people who are Deaf-blind, and a caption file and transcript can often begin with the same reviewed text.

Audio description is spoken narration of visual information that viewers need in order to understand the content. It might explain a chart’s conclusion, identify an on-screen instruction, or describe a critical step in a demonstration. When possible, an organization can build that information into the regular narration while writing the script. W3C’s guidance on visual description explains that separate description is not necessary when visuals add no substantive information beyond what the audio already says.

A practical decision for prerecorded video

Start by asking whether the video has meaningful audio. If it does, provide synchronized captions. Under WCAG 2.1, captions are the relevant Level A provision for prerecorded synchronized media with audio. A transcript alone is not a substitute for captions in an ordinary video.

Then ask whether a viewer must see something to understand the communication. A program explainer in which the narrator states every essential point may need captions but no separate audio description. Emotional B-roll in a beneficiary story may enrich the piece without changing its meaning. In contrast, a how-to video in which visual steps are essential needs those steps conveyed through narration or audio description. The same is true when changing on-screen text, a data graphic, or a person’s action carries information that the audio does not provide.

For a WCAG 2.1 AA target, prerecorded synchronized video with meaningful visual information calls for audio description. A descriptive transcript can help address visual information at Level A, but it does not replace the Level AA audio-description requirement. When practical, publish both captions and a clearly available transcript near the video.

Silent media needs its own review. A silent montage with no meaningful audio does not call for captions of speech, but viewers may still need an equivalent way to receive its meaningful visual message. An audio-only podcast, by contrast, should have an equivalent time-based alternative, commonly a transcript, under WCAG 2.1 Level A.

Plan separately for live streams

For a live webinar, virtual town hall, board presentation, or streamed fundraiser with audio, WCAG 2.1 AA calls for live captions. Decide how access will be provided before promoting the event, rather than waiting for an attendee to request it. WCAG 2.1 does not require live audio description at Level AA, although effective communication and the needs of participants may support additional accommodations in a particular setting.

Review the recording before posting it as an on-demand video. The prerecorded rules and questions about essential visual information then apply to that version.

Build accessibility into the editorial workflow

During scripting, identify every visual fact a person needs to understand the message, complete a task, or respond to a call to action. Put those facts into the narration where that works naturally. This reduces the need to fit separate descriptive narration into pauses later.

Prepare captions from a reviewed transcript, then check timing, names, acronyms, speaker labels, and meaningful sounds. Do not treat automatically produced text as finished captions without review. The U.S. Department of Justice emphasizes captions that are accurate, synchronized, and identify speakers where appropriate in its web accessibility guidance. After publishing, verify that the player’s caption controls and keyboard access work, and make the transcript easy to find.

Know when the compliance stakes are higher

Nonprofit status alone does not create an exemption. DOJ’s effective communication guidance says ADA Title III obligations apply to businesses and nonprofit organizations that serve the public, and identifies captioning and video description as possible aids and services. At the same time, DOJ’s general guidance does not establish one detailed technical web standard for every private nonprofit. Whether a particular organization and online offering are covered can be fact-specific, so do not present WCAG as a universally codified Title III rule.

A nonprofit providing an online public service for a state or local government should treat accessibility as an urgent contract and publishing issue. The current Title II rule requires covered government web content and mobile apps to meet WCAG 2.1 AA. Content made available through contractual arrangements is included, and DOJ says governments using nonprofit contractors must ensure those contractors comply. The compliance date is April 26, 2027 for public entities serving populations of 50,000 or more, and April 26, 2028 for smaller public entities and special districts. See DOJ’s Title II web rule fact sheet.

There is also a specific HHS Section 504 rule for programs or activities receiving HHS financial assistance. It requires WCAG 2.1 AA for covered web content and mobile apps, including content provided through contractual or licensing arrangements. The deadline is May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for recipients with fewer than 15 employees. HHS financial assistance can include grants, loans, cooperative agreements, certain contracts, and subgrants; federal procurement contracts are not financial assistance. These dates should not be applied to nonprofits merely because they receive unrelated federal funding. The governing text is available at 45 CFR 84.84.

One narrow broadcast-related rule may also matter. FCC internet-protocol captioning rules can apply to covered, nonexempt full-length video programming distributed online after it was shown on U.S. television with captions. That specialized requirement does not govern every online-only nonprofit video.

Sources / References

W3C: Web Content Accessibility Guidelines (WCAG) 2.1

W3C WAI: Planning Audio and Video Media

W3C WAI: Description of Visual Information

ADA.gov: Guidance on Web Accessibility and the ADA

ADA.gov: ADA Requirements—Effective Communication

ADA.gov: Fact Sheet—New Rule on State and Local Government Web Content and Mobile Apps

eCFR: 28 CFR 35.200, Requirements for Web and Mobile Accessibility

eCFR: 45 CFR 84.84, Requirements for Web and Mobile Accessibility

HHS OCR: Section 504 Final Rule Fact Sheet for HHS Financial Assistance Recipients

FCC Enforcement Bureau: Internet-Protocol Video Closed-Captioning Requirements