[develop] Fix: UWP→WinAppSDK migration — input & devices

[qiutongMS]

Summary

Fixes UWP→WinAppSDK migration issues on kbridge-owned develop pages by updating WinAppSDK API links, WinUI namespace references, and stale sample links.

Owner

kbridge (resolved via: docfx_file_metadata)

Root Causes

1. UWP→WinAppSDK migration: outdated UWP API links, WinUI namespace references, and archived sample links remained on input, accessibility, and globalization pages. (41 findings total; 36 addressed, 5 skipped after verification)

Changes

• 9 files modified across 9 pages
• Fix types: link-replace, namespace-replace, sample-replace

Affected pages

Page	File
Custom automation peers	hub/apps/design/accessibility/custom-automation-peers.md
Expose basic accessibility information	hub/apps/design/accessibility/basic-accessibility-information.md
Contrast themes	hub/apps/design/accessibility/high-contrast-themes.md
Keyboard accessibility	hub/apps/design/accessibility/keyboard-accessibility.md
Adjust layout and fonts, and support RTL	hub/apps/design/globalizing/adjust-layout-and-fonts--and-support-rtl.md
User profile and app manifest languages	hub/apps/design/globalizing/manage-language-and-region.md
Make your app localizable	hub/apps/design/globalizing/prepare-your-app-for-localization.md
Tailor your resources for language, scale, contrast, others	hub/apps/windows-app-sdk/mrtcore/tailor-resources-lang-scale-contrast.md
Tutorial: Build XAML templated controls	hub/apps/winui/winui3/xaml-templated-controls-winui-3.md

Skipped Findings

• Screen readers and hardware system buttons (hub/apps/design/accessibility/system-button-narration.md) — skipped 3 findings after verification. The page explicitly states WinUI 3 still consumes this API from Windows::UI::Input, and Microsoft Learn does not expose a Windows App SDK SystemButtonEventController page to replace the current UWP references.
• Accessible text requirements (hub/apps/design/accessibility/accessible-text-requirements.md) — skipped 2 findings after verification. Microsoft Learn does not expose a Microsoft.UI.Windowing.UISettings API page, so changing the sample from Windows.UI.ViewManagement.UISettings would introduce an invalid migration.

Cross-owner Dependencies

None.

Source

Generated by page-analyzer pipeline from fix-uwp-migration-kbridge-input-devices-1.md

[qiutongMS]

✅ Review Result: APPROVED

Summary

All changes successfully migrate UWP references to Windows App SDK. API links, namespaces, and sample links are technically correct and reachable. The PR is ready to merge.

Page Health Assessment

File	Overall Quality	Notes
basic-accessibility-information.md	✅ Good	Sample link updated correctly; page reads well
custom-automation-peers.md	✅ Good	API links migrated to WinAppSDK; terminology consistent
high-contrast-themes.md	⚠️ Minor note	All three sample links point to same file (intentional consolidation?)
keyboard-accessibility.md	✅ Good	Sample link updated; content coherent
adjust-layout-and-fonts--and-support-rtl.md	✅ Good	Namespace changes applied consistently across C#/C++/CX examples
manage-language-and-region.md	✅ Good	API link and sample link updated; prose-code alignment maintained
prepare-your-app-for-localization.md	✅ Good	Sample link updated
tailor-resources-lang-scale-contrast.md	✅ Good	FlowDirection API link updated
xaml-templated-controls-winui-3.md	✅ Good	DependencyProperty API links updated; namespace change in pch.h correct

Link Verification

• ✅ All new WinUI Gallery sample links return 200 OK
• ✅ All new Windows App SDK API links resolve correctly
• ✅ New WindowsAppSDK-Samples links return 200 OK

Technical Correctness

• ✅ Namespace migrations (Windows.UI.Xaml → Microsoft.UI.Xaml) are correct
• ✅ Code samples updated consistently across all language variants (C#, C++/WinRT, C++/CX)
• ✅ API link paths follow correct Windows App SDK pattern
• ✅ No new syntax errors introduced

Recommendation: Merge

---

Note: Formal approval blocked (cannot approve own PR). This is an informational review comment.