accessible-website-check

Audit website accessibility issues and identify WCAG gaps.

4|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AMindToThink/claude-code-settings --skill accessible-website-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessible-website-check
Source: https://github.com/AMindToThink/claude-code-settings/tree/main/skills/accessible-website-check
Command: npx skills add https://github.com/AMindToThink/claude-code-settings --skill accessible-website-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you spot and fix accessibility barriers in websites and web apps so more people can use your product with keyboards, screen readers, and other assistive tools.

Core Features & Use Cases

  • Accessibility Audits: Review pages, components, and front-end projects for WCAG-related issues such as contrast, focus states, labels, and keyboard access.
  • Prioritized Remediation: Turn audit findings into a clear plan that separates blockers, major issues, and minor polish.
  • Implementation Guidance: Apply approved fixes methodically and verify the results against a structured checklist.
  • Use Case: Use this Skill before launch to catch missing alt text, broken heading structure, inaccessible custom controls, and other common a11y regressions.

Quick Start

Ask the Skill to audit the website or repository for accessibility issues and return a prioritized remediation plan.

Frequently Asked Questions about accessible-website-check

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

FAQPage Schema
How do I audit my website for WCAG and keyboard navigation issues?

Run an accessibility audit on your web pages or front-end project to identify WCAG gaps in keyboard navigation, screen reader support, and contrast. The review produces a prioritized remediation plan with concrete fixes and verification steps.

What is the best way to check screen reader support and alt text before launch?

Perform a pre-launch accessibility audit to check screen reader support and alt text. This review catches missing alt text, broken heading structures, and inaccessible custom controls, then returns a prioritized list of blockers and major issues.

Can I use an accessibility audit to fix form semantics and focus states?

Yes, you can use an accessibility audit to fix form semantics and focus states. The audit reviews front-end components for label compliance and focus management, separating blockers from minor polish to guide methodical implementation.

Does this web audit work for individual front-end components or only full pages?

This web audit works for both individual front-end components and full pages. It applies plan-mode reviews against design and code checklists to evaluate contrast, labels, and keyboard access regardless of the project scope.

How do I prioritize accessibility fixes when I find multiple WCAG gaps?

Prioritize accessibility fixes by separating audit findings into blockers, major issues, and minor polish. This structured remediation plan ensures critical keyboard navigation and screen reader barriers are resolved before minor contrast adjustments.

When should I not rely on a checklist-based web accessibility audit?

A checklist-based web accessibility audit may not catch dynamic runtime issues if the front-end project lacks static HTML to review. Use it to identify structural WCAG gaps in semantics and contrast, but verify interactive keyboard behavior manually.