Microsoft made its Gaming for Everyone Product Inclusion Framework public on March 20, 2024, at Game Developers Conference 2024. It gives game teams four “Inclusive Growth Doorways” and 10 recommended actions for considering approachability, representation, globalization and accessibility throughout a game’s lifecycle. It is guidance—not an SDK, certification, legal standard or mandatory checklist.
What Microsoft released—and where to find it
The release is a set of planning and learning resources for game developers and the wider games industry, not a technical tool to install. The Product Inclusion Resource Hub provides the framework, downloadable documentation, examples, best practices, case studies and a Game Accessibility Workshop Toolkit. The hub lists downloads in English, French, German, Italian, Japanese, Korean, Brazilian Portuguese, Spanish and Simplified Chinese.
Microsoft announced the public release at GDC 2024 on March 20, 2024. Xbox says it had developed and used the framework internally since 2019; Microsoft’s Gaming for Everyone initiative began in 2015. The announcement describes the framework as a flexible guide to help teams make deliberate inclusion decisions, not a prescription for what every game must contain.
The goal is to give teams shared language and practical prompts for barriers that can arise from experience level, hardware, disability, safety, language, cultural relevance, representation and access to feedback. Microsoft presents inclusion as a way to broaden reach and deepen engagement; the release does not establish that using the framework guarantees commercial results.
#1 Best Overall
The four Inclusive Growth Doorways
The doorways are lenses for examining a product and its player journey. They can overlap, and a team’s priorities will depend on its audience, design and platforms.
Approachability: make it easier to enter and keep playing
Approachability is about helping new and experienced players feel welcome. The framework encourages more entryways and fewer unintended offramps: avoid assumptions about genre knowledge, unfamiliar controls, available time or hardware. A clear tutorial, revisitable practice, adjustable pacing and reversible early choices can help; safe multiplayer defaults and a straightforward way to leave unsuitable content can also matter.
Rank #2
Approachability is not simply making a game easy. It means examining where players can get confused, stuck or pushed out, then deciding which obstacles the design can remove without undermining the intended experience.
Representation: help players feel they belong
Representation spans creators, content and players: who helps make the game, whose stories and themes it includes, and whether players can see themselves and connect with meaningful experiences. It reaches beyond character art into dialogue, quests, worldbuilding, social systems, marketing and creator partnerships.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCharacter creation with meaningful variation in body type, hair, clothing, voice and gender expression is one possible approach, not a complete answer on its own. Consult people with relevant experience when handling sensitive material, and avoid treating one character, consultant or portrayal as representative of an entire community.
Globalization: make the experience locally relevant
Globalization goes beyond translating text. It asks whether the game’s language, technology and connectivity assumptions, financial access, identity-related choices, market expectations and communications make sense for intended regions. UI layouts need to accommodate translated text; hardware and connectivity requirements can affect who can play; regional marketing and store presentation may need local context.
Localization is one part of this work. A translated store page cannot compensate for systems, content or payment assumptions that do not fit a market.
Accessibility: enable people with disabilities to play and create
Microsoft calls for accessibility by design: identify disabled players’ needs early, build access into the game from the start and revisit it throughout development. The relevant systems may involve input and controls, vision, hearing, speech and communication, cognition, motion and camera behavior, reading load, timing, menus, online interaction, or platform and hardware compatibility.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Best Value
There is no single feature that makes a game accessible. Subtitles, remapping and color options can be useful, but they address different needs and do not replace broader design, testing or clear communication about what a game supports.
The 10 Product Inclusion Actions
The English framework names 10 actions. The questions below translate them into prompts a team can take into planning and reviews; they are not additional requirements imposed by Microsoft.
| Action | Doorway or scope | Practical development question |
|---|---|---|
| Design for Customer Safety & Trust | Approachability | How might player interactions create harm, and what reporting, blocking, privacy, moderation or communication controls are appropriate? |
| Create Entryways for New Users | Approachability | What prevents a new, returning or genre-inexperienced player from starting and learning? |
| Co-Create with Communities | Representation | Which players or communities should inform research, design and testing, and how will their input shape decisions? |
| Help Customers Feel Seen | Representation | Is representation respectful and meaningful across the experience, rather than limited to token presence? |
| Design for Our Global Customers | Globalization | What financial, technical, language or identity-related barriers could affect intended players? |
| Engage Local Markets | Globalization | What needs to change in local communication, marketing, support or presentation for the experience to feel relevant? |
| Make Products Accessible by Design from Day 1 | Accessibility | Which access needs must inform core systems, requirements and testing from early production? |
| Share Inclusive Features in Product & Marketing | Accessibility | Can players discover and assess relevant features before purchase and find them in the game? |
| Leverage Inclusive Listening Systems | All doorways | How will the team hear from players it might otherwise miss, and close the feedback loop? |
| Create Customized & Personalized Experiences | All doorways | Which clear, usable options let players adapt the experience to their needs? |
These prompts do not supply a moderation system, guarantee respectful representation or prescribe a feature list. For example, customization can help players adapt controls, subtitles, audio, timing, camera behavior or difficulty, but a crowded settings menu can itself be hard to use. Sensible defaults and understandable labels matter alongside choice.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How a studio can apply the framework during production
- Map the audience and player journey. Identify intended players, platforms and markets, then note where people encounter the game: discovery, purchase, setup, onboarding, play, multiplayer and support.
- Identify barriers before choosing solutions. Consider experience, disability, safety, language, connectivity, hardware and financial assumptions. Ask whose perspective is missing from the team’s current understanding.
- Select relevant doorways and actions. Use the framework as a set of lenses, not a demand to apply every action identically to every game. Some concerns may be central to a game’s mechanics or audience; others may need a different response.
- Turn priorities into owned work. Translate decisions into design requirements, user stories or review criteria, and assign responsibility. Consider accessibility in game pillars, UI wireframes, controls, engine and middleware choices, build reviews and testing—not only as a late audit.
- Involve players and specialists early and repeatedly. Use appropriate accessibility playtesting, user research, localization testing and cultural consultation. Community input should be connected to decisions and compensated where appropriate; it is not a substitute for professional design, research or QA.
- Check how features work and whether players can find them. Test in the context where they will be used, including menus, onboarding and platform constraints. Communicate supported features accurately in store pages, trailers, product descriptions, tutorials and support material.
- Listen after launch and iterate. Review support issues, playtest feedback, surveys, forums and other suitable channels. Track accessibility impact and show how feedback informs prioritization; collecting comments without a visible response can undermine trust.
What the framework does not establish
- It is not an SDK, engine plug-in or automated audit tool.
- It is not a certification, legal standard, platform compliance guarantee or proof that a game is accessible, inclusive or safe.
- Its 10 actions are not a universal checklist requiring every team to implement every possible feature.
- It does not replace testing with disabled players, accessibility expertise, localization QA, cultural consultation, platform requirements, safety operations or legal review where applicable.
Teams still need to make and test their own decisions. More options can increase interface complexity and QA work; deeper localization can add production and support costs; safety controls can create friction or false positives; and broad hardware targets may constrain performance or visual goals. These are design and production trade-offs to manage, not reasons to leave inclusion until late, when underlying systems may be harder to change.
Related Microsoft resources
The Product Inclusion Resource Hub also lists the Game Accessibility Workshop Toolkit for teams planning accessibility-focused workshops. Microsoft’s hub points developers to its Game Dev community and Product Inclusion channel at aka.ms/ProductInclusion. These resources can support planning and discussion; they do not replace professional testing or specialist input.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
