skills.rest
vh2224
vh2224COMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web pages for WCAG 2.1 compliance and suggest fixes.

1|Updated Jul 13, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#wcag#contrast
One-click install
npx skills add https://github.com/vh2224/forge-executor --skill accessibility-vh2224
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/vh2224/forge-executor/tree/main/src/resources/skills/accessibility
Command: npx skills add https://github.com/vh2224/forge-executor --skill accessibility-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you audit and improve web interfaces so they work well for people using keyboards, screen readers, high-contrast modes, reduced motion settings, and other assistive technologies.

Core Features & Use Cases

  • WCAG 2.1 Guidance: Apply clear accessibility requirements across perceivable, operable, understandable, and robust design.
  • Practical Audit Checklist: Check alt text, labels, contrast, focus states, keyboard access, live regions, and semantic HTML.
  • Reference-Backed Fixes: Use the included WCAG quick reference to validate issues and prioritize fixes by impact.
  • Use Case: Review a product page for missing form labels, poor contrast, and broken keyboard navigation, then rewrite the markup to meet accessibility standards.

Quick Start

Audit the attached web page for WCAG 2.1 issues and suggest the highest-priority fixes.

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 page for WCAG 2.1 compliance issues?▼

To audit web accessibility for WCAG 2.1 compliance, check semantic HTML structure, keyboard navigation, focus states, form labels, and color contrast against established quick reference criteria to identify and prioritize fixes.

What is the best way to fix keyboard navigation and screen reader compatibility on my site?▼

Fixing keyboard navigation and screen reader compatibility requires applying proper ARIA patterns, ensuring accessible HTML semantics, and validating focus management so dynamic UI components remain fully operable without a mouse.

Can I use this to check color contrast and alt text for web accessibility?▼

Yes, you can check color contrast ratios and image alt text by applying a practical audit checklist that verifies perceivable content requirements against WCAG 2.1 standards and suggests reference-backed fixes.

How do I make dynamic UI components and live regions accessible?▼

Make dynamic UI components and live regions accessible by implementing correct ARIA patterns and semantic HTML, ensuring that screen readers properly announce content changes and keyboard focus remains logically managed.

Does WCAG 2.1 compliance cover forms, media, and frontend navigation?▼

Yes, WCAG 2.1 compliance covers forms, media, and frontend navigation by requiring accessible HTML semantics, proper input labels, keyboard support, and screen reader compatibility across common frontend workflows.

What are common limitations when applying ARIA patterns for web accessibility?▼

A limitation when applying ARIA patterns for web accessibility is that misconfigured roles can break screen reader compatibility if the underlying HTML semantics are not properly structured and valid first.

Related Skills

Explore More Design & Creative Skills→
koralliskorallis
90

accessibility-wcag

Ensure web applications comply with WCAG 2.1/2.2 accessibility guidelines.

Community
Intermediate
kennedym-dskennedym-ds
14

accessibility-wcag

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

Community
Advanced
thec3ukthec3uk

Frontend Accessibility

Guide frontend code to meet accessibility standards like ARIA and keyboard navigation.

Official
Basic
sncollectivesncollective

scan-accessibility

Scan TSX files for WCAG 2.2 AA accessibility issues statically detectable in codebases.

Official
Intermediate