skills.rest
yonetim258852
yonetim258852COMMUNITY
Explore all skills by this author →
GitHub

wcag-accessibility

Audit UI design and code for WCAG 2.2 AA conformance.

Updated May 24, 2026
Search Tags:#accessibility#a11y#wcag#contrast#keyboard-navigation#eu#en-301-549
One-click install
npx skills add https://github.com/yonetim258852/ozgur-os --skill wcag-accessibility-yonetim258852
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wcag-accessibility
Source: https://github.com/yonetim258852/ozgur-os/tree/main/.claude/skills/wcag-accessibility
Command: npx skills add https://github.com/yonetim258852/ozgur-os --skill wcag-accessibility-yonetim258852

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures user interfaces meet WCAG 2.2 Level AA requirements under the European Accessibility Act (EN 301 549), preventing inaccessible design decisions and reducing usability and legal risks.

Core Features & Use Cases

  • Guidance and checks for perceivable, operable, understandable, and robust UI across web and app platforms.
  • Covers critical WCAG topics such as color contrast, text alternatives, captions, keyboard navigation, focus visibility, and proper semantic HTML with ARIA where appropriate.
  • Use Case: designers, developers, and product teams audit and remediate accessibility issues during UI design, code reviews, and product launches to ensure EU-market readiness.

Quick Start

Audit your user interface for WCAG 2.2 AA conformance and implement fixes to meet EN 301 549 requirements.

Frequently Asked Questions about wcag-accessibility

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

FAQPage Schema
How do I audit my UI for WCAG 2.2 AA conformance?▼

To meet EN 301 549 requirements, apply WCAG 2.2 AA checks covering color contrast, text alternatives, captions, keyboard navigation, focus visibility, and proper semantic HTML with ARIA. This ensures EU-market readiness for your user interfaces.

What is WCAG 2.2 AA compliance needed for under the European Accessibility Act?▼

WCAG 2.2 AA compliance is required under the European Accessibility Act (EN 301 549) to prevent inaccessible design decisions and reduce usability and legal risks. It ensures user interfaces are accessible to all users in the EU market.

Can I use this to check keyboard navigation and color contrast in my app?▼

Yes, you can check keyboard navigation, focus visibility, and color contrast in your app. The audit covers critical WCAG topics including text alternatives, captions, and proper semantic HTML with ARIA where appropriate across web and app platforms.

What's the best way to remediate accessibility issues during a code review?▼

The best way to remediate accessibility issues during a code review is to audit semantic HTML and ARIA usage against WCAG 2.2 AA standards. This identifies non-compliant elements and provides guidance for implementing perceivable and operable UI fixes.

Why does my UI fail EN 301 549 requirements despite passing basic contrast checks?▼

Your UI may fail EN 301 549 requirements because WCAG 2.2 AA conformance extends beyond color contrast to include keyboard navigation, focus visibility, text alternatives, and semantic HTML. A comprehensive audit of perceivable, operable, understandable, and robust content is required.

Related Skills

Explore More Design & Creative Skills→
CENKSSSCENKSSS

accessibility-testing

Validate web application accessibility against WCAG 2.2 standards.

Community
Advanced
timsvoicetimsvoice

specimin-ui-accessibility

Audit and fix generated UI code for WCAG 2.1 AA compliance.

Community
Advanced
pixels-and-codepixels-and-code

Accessibility (a11y)

Provides WCAG 2.1 guidelines and code examples for web accessibility testing.

Official
Intermediate
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced