skills.rest
AGIBuild
AGIBuildCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-accessibility

Guide accessible .NET UI development across Blazor, MAUI, and WinUI.

10|Updated Jan 28, 2026
Search Tags:#accessibility#screen reader#wcag#.net#blazor#maui#winui
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-accessibility
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-accessibility
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-accessibility
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers build .NET applications with robust accessibility features, ensuring usability for all users, including those with disabilities.

Core Features & Use Cases

  • Cross-Platform Accessibility: Implements semantic markup, keyboard navigation, focus management, and color contrast across Blazor, MAUI, and WinUI.
  • Platform-Specific APIs: Details the use of ARIA for Blazor, SemanticProperties for MAUI, and AutomationProperties for WinUI.
  • Use Case: A developer building a cross-platform mobile app with MAUI can use this Skill to correctly implement SemanticProperties for all interactive elements, ensuring screen readers like VoiceOver and TalkBack can announce them accurately.

Quick Start

Use the dotnet-accessibility skill to implement semantic properties for a MAUI button.

Frequently Asked Questions about dotnet-accessibility

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

FAQPage Schema
How do I implement screen reader support for a MAUI button?▼

To implement screen reader support for a MAUI button, use the SemanticProperties API to set semantic descriptions, ensuring screen readers like VoiceOver and TalkBack announce interactive elements accurately.

What is the best way to add ARIA attributes in Blazor apps?▼

Adding ARIA attributes in Blazor apps involves applying standard ARIA attributes to HTML elements to provide semantic markup, which this Skill details alongside keyboard navigation and focus management techniques.

Does this Skill cover WCAG compliance for .NET UI frameworks?▼

Yes, this Skill covers WCAG compliance for .NET UI frameworks by providing testing tools and WCAG references to ensure your Blazor, MAUI, and WinUI applications meet accessibility standards.

How do I manage focus and keyboard navigation across Blazor, MAUI, and WinUI?▼

Managing focus and keyboard navigation across Blazor, MAUI, and WinUI requires using platform-specific APIs like ARIA, SemanticProperties, and AutomationProperties to build accessible user interfaces.

Can I use AutomationProperties for accessible WinUI development?▼

Yes, you can use AutomationProperties for accessible WinUI development to provide semantic markup and UI automation information, ensuring robust usability for users relying on assistive technologies.

What color contrast guidelines should I follow for accessible .NET applications?▼

Accessible .NET applications should follow color contrast guidelines referenced within this Skill to ensure visual elements meet WCAG compliance across Blazor, MAUI, and WinUI platforms.

Related Skills

Explore More Software Engineering Skills→
dodygdodyg

dotnet-accessibility

Implement accessibility features for .NET UI applications.

Community
Intermediate
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate
lexicalninjalexicalninja
2

accessibility-design-checker

Identify accessibility issues in UI designs, wireframes, and prototypes.

Community
Intermediate
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced