> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/interview-studies/conduct-an-interview-session/enable-closed-captions-during-an-interview-session.md).

# Enable closed captions during an interview session

Closed captions are a great accessibility option for anyone taking part in an interview session, whether you’re a moderator, observer, or guest. Closed captions provide a live transcript of what's being said during an interview session at the bottom of your video feed.

{% hint style="info" %}
**Note:** Captions are automatically displayed in the interview study’s selected language. For more information, see [Manage language of an interview study](/interview-studies/create-an-interview-study/manage-language-of-an-interview-study.md).
{% endhint %}

To enable closed captions, click the **Closed captions** icon in the bottom right of the interview window:

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/ho2lIM6GG5zDjgzOr3n9/47105481927828)

Now, closed captions are displayed at the bottom of your session's video feed. To turn closed captions off, click the **Closed captions** icon again.

{% hint style="success" %}
**Tip:** Participants can also enable closed captions on their end using the following steps. Feel free to share these instructions with them or point them in the right direction using the chat. For more information, see [Chat during an interview session](/interview-studies/conduct-an-interview-session/chat-during-an-interview-session.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/interview-studies/conduct-an-interview-session/enable-closed-captions-during-an-interview-session.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
