[UI/UX] (keyboard shortcuts) Correct localization guidance #5514

samantharamon · 2025-11-25T20:13:07Z

The localization JSON file only provides alternative keyboard shortcuts and strings for one additional locale.

learn-build-service-prod · 2025-11-25T20:14:35Z

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

learn-build-service-prod · 2025-11-25T20:15:16Z

Learn Build status updates of commit 2647470:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/design/keyboard-shortcuts.md	✅Succeeded	View

For more details, please refer to the build report.

Copilot

Pull request overview

This PR updates the keyboard shortcuts localization documentation to clarify that the localization JSON file only provides alternative keyboard shortcuts and strings for one additional locale, rather than supporting multiple locales.

Key changes:

Updated guidance text to reflect single additional locale support instead of multiple locales
Modified JSON examples to show a single locale configuration
Clarified the relationship between the shortcuts JSON file and localization resource file

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

docs/design/keyboard-shortcuts.md

Copilot · 2025-11-25T20:19:14Z

docs/design/keyboard-shortcuts.md

-                "value": "Afficher le volet de tâche pour add-in"
-              } 
+    "resources":{
+        "default": {


The localization resource file example shows "default" as the locale property, but the text in line 341 states it should configure "alternative keyboard shortcuts for one additional locale" with an "ll-cc" property (like "es-es"). The property should be "es-es" instead of "default" to match the guidance and show an actual locale-specific configuration.

Suggested change

"default": {

"es-es": {

learn-build-service-prod · 2025-11-25T20:24:09Z

Learn Build status updates of commit 2e8a60e:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/design/keyboard-shortcuts.md	✅Succeeded	View

For more details, please refer to the build report.

learn-build-service-prod · 2025-11-25T20:24:14Z

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

docs/design/keyboard-shortcuts.md

vilit1

Please double check the file included in the email.

learn-build-service-prod · 2026-01-05T22:14:56Z

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

learn-build-service-prod · 2026-01-05T22:15:04Z

Learn Build status updates of commit 87c24cc:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/design/keyboard-shortcuts.md	✅Succeeded	View

For more details, please refer to the build report.

docs/design/keyboard-shortcuts.md

Rick-Kirkham · 2026-01-06T00:14:06Z

docs/design/keyboard-shortcuts.md

- The tokens must have the format **${resource.*name-of-resource*}**. The resource name must match the applicable locale string specified in the localization resource file.
- Default strings *must be defined in the extended overrides file itself*. Default strings are used when the locale of the Microsoft 365 host application doesn't match any of the *ll-cc* properties in the resources file. Defining the default strings directly in the extended overrides file ensures that Microsoft 365 doesn't download the resource file when the locale of the Microsoft 365 application matches the default locale of the add-in (as specified in the manifest).
+- The tokens must have the format **${resource.*name-of-resource*}**. The resource name must match the applicable string specified in the shortcuts and localization resource files.
+- Default strings *must be defined in the shortcuts JSON file itself*. Default strings are used when the locale of the Microsoft 365 host application doesn't match the other *ll-cc* property in the localization resource file. Defining the default strings directly in the shortcuts file ensures that Microsoft 365 doesn't download the localization resource file when the locale of the Microsoft 365 application matches the default locale of the add-in (as specified in the manifest).


There could be more than one, couldn't there?

Suggested change

- Default strings *must be defined in the shortcuts JSON file itself*. Default strings are used when the locale of the Microsoft 365 host application doesn't match the other *ll-cc* property in the localization resource file. Defining the default strings directly in the shortcuts file ensures that Microsoft 365 doesn't download the localization resource file when the locale of the Microsoft 365 application matches the default locale of the add-in (as specified in the manifest).

- Default strings *must be defined in the shortcuts JSON file itself*. Default strings are used when the locale of the Microsoft 365 host application doesn't match the other *ll-cc* property in any of the localization resource files. Defining the default strings directly in the shortcuts file ensures that Microsoft 365 doesn't download the localization resource file when the locale of the Microsoft 365 application matches the default locale of the add-in (as specified in the manifest).

At the moment, only one other locale is supported.

Rick-Kirkham · 2026-01-06T00:22:04Z

docs/design/keyboard-shortcuts.md

 You may need to localize your custom keyboard shortcuts in the following scenarios.

- Your add-in supports multiple locales.
+- Your add-in supports another locale.


Suggested change

- Your add-in supports another locale.

- Your add-in supports other locales.

Co-authored-by: Rick Kirkham <[email protected]>

learn-build-service-prod · 2026-01-07T00:22:30Z

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

learn-build-service-prod · 2026-01-07T00:22:43Z

Learn Build status updates of commit 1b40c59:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/design/keyboard-shortcuts.md	✅Succeeded	View

For more details, please refer to the build report.

Correct localization guidance

2647470

samantharamon requested a review from Copilot November 25, 2025 20:17

Copilot started reviewing on behalf of samantharamon November 25, 2025 20:17 View session

Copilot finished reviewing on behalf of samantharamon November 25, 2025 20:18

Copilot AI reviewed Nov 25, 2025

View reviewed changes

Fix casing

2e8a60e

vilit1 approved these changes Jan 5, 2026

View reviewed changes

vilit1 reviewed Jan 5, 2026

View reviewed changes

docs/design/keyboard-shortcuts.md Outdated Show resolved Hide resolved

vilit1 suggested changes Jan 5, 2026

View reviewed changes

Apply feedback from review

87c24cc

samantharamon requested a review from vilit1 January 5, 2026 22:16

vilit1 approved these changes Jan 5, 2026

View reviewed changes

samantharamon requested a review from Rick-Kirkham January 5, 2026 23:33

Rick-Kirkham requested changes Jan 6, 2026

View reviewed changes

Update ms.date

1b40c59

Co-authored-by: Rick Kirkham <[email protected]>

Rick-Kirkham approved these changes Jan 7, 2026

View reviewed changes

samantharamon merged commit 0d56fd5 into main Jan 7, 2026
3 checks passed

samantharamon deleted the samramon-localization branch January 7, 2026 00:50

	- Your add-in supports another locale.
	- Your add-in supports other locales.

[UI/UX] (keyboard shortcuts) Correct localization guidance #5514

[UI/UX] (keyboard shortcuts) Correct localization guidance #5514

Uh oh!

Conversation

samantharamon commented Nov 25, 2025

Uh oh!

learn-build-service-prod bot commented Nov 25, 2025

PoliCheck Scan Report

✅ No issues found

More information about PoliCheck

Uh oh!

learn-build-service-prod bot commented Nov 25, 2025

✅ Validation status: passed

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI Nov 25, 2025

Choose a reason for hiding this comment

Uh oh!

learn-build-service-prod bot commented Nov 25, 2025

✅ Validation status: passed

Uh oh!

learn-build-service-prod bot commented Nov 25, 2025

PoliCheck Scan Report

✅ No issues found

More information about PoliCheck

Uh oh!

Uh oh!

vilit1 left a comment

Choose a reason for hiding this comment

Uh oh!

learn-build-service-prod bot commented Jan 5, 2026

PoliCheck Scan Report

✅ No issues found

More information about PoliCheck

Uh oh!

learn-build-service-prod bot commented Jan 5, 2026

✅ Validation status: passed

Uh oh!

Uh oh!

Rick-Kirkham Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

samantharamon Jan 7, 2026

Choose a reason for hiding this comment

Uh oh!

Rick-Kirkham Jan 6, 2026

Choose a reason for hiding this comment

Uh oh!

learn-build-service-prod bot commented Jan 7, 2026

PoliCheck Scan Report

✅ No issues found

More information about PoliCheck

Uh oh!

learn-build-service-prod bot commented Jan 7, 2026

✅ Validation status: passed

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants