accessibility

YosrBennagra's avatarfrom YosrBennagra

Implement accessibility for the .NET 8 WPF widget host app. Use when improving keyboard navigation, screen reader support, focus states, and color contrast in XAML and styles.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 4, 2026⬇️1downloads
[Testing and QA]

When & Why to Use This Skill

This Claude skill provides comprehensive support for implementing and auditing accessibility in .NET 8 WPF applications. It focuses on making software inclusive by automating the integration of keyboard navigation, screen reader semantics, and high-contrast visual states within XAML and styles, ensuring compliance with modern accessibility standards.

Use Cases

  • Keyboard Navigation Optimization: Ensuring all interactive UI controls are fully reachable and functional using Tab, Enter, and Escape keys to support users without mouse access.
  • Screen Reader Enhancement: Implementing AutomationProperties.Name and HelpText in XAML to provide clear, descriptive labels for buttons and controls that lack visible text.
  • Visual Accessibility & Contrast: Refining focus visuals and color contrast ratios for both Light and Dark themes to ensure UI elements are distinguishable for users with visual impairments.
  • Accessibility Compliance Auditing: Validating WPF widgets against a strict 'Definition of Done' to ensure that information is never conveyed through color alone and that the interface works seamlessly with Windows Narrator.
nameaccessibility
descriptionImplement accessibility for the .NET 8 WPF widget host app. Use when improving keyboard navigation, screen reader support, focus states, and color contrast in XAML and styles.

Accessibility

Overview

Make the shell and widgets usable with keyboard navigation and assistive technologies.

Core areas

  • Keyboard navigation and focus order
  • Screen reader semantics
  • Color contrast and focus visuals

Definition of done (DoD)

  • All interactive controls are keyboard-accessible (Tab/Enter/Escape)
  • AutomationProperties.Name set on buttons/controls without visible text
  • Focus visuals visible in both Light and Dark themes
  • No reliance on color alone to convey information
  • Tested with Windows Narrator or similar screen reader

Workflow

  1. Validate tab order and keyboard interactions.
  2. Add automation properties for screen readers.
  3. Ensure focus visuals are visible and consistent.
  4. Check color contrast in Light/Dark themes.

Guidance

  • Use AutomationProperties.Name and HelpText where needed.
  • Avoid removing focus outlines without replacement.
  • Test with high contrast mode if possible.

References

  • references/keyboard.md for keyboard nav patterns.
  • references/screen-readers.md for automation properties.
  • references/color-contrast.md for contrast rules.