skills.rest
svengraziani
svengrazianiCOMMUNITY
Explore all skills by this author →
Website𝕏@graziani_svenGitHub

wcag-2.2

Provide WCAG 2.2 accessibility guidelines and implementation rules for web developers.

2|Updated Feb 5, 2026
Search Tags:#accessibility#a11y#frontend#compliance#wcag#web-standards
One-click install
npx skills add https://github.com/svengraziani/ui-design --skill wcag-2-2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wcag-2.2
Source: https://github.com/svengraziani/ui-design/tree/main/.claude/skills/wcag-2.2
Command: npx skills add https://github.com/svengraziani/ui-design --skill wcag-2-2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of maintaining web accessibility compliance, helping developers identify and fix barriers that prevent users with disabilities from interacting with digital content.

Core Features & Use Cases

  • Actionable Implementation: Provides specific rules for contrast ratios, keyboard navigation, and focus management.
  • Compliance Coverage: Includes all Level A and AA criteria, plus new WCAG 2.2 requirements like target size minimums and focus appearance.
  • Use Case: When building a new interactive component, use this skill to verify that your focus states, ARIA roles, and keyboard event handlers meet current accessibility standards.

Quick Start

Apply the wcag-2.2 skill to review the current form implementation for accessibility compliance and suggest necessary improvements.

Frequently Asked Questions about wcag-2.2

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

FAQPage Schema
How do I make my web components compliant with WCAG 2.2 accessibility standards?▼

To achieve WCAG 2.2 compliance, verify interactive components meet Level A and AA criteria for contrast ratios, keyboard operability, semantic HTML, and ARIA state management for inclusive user experiences.

What are the new WCAG 2.2 requirements for frontend accessibility?▼

New WCAG 2.2 frontend accessibility requirements include target size minimums and focus appearance rules, expanding on existing Level A and AA criteria to ensure better operability for interactive web elements.

How do I fix keyboard navigation and focus management issues in HTML forms?▼

Fix keyboard navigation and focus management by implementing correct ARIA roles, semantic HTML, and specific event handlers to ensure digital interfaces meet current web accessibility standards.

What contrast ratios are needed for web accessibility compliance?▼

Web accessibility compliance requires specific contrast ratios between text and background, ensuring digital content is readable for users with visual impairments under Level A and AA criteria.

Does WCAG 2.2 Level AA compliance cover ARIA state management?▼

Yes, WCAG 2.2 Level AA compliance covers ARIA state management by providing specific implementation rules to ensure interactive components are properly accessible and operable.

Related Skills

Explore More Software Engineering Skills→
SAPSAP
294

a11y-audit

Audit UI components for WCAG AA accessibility compliance.

Official
Advanced
telum-aitelum-ai
2

visual-testing

Validate UI components against design tokens and WCAG AA standards.

Official
Advanced
ksciuskscius
2

web-accessibility

Enforce WCAG 2.1 AA accessibility requirements for web UI components.

Community
Intermediate
JosiahSiegelJosiahSiegel
51

tailwindcss-accessibility

Provide Tailwind CSS utility classes for WCAG 2.2 accessibility features.

Community
Intermediate