skills.rest
nshonda
nshondaCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web projects for WCAG 2.1 accessibility issues and apply fixes.

Updated Aug 23, 2026
Search Tags:#accessibility#a11y#usability#wcag#screen-reader#aria#keyboard-navigation
One-click install
npx skills add https://github.com/nshonda/workstation-setup --skill accessibility-nshonda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/nshonda/workstation-setup/tree/main/claude/skills/accessibility
Command: npx skills add https://github.com/nshonda/workstation-setup --skill accessibility-nshonda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and fix accessibility issues that prevent users with disabilities from effectively using a website, reducing friction and risk of non-compliance.

Core Features & Use Cases

  • Automated audits identify missing alt text, color contrast failures, keyboard traps, and ARIA misuse.
  • Guidance & patterns provide practical WCAG-aligned examples and implementation tips for developers.
  • Use Case: When shipping a new web app or updating an existing site, run audits and apply fixes to reach accessibility standards.

Quick Start

Audit a web project for accessibility using the guidance in this skill.

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

Audit your web application for WCAG 2.1 compliance by running automated checks to identify missing alt text, color contrast failures, keyboard traps, and ARIA misuse. This process helps ensure digital experiences are perceivable, operable, understandable, and robust for users with disabilities.

What is the best way to fix keyboard navigation and screen reader support issues?▼

Fix keyboard navigation and screen reader support issues by applying practical WCAG-aligned examples and semantic HTML patterns. These implementations guide developers in resolving accessibility barriers like keyboard traps and improper ARIA usage during development and review cycles.

How do I check color contrast and ARIA usage against Lighthouse accessibility practices?▼

Check color contrast and ARIA usage against Lighthouse practices by auditing your web project for accessibility failures. The audit identifies specific color contrast issues and ARIA misuse, providing actionable guidance to align your components with standard practices.

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

Yes, this accessibility audit works for both new web apps and existing websites across platforms. When shipping new projects or updating existing sites, you can run these automated audits and apply fixes to reach accessibility standards.

Why does my web accessibility audit fail on missing alt text and semantic HTML?▼

Your web accessibility audit fails on missing alt text and semantic HTML because these elements are required to make digital experiences perceivable and operable. The audit identifies these specific failures and provides practical implementation tips to resolve them.

Related Skills

Explore More Software Engineering Skills→
BambibannersBambibanners
1

Accessibility Audit (WCAG)

Scan React/HTML source files for WCAG accessibility violations and generate line-referenced reports.

Community
Intermediate
nhonvonhonvo

accessibility-expert

Identify web accessibility issues and propose WCAG-compliant fixes including ARIA, keyboard navigation, and screen reader compatibility.

Community
Advanced
AZANIRAZANIR
2

qa-accessibility-test-writer

Generate automated WCAG 2.2 accessibility tests using axe-core, Pa11y, Lighthouse, Playwright, Cypress, and Jest.

Community
Intermediate
soeiroosoeiroo

accessibility-test-plan

Plan WCAG-aligned accessibility testing strategies for web applications.

Community
Intermediate