Accessibility across AI/CGI video versions: which decisions belong in the brief?

A brand can commission a website film, a vertical advertisement and a silent event loop from the same AI/CGI project. Those outputs do not necessarily carry the message in the same way. A spoken explanation may disappear from one version, while a visual demonstration becomes harder to interpret after another edit.

The research question is practical: how should a buyer organise accessibility decisions when one production becomes several deliverables? We compare the scope of official accessibility guidance with selected advertising guidance, then propose a review framework for digital product films.

Sources and method

The review selected public primary sources that directly address media accessibility or delivery presentation. It uses three W3C Web Accessibility Initiative pages and one Google Ads Help page, all checked on 27 September 2026. Third-party summaries, broad marketing surveys and legal interpretations were excluded.

WAI’s planning guidance, updated on 17 September 2024, distinguishes prerecorded and live media and different combinations of audio and video. It maps accessibility features to WCAG levels.

WAI’s caption guidance, updated on the same date, explains the role of captions and the need to verify automatically generated text. Its visual-description guidance, also updated on that date, addresses conveying essential visual information.

Google Ads’ guidance on square and vertical video recommends 16:9, 9:16 and 1:1 in specified campaign contexts and discusses overlays. Its page revision date was not shown at retrieval.

This is a narrative comparison of requirements and recommendations. The practical framework below is our analysis of how a buyer can organise decisions; it is not an accessibility audit of a particular film or website.

The comparison reveals different units of concern

Accessibility review asks whether people can access the information. Advertising-format review asks how a creative asset is presented in selected placements. Both affect production, but they do not answer the same acceptance question.

A correctly shaped advertisement may still leave an essential visual fact unexplained. Conversely, a film with carefully prepared text alternatives may need a different composition for a particular placement. The buyer should preserve both questions in the delivery brief.

Access to audio information. Buyer’s question: What must a viewer obtain from the soundtrack?. Evidence to inspect: Accurate text representation and its presentation.

Access to visual information. Buyer’s question: Which essential facts appear only visually?. Evidence to inspect: Agreed way of conveying those facts.

Placement presentation. Buyer’s question: What will the chosen layout show or obscure?. Evidence to inspect: Actual composition in the intended context.

Version consistency. Buyer’s question: Does the adapted edit still communicate the intended message?. Evidence to inspect: Version-specific content review.

These are separate review rows, not alternative ways to approve the same thing.

A hypothetical product demonstration

Consider a digitally created film showing how a replaceable cartridge fits into a device. The website version includes narration. A vertical cut focuses on the replacement action. An event loop runs without a spoken explanation.

Begin with the message: the viewer should understand which component is being shown and what action the scene communicates. Identify where that information currently lives. It might be split between narration, a label and the animated action.

For each planned output, ask what changes. If the vertical edit removes the identifying sentence, the buyer needs to decide how identification remains clear. If the loop removes narration entirely, carrying over the same pictures does not by itself settle the communication task.

This exercise concerns the content of the example. It does not determine a conformance level or a legal obligation for an unspecified publication.

Build an information inventory before an export inventory

A conventional delivery list might begin with dimensions, duration and language. Add an earlier list of information units: product identity, the action, any qualification and the next step.

For each unit, record where it is expressed and who can approve its accuracy. This makes omissions easier to discuss. A short cut may intentionally omit a secondary point, but that should be a decision rather than an accidental result of editing.

The inventory can stay concise. It should contain facts that matter to understanding the film, not a description of every decorative element. A product owner and an accessibility reviewer can then work from the same intended message.

A useful prompt for the review meeting is: “If this channel of information were unavailable, what essential meaning would be missing?” The answer identifies the decision the team needs to make for that version.

Plan captions and descriptions as named deliverables

Do not hide all text work under a single line called subtitles. State which language is required, which information the deliverable conveys and how it will accompany the video.

Where automatic tools are used as a starting point, assign a human review of wording and timing. In a product film, the reviewer should pay particular attention to product names, quantities and qualifications supplied by the buyer.

For essential visual information, decide how it will be communicated in the intended output. This may influence the script and pacing, so it belongs in planning rather than only in final export.

The delivery brief should also identify who prepares, checks and supplies each item. A production team may create the video while another team publishes it; the handover needs to make those responsibilities visible.

Review the actual combination of video and presentation

Approval of a text file is one part of acceptance. The buyer also needs to examine how the relevant content is made available alongside the final film.

A caption that is correct in isolation still needs to correspond to the accepted edit. A later change in scene order or narration should trigger review of the associated text. Record the version relationship so publication teams do not pair a revised film with an older file.

Likewise, a description written for one cut should be assessed after a substantive adaptation. The buyer should identify what changed and whether the same explanation remains appropriate.

For placement, review the actual composition. Product detail, text and interface elements may compete for space. Resolve that within the intended layout rather than assuming that approval of the master covers every output.

What to ask for in the proposal

Request a delivery schedule that names the film versions and their associated information assets. For each item, specify the content owner, review stage and publication responsibility.

Ask the supplier to identify dependencies. These can include an unapproved translation, missing product terminology or a publisher’s unresolved presentation choice. A clear dependency is easier to manage than an assumption that will only emerge at delivery.

Accessible AI/CGI versions: language, message and associated text

If the buyer adds a language or changes the message, assess the related outputs together. The extra work is not limited to producing another video file; it may include updating associated text and checking the resulting combination.

A translation can change caption length and reading time. Check that product-part names and action descriptions agree across narration, captions and the text accompanying the video. For a new AI/CGI version, review each combination against the current edit: a caption should describe the action on screen, not a shot from an earlier version. Recheck the associated text when the message changes. Exporting a file does not verify translation, timing or meaning.

Limits of this study

No user testing, assistive-technology testing or platform delivery experiment was performed. We did not assess a live SHAR film for conformance. The selected guidance is a starting point for project requirements, not a determination of applicable law.

Google’s recommendations apply to its stated advertising contexts. We do not transfer its published performance figures to SHAR projects or infer a ranking benefit from accessibility work.

The original framework organises buyer decisions. Its effectiveness would need to be evaluated on real projects with their audience, publication environment and agreed accessibility target.

Practical conclusion for the buyer

Specify the information that must survive adaptation, then attach accessibility and placement decisions to each output. This produces a more useful acceptance brief than a list of file sizes alone.

For an AI/CGI video project, include intended audiences, placements, languages and publication responsibilities in the brief. Discuss the associated deliverables within the actual scope and current pricing context. Final acceptance should name the video version, its accompanying information and the environment in which they were reviewed together.