Build Audience Access Into the Film Proposal, Not Just the Final Export

An access paragraph should tell a producer what work has to happen, who will do it, and when the film can still respond to what they learn. “The finished film will be fully accessible” tells them none of those things.

Start with the intended viewing routes and the information the film asks viewers to recover. Then connect those needs to creative decisions, production materials, paid work, and review. Where a collaborator or delivery specification is not confirmed, say so. A proposal can describe a serious commitment without pretending the work has already been completed.

Keep two tasks separate. Making the proposal usable by its recipient is one task. Planning access to the film being proposed is another. An accessible PDF does not establish that someone can use the film’s captions or described soundtrack; a finished caption file does not make the proposal itself readable.

Give the plan a viewing situation

“Our film is for everyone” is a statement of welcome, not a production brief. A more useful starting point might be: a proposed cinema release, community screenings, and an online version. Mark each as intended or confirmed. Do not turn hoped-for distribution into a secured route simply to make the access paragraph sound settled.

For each route, identify the decision you can make now and the information you still need. An online release prompts questions about the player, the available tracks, and how viewers find the relevant version. A community screening also prompts questions about the organizer, venue, and actual presentation setup. Those questions need answers from the parties involved; they are not answered by writing “accessible screening” on a slide.

W3C’s web-media planning guidance places accessibility in project requirements and assigns responsibilities across production and implementation. Its scope is web media, not a universal rulebook for cinema exhibition. The useful planning principle is to make the intended access work part of the project rather than leave it as an unnamed export task.[^1]

A proposal does not need every release detail at development stage. It does need to distinguish uncertainty about the eventual venue from uncertainty about who is responsible for finding out.

For example: “The producer will confirm the screening partner’s presentation requirements before commissioning final delivery materials.” That is an assigned task. “Requirements will be confirmed” is a sentence in which nobody has to make the call.

Follow one scene’s information

Consider this fictional passage from a coastal drama, Before the Last Ferry:

Rae sits at the kitchen table with an opened letter. A ferry horn sounds outside. She looks toward the harbor, folds the letter, and slides it beneath a loose floorboard. Footsteps stop outside the door. “You’re early,” she says.

Assume the film has already established that this horn marks the ferry’s arrival. The audience is meant to connect the sound with someone’s return, see Rae conceal the letter, and wonder why. The letter’s sender and contents are deliberately withheld.

This is an original planning example, not an access solution tested with viewers. Its purpose is to identify decisions for access collaborators, not to prescribe a finished caption or description.

First separate what the scene communicates from the means it uses:

A dialogue transcript alone would contain two words. Those words would not carry the entire scene.

Captions represent relevant speech and non-speech audio in synchronized text. W3C’s terminology distinguishes this from translation subtitles, which may concentrate on spoken language. For this scene, translating “You’re early” would leave the ferry horn unresolved.[^2]

Audio description conveys important visual information through audio. Here, the letter’s concealment is the obvious question to address; a description that supplies a reason for Rae’s action would go beyond the action the example establishes. W3C describes several delivery methods, including separate described versions and separate tracks, whose suitability depends on the content and playback route.[^3]

A descriptive transcript brings significant visual information into a text account alongside relevant audio information. It is not simply the dialogue transcript with a new filename.[^4] In our example, that means considering the horn and the hidden letter together, rather than treating one as somebody else’s problem.

These formats do related work, but they are not interchangeable assurances. Naming all three in a proposal does not yet say how any of them will serve this particular film.

Protect the scene’s uncertainty, not its barriers

The useful creative question is not “How little can we describe?” It is “What does this scene reveal, and when?”

In Before the Last Ferry, concealment is available to the audience; motive is not. An access discussion can work from that distinction. “Rae hides a letter beneath the floorboard” and “Rae hides evidence of her betrayal” do not make the same claim. The second invents an interpretation that the scene has not earned.

The horn raises a different problem. Identifying a sound can disclose more than its acoustic character alone. If the film has already established the ferry association, the team should take that preceding context into the discussion. Reviewing the kitchen scene in isolation would omit part of its meaning.

The timing of information also matters to this example. Revealing the concealment after the visitor’s reaction would change the order in which the audience learns about it. Speaking over an essential sound could introduce another conflict. The proposal’s job is to make room for qualified decisions about these relationships, not to resolve them through a generic instruction to “add narration.”

There is precedent for films offering deliberately different listening routes. BFI’s published description of Notes on Blindness distinguishes its standard soundtrack, an audio-described version, and an enhanced soundtrack using additional narration, sound design, and music. BFI describes the enhanced version as a different approach from literal description.[^5] That documented example does not tell us which route suits Rae’s scene. It demonstrates why a proposal should name a creative question rather than assume that every access version is the same technical conversion.

Early discussion leaves the director, editor, sound team, and access collaborators something to decide together. It need not mean rewriting every visual action as dialogue or making every version identical.

Commission decisions as well as files

For the fictional scene, a workable next step is to bring the scene, its preceding ferry reference, and the intended viewing routes to qualified access collaborators. Include people who use the proposed access methods in an appropriately scoped, paid review process. Do not treat one person’s feedback as a verdict on behalf of every viewer.

Write down what you are asking those collaborators to assess. “Tell us whether this is accessible” is an enormous, undefined request. “Review how the ferry arrival and letter concealment are communicated, including the order in which each becomes known” gives the discussion a concrete object.

That does not confine reviewers to the producer’s assumptions. Leave room for them to identify a problem the brief missed. The distinction is between supplying a useful starting point and deciding in advance what the feedback is allowed to be.

For planning purposes, organize the work around dependencies rather than a single final date:

During script and scene development, identify information carried only by sound, images, or onscreen text. Ask which decisions need attention before production. For our scene, the team can discuss the importance of the horn and concealment before footage exists, while acknowledging that exact timing remains unresolved.

When an assembly is available, review the passage in context. The question is no longer only what the script intends; it is what the cut actually presents and what space or materials the proposed access approach needs.

Once the relevant picture and sound versions are stable, prepare and review the corresponding access materials. The team should establish what later changes would trigger revision, rather than assume that a version called “final” can never change.

At delivery, check the actual route by which the audience will obtain and use those materials. A file existing in a production folder and a viewer being able to select it are different conditions.

This is a proposed workflow for the example, not a prescribed schedule for every film. Its value lies in making the dependencies visible enough for collaborators to correct them.

Put owners and resources beside the promise

Compare two budget notes:

Accessibility included in final export.

Producer to obtain a scoped quote for captioning, description development and production, descriptive transcript preparation, relevant-user review, and delivery checks. The post supervisor will coordinate source materials and version changes. Release specifications and collaborator appointments remain unconfirmed.

The second note does not prove that the allowance is sufficient. It identifies what the allowance is supposed to cover and what still needs a price, an owner, or a decision.

Budget and proposal language should agree. The June 2025 Nonfiction Core Application 3.1 asks about film or production accessibility and asks applicants to reflect those costs in the submitted budget. That is a dated documentary application framework, not a requirement imposed on every film proposal.[^6] It nevertheless supplies a concrete example of a recipient expecting the access account and the resourcing account to describe the same project.

For your own proposal, distinguish an estimate from a quote, a quote from an agreed scope, and an agreed scope from work already delivered. These are different states, not stylistic variations.

Do the same with personnel. “Access consultant attached” should not mean “we have someone in mind.” Where nobody is appointed, name the hiring responsibility and the decision that depends on the appointment. Do not fill the gap with a fictional adviser or an unapproved organization logo.

Return to Rae’s scene. Suppose a later edit replaces the ferry horn with a telephone vibration and removes the shot of the floorboard. The access team now has different information to convey. An old caption cue about the ferry and an old description of the concealment could no longer be accepted merely because they were reviewed against an earlier cut. The example’s change record should identify the affected passage, the new version, and the person responsible for coordinating another review.

That is the kind of ordinary production detail an access paragraph can make visible. It need not describe every cue to establish that changes have consequences and somebody owns them.

Write the proposal at its actual stage

Here is a bounded paragraph for the fictional project at development stage:

Before the Last Ferry is being developed for cinema and community screenings, with an online version also intended; no release partner is confirmed. We plan captioned and audio-described versions and a descriptive transcript, subject to development with qualified collaborators and relevant-user review. Particular attention will go to offscreen sound and silent actions that reveal story information. The producer will commission and resource this work; the director and post supervisor will coordinate creative and editorial decisions. Collaborators, detailed costs, and route-specific delivery requirements remain to be confirmed.

This paragraph does not announce a completed consultation, a tested viewing experience, or legal compliance. It states a plan and identifies its unfinished commitments. It also leaves room for collaborators to change the proposed methods.

The accompanying production note should now name the next decision: scope and commission the initial access discussion, using the ferry scene and its preceding context. Assign who obtains the quote, who supplies the material, and when the resulting decisions must reach the director and editor.

The proposal is not stronger because it says “fully.” It is stronger when a reader can see the work behind the promise—and the people who will have the time, materials, and authority to do it.

Sources

[^1]: W3C Web Accessibility Initiative, Planning Audio and Video Media, “Project Management,” “Example Workflow and Responsibilities,” and “Resourcing Accessibility.” Inspected September 19, 2026. Web-media planning guidance; not a cinema compliance determination.

[^2]: W3C Web Accessibility Initiative, Captions/Subtitles, “Introduction,” “Captions and Subtitles,” and “Skills and Tools.” Inspected September 19, 2026.

[^3]: W3C Web Accessibility Initiative, Description of Visual Information, “Introduction” and “What Method of Description?” Inspected September 19, 2026. The scene analysis is an original editorial example, not an adopted description script.

[^4]: W3C Web Accessibility Initiative, Transcripts, “Introduction” and “Creating Transcripts.” Inspected September 19, 2026.

[^5]: British Film Institute, Notes on Blindness—Introduction to the Audio Soundtracks, published description of the 2016 introduction and its three soundtrack variants. Page inspected September 19, 2026; this account does not report a new viewing or user test.

[^6]: International Documentary Association, Nonfiction Core Application 3.1, June 2025, page 3, “Accessibility,” and page 4, “Comprehensive Line-Item Expense Budget.” Text and page images inspected September 19, 2026. Recipient-specific instructions still need checking for an actual application.

Frequently asked questions

What should an access paragraph in a film proposal tell its reader, and what two tasks should stay separate?

It should tell a producer what work has to happen, who will do it, and when the film can still respond to what they learn—not just say the finished film will be fully accessible. Keep separate (1) making the proposal usable by its recipient and (2) planning access to the film. An accessible PDF does not establish that someone can use the film's captions or described soundtrack; a finished caption file does not make the proposal readable.

How does the Before the Last Ferry scene show what access planning must address?

The scene has Rae hiding a letter after a ferry horn sounds, footsteps stopping outside, and the line "You're early." The dialogue alone is two words. Captions represent relevant speech and non-speech audio in synchronized text; a translation subtitle of "You're early" would leave the ferry horn unresolved. Audio description conveys important visual information through audio; the letter's concealment is an obvious question, but a description supplying Rae's motive would go beyond the action. A descriptive transcript brings significant visual information into a text account alongside relevant audio information; it is not just the dialogue transcript renamed.

What does the BFI Notes on Blindness example contribute, and what limit does it have?

BFI's published description distinguishes a standard soundtrack, an audio-described version, and an enhanced soundtrack using additional narration, sound design, and music. BFI describes the enhanced version as a different approach from literal description. The example does not tell which route suits Rae's scene; it shows why a proposal should name a creative question rather than assume every access version is the same technical conversion.

How should access costs and personnel be described at proposal stage?

Put owners and resources beside the promise. Distinguish an estimate from a quote, a quote from an agreed scope, and an agreed scope from work already delivered. "Accessibility included in final export" is weaker than naming what the allowance must cover: captioning, description development and production, descriptive transcript preparation, relevant-user review, and delivery checks—plus who coordinates source materials and version changes. "Access consultant attached" should not mean someone is merely in mind; if nobody is appointed, name the hiring responsibility and the decision that depends on the appointment.

What is the proposed access workflow across production stages?

During script and scene development, identify information carried only by sound, images, or onscreen text and flag decisions needing attention before production. When an assembly is available, review the passage in context. Once the relevant picture and sound versions are stable, prepare and review corresponding access materials and establish what later changes would trigger revision. At delivery, check the actual route by which the audience will obtain and use those materials. This is a proposed workflow for the example, not a prescribed schedule.

Further reading

• Show a Film’s Release Sequence, Not a Wishlist of Platforms — Use this to turn a loose list of cinemas, community screenings, and online access into a sequence with prerequisites and honest confirmed, intended, or alternative labels.
• What Can You Say About a Film’s Budget Before It Has Been Priced? — Read this before writing an access budget line, to keep a target, an early estimate, a quote, and an agreed scope from sounding like the same state.
• Make a Descriptive Transcript of a Commercial Pitch Sample — Turn to this when the proposal promises a descriptive transcript and you need a model for combining speech, meaningful sounds, and visual facts in reveal order.