skills.rest
kevyder
kevyderCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Audit web content for WCAG 2.2 compliance using POUR principles.

Updated Aug 23, 2026
Search Tags:#checklist#accessibility#a11y#usability#wcag#web-a11y#a11y-patterns
One-click install
npx skills add https://github.com/kevyder/thekevshot --skill accessibility-kevyder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/kevyder/thekevshot/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/kevyder/thekevshot --skill accessibility-kevyder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

Core Features & Use Cases

  • POUR framework: Perceivable, Operable, Understandable, Robust guidelines to evaluate and improve content.
  • Conformance levels: Explain Level A/AA/AAA requirements and how to target them.
  • Practical patterns: Reference accessible patterns and checklists in references/A11Y-PATTERNS.md and WCAG.md to implement fixes in real projects.
  • Use Case: When auditing a site, identify missing alt text, keyboard traps, or color contrast issues, and craft remediation tasks.

Quick Start

Audit a web page for accessibility and implement WCAG 2.2 compliant improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit web content for WCAG 2.2 compliance?▼

To audit web content for WCAG 2.2 compliance, evaluate your site against the POUR framework principles: Perceivable, Operable, Understandable, and Robust. This identifies accessibility barriers like missing alt text or keyboard traps and generates prioritized remediation tasks.

What is the difference between WCAG 2.2 conformance levels A, AA, and AAA?▼

WCAG 2.2 conformance levels A, AA, and AAA represent increasing degrees of web accessibility requirements. Level A addresses basic barriers, AA targets common accessibility issues, and AAA represents the highest, most specialized compliance tier.

How do I fix keyboard navigation traps and screen reader support issues?▼

Fix keyboard navigation traps and screen reader support issues by applying practical A11Y patterns from the references directory. Implement standard interactive roles, manage focus logically, and ensure all operable elements are fully accessible without a mouse.

Does this accessibility audit approach work for both websites and web apps?▼

Yes, this accessibility audit approach works for both websites and web apps. It systematically applies WCAG 2.2 guidelines and POUR principles across diverse web content, ensuring robust usability and compliance for all digital interfaces.

What is the best way to prioritize accessibility remediation tasks?▼

The best way to prioritize accessibility remediation tasks is by evaluating WCAG 2.2 conformance levels and POUR principles. Address Level A barriers first, such as missing alt text and severe color contrast issues, before progressing to Level AA and AAA requirements.

Related Skills

Explore More Design & Creative Skills→
rohitg00rohitg00
2.5k

accessibility-wcag

Identify accessibility gaps and enforce WCAG 2.2 patterns on web content.

Community
Intermediate
imkdwimkdw
1

Frontend Accessibility

Implement accessible React components with ARIA, keyboard navigation, and WCAG compliance.

Community
Intermediate
Community-AccessCommunity-Access
387

Contrast Master

Audit color contrast and visual accessibility for WCAG AA compliance.

Official
Advanced
RepairYourTechRepairYourTech
6

accessibility

Audit web accessibility against WCAG 2.1 guidelines and provide code examples.

Community
Intermediate