AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

winui-app

Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.

Original source
openai
License
Apache-2.0
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--winui-app at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 18

references/accessibility-input-and-localization.md


title: Accessibility, Input, and Localization priority: HIGH tags: accessibility, keyboard, narrator, automation, localization, high-contrast sources:

  • https://learn.microsoft.com/windows/apps/design/accessibility/accessibility
  • https://learn.microsoft.com/windows/apps/design/accessibility/keyboard-accessibility
  • https://learn.microsoft.com/windows/apps/design/accessibility/high-contrast-themes
  • https://learn.microsoft.com/windows/apps/design/globalizing/globalizing-portal
  • https://github.com/microsoft/WinUI-Gallery

What This Reference Is For

Use this file for keyboard accessibility, Narrator support, automation properties, input parity, high contrast, and localization-ready UI.

Prefer

  • Accessible names, help text, and landmarks for meaningful UI elements.
  • Full keyboard reachability for the main workflow.
  • High-contrast-safe visuals.
  • Localizable strings and layouts that tolerate growth.
  • Equal support for mouse, touch, pen, and keyboard where the platform expects it.

Avoid

  • Icon-only interactions without accessible naming.
  • Focus traps, hidden tab stops, or keyboard-only dead ends.
  • Hard-coded strings in XAML or code-behind that block localization.
  • Text layouts that collapse when strings expand.

Guidance

  • Use automation properties intentionally.
  • Preserve visible focus and logical tab order.
  • Verify context menus, flyouts, and dialogs by keyboard as well as mouse.
  • Respect text scaling, contrast changes, and RTL where relevant.
  • Keep touch targets and spacing usable on both mouse and touch hardware.

WinUI Gallery Anchors

  • Accessibility-related control samples
  • Automation helper patterns in shell code
  • Standard WinUI controls that already expose useful accessibility behavior

Review Checklist

  • Can a keyboard-only user complete the task?
  • Does Narrator have enough information to describe the important UI?
  • Does the experience stay legible in high contrast?
  • Are strings and layout ready for localization and RTL growth?