Merge pull request #6598 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-08 05:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -1500,11 +1500,6 @@
       "redirect_url": "/windows/uwp/design/accessibility/accessibility-overview",
       "redirect_document_id": false
     },
-    {
-      "source_path": "hub/apps/design/accessibility/accessibility.md",
-      "redirect_url": "/windows/uwp/design/accessibility/accessibility-overview",
-      "redirect_document_id": false
-    },
     {
       "source_path": "uwp/accessibility/accessible-text-requirements.md",
       "redirect_url": "/windows/uwp/design/accessibility/accessible-text-requirements",
@@ -11082,17 +11077,17 @@
     },
     {
       "source_path": "hub/apps/how-tos/chatgpt-openai-winui3.md",
-      "redirect_url": "/windows/apps/how-tos/github-copilot-winui-vs",
+      "redirect_url": "/windows/apps/how-tos/ai-build",
       "redirect_document_id": false
     },
     {
       "source_path": "hub/apps/how-tos/copilot-chat-winui3.md",
-      "redirect_url": "/windows/apps/how-tos/github-copilot-winui-vs",
+      "redirect_url": "/windows/apps/how-tos/ai-build",
       "redirect_document_id": false
     },
     {
       "source_path": "hub/apps/how-tos/dall-e-winui3.md",
-      "redirect_url": "/windows/apps/how-tos/github-copilot-winui-vs",
+      "redirect_url": "/windows/apps/how-tos/ai-build",
       "redirect_document_id": false
     },
     {
@@ -11410,6 +11405,26 @@
       "redirect_url": "/windows/apps/dev-tools/visual-studio",
       "redirect_document_id": false
     },
+    {
+      "source_path": "hub/apps/design/accessibility/accessibility.md",
+      "redirect_url": "/windows/apps/design/accessibility/accessibility-overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/accessibility/practices-to-avoid.md",
+      "redirect_url": "/windows/apps/design/accessibility/accessibility-overview#practices-to-avoid",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/design/accessibility/developing-inclusive-windows-apps.md",
+      "redirect_url": "/windows/apps/develop/accessibility",
+      "redirect_document_id": false
+    },
+    {      
+      "source_path": "hub/apps/package-and-deploy/choose-packaging-model.md",
+      "redirect_url": "/windows/apps/package-and-deploy/packaging/",
+      "redirect_document_id": false
+    },
     {
       "source_path": "hub/apps/design/globalizing/use-patterns-to-format-dates-and-times.md",
       "redirect_url": "/windows/apps/design/globalizing/use-global-ready-formats#use-templates-and-patterns-for-advanced-datetime-formatting",
@@ -11479,6 +11494,36 @@
       "source_path": "uwp/files/fast-file-properties.md",
       "redirect_url": "/windows/apps/develop/files/fast-file-properties",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/desktop/modernize/modernize-wpf-tutorial.md",
+      "redirect_url": "/windows/apps/desktop/modernize/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/desktop/modernize/modernize-wpf-tutorial-1.md",
+      "redirect_url": "/windows/apps/desktop/modernize/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/desktop/modernize/modernize-wpf-tutorial-2.md",
+      "redirect_url": "/windows/apps/desktop/modernize/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/desktop/modernize/modernize-wpf-tutorial-3.md",
+      "redirect_url": "/windows/apps/desktop/modernize/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/desktop/modernize/modernize-wpf-tutorial-4.md",
+      "redirect_url": "/windows/apps/desktop/modernize/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "hub/apps/desktop/modernize/modernize-wpf-tutorial-5.md",
+      "redirect_url": "/windows/apps/desktop/modernize/",
+      "redirect_document_id": false
     }
   ]
 }

hub/apps/design/accessibility/accessibility-checklist.md

@@ -12,67 +12,65 @@ ms.localizationpriority: medium
 
 # Accessibility checklist
 
-This topic provides recommendations for making your Windows app accessible and discoverable to customers looking for accessible apps in the Microsoft Store.
+This article provides recommendations for making your Windows app accessible and discoverable to customers looking for accessible apps in the Microsoft Store. Use the following recommendations during design, implementation, and testing. Together, they cover core accessibility expectations for keyboard use, readable content, assistive technology compatibility, and Microsoft Store discoverability.
 
-> [!NOTE]
-> This guidance is written for WinUI 3 / Windows App SDK apps. If you are maintaining a legacy UWP app, equivalent APIs are available in the `Windows.UI.Xaml` namespaces.
+## 1. Set accessible names and descriptions
 
-Use the following recommendations during design, implementation, and testing. Together, they cover core accessibility expectations for keyboard use, readable content, assistive technology compatibility, and Microsoft Store discoverability.
+Set the accessible name (required) and description (optional) for content and interactive UI elements in your app.
 
-1. Set the accessible name (required) and description (optional) for content and interactive UI elements in your app.
+An accessible name is a short, descriptive text string that a screen reader uses to announce a UI element. Some UI elements such as [TextBlock](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.textblock) and [TextBox](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.textbox) promote their text content as the default accessible name; see [Name from inner text](basic-accessibility-information.md#name-from-inner-text).
 
-    An accessible name is a short, descriptive text string that a screen reader uses to announce a UI element. Some UI elements such as [TextBlock](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.textblock) and [TextBox](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.textbox) promote their text content as the default accessible name; see [Name from inner text](basic-accessibility-information.md#name-from-inner-text).
+You should set the accessible name explicitly for images or other controls that do not promote inner text content as an implicit accessible name. You should use labels for form elements so that the label text can be used as a [LabeledBy](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.automation.automationproperties.labeledby) target in the Microsoft UI Automation model for correlating labels and inputs. If you want to provide more UI guidance for users than is typically included in the accessible name, accessible descriptions and tooltips help users understand the UI.
 
-    You should set the accessible name explicitly for images or other controls that do not promote inner text content as an implicit accessible name. You should use labels for form elements so that the label text can be used as a [LabeledBy](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.automation.automationproperties.labeledby) target in the Microsoft UI Automation model for correlating labels and inputs. If you want to provide more UI guidance for users than is typically included in the accessible name, accessible descriptions and tooltips help users understand the UI.
+For more info, see [Accessible name](basic-accessibility-information.md#accessible-name) and [Accessible description](basic-accessibility-information.md).
 
-    For more info, see [Accessible name](basic-accessibility-information.md#accessible-name) and [Accessible description](basic-accessibility-information.md).
+## 2. Implement keyboard accessibility
 
-2. Implement keyboard accessibility:
+- Test the default tab index order for a UI. Adjust the tab index order if necessary, which may require enabling or disabling certain controls, or changing the default values of [TabIndex](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.tabindex) on some of the UI elements.
+- Use controls that support arrow-key navigation for composite elements. For default controls, the arrow-key navigation is typically already implemented.
+- Use controls that support keyboard activation. For default controls, particularly those that support the UI Automation [Invoke](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.automation.provider.iinvokeprovider.invoke) pattern, keyboard activation is typically available; check the documentation for that control.
+- Set access keys or implement accelerator keys for specific parts of the UI that support interaction.
+- For any custom controls that you use in your UI, verify that you have implemented these controls with correct [AutomationPeer](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.automation.peers.automationpeer) support for activation, and defined overrides for key handling as needed to support activation, traversal and access or accelerator keys.
 
-    - Test the default tab index order for a UI. Adjust the tab index order if necessary, which may require enabling or disabling certain controls, or changing the default values of [TabIndex](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.tabindex) on some of the UI elements.
-    - Use controls that support arrow-key navigation for composite elements. For default controls, the arrow-key navigation is typically already implemented.
-    - Use controls that support keyboard activation. For default controls, particularly those that support the UI Automation [Invoke](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.automation.provider.iinvokeprovider.invoke) pattern, keyboard activation is typically available; check the documentation for that control.
-    - Set access keys or implement accelerator keys for specific parts of the UI that support interaction.
-    - For any custom controls that you use in your UI, verify that you have implemented these controls with correct [AutomationPeer](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.automation.peers.automationpeer) support for activation, and defined overrides for key handling as needed to support activation, traversal and access or accelerator keys.
+For more info, see [Keyboard interactions](../input/keyboard-interactions.md).
 
-    For more info, see [Keyboard interactions](../input/keyboard-interactions.md).
+## 3. Ensure text is a readable size
 
-3. Ensure text is a readable size
+Windows includes various accessibility tools and settings that users can take advantage of and adjust to their own needs and preferences for reading text. These include:
 
-    - Windows includes various accessibility tools and settings that users can take advantage of and adjust to their own needs and preferences for reading text. These include:
-        - The Magnifier tool, which enlarges a selected area of the UI. You should ensure the layout of text in your app doesn't make it difficult to use Magnifier for reading.
-        - Global scale and resolution settings in **Settings->System->Display->Scale and layout**. Exactly which sizing options are available can vary as this depends on the capabilities of the display device.
-        - Text size settings in **Settings->Ease of access->Display**. Adjust the **Make text bigger*- setting to specify only the size of text in supporting controls across all applications and screens (XAML text controls support text scaling without additional customization in standard scenarios).
-        > [!NOTE]
-        > The **Make everything bigger*- setting lets a user specify their preferred size for text and apps in general on their primary screen only.
+* The Magnifier tool, which enlarges a selected area of the UI. You should ensure the layout of text in your app doesn\'t make it difficult to use Magnifier for reading.
+* Global scale and resolution settings in **Settings->System->Display->Scale and layout**. Exactly which sizing options are available can vary as this depends on the capabilities of the display device.
+* Text size settings in **Settings->Ease of access->Display**. Adjust the **Make text bigger** setting to specify only the size of text in supporting controls across all applications and screens (all WinUI text controls support the text scaling experience without any customization or templating).
 
-4. Visually verify your UI to ensure that the text contrast is adequate, elements render correctly in the high-contrast themes, and colors are used correctly.
+## 4. Verify color and contrast
 
-    - Use a color analyzer tool to verify that the visual text contrast ratio is at least 4.5:1.
-    - Switch to a high contrast theme and verify that the UI for your app is readable and usable.
-    - Ensure that your UI doesn't use color as the only way to convey information.
+Visually verify your UI to ensure that the text contrast is adequate, elements render correctly in the high-contrast themes, and colors are used correctly.
 
-    For more info, see [High-contrast themes](high-contrast-themes.md) and [Accessible text requirements](accessible-text-requirements.md).
+* Use a color analyzer tool to verify that the visual text contrast ratio is at least 4.5:1.
+* Switch to a high contrast theme and verify that the UI for your app is readable and usable.
+* Ensure that your UI doesn\'t use color as the only way to convey information.
 
-5. Run accessibility tools, address reported issues, and verify the screen reading experience.
+For more info, see [High-contrast themes](high-contrast-themes.md) and [Accessible text requirements](accessible-text-requirements.md).
 
-    Use tools such as [Inspect](/windows/desktop/WinAuto/inspect-objects) to verify programmatic access, run diagnostic tools such as [AccChecker](/windows/desktop/WinAuto/ui-accessibility-checker) to discover common errors, and verify the screen reading experience with Narrator.
+## 5. Run accessibility tools and verify screen reading
 
-    For more info, see [Accessibility testing](accessibility-testing.md).
+Use tools such as [Inspect](/windows/desktop/WinAuto/inspect-objects) to verify programmatic access, run diagnostic tools such as [AccChecker](/windows/desktop/WinAuto/ui-accessibility-checker) to discover common errors, and verify the screen reading experience with Narrator.
 
-6. Add automated accessibility regression checks to your CI pipeline.
+For more info, see [Accessibility testing](accessibility-testing.md).
 
-    Run automated checks for critical screens and flows in pull requests and continuous integration. Configure your pipeline to block merges or releases when critical accessibility regressions are detected.
 
-7. Make sure your app manifest settings follow accessibility guidelines, see [Security Considerations for Assistive Technologies](/windows/win32/winauto/uiauto-securityoverview).
+## 6. Add automated accessibility regression checks to your CI pipeline.
 
-8. Declare your app as accessible in the Microsoft Store.
+Run automated checks for critical screens and flows in pull requests and continuous integration. Configure your pipeline to block merges or releases when critical accessibility regressions are detected.
 
-    If you implemented the baseline accessibility support, declaring your app as accessible in the Microsoft Store can help reach more customers and potentially improve ratings.
+## 7. Verify app manifest settings
+Make sure your app manifest settings follow accessibility guidelines, see [Security Considerations for Assistive Technologies](/windows/win32/winauto/uiauto-securityoverview).
 
-    For more info, see [Accessibility in the Store](accessibility-in-the-store.md).
+## 8. Declare your app as accessible in the Microsoft Store.
 
-## Related topics  
+If you implemented the baseline accessibility support, declaring your app as accessible in the Microsoft Store can help reach more customers and potentially improve ratings. See [Accesibility in the Store](accessibility-in-the-store.md)
+
+## Related topics
 
 - [Accessible text requirements](accessible-text-requirements.md)
 - [Text scaling](../input/text-scaling.md)

hub/apps/design/accessibility/accessibility-overview.md

@@ -62,7 +62,7 @@ There are several other automation properties available (including the keyboard
 
 Building keyboard accessibility (for traditional, modified, or keyboard emulation hardware) into your app, helps users who are blind, have low vision, or have motor control issues, to navigate through and use the full functionality of your app. It also lets users without disabilities choose the keyboard for navigation due to preference or efficiency.
 
-The basic XAML control model provides built-in keyboard support including tab navigation, text input, and control-specific support. The elements that serve as layout containers (such as panels) use the layout order to establish a default tab order and provide an accessible representation of the UI. [ListBox](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.listbox) and [GridView](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.gridview) controls provide built-in arrow-key navigation. [Button](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.button) controls handle the Spacebar or Enter keys for button activation.
+The basic XAML control model provides built-in keyboard support including tab navigation, text input, and control-specific support. The elements that serve as layout containers (such as panels) use the layout order to establish a default tab order and provide an accessible representation of the UI. [ListView](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.listview) and [GridView](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.gridview) controls provide built-in arrow-key navigation. [Button](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.button) controls handle the Spacebar or Enter keys for button activation.
 
 For more info about all the aspects of keyboard support, including tab order and key-based activation or navigation, see [Keyboard accessibility](keyboard-accessibility.md).
 

hub/apps/design/accessibility/accessibility-testing.md

@@ -164,4 +164,4 @@ Verify that only intended elements appear in each accessibility view and that re
 - [Practices to avoid](practices-to-avoid.md)
 - [UI Automation](/windows/desktop/WinAuto/entry-uiauto-win32)
 - [Accessibility in Windows](https://www.microsoft.com/accessibility/)
-- [Get started with Narrator](https://support.microsoft.com/help/22798/windows-10-complete-guide-to-narrator)
+- [Get started with Narrator](https://support.microsoft.com/help/22798/windows-10-complete-guide-to-narrator)

hub/apps/design/accessibility/accessible-text-requirements.md

@@ -118,6 +118,7 @@ You should then validate against Windows text-related accessibility settings, in
 - Magnifier, which enlarges part of the UI. Ensure layout and line wrapping remain readable under magnification.
 - Global scale and resolution settings in **Settings->System->Display->Scale and layout**. Available values vary by display hardware.
 - Text size settings in **Settings->Ease of access->Display**. **Make text bigger** scales text in supported controls across apps and screens (WinUI text controls support this by default).
+
 > [!NOTE]
 > The **Make everything bigger** setting lets a user specify their preferred size for text and apps in general on their primary screen only.
 

hub/apps/design/accessibility/basic-accessibility-information.md

@@ -130,4 +130,4 @@ Attached properties in [**AutomationProperties**](/windows/windows-app-sdk/api/w
 * [Accessibility overview](accessibility-overview.md)
 * [**AutomationProperties.Name**](/dotnet/api/system.windows.automation.automationproperties.name)
 * [XAML accessibility sample](https://github.com/microsoftarchive/msdn-code-gallery-microsoft/tree/411c271e537727d737a53fa2cbe99eaecac00cc0/Official%20Windows%20Platform%20Sample/XAML%20accessibility%20sample) (archived legacy sample)
-* [Accessibility testing](accessibility-testing.md)
+* [Accessibility testing](accessibility-testing.md)