accessibility

Audit and remediate web interfaces for WCAG 2.1 accessibility barriers.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ricable/mcai --skill accessibility-ricable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/ricable/mcai/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/ricable/mcai --skill accessibility-ricable

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams find and fix web accessibility barriers that prevent people with disabilities from using content, forms, navigation, and interactive components effectively.

Core Features & Use Cases

  • WCAG 2.1 Guidance: Apply practical rules for perceivable, operable, understandable, and robust experiences.
  • Implementation Remediation: Improve alt text, labels, contrast, focus visibility, keyboard support, ARIA usage, and reduced-motion behavior.
  • Audit Support: Use the included reference material to review pages against common accessibility issues and prioritize fixes before release.
  • Use Case: A developer can use this Skill to audit a checkout form, identify missing labels and weak focus states, and rewrite the markup so it works with screen readers and keyboard-only users.

Quick Start

Ask the accessibility skill to review your page or component for WCAG 2.1 issues and suggest concrete markup and interaction fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I fix web accessibility barriers for keyboard navigation and screen readers?

Audit web interfaces against WCAG 2.1 to identify and fix accessibility barriers. Remediation includes improving keyboard operability, screen reader compatibility, valid HTML, ARIA correctness, focus visibility, and semantic markup for forms and navigation.

What is WCAG 2.1 compliance for web applications and when is it required?

WCAG 2.1 compliance ensures web interfaces are perceivable, operable, understandable, and robust. It is required when users with disabilities cannot effectively use content, forms, navigation, and interactive components due to accessibility barriers.

How do I audit a web form for missing labels and weak focus states?

Audit a web form by reviewing markup for missing labels and weak focus states. Remediation involves rewriting HTML and ARIA attributes to ensure keyboard operability, screen reader compatibility, and visible focus behavior for all interactive elements.

Does this approach support reduced-motion behavior and contrast fixes?

Yes, this approach supports reduced-motion behavior and contrast fixes. Remediation applies practical WCAG 2.1 rules to improve alt text, labels, contrast ratios, focus visibility, keyboard support, ARIA correctness, and reduced-motion behavior.

What is the best way to correct invalid ARIA attributes in semantic markup?

Correct invalid ARIA attributes by auditing semantic markup for ARIA correctness and valid HTML. Remediation aligns interactive components with WCAG 2.1 standards, ensuring keyboard operability and screen reader compatibility through proper ARIA implementation.