Accessible architecture videos for US audiences: captions, transcripts, WCAG and the ADA web rule

An architecture video that a school district, a city council or a state agency posts on its own website is no longer just a marketing clip; under the US Department of Justice's 2024 web accessibility rule, it becomes web content the public body is responsible for. Firms presenting to public clients in Austin, Chicago, Raleigh or Washington DC are already being asked for captioned, described versions. This guide covers how to make architecture videos accessible for US audiences: open versus closed captions, transcripts, audio description, color contrast of on-screen text, the WCAG criteria for prerecorded video, what the DOJ rule says, and a checklist for every export.

Key takeaways

• WCAG 2.1 Level AA is the technical standard the 2024 DOJ rule requires of state and local government web content, with compliance dates of April 26, 2027 or April 26, 2028 depending on population, as of October 2026.
• The two criteria that matter most for a prerecorded architecture film are captions (1.2.2, Level A) and audio description or a media alternative (1.2.3 at Level A, 1.2.5 at Level AA).
• A music-only film still needs a caption track that names the non-speech audio, and a descriptive transcript is the practical way to make a narration-free film accessible to people who cannot see it.
• On-screen text needs a contrast ratio of at least 4.5:1 against the footage behind it, or 3:1 for large text; a solid band behind the text is the simplest fix.
• Open captions travel with the file and work on every social platform; closed captions are a separate file the viewer can turn on or off and are the right choice for websites and YouTube.

This article describes published standards and a federal rule in general terms and is not legal advice; for a specific contract, ask the agency's accessibility coordinator or your attorney.

Why this applies to architects

Most architecture films are posted by the firm, on its own accounts, and the only accessibility pressure is the audience: many viewers watch with sound off, and some are deaf, hard of hearing, blind or low vision. That alone justifies captions.

The DOJ rule adds a second reason. When a firm delivers a rendering video for a school bond campaign, a library referendum or a planning hearing, the district or city often posts it on its own site and social channels. At that point the content belongs to a public entity with a legal deadline, and an architect who hands over an accessible file is easier to work with than one whose video the district has to caption itself.

What the 2024 DOJ ADA Title II web rule says

The DOJ published a fact sheet on the rule, and as of October 2026 the ADA.gov summary of the 2024 web rule states the following.

The rule applies to all state and local governments, including their agencies and departments, as well as special purpose districts, Amtrak and other commuter authorities. The page's examples include public schools, libraries, courts, elections offices, hospitals and transit agencies. It does not apply to private firms directly; it applies to the public bodies that post your work.

The technical standard is WCAG 2.1, Level AA, for both web content and mobile apps that these governments provide or make available. The page names "requirements for captions for videos" as an example of what WCAG requires.

Compliance dates depend on population: state and local governments with a population of 50,000 or more must comply by April 26, 2027; those under 50,000 and special district governments by April 26, 2028.

The page lists exceptions, including archived web content, preexisting conventional documents such as PDFs posted before the compliance date, individualized password-protected documents, preexisting social media posts, and content posted by third parties. The third-party exception, as the page describes it, does not cover content the government itself posts or content a contractor created for it. A rendering film that an architecture firm produces under contract and the district uploads is, on that description, the district's responsibility to make accessible. Read the page itself before quoting it to a client.

The WCAG criteria that matter for prerecorded video

WCAG is published by the W3C. The quick reference I read is for WCAG 2.2; the criteria quoted below carry the same numbers in 2.1, which is the version the DOJ rule names. As of October 2026, the WCAG 2.2 quick reference lists these under Guideline 1.2, Time-based Media:

• 1.2.2 Captions (Prerecorded), Level A. "Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such."
• 1.2.3 Audio Description or Media Alternative (Prerecorded), Level A. "An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media," with the same exception.
• 1.2.5 Audio Description (Prerecorded), Level AA. "Audio description is provided for all prerecorded video content in synchronized media."

Four criteria outside Guideline 1.2 also bite on architecture films:

• 1.4.2 Audio Control, Level A. If audio plays automatically for more than three seconds, there must be a way to pause or stop it, or to control its volume independently of the system volume. This is the criterion a looping, sound-on website hero video can fail; mute it by default and show a pause control.
• 1.4.3 Contrast (Minimum), Level AA. Text needs a contrast ratio of at least 4.5:1; large-scale text needs at least 3:1.
• 1.4.11 Non-text Contrast, Level AA. User interface components and graphical objects need a contrast ratio of at least 3:1 against adjacent colors; this covers a play button or a progress bar you draw over the footage.
• 2.3.1 Three Flashes or Below Threshold, Level A. Avoid strobing cuts and flashing transitions.

Level AA means meeting every Level A and Level AA criterion: for a prerecorded architecture film, captions, audio description, controllable autoplay audio, sufficient contrast on text and controls, and no flashing.

Captions: open versus closed

The W3C's media accessibility guidance describes captions as "a text version of the speech and non-speech audio information needed to understand the content." Two points follow for architecture films.

First, a film with no narration still has audio content: the soundtrack. A caption track for a music-only film is short, often a single cue such as "[quiet piano music]" at the start and "[music ends]" at the close, but it is what tells a deaf viewer that there is nothing spoken to miss. Films produced with Arch2Video ship with one of three original soundtracks or none; a one-line caption naming the music, or a note that the film is silent, covers 1.2.2 for the audio.

Second, where the film has narration, the captions must carry all of it, plus any sound that matters to understanding.

Open captions are burned into the picture. They cannot be turned off, they survive every re-upload and re-share, and they work on platforms whose caption tools are unreliable. For a 1080 × 1920 vertical film destined for Instagram, TikTok or LinkedIn, open captions are the practical default; keep them inside the safe zone so interface elements do not cover them.

Closed captions are a separate timed-text file, commonly SRT or WebVTT, that the player loads and the viewer can switch on or off. They are the right choice for the firm's website, YouTube and any public body's media player, because they can be edited without re-exporting the video, searched, and translated. For public clients, deliver a caption file alongside the MP4 even if you also post an open-captioned social cut, and edit any machine-generated track: automatic captions mishandle project names, street names and architectural terms.

Transcripts and audio description

The W3C guidance distinguishes a basic transcript, "a text version of the speech and non-speech audio information," from a descriptive transcript, which also includes a text description of the visual information and which the page says is required to provide video content to people who are both deaf and blind.

For an architecture film, the visual information is nearly all the information. A descriptive transcript for a 30-second, six-scene film is six short paragraphs: "Scene 1: a slow approach to a two-story brick school entrance at morning, students crossing a plaza." It takes ten minutes to write from the storyboard, posts beneath the video, and satisfies the "media alternative" route in 1.2.3 at Level A.

Audio description is a narrated version of that visual information, mixed into or alongside the soundtrack so a blind viewer hears what the picture shows. At Level AA, 1.2.5 requires it for prerecorded video. There are two ways to meet it in principle: a separate described audio track, or what the W3C page calls integrated description, where the narration itself is written to say what is on screen. For a film with a voiceover, writing the script to name the spaces as they appear ("the new gymnasium, seen from the mezzanine") is both better presenting and better accessibility. For a music-only social film, a descriptive transcript is the realistic route; a described audio version for the public client's website copy is the next step up.

On-screen text and color contrast

Project titles, firm names, "concept rendering" labels and calls to action are the on-screen text in most architecture films, and most of them fail contrast because they sit on changing footage. Under 1.4.3 the text needs at least 4.5:1 against what is behind it, or 3:1 if it is large.

Three ways to get there: put the text on a solid or near-solid band; add a gradient or drop shadow heavy enough to hold the ratio against the brightest frame the text crosses; or place the text on a frame that stays dark or light for its whole duration. Check against the worst frame, not the first one. Captions follow the same rule: white text with a thin outline over a bright exterior often falls below 4.5:1; white text on a semi-opaque black band almost never does.

Platform caption tools in principle

Instagram, TikTok, YouTube, LinkedIn and Facebook all offer some form of automatic captioning, and YouTube and most website players accept uploaded caption files. The details change often; the principles do not: automatic captions are a draft to edit. Open captions are the only ones that reliably survive a repost. Closed caption files belong with every delivery to a client who will host the video. And accessibility is judged where the video is posted, not where it was made.

Accessible delivery checklist

Run this on every export.

A reviewed, labeled film is the starting point; the AI video quality checklist covers the review of the picture itself, and the checklist above covers what you add after.

Frequently asked questions

Does the ADA web rule apply to an architecture firm's own website?

The 2024 DOJ rule described on ADA.gov applies to state and local governments and the entities it names, not to private firms directly. It matters to architects because public clients post the firm's videos, and that content must then meet WCAG 2.1 Level AA by the client's compliance date. Questions about private business websites are outside this article; ask your attorney.

Do I need captions on a video that has no narration?

Under WCAG 1.2.2, captions are required for prerecorded audio content in synchronized media, and a soundtrack is audio content. A music-only film needs a short caption track that names the music, or a note that the film is silent, so a deaf viewer knows nothing spoken is being missed. It also needs a text or audio alternative that describes the visual content, which for a narration-free film carries all the meaning.

What is the difference between open and closed captions?

Open captions are burned into the picture, cannot be turned off, and survive reposting; they are the right default for vertical social films. Closed captions are a separate timed file, such as SRT or WebVTT, that the player loads and the viewer can switch on or off; they are the right delivery for websites, YouTube and any public client's media player, and can be edited without re-exporting the video.

What contrast ratio does on-screen text in a video need?

WCAG 1.4.3 at Level AA calls for at least 4.5:1 for text and 3:1 for large-scale text, measured against the background behind it. Because footage changes, check against the frame where the background is closest to the text color, and use a solid band or heavy gradient when the footage alone cannot hold the ratio.