accessibility-standards

Guide WCAG 2.1 AA and 2.2 AA conformance with ARIA implementation rules.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/MayaDispeler/TheOrqestra --skill accessibility-standards-mayadispeler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-standards
Source: https://github.com/MayaDispeler/TheOrqestra/tree/main/skills/accessibility-standards
Command: npx skills add https://github.com/MayaDispeler/TheOrqestra --skill accessibility-standards-mayadispeler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides expert reference for digital accessibility, helping ensure WCAG conformance, ARIA usage, and inclusive design patterns.

Core Features & Use Cases

  • WCAG 2.1 AA and 2.2 AA Compliance: Ensures adherence to web accessibility standards.
  • ARIA and Inclusive Design: Offers guidance on implementing ARIA roles and properties, as well as inclusive design patterns.
  • Decision Rules: Provides rules for determining correct ARIA implementation and HTML usage.
  • Common Mistakes and Fixes: Identifies common accessibility pitfalls and offers solutions.

Quick Start

Use the accessibility-standards skill to check a website for WCAG 2.1 AA conformance.

Frequently Asked Questions about accessibility-standards

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

FAQPage Schema
Does this accessibility guidance cover inclusive design patterns for web developers?

Yes, this accessibility guidance covers inclusive design patterns for web developers, offering specific rules for ARIA implementation, WCAG 2.1 AA conformance, and resolving common digital accessibility errors.

How do I check my website for WCAG 2.1 AA conformance?

Check website WCAG 2.1 AA conformance by evaluating HTML structure against accessibility standards, implementing correct ARIA roles, and applying inclusive design patterns to resolve common compliance mistakes.

When do I need ARIA roles in my web application?

You need ARIA roles in your web application when standard HTML elements cannot convey semantic meaning to assistive technologies, requiring decision rules to determine correct ARIA implementation for digital accessibility.

What is the difference between WCAG 2.1 AA and 2.2 AA compliance?

WCAG 2.2 AA compliance builds upon the 2.1 AA standards by adding new success criteria for digital accessibility, requiring updated inclusive design patterns and ARIA implementation to ensure full conformance.

How do I fix common digital accessibility mistakes in web development?

Fix common digital accessibility mistakes by identifying incorrect ARIA usage and non-inclusive design patterns, then applying WCAG 2.1 AA decision rules to implement correct HTML and ARIA properties.

Does this accessibility guidance cover inclusive design patterns for web developers?

Yes, this accessibility guidance covers inclusive design patterns for web developers, offering specific rules for ARIA implementation, WCAG 2.1 AA conformance, and resolving common digital accessibility errors.