accessibility-ux

Apply WCAG 2.2 AA accessibility patterns to Power Platform UI components.

46|6|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/korchard333/claude-power-platform-community --skill accessibility-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-ux
Source: https://github.com/korchard333/claude-power-platform-community/tree/main/.claude/skills/accessibility-ux
Command: npx skills add https://github.com/korchard333/claude-power-platform-community --skill accessibility-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility gaps in Power Platform UI lead to barriers for users with disabilities. This skill provides guidelines and patterns to achieve WCAG 2.2 AA compliance across Code Apps, Canvas Apps, and PCF controls.

Core Features & Use Cases

  • Auditing UI components for keyboard navigation, focus management, color contrast, and screen reader compatibility.
  • Designing accessible layouts and components using Fluent UI tokens and responsive patterns.
  • Use Cases: ensures forms, loading/empty/error states, and dynamic content remain accessible in enterprise apps.

Quick Start

Use the accessibility-ux skill to audit a UI page for WCAG compliance.

Frequently Asked Questions about accessibility-ux

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

FAQPage Schema
How do I make Power Platform Canvas Apps meet WCAG 2.2 AA accessibility standards?

To achieve WCAG 2.2 AA accessibility in Power Platform Canvas Apps, apply targeted UI patterns for keyboard navigation, focus management, and screen reader compatibility across layouts, forms, and loading or error states.

What is the best way to audit UI components for screen reader compatibility in Code Apps?

Auditing screen reader compatibility in Code Apps involves checking UI components against WCAG 2.2 AA patterns, ensuring forms, dynamic content, and empty states are properly announced using Fluent UI V9 accessibility guidance.

Can I use this approach to fix keyboard navigation and focus management in PCF controls?

Yes, you can fix keyboard navigation and focus management in PCF controls by applying inclusive design patterns and WCAG 2.2 AA rules to eliminate accessibility gaps within custom components.

How do I design accessible layouts and error states for enterprise Power Platform applications?

Design accessible layouts and error states by utilizing Fluent UI tokens and responsive patterns, ensuring dynamic content, forms, and empty states remain fully accessible and meet WCAG 2.2 AA compliance.

Does Power Platform support Fluent UI V9 accessibility patterns for custom components?

Power Platform custom components support Fluent UI V9 accessibility patterns by referencing its guidance to build robust, rule-based implementations that pass WCAG 2.2 AA accessibility checks.