Pitch a Series Told in Sign Language Without Treating Language as an Add-On
Pitch a Series Told in Sign Language Without Treating Language as an Add-On
A pitch document introduces one of its leads. The line goes like this — a construction, not a quotation, but you will recognize the shape:
MAYA (30s, Deaf) — guarded, funny, signs.
That is the whole of it. The next nineteen pages argue the premise, map the season, name the tone, and sketch three set pieces. On the last page, under ACCESSIBILITY, a sentence mentions captions and an interpreter.
Look at what those nineteen pages already decided. A script format. A shot list. A casting brief. A rehearsal schedule. A budget line for the room and a budget line for the truck. All of it built for a show whose conversations happen in a language that arrives last, in a paragraph that does not touch anything else in the document.
The fix is not to write a more sensitive sentence on the last page. It is to move the language into the scene description and let it change what the scene is. That is a pitch problem, and it has describable parts.
Specify the language and the relationships within the scene
Start with the name. American Sign Language, British Sign Language, French Sign Language, Auslan, and the rest are different languages, not accents of one system. A show is in one of them, or in a stated combination, or it has not decided yet — and "has not decided yet" is a legitimate thing to write in a pitch, provided you say who will decide and when.
Suppose the character line instead reads like this:
MAYA (30s, Deaf) signs ASL at speed with her sister, slows down for her mother, and reads her boss's signing the way you read a form — accurately, and without pleasure.
Nobody has been explained to. But three relationships just became visible: who she is fluent with, who she accommodates, and where the language costs her something. That is more useful to a casting director, a director, and a reader deciding whether to keep going than any adjective about being guarded.
The W3C's Web Accessibility Initiative page on sign languages notes that sign languages vary — it is not describing one universal system — and that meaning is conveyed through the hands, arms, face, and body together. That is the page's territory and it stops there; it is guidance about sign-language accessibility and interpreted media, not a rulebook for drama. What it is good for here is the reminder that a scene description cannot be complete if it only accounts for hands.
Three questions, asked per scene, will do most of the work:
- Who is in the room?
- What can each of them perceive, at speed, without effort?
- What does each of them want in the next thirty seconds?
Where the answers line up, you have a conversation. Where they do not, you have a scene. A character who must be looked at before she can be understood is in a different situation from one who can talk while someone's back is turned — and that difference is not a footnote about deafness. It is the physical condition of every exchange in the episode.
You do not need a paragraph about identity. You need to say who can talk to whom.
Make performance available without prescribing one camera rule
The instinct, once you accept that the language matters, is to solve it with a lens. "We shoot the signing in a wide two-shot, always." That single rule will be wrong within an episode, and possibly within a scene.
The W3C guidance addresses keeping signing visually available, and it identifies meaning as carried through hands, arms, face, and body, with variation across languages. Its scope is accessibility advice for sign-language video and interpreted media. It does not hand you a shot distance for a drama, and importing the framing conventions of an interpreter panel into a dramatic scene is a category error — you would be using a delivery format as a directing rule.
Here is a method that survives contact with a script. Go beat by beat and ask what the viewer must perceive for that beat to land. Then write it down.
Some beats need both bodies and the space between them, because the exchange uses that space. Some need a face, because in many sign languages the face is doing grammatical work and not just emotional work. Some need a hand on a box, because the beat is about a hand on a box. And some beats need to withhold. A body out of frame, a face turned away, a line the camera does not catch — those can be excellent choices.
The difference between a deliberate restriction and an accident is whether the pitch says so. If the viewer is meant to miss something, say what they miss and say what pays it off later. If it is not deliberate, you have simply made a scene the audience cannot read. On screen those two look identical for about ten seconds and completely different over ten episodes.
So do not write a universal rule into the pitch. Write who makes the call, with whom, and on what basis. Framing decisions belong to a director of photography working with the language collaborators on the actual beat. Naming that arrangement is more convincing than any claim about shot size, and it survives the first table read.
Separate access inside the story from access to the program
Two different things are often smuggled into one word, and they behave differently.
Inside the story is who can see whom and whether they are attended to. A character can miss a contribution the audience understood perfectly. Another character can catch something the audience never saw. A character can choose not to be understood, or can be understood only by one person in the room. This is drama, and it is yours to stage.
Outside the story is the route the audience takes to the material: written translation, an interpretation track, a dubbed voice, audio description, a separate signed version in another language. This is delivery, and it is a production decision with costs attached. Neither one repairs the other. A beautifully captioned scene in which nobody can see anybody is still a scene in which nobody can see anybody.
Four distinctions worth holding onto:
Written translation is not the performance. A caption renders what was said in written form. It does not carry the face, the rhythm, the choice of how something was said, or the timing of a turn away. Captions are a translated text and should be described as one — never as reproducing the complete performance.
Original signed dialogue is not an added track. A line performed in ASL by an actor in the scene and a line voiced by a separate performer in post are different objects with different authorship, cost, and permanence. If you propose an on-screen interpreter, you have added a second performer to every frame that includes them. If you propose a dub, you have replaced one performance with another. Neither is neutral, and neither is a technicality.
Audiences are plural. A viewer who reads ASL takes the beat directly. A viewer who does not needs a written route, or a fifth object called an interpretation. Viewers using audio description need a route into a visual language that narration handles poorly. Say which route serves which viewer, and admit which ones you have not priced. A statement like "some viewers will read the original, others will read a translation, and we have not yet settled the route for the rest" is an honest pitch line. "Fully accessible" is not.
Access is not an alibi for a shot, and a shot is not an alibi for access. Using "artistic choice" to cover a framing problem, or "accessibility" to justify a composition the scene does not want, are the same failure in two directions. State the choice, and let the reader agree or disagree.
Give collaborators concrete creative responsibilities
A pitch that says "we will consult the Deaf community" has said nothing a reader can evaluate. Replace it with verbs, attached to phases, and separated into what is settled and what is still open.
In development: who co-authors the language of scenes; who determines each character's language history and fluency; who reviews the script as written rather than as translated.
In production: who directs performance; who has input on casting; who sets framing requirements for a given beat.
In post: who produces the written translation; who times it; whether an interpretation track exists and who performs it; who reviews the cut.
Then label the state. If a Deaf co-writer is attached, say so. If you are seeking one, say that too — it is information, not weakness, and a reader who knows the field will respect the difference more than a vague promise. Confirmed and proposed are different words for a reason.
The harder point is authorship. If a collaborator is devising how the scenes speak — the register, the argument's shape, the way these two people actually contradict each other — that is writing, and it should be structured, credited, and paid as writing. Writing a complete invented language practice for the show and then asking someone to approve it is not collaboration, it is a signature request, and the people you most want will read it that way instantly.
Two practical guards. One collaborator cannot represent every sign language; a BSL strand needs BSL-specific engagement, and a second sign language in the story is a second engagement. And interpreting is its own profession with its own standards. Do not ask your scene-language author to interpret on set, and do not ask your on-set interpreter to be your dramaturg. They are different jobs and the person doing both badly helps nobody.
A scene, described twice
The following is a proposed fictional ASL scene, awaiting Deaf-led and ASL-specific development. Nothing described here has been signed, translated, performed, or shown to a viewer.
Two siblings, Nia and Sam, are clearing out a room. They disagree about whether to finish tonight. Nia has been making the case. Sam has stopped making anything, and has turned back to the boxes. The dramatic question is not how either of them signs. It is whether the conversation continues.
Version one — the description that loses Sam's contribution.
NIA argues at SAM. SAM keeps taping. NIA signs harder. SAM doesn't turn. NIA gives up and starts on the shelf. Camera: medium on Nia, over Sam's shoulder.
Read that as a statement of content and you can see the problem. Everything Sam does is written as an absence. Sam keeps taping, does not turn, gives nothing. The description does not know whether Sam is refusing, stalling, exhausted, finishing a box, or simply has not seen the last thing Nia said — and a shot plan that keeps him as a foreground shape guarantees the viewer will not know either. Then the written translation arrives, carries Nia's signing, and inherits the same gap: Sam ends up with no position in the scene, in the captions, and in the reader's understanding.
Version two — the design that says who can perceive what.
Nia is behind Sam and off his shoulder. Sam is at the boxes, half turned. Sam cannot see Nia unless he turns. Nia has two ways to be heard: cross into his field of view, or wait for him to look up. She has been crossing all night. This time she does not.
She stays where she is and waits. Sam finishes the strip of tape — a beat the viewer watches on his hands and the box — then straightens and turns, far enough to bring her into view. She signs one short line. He holds her look for one beat, then turns back to the boxes, reaches for a new roll, and goes on taping.
The beat: Nia asks for the conversation to continue by not chasing it. The pressure she has been applying all night has stopped, and when Sam turns to check, she is where he can see her. She gets one line through. He receives it and turns away. That is how he ends it, and the viewer watches him choose it.
Now the frame has a reason. It has to hold two bodies that are not looking at each other, plus the hands, plus the one look the scene turns on, plus the turn away — because that sequence is the content. That is not a rule about shot distance. It is a requirement this scene generated, and any pitch can generate its own.
Note also that a turned back does not mean anything on its own. It could be refusal, a stall, exhaustion, a miss, or a move to keep working. Which one it is has to be built: by what came before — Nia crossed every night, and Sam turned to her every time — and by what comes after, the turn away and the reach for a new roll that says he is staying here. The intention lives in the developed scene, not in a presumed universal meaning for the gesture.
Two notes travel separately from the scene.
On written translation: the caption carries Nia's short line. It cannot carry "she did not cross this time" or Sam's decision, and it should not try — a caption reading "(Sam ends it)" would assert the intent the performance is supposed to deliver. The translation carries the words. The scene carries the choice.
On audience access: a viewer who reads ASL takes the beat as performed. A viewer who does not needs a written route, and the scene should be strong enough in action to survive that route rather than depend on it. Whether an interpretation track exists, and what form it takes, is a separate proposal with a separate cost.
A third option exists and is worth naming: hold on Sam's hands and the box through the whole beat, so the viewer never sees the line, only what it does to him, and learns later what she said. That is a legitimate restriction. It is legitimate because it is stated, and because a later scene can pay it off — not because the camera happened to be there.
What to put in the document
Close the pitch double: the scene, then the plan.
Settled: the show is in ASL. The dialogue happens in it. Framing is decided per beat, by the director of photography with the language collaborators, against what each beat requires the viewer to perceive. Written translation is separate from the performance and is not described as reproducing it.
Open: which Deaf co-writer joins and in what role; the translation approach; the audience access route; whether an interpretation track exists at all.
That mix is fine. A pitch is a proposal. What it cannot do is claim that any of this has been validated, tested with an audience, or reviewed by people who have not yet been asked.
Then apply the test. Hand the pitch to someone who has never seen the show and ask them to describe how a conversation in it works. If the answer is "the characters sign," the scene is not in the document yet. If the answer is "one of them has to be looked at before a single line can land, and the other ends the conversation by turning back to the boxes," you have written a series whose language is doing the storytelling rather than appearing in it.
Frequently asked questions
What is wrong with describing a Deaf character mainly as 'signs'?
It treats the language as an add-on rather than part of the scene. The body suggests naming the specific sign language and showing relationships: who the character is fluent with, who she accommodates, and where the language costs her something. That gives casting, directing, and reading more to work with than an adjective.
What three questions can guide each scene?
Who is in the room? What can each person perceive, at speed, without effort? What does each want in the next thirty seconds? Where the answers line up, the body says, you have a conversation; where they do not, you have a scene.
Should a pitch prescribe one camera rule for signing?
No. The body argues that a single rule such as 'wide two-shot, always' will be wrong somewhere. Go beat by beat and state what the viewer must perceive for that beat to land. Framing decisions belong to a director of photography working with language collaborators on the actual beat. If a restriction is deliberate, say what the viewer misses and what pays it off later.
What is the difference between access inside the story and access to the program?
Inside the story is who can see whom and whether they are attended to—that is drama and can be staged. Outside the story is the audience's route to the material: written translation, an interpretation track, a dub, audio description, or a separate signed version. Those are delivery decisions with costs. Neither repairs the other; a well-captioned scene where nobody can see anybody still has that staging problem.
How should a pitch describe collaborators' roles and authorship?
Give concrete responsibilities across development, production, and post, and label whether they are confirmed or proposed. If a collaborator is devising how the scenes speak—register, shape of argument, how characters contradict each other—that is writing and should be structured, credited, and paid as writing. One collaborator cannot represent every sign language, and interpreting is a separate profession from scene-language authorship or dramaturgy.