skills.rest
yahav123147
yahav123147COMMUNITY
Explore all skills by this author →
GitHub

accessibility

Diagnose WCAG 2.1 compliance issues and recommend HTML/CSS/JS fixes.

1|Updated Apr 13, 2026
Search Tags:#screen reader#keyboard navigation#color contrast#web accessibility#wcag 2.1#lighthouse audit#form error handling
One-click install
npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill accessibility-yahav123147
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/yahav123147/paid-ads-cro-skills/tree/main/skills/accessibility
Command: npx skills add https://github.com/yahav123147/paid-ads-cro-skills --skill accessibility-yahav123147

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify and correct accessibility issues so your website or web app is usable for people with disabilities and meets WCAG 2.1 expectations.

Core Features & Use Cases

  • WCAG 2.1 guidance (POUR + conformance A/AA/AAA) to structure improvements around perceivable, operable, understandable, and robust principles.
  • Practical audits and fixes for common high-impact areas like text alternatives, color contrast, keyboard navigation, focus visibility, form labeling, error handling, and ARIA/live-region patterns.
  • Reference-backed implementation notes including Lighthouse/accessibility testing guidance and actionable patterns for screen readers, focus management, and non-text media.

Quick Start

Use the accessibility skill to audit your page for WCAG 2.1 issues and return a prioritized checklist of fixes for keyboard support, contrast, labels, and screen-reader behavior.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my website for WCAG 2.1 compliance issues?▼

To audit for WCAG 2.1 compliance, diagnose UI issues across keyboard navigation, focus management, form labeling, color contrast, and ARIA usage to generate a prioritized, implementation-ready checklist of HTML, CSS, and JS fixes.

What is the best way to fix keyboard navigation and focus visibility problems?▼

Fix keyboard navigation and focus visibility by mapping UI issues to relevant WCAG 2.1 success criteria under the Operable principle, then applying implementation-ready HTML, CSS, and JS patterns to manage focus states.

How do I handle form error states and labeling for screen readers?▼

Handle form error states and labeling for screen readers by applying ARIA and live-region patterns to structure error announcements, mapping fixes to WCAG 2.1 Understandable criteria for robust user input validation.

Does this accessibility audit approach support Lighthouse testing workflows?▼

Yes, this approach supports Lighthouse testing workflows by providing reference-backed implementation notes and actionable patterns that align with automated accessibility testing guidance for screen readers and non-text media.

Can I use this to evaluate color contrast and media alternatives for marketing pages?▼

Yes, you can evaluate color contrast and media alternatives for marketing pages by applying WCAG 2.1 Perceivable principles to diagnose content issues and provide implementation-ready patterns for non-text media.

When should I structure accessibility fixes around POUR principles?▼

Structure accessibility fixes around POUR principles when auditing complex product or marketing pages, ensuring perceivable, operable, understandable, and robust compliance by mapping each fix to specific WCAG 2.1 success criteria.

Related Skills

Explore More Legal & Compliance Skills→
shawn-sandyshawn-sandy

wcag-compliance-reviewer

Identify WCAG 2.1 AA accessibility violations in HTML/CSS and React/TypeScript code.

Community
Intermediate
MercurykzMercurykz

accessibility

Audit web pages against WCAG 2.1 and generate prioritized remediation plans.

Community
Intermediate
doanchienthangdevdoanchienthangdev
4

implementing-accessibility

Implement WCAG 2.1 AA compliant React interfaces with ARIA and keyboard navigation.

Community
Intermediate
matteocervellimatteocervelli
25

accessibility-checker

Identify and report WCAG 2.1 Level AA accessibility violations on web pages.

Community
Advanced