skills.rest
wshaddix
wshaddixCOMMUNITY
Explore all skills by this author →
Website𝕏@wshaddixGitHub

dotnet-accessibility

Guide accessible UI development across .NET frameworks with semantic properties.

71|10|Updated Feb 11, 2026
Search Tags:#accessibility#wcag#.net#blazor#maui#winui#assistive technology
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-accessibility-wshaddix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-accessibility
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-accessibility
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-accessibility-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers build user interfaces for .NET applications that are usable by everyone, including people with disabilities, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • Cross-Platform Guidance: Provides accessibility patterns for Blazor, MAUI, WinUI, WPF, and Uno Platform.
  • Semantic Markup & Keyboard Navigation: Ensures UI elements are understandable and operable via assistive technologies like screen readers and keyboards.
  • Testing & Compliance: Offers testing tools and references to WCAG standards for validation.
  • Use Case: A developer building a new MAUI app can use this skill to learn how to correctly implement SemanticProperties for all interactive elements, ensuring screen readers announce them accurately and users can navigate with a keyboard.

Quick Start

Use the dotnet-accessibility skill to learn how to implement keyboard navigation for a Blazor component.

Frequently Asked Questions about dotnet-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement keyboard navigation and focus management in Blazor components?▼

Implement keyboard navigation in Blazor by using semantic markup and ARIA attributes to ensure interactive elements are operable via keyboard and announced accurately by screen readers.

How do I use SemanticProperties to make MAUI controls accessible to screen readers?▼

Use SemanticProperties in MAUI to set semantic descriptions, headings, and hints on UI elements, ensuring screen readers can accurately announce custom controls and users can navigate effectively.

Does this guidance cover AutomationProperties for WPF and WinUI accessibility?▼

Yes, this guidance covers framework-specific APIs including AutomationProperties for WPF and WinUI, helping you set accessibility properties and automate UI testing across .NET applications.

What is the best way to test .NET user interfaces for WCAG compliance?▼

The best way to test .NET UIs for WCAG compliance involves using specialized testing methodologies and tools to validate color contrast, keyboard operability, and screen reader functionality across platforms.

How do I add ARIA attributes and live regions in Blazor for dynamic content updates?▼

Add ARIA attributes and live regions in Blazor to announce dynamic content updates to assistive technologies, ensuring screen readers automatically read changes without requiring manual focus shifts.

Can I build accessible custom controls across Uno Platform and .NET UI frameworks?▼

Yes, you can build accessible custom controls across Uno Platform, Blazor, and MAUI by applying cross-platform accessibility principles and framework-specific semantic APIs to expose control behavior to assistive technologies.

Related Skills

Explore More Software Engineering Skills→
pascalvanderheidenpascalvanderheiden
4

dotnet-ui

Guide .NET UI development across Blazor, MAUI, Uno Platform, WPF, and WinUI 3.

Community
Advanced
zenobi-uszenobi-us
68

accessibility-tester

Audit digital interfaces for WCAG 2.1 compliance and accessibility gaps.

Official
Advanced
belokonmbelokonm
8

frontend-ui-ux-engineer

Transform basic React components into polished interfaces with typography, color, motion, and accessibility.

Community
Advanced
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced