How International Theatre Festivals Handle Language Access

The short answer: treat language access as infrastructure

International theatre festivals should handle language access for visiting companies by planning it from the moment of invitation and treating it as part of production, audience access and artist care. The minimum standard is not an English synopsis in the programme. It is a named system: clear decisions about which languages are served and for whom; contracts that allocate translation, surtitle and interpretation responsibilities; qualified theatre translators and checked cue scripts; rehearsed surtitle or interpretation operation; and public information that tells audiences exactly what will be available, where and in which language. Language access should be budgeted, credited and reviewed like any other production department.

That answer applies to festivals of different scales. A small festival may use one operator and two languages; a large one may run several venues and audiences with different needs. The principle does not change: language access must be designed with the specific production, venue and audience in view, not copied as a generic international courtesy.

What counts as language access?

In this context, language access means the practical arrangements that allow audiences to follow work in a language they do not speak, and allow visiting artists to work, rehearse, negotiate and speak about their work in a language they can use. It includes:

• translation and adaptation of the play text, libretto or performance text;
• surtitles, captions, simultaneous interpretation or whispered interpretation, depending on the form;
• translated programmes, content notes, schedules, technical documents and safety information;
• interpretation for rehearsals, technical meetings, talks, press and contractual discussions;
• front-of-house information about which languages are spoken, translated or interpreted.

It is useful to separate audience-facing access from company-facing access. A festival can provide elegant English surtitles for the public and still leave a visiting company unable to discuss lighting cues or contract changes in a shared language. Both dimensions matter. Language access is also not identical to accessibility, although the two overlap: captioning and sign-language interpretation for deaf and hard-of-hearing audiences are specialist access services, not simply extra surtitle languages.

Decide the language architecture early

The planning source Pockitle Cue argues that multilingual subtitles for festivals succeed when language scope, audience entry and live operator workflow are planned together, because translation coverage alone is not enough. It also notes that audience language needs can change between performances and venues, and that the same team may not be present at every setup (Pockitle Cue). That is a useful warning against the common practice of commissioning a translation late and hoping the venue will solve the rest.

Festivals should answer three questions before contracts are signed. First, which languages are genuinely necessary for this audience and this production, not merely desirable in principle? Second, how will audiences discover the service, obtain a device or read a screen, and know when it starts? Third, who will operate the service, with what backup, and how will the festival avoid creating a separate control workflow for every language? The answers should appear in the production schedule and budget, not only in a marketing plan.

This is also where festivals should resist the assumption that English is a neutral lingua franca. English may be the shared working language for a tour, but it is not automatically the right audience language, and it may not be the language in which the visiting company is most articulate during talks or rehearsals. The festival should name the languages explicitly: the spoken language or languages of the performance, the surtitle language or languages, the language of public discussion, and the working language for technical and contractual communication.

Match the format to the performance

Different forms need different language-access solutions. A text-heavy drama may need line-by-line surtitles, while dance, physical theatre or visual work may need scene summaries, content notes or a spoken introduction. Opera may require libretto translation and careful cueing against music. A multilingual devised production may need language labelling, selective interpretation and a dramaturgical explanation of how languages function in the work. The festival should not impose one surtitle template on every visiting company simply because it is administratively convenient.

Commission translation as an artistic and legal process

Theatre translation is not a mechanical substitution of words. The Theatre Translation Handbook published by the Arts and Theatre Institute treats translation as an artistic activity and addresses practical questions such as legal permissions, financial conditions and the pitfalls of machine translation (Institut umění – Divadelní ústav). Festivals do not need to become translation specialists, but they do need to know that a good surtitle script depends on dramaturgical judgement: line breaks, cue points, compression, tone and cultural reference all affect the audience’s experience.

Contracts should therefore state who supplies the source text, who commissions the translation, who checks it against the rehearsal, who owns or licenses the translation for performance and recording, and what happens if the production changes. A visiting company may arrive with an existing translation or surtitle file; that does not remove the need to check rights, accuracy, cueing and compatibility with the venue. If the festival commissions a new translation, the translator should have access to a rehearsal or recording and should be credited in the programme and on the surtitle display where appropriate.

Machine translation can be useful for internal drafts, schedules or low-risk information, but it should not be presented as a finished theatrical translation without expert review. The handbook’s discussion of AI pitfalls is a reminder that fluency is not the same as theatrical accuracy. Names, jokes, verse, dialect, overlapping dialogue and songs are common failure points.

Rehearse the surtitle and interpretation operation

Surtitling has moved from being treated as an accessory to being recognised as essential to the international dissemination of theatre. The European Theatre Lab’s account of the re-invention of surtitling describes how the titlist became central to international presentation, rather than someone supplying minimal assistance after the fact (European Theatre Lab). The practical implication is that surtitles need rehearsal time, not just a file and a projector.

A robust operation usually includes a cue script marked against the performance, a named operator, a rehearsal or technical run with the operator present, a backup copy, and a plan for late changes. The operator needs to see and hear the performance, and the audience needs a readable sightline. If the festival uses several languages, the operator interface should be tested so that switching language does not create a separate, error-prone workflow. For spoken interpretation, the festival needs to decide whether it is simultaneous, consecutive or whispered, who supplies headsets, and how the interpreter will receive the script and any late changes.

For deaf and hard-of-hearing audiences, captioning and sign-language interpretation require specialist providers and should be planned with the same rigour. A festival that advertises itself as accessible should be precise about which access features are available at which performance.

Make the service visible and usable

Language access fails if audiences cannot find it. Festivals should publish a clear language-access page or performance-level note that states the spoken language or languages, the surtitle or interpretation languages, how to obtain devices, whether booking is required, and where to sit. The information should be available before booking, not only in a programme collected at the door.

Public accessibility pages can provide a useful model. Wiener Festwochen’s Good to know page, for example, publishes an accessibility contact and states a commitment to identifying and removing barriers on, in front of and behind the stage and in its online presence (Wiener Festwochen). That is not a statement that the festival provides every language service, but it shows the value of a named route for access questions. A festival should similarly name who is responsible for language-access enquiries and how a visiting company can raise a problem during the run.

Front-of-house staff need a simple briefing: which performances have surtitles, which language is on which channel, what to do if a device fails, and how to direct audience members who need assistance. Interpreters and operators should be included in the production’s communication chain, not treated as external contractors who appear at the last minute.

Budget roles and evaluation

Language access should have a visible budget line for translation, proofreading, surtitle preparation, operator fees, equipment, interpretation, translated printed or digital materials and contingency. It should also have named roles: a language-access producer or coordinator, a translation lead, a surtitle operator and a front-of-house access contact. On small festivals these roles may be combined, but they should not be nobody’s job.

Evaluation can be modest and useful: track which services were booked or used, collect audience and company feedback, note technical failures, and record which language combinations caused the most pressure. This information helps the next edition and makes the case for continuing or changing provision. It also avoids the trap of treating language access as a one-off gesture rather than a repeatable system.

A phase-by-phase checklist

Common failures to avoid

• Treating English as a universal solution and providing no other language access.
• Commissioning translation after the programme is printed and the technical schedule is fixed.
• Assuming a visiting company’s existing surtitle file is accurate, licensed and venue-compatible.
• Giving the operator a script but no rehearsal or sightline.
• Advertising accessibility without specifying which performances and which features.
• Forgetting the company’s own access needs in rehearsal, tech, talks and contracts.

The underlying discipline is straightforward: decide early, contract clearly, translate artistically, rehearse technically, publish plainly and review honestly. Festivals that do this are not adding a luxury. They are making international work actually international for the people in the room.