What do XAG 106 and GAG require for screen-reader and screen-narration support, and how do they differ?

XAG 106 asks games to voice all core UI text (menus, HUD, state changes, timed events) through the platform screen reader or a speech synthesizer; recorded audio files work but are 'not ideal'. Each control should be announced with role, state and position (e.g. 'Gamma, slider, 38%, 6 of 9'), non-decorative images need alt text, the game language should be exposed to screen readers, and focus order should follow meaning or visual flow. The Game Accessibility Guidelines rate full screen-reader support including menus as Vision, Advanced (mobile support Intermediate) and point to Tolk and the Xbox SDK text-to-speech API. Curator qualifications: Guideline pages read 2026-10-22; no game tested. XAGs are written as implementation guidelines with examples; treat 'requires' in the offered text as guideline language, not platform certification (certification status not checked). Limitations: Guideline pages read 2026-10-22; no game tested. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://learn.microsoft.com/en-us/xbox/accessibility/xbox-accessibility-guidelines/106",
      "note": "XAG 106 Implementation guidelines; GAG: Ensure screen reader support, including menus & installers"
    },
    {
      "url": "https://gameaccessibilityguidelines.com/full-list/",
      "note": "XAG 106 Implementation guidelines; GAG: Ensure screen reader support, including menus & installers"
    },
    {
      "url": "https://gameaccessibilityguidelines.com/ensure-screenreader-support-including-menus-installers/",
      "note": "XAG 106 Implementation guidelines; GAG: Ensure screen reader support, including menus & installers"
    }
  ]
}