maui-accessibility

Guide MAUI app accessibility with SemanticProperties and heading semantics.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/snailb1007/snail-codex-skills --skill maui-accessibility-snailb1007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maui-accessibility
Source: https://github.com/snailb1007/snail-codex-skills/tree/main/skills/maui-accessibility
Command: npx skills add https://github.com/snailb1007/snail-codex-skills --skill maui-accessibility-snailb1007

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers overcome accessibility gaps in .NET MAUI apps by providing guidelines and best practices for screen reader compatibility, semantic naming, and platform-specific behavior.

Core Features & Use Cases

  • SemanticProperties usage and heading level guidance for MAUI controls to ensure meaningful screen reader output.
  • Accessibility checklist covering images, labels, descriptions, placeholders, focus management, and dynamic content announcements.
  • Use Case: Validate cross-platform accessibility on Android TalkBack, iOS VoiceOver, and Windows Narrator with practical examples and a reusable pattern.

Quick Start

Identify UI elements and apply SemanticProperties, heading levels, and accessibility attributes to enable screen readers.

Frequently Asked Questions about maui-accessibility

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

FAQPage Schema
How do I make MAUI apps accessible for screen readers?

Apply SemanticProperties to MAUI controls to provide semantic names, set heading levels, and manage focus. This ensures screen readers properly interpret and announce your app's interface elements.

What are SemanticProperties in .NET MAUI and when do I need them?

SemanticProperties in .NET MAUI are attributes that define how screen readers interpret UI elements. You need them when building cross-platform apps to provide descriptive labels, heading semantics, and hints for accessibility tools like TalkBack and VoiceOver.

How do I set heading levels for MAUI controls to work with screen readers?

Set heading levels using SemanticProperties to define heading semantics for MAUI controls. This enables screen readers to announce structural hierarchy, helping users navigate your app's content sections effectively.

Does MAUI accessibility support work across Android TalkBack, iOS VoiceOver, and Windows Narrator?

MAUI accessibility supports cross-platform screen readers including Android TalkBack, iOS VoiceOver, and Windows Narrator. The Skill provides practical rules and a verification checklist to validate UI semantics and platform-specific accessibility behavior across these platforms.

How do I verify MAUI app accessibility for dynamic content and focus management?

Verify MAUI app accessibility using a checklist covering dynamic content announcements, focus management, images, labels, and placeholders. This validates screen readers correctly announce UI updates and manage focus transitions.

Why does the screen reader skip elements in my MAUI app?

Screen readers skip MAUI elements when SemanticProperties are missing or incorrectly applied. Ensure UI controls have semantic names, proper heading levels, and accessibility attributes so screen readers can identify and announce them.