accessibility

Audit web accessibility against WCAG 2.1 and generate remediation plans.

11|2|Updated Jan 15, 2026

Search Tags:#accessibility #a11y #screen reader #ARIA #WCAG #audit

Ready to run

npx skills add https://github.com/runkids/my-skills --skill accessibility-runkids

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/runkids/my-skills/tree/main/accessibility
Command: npx skills add https://github.com/runkids/my-skills --skill accessibility-runkids

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility is often overlooked in web development, leaving sites unusable for users with disabilities. This Skill provides practical guidance, checklists, and examples to help teams identify and fix accessibility gaps in line with WCAG 2.1.

Core Features & Use Cases

WCAG-aligned audits: quick gap analysis against WCAG 2.1 criteria to prioritize fixes.
ARIA & semantics guidance: recommendations for proper labeling, roles, and relationships to improve assistive technology compatibility.
Remediation planning: actionable steps, sample code snippets, and a prioritized roadmap for fixes.
Use Case: audit a product page and generate a prioritized remediation list for developers.

Quick Start

Start by asking the Skill to review a given page for accessibility issues and return a remediation plan with concrete steps.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit a website for WCAG 2.1 accessibility compliance?▼

WCAG 2.1 audits identify gaps against accessibility standards by reviewing criteria across perceivability, operability, understandability, and robustness. Start by asking the Skill to review your page and generate a prioritized remediation list with concrete steps and fixes aligned to WCAG 2.1 guidelines.

What's the difference between ARIA roles and semantic HTML for accessibility?▼

Semantic HTML provides native meaning to assistive technologies; ARIA (Accessible Rich Internet Applications) adds roles, properties, and states when semantics alone are insufficient. Proper labeling and relationships through both improve screen reader compatibility and keyboard navigation.

How do I make a web application keyboard navigable?▼

Keyboard navigation ensures users without a mouse can reach all interactive elements. Implement logical tab order, visible focus indicators, and keyboard shortcuts aligned to ARIA patterns. The Skill provides actionable guidance and sample code for common components.

Can I test accessibility without specialized tools?▼

Yes. Manual testing with screen readers, keyboard-only navigation, and WCAG 2.1 checklists form the foundation. This Skill generates remediation plans with specific criteria to check, though full validation requires assistive technology testing and expert accessibility review.

What should I prioritize when fixing accessibility issues?▼

Prioritize by impact and effort. The Skill returns a prioritized roadmap ordering fixes—typically starting with critical barriers like missing alt text, keyboard traps, and focus management—before addressing nuanced ARIA improvements.

Does this work for single-page applications and complex web apps?▼

Yes. WCAG 2.1, ARIA patterns, and keyboard navigation apply across websites and web applications. The Skill provides guidance for dynamic content, form validation, modals, and other patterns common in SPAs and complex interfaces.