skills.rest
pepeccz
pepecczCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Audit websites for WCAG 2.2 accessibility gaps and generate remediation plans.

Updated Jan 7, 2026
Search Tags:#accessibility#a11y#WCAG#screen-reader#color-contrast#keyboard-navigation
One-click install
npx skills add https://github.com/pepeccz/msi-a --skill accessibility-pepeccz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/pepeccz/msi-a/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/pepeccz/msi-a --skill accessibility-pepeccz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Websites with accessibility gaps hinder users with disabilities. This skill provides guidelines and patterns to audit and improve WCAG 2.2 conformance.

Core Features & Use Cases

  • Accessibility guidelines: WCAG 2.2 reference, POUR principles.
  • Practical patterns: A11Y patterns and best practices for keyboard, color contrast, semantics, ARIA, and screen reader compatibility.
  • Use Case: Designers and developers performing quick audits on web pages, components, and live content to produce actionable remediation notes.

Quick Start

Audit a web page for WCAG 2.2 conformance and generate a remediation plan.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I check my website for WCAG 2.2 conformance?▼

To check website WCAG 2.2 conformance, audit pages and components for keyboard navigation, color contrast, HTML semantics, ARIA, and screen reader compatibility. This generates structured checks aligned with POUR principles and produces actionable remediation notes.

What is the best way to fix color contrast and keyboard navigation accessibility issues?▼

Fixing color contrast and keyboard navigation accessibility issues requires applying practical A11Y patterns during design reviews and development workflows. You identify specific gaps against WCAG guidelines and implement actionable remediation recommendations to ensure full screen reader compatibility.

Do I need ARIA attributes for screen reader compatibility on every component?▼

You do not need ARIA attributes for screen reader compatibility on every component. ARIA should only be applied when needed to supplement HTML semantics, following structured checks aligned with POUR principles to ensure proper keyboard navigation and accessible web content.

Can I use these accessibility guidelines for component-level design reviews?▼

Yes, you can use these accessibility guidelines for component-level design reviews. The structured checks evaluate keyboard navigation, color contrast, and HTML semantics across both full web pages and individual components, providing actionable remediation recommendations for designers and developers.

Why does my web content fail screen reader compatibility during accessibility audits?▼

Web content fails screen reader compatibility during accessibility audits due to gaps in HTML semantics, missing ARIA attributes, or poor keyboard navigation. Identifying these issues against WCAG 2.2 guidelines and POUR principles allows you to generate a targeted remediation plan.

When should I not use ARIA to fix accessibility gaps?▼

You should not use ARIA to fix accessibility gaps when standard HTML semantics already provide the necessary screen reader support. Overusing ARIA can break keyboard navigation and contradict WCAG 2.2 guidelines, so apply it only when needed and guided by structured POUR principle checks.

Related Skills

Explore More Design & Creative Skills→
bdbchbdbch
2

accessibility-audit

Audit web pages for WCAG 2.1/2.2 compliance and report issues.

Community
Advanced
bipinksbipinks
3

accessibility-patterns

Apply WCAG 2.1 AA/AAA patterns to improve UI accessibility.

Community
Advanced
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced
AI-Foundry-CoreAI-Foundry-Core
4

wcag-audit-patterns

Audit WCAG 2.2 accessibility with automated testing and remediation guidance.

Official
Advanced