Xbox Accessibility Guideline 104: Subtitles and captions

Goal

The goal of this Xbox Accessibility Guideline (XAG) is to ensure that all audio information that's portrayed by a game can also be understood by players who can't rely on audio, such as players who are d/Deaf or hard of hearing.

This audio information includes full motion videos (FMVs), cutscenes, in-game non-player chatter, and important audio cues (for example, sounds of gunfire or footsteps).

Overview

Subtitles are text equivalents for the speech or dialogue of a character, while captions are text equivalents for all audio. Captions include text equivalents for non-speech sounds like background music playing ["Name of song, artist", "lyrics"], sound effects ["dogs barking"], ["knocking on door"], and other audio cues. Captions can also include important information like who is speaking, their tone ["sarcasm"], or where a sound comes from ["over the radio"].

When subtitles and captions aren't present during game experiences (like FMVs, non-player character (NPC) chatter dialogues, or other audio cues), a player might miss out on a game's backstory, important context within the game's storyline, and key tasks and objectives that inform gameplay.

Scoping questions

Does your game include any of the following elements that contain audio or dialogue that can be heard by players?

• Does your game include FMVs or cutscenes?

• Does your game include NPC chatter or dialogue?

• Does your game include audio cues (for example, sounds of gunfire or footsteps) that inform key components of gameplay?

Implementation guidelines

• Subtitles (text equivalents for speech) are provided for all spoken content.

• Identify the speaker, and use visual spatial indicators to indicate which direction the speaker's voice is coming from if it's not immediately clear.

  • The speaker's name should be identified in the subtitle line each time a new speaker begins talking. Once the speaker's name is established, the speaker name does not have to re-appear on every subsequent subtitle line while the same speaker is talking. The name of the speaker only needs to appear again in the subtitle line when there is a change in speakers, or if a significant pause (greater than 1-2 minutes) has taken place during the same speaker's dialogue.
  • Color can be used to distinguish who is speaking. However, color should be used in conjunction with another means of portraying information, such as text.

  Note

  In scenarios where the speaker is an unidentified “narrator,” and there are no other speakers, identifying “narrator:” in the subtitle or caption text is not required.

• Players can adjust the option before starting the game, or subtitles are enabled by default. This ensures that players don't get dropped into a long introduction cinematic without being able to follow along.

• Captions (text equivalents for all audio) are provided for all important sounds that aren't already communicated visually. Spatial indication (like arrows next to the text) should be provided to indicate which direction a sound is coming from if it's not immediately clear (for example, if the sound is coming from something occurring offscreen).

• Subtitles and captions can be turned on or off at any time and configured easily through a discoverable setting.

  • Allow different types of caption information (like main character dialogue, background character dialogue, or ambient noises) to be toggled on or off independently of one another.

• Whenever possible, the title should use the caption/subtitle settings that are configured by the player at the platform level by default.

• Subtitle and caption text should conform to the following standards.

  • Size: Text size should meet the minimum defined pixel height by default as defined in XAG 101: Text display. (The ability to configure text to be smaller or larger than the default minimum in the settings is also beneficial to players.)

  Note

  Unlike static text in menus, subtitle and caption text for spoken dialogue is typically only displayed on-screen for short periods of time. Given this, developers are encouraged to offer larger minimum default sizes for caption and subtitle text to facilitate ease of rapid reading.

  • Adjustable size: Scalable to a large size (minimum of 200 percent of minimum default text size). For more information, see XAG 101: Text display.

  • Spacing: Readability is improved when words and lines of text aren't very close to each other. Avoid offering a font that has small spacing between the characters.

  • Length: Avoid long lines of text (more than 40 characters), especially when the dialogue is fast. When text appears rapidly, longer lines of text are harder to read than shorter ones. Show no more than two lines of subtitles on screen at a time (three can be used in exceptional cases).

    • When possible, line breaks should be entered manually (as opposed to automatic wrapping or splitting) to ensure that breaks occur at editorially sensible points.

  • Case: Font should be in mixed case. It's much easier to read than all the same case. For example, "Hello. How have you been?" versus "HELLO. HOW HAVE YOU BEEN?"

  • Sans serif: Ensure that at least one san serif font option is available for subtitles and closed captions.

  • Background color: Players should be able to place a solid background behind subtitle and caption text to ensure readability of that text, regardless of the game's background. (For example, white text presented over light desert sand looks virtually invisible to the player.) The color of this background should be configurable by the player.

  • Background opacity: Players should be able to adjust the opacity of the background on a scale from 0 to 100 percent. This supports players who might require high contrast as well as others who might find an opaque background obtrusive.

  • Placement: Ensure that important UI/gameplay elements are designed to avoid being obscured by subtitles when scaled to the largest size. This can generally be achieved by ensuring that placement is toward the bottom of the screen.

• Provide a visual simulation of what subtitle and caption presentation options will look like based on the player's current configuration settings.

  • If possible, this preview should be shown in a realistic game context.

• Caption and subtitle information should persist during screen recordings, captures, and other user-generated content (UGC). Other players viewing that content can choose to display it.

• Full transcripts of FMVs should be made available via an accessible website.

• Sign language interpretation is provided for scripted in-game cutscenes and prerecorded/pre-rendered sequences of media that include speech, such as full motion videos (FMV’s).

  • Signing requires localization, just like spoken languages do. For example, American Sign Language, British Sign Language, and Japanese Sign Language are all vastly different from one another.

Potential player impact

The guidelines in this XAG can help reduce barriers for the following players.

Resources and tools