accessibility

Audit web interfaces for WCAG 2.2 compliance and implement accessible patterns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of ensuring web content is usable by everyone, including individuals with disabilities, by providing a structured framework for WCAG 2.2 compliance.

Core Features & Use Cases

  • WCAG Compliance Auditing: Provides a comprehensive checklist based on the POUR principles (Perceivable, Operable, Understandable, Robust).
  • Code Pattern Implementation: Offers ready-to-use patterns for accessible components like modals, skip links, and error handling.
  • Use Case: Use this skill to perform a manual accessibility audit on a new landing page to ensure all interactive elements meet the 24x24px target size requirement and have proper ARIA labels.

Quick Start

Use the accessibility skill to perform a WCAG 2.2 audit on the current project and identify critical missing labels or contrast issues.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my web project for WCAG 2.2 compliance?

To audit web accessibility for WCAG 2.2 compliance, evaluate your interface against the POUR principles (Perceivable, Operable, Understandable, Robust) to identify missing labels, contrast issues, and keyboard navigation gaps.

What are the best accessible design patterns for modals and skip links?

The best accessible design patterns for modals and skip links use semantic HTML and standardized ARIA attributes to ensure robust screen reader support, proper keyboard navigation, and focus management across interactive web components.

How do I fix color contrast and target size issues for inclusive design?

To fix color contrast and target size issues in inclusive design, verify that interactive elements meet the 24x24px target size requirement and adjust foreground and background color ratios to satisfy WCAG 2.2 contrast compliance standards.

When do I need standardized ARIA usage and semantic HTML for assistive technologies?

You need standardized ARIA usage and semantic HTML for assistive technologies when interactive web elements lack native semantics, ensuring screen readers properly interpret keyboard navigation, error handling, and dynamic UI updates.

Does this accessibility audit approach work for manual landing page reviews?

Yes, this accessibility audit approach works for manual landing page reviews by systematically checking all interactive elements against the WCAG 2.2 checklist to ensure proper ARIA labels, contrast, and target sizes are met.

Why does my screen reader skip interactive elements during keyboard navigation?

Your screen reader skips interactive elements during keyboard navigation when semantic HTML is missing or ARIA roles are misconfigured, preventing assistive technologies from properly mapping focus states and element functionality.