Skip to main content
Accessibility feature tags let players filter game catalogs for the accessibility features they need. You declare them in Partner Center using the Accessibility feature in the Gaming Metadata module.
Current version: Accessibility Feature Tags v2.0.1 (published March 14, 2025).
There are two families of tags:
  • Accessible Games Initiative tags — 24 tags created by the Entertainment Software Association (ESA) and adopted across the industry.
  • XBOX Accessibility Feature Tags — 6 additional tags Microsoft created before the Accessible Games Initiative, which have no ESA equivalent. All previous XBOX tags that overlap with ESA tags have been renamed to align.

How tagging works

1

Check the criteria

Every tag has strict player-facing requirements. Confirm your game meets all requirements before declaring the tag.
2

Declare in Partner Center

Add tags via Accessibility in the Gaming Metadata module of your Catalog Listing.
3

Ship

Tags surface on the Microsoft Store product page. Players can filter by them.
4

Microsoft validates

After publication, Microsoft verifies that the game actually delivers the tagged features. Inaccurate tags will be flagged for removal by your Microsoft representative.
Only declare tags your game truly meets. Store auditing verifies them, and tags can be revoked if they don’t match the shipped experience.

Accessible Games Initiative tags (24)

Sourced from the Accessible Games Initiative. Each tag has a specific player-facing description, a goal, developer requirements, and Microsoft test criteria — refer to the source spec before declaring.

Auditory features

Gameplay features

Input features

Visual features

XBOX Accessibility Feature Tags (6)

Six additional tags with no Accessible Games Initiative equivalent.

Where to get the full criteria

Every tag ships with:
  • Player-facing description — what the player will see on the Store PDP.
  • Goal — the intended player outcome.
  • Developer-facing requirements — the minimum bar to declare the tag.
  • Tips and context — recommended practices beyond the minimum.
  • Microsoft test steps — the exact validation Microsoft runs post-publication.
  • Pass / fail examples — concrete scenarios.
Get the current specification from your Microsoft representative and cross-reference it against your build before declaring any tag.

Questions or unsure whether you qualify?

  • Cross-reference the XBOX Accessibility Guidelines — the XAGs are the underlying best practices; the tags describe player-facing outcomes.
  • Email xpaq@microsoft.com with XBOX Partner Accessibility questions.
  • Request a MGATS evaluation to validate tag readiness before you publish.

See also

Last modified on August 5, 2026