# Accessibility

The player can be fully controlled using the keyboard. **Keyboard** navigation is supported for common playback actions such as play/pause, seeking, volume control, fullscreen mode, and chapter navigation.

The player is fully **WCAG** compliant and **BITV** compliant, ensuring accessible interaction for keyboard and assistive-technology users.

Keyboard shortcuts are active when the player container is focused.

### Key Bindings (Desktop)

| Key                       | Action                        |
| ------------------------- | ----------------------------- |
| Space                     | Play / Pause                  |
| K                         | Play / Pause                  |
| F                         | Toggle Fullscreen             |
| Left Arrow                | Seek −10 seconds              |
| Right Arrow               | Seek +10 seconds              |
| Shift + Left Arrow        | Seek −60 seconds              |
| Shift + Right Arrow       | Seek +60 seconds              |
| Up Arrow                  | Increase Volume               |
| Down Arrow                | Decrease Volume               |
| M                         | Mute / Unmute                 |
| Ctrl (or ⌘) + Left Arrow  | Previous Chapter              |
| Ctrl (or ⌘) + Right Arrow | Next Chapter                  |
| Esc                       | Close open menus and overlays |

### Touch Gestures (Mobile)

| Gesture                            | Action           |
| ---------------------------------- | ---------------- |
| Two-finger double tap (left side)  | Previous Chapter |
| Two-finger double tap (right side) | Next Chapter     |

**Accessibility Notes**

The Tab key is intentionally not intercepted by the player. This allows users to navigate normally through focusable elements such as controls, buttons, and interactive UI components using standard keyboard navigation patterns.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://player.docs.3q.video/player-web-sdk/accessibility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.