> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# XAG 121: Accessible feature documentation

> XAG 121 guidance for publishing accessible online feature documentation so players can assess your title's accessibility before purchase and get support after.

## Goal

Ensure players can get a sense of whether a title will be playable for them **before** they purchase it, and provide support and guidance on accessibility features they can use **after** purchase.

## Overview

When a title lacks an accessibility feature a player needs, the game may be unplayable immediately or after some progress. For example, a d/Deaf player who buys a game without subtitles for NPC chat or visual cues for critical audio may be blocked entirely — resulting in wasted money and emotional disappointment.

Well-documented accessibility features on accessible, easy-to-find pages let players assess a game before buying it. Publishing this information before launch also helps build excitement in the Gaming & Disability Community and supports informed preorders.

## Scoping questions

* Does your game include audio, visual, input, or difficulty configuration options that improve usability for players with disabilities?
* Does your game include accessibility-specific features such as single-stick mode, toggle aim, auto-reload, screen narration, subtitles and captions, or reduced button hold time?

## Implementation guidelines

<Card title="Publish accessible online documentation" icon="globe">
  All accessibility features, functionality, user guides, and product support options should be described in accessible, easy-to-discover online product documentation.

  * Websites must conform to [WCAG 2 Level AA](https://www.w3.org/WAI/WCAG2AA-Conformance).
  * Give **each title its own dedicated accessibility page**. Avoid combining multiple titles onto a single page.
</Card>

<Card title="Localize accessibility documentation" icon="language">
  If the game ships in multiple languages, accessibility documentation should be available in the same languages.
</Card>

<Card title="Make in-game Help accessible" icon="circle-question">
  When in-game Help systems (tutorial hints, contextual prompts) are present, all accessibility features must also be explained in an accessible format — meeting text display, contrast, and narration guidelines.
</Card>

<Card title="Use respectful, up-to-date terminology" icon="comments">
  Documentation — in-game or online — should use respectful, current disability language.

  * Person-first language (e.g., "gamers with disabilities") is generally recommended over disability-first language, though preferences vary regionally.
  * Avoid antiquated or offensive terms like "handicapped," "impaired," or "incapacitated." Reference the [NCDJ Disability Language Style Guide](https://ncdj.org/style-guide/).
</Card>

<Tip>
  Examples of strong documentation practice include the dedicated [Gears 5 accessibility site](https://www.gears5.com/accessibility/) and Ubisoft's per-feature FAQ pages for Assassin's Creed Valhalla.
</Tip>

## Potential player impact

This XAG reduces barriers for:

* Players without vision or with low vision
* Players with little or no color perception
* Players without hearing or with limited hearing
* Players without speech
* Players with cognitive or learning disabilities
* Players with limited reach, strength, or manual dexterity
* Players using prosthetic devices
* Players with limited ability to use time-dependent controls
* Players who don't want to share their voice online, or who don't own a microphone or headset

## Resources and tools

| Type     | Link                                                                                                                                                                                 |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Article  | [Provide details of accessibility features on packaging and/or website](http://gameaccessibilityguidelines.com/provide-details-of-accessibility-features-on-packaging-andor-website) |
| Article  | [Provide details of accessibility features in-game](http://gameaccessibilityguidelines.com/provide-details-of-accessibility-features-in-game)                                        |
| Article  | [Disability Language Style Guide](https://ncdj.org/style-guide/)                                                                                                                     |
| Standard | [WCAG 2 Level AA Conformance](https://www.w3.org/WAI/WCAG2AA-Conformance)                                                                                                            |
| Tool     | [Accessibility Insights for Web](https://accessibilityinsights.io/docs/en/web/overview/)                                                                                             |


## Related topics

- [XBOX Accessibility Guidelines (XAG)](/build/game-principles/accessibility/xbox-accessibility-guidelines.md)
- [Accessibility metadata](/publishing/game-publishing/concepts/metadata-accessibility.md)
- [XAG 122: Accessible customer support](/build/game-principles/accessibility/xag-deep-dives/xag-122-accessible-customer-support.md)
- [XAG 120: Communication experiences](/build/game-principles/accessibility/xag-deep-dives/xag-120-communication-experiences.md)
- [XAG 123: Mental health best practices](/build/game-principles/accessibility/xag-deep-dives/xag-123-mental-health-best-practices.md)