accessibility-compliance

Implement WCAG 2.2 compliant interfaces with ARIA patterns and screen reader support.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/daniellelooo/velour --skill accessibility-compliance-daniellelooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-compliance
Source: https://github.com/daniellelooo/velour/tree/main/.agents/skills/accessibility-compliance
Command: npx skills add https://github.com/daniellelooo/velour --skill accessibility-compliance-daniellelooo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures your digital interfaces are usable by everyone, including people with disabilities, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • WCAG Compliance: Implement guidelines like WCAG 2.2 AA/AAA for perceivable, operable, understandable, and robust experiences.
  • Assistive Technology Support: Ensure compatibility with screen readers, keyboard navigation, and other assistive technologies.
  • Use Case: You are developing a new web application and need to ensure it meets Level AA accessibility standards, including proper ARIA implementation, keyboard navigation, and screen reader compatibility.

Quick Start

Use the accessibility-compliance skill to audit the accessibility of the provided webpage.

Frequently Asked Questions about accessibility-compliance

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

FAQPage Schema
How do I audit a web application for WCAG 2.2 compliance?

You can audit a web application for WCAG 2.2 compliance by evaluating the interface against perceivable, operable, understandable, and robust guidelines, focusing on mobile accessibility and assistive technology compatibility.

What is the best way to implement ARIA patterns for screen reader compatibility?

The best way to implement ARIA patterns for screen reader compatibility involves applying Web Content Accessibility Guidelines to ensure assistive technologies accurately perceive and navigate interactive interface elements.

How do I ensure keyboard navigation meets Level AA accessibility standards?

To ensure keyboard navigation meets Level AA accessibility standards, build operable interfaces where all interactive functionality is accessible sequentially via keyboard input without requiring a mouse.

Does this approach address mobile accessibility and inclusive design patterns?

Yes, this approach addresses mobile accessibility and inclusive design patterns by implementing WCAG 2.2 compliant interfaces that ensure usable, robust experiences across diverse mobile devices and assistive technologies.

When do I need to implement inclusive design patterns for assistive technology support?

You need to implement inclusive design patterns for assistive technology support when developing web applications to guarantee digital interfaces are fully operable and perceivable by people with disabilities.