skills.rest
dodyg
dodygCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dotnet-accessibility

Implement accessibility features for .NET UI applications.

Updated Aug 16, 2025
Search Tags:#ui#accessibility#dotnet#semanticmarkup#keyboardnavigation#colorcontrast
One-click install
npx skills add https://github.com/dodyg/blue-nile-pds --skill dotnet-accessibility-dodyg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-accessibility
Source: https://github.com/dodyg/blue-nile-pds/tree/main/.agents/skills/dotnet-accessibility
Command: npx skills add https://github.com/dodyg/blue-nile-pds --skill dotnet-accessibility-dodyg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many .NET applications lack built‑in accessibility support, making them difficult or impossible for people using screen readers, keyboard navigation, or high‑contrast settings. This skill provides concrete guidance to bridge that gap across multiple UI frameworks.

Core Features & Use Cases

  • Cross‑platform principles: Semantic markup, logical tab order, focus management, and WCAG‑compliant color contrast that apply to any .NET UI.
  • Framework‑specific guidance: Detailed patterns for Blazor (ARIA), MAUI (SemanticProperties), WinUI (AutomationProperties), plus references for WPF, Uno Platform, and terminal UI frameworks.
  • Testing & validation: Recommended tools such as Accessibility Insights, axe‑core, and platform‑specific inspectors, plus automated test snippets for CI pipelines.

Quick Start

Use the dotnet-accessibility skill to evaluate and improve accessibility of a Blazor app by applying ARIA attributes and testing keyboard navigation.

Frequently Asked Questions about dotnet-accessibility

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

FAQPage Schema
How do I implement accessibility features in a Blazor application?▼

To implement accessibility in Blazor, apply ARIA attributes for semantic markup, ensure logical keyboard navigation, and use testing tools like axe-core to validate WCAG color contrast compliance.

What is the best way to add screen reader support to .NET MAUI apps?▼

Screen reader support in .NET MAUI is added by utilizing the SemanticProperties API to provide accessible names and roles, ensuring UI elements are properly announced to assistive technologies.

Does WinUI support semantic markup and focus management for accessible UIs?▼

Yes, WinUI supports accessible UIs by using AutomationProperties to apply semantic markup and manage focus, ensuring keyboard navigation and screen reader compatibility across .NET 8+ environments.

Can I automate accessibility testing for .NET UI applications in my CI pipeline?▼

You can automate accessibility testing in CI pipelines by integrating axe-core and Accessibility Insights, executing automated test snippets to validate WCAG color contrast and keyboard navigation.

How do I manage keyboard navigation and focus across multiple .NET frameworks?▼

Managing keyboard navigation requires establishing a logical tab order and applying focus management techniques using framework-specific APIs like AutomationProperties or SemanticProperties across Blazor and MAUI.

Related Skills

Explore More Software Engineering Skills→
AarononthewebAaronontheweb
1.1k

dotnet-local-tools

Manage per-repo .NET CLI tools via dotnet-tools.json manifests.

Community
Intermediate
fugazifugazi
215

accessibility-selenium-testing

Automate WCAG compliance scans by integrating axe-core with Selenium WebDriver.

Community
Advanced
wshaddixwshaddix
71

dotnet-accessibility

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

Community
Advanced
pascalvanderheidenpascalvanderheiden
4

dotnet-ui

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

Community
Advanced