accessibility-checker

Audit web content for WCAG 2.1 AA accessibility issues and output a prioritized remediation report.

3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/peopleforrester/claude-dotfiles --skill accessibility-checker-peopleforrester
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-checker
Source: https://github.com/peopleforrester/claude-dotfiles/tree/main/skills/quality/accessibility-checker
Command: npx skills add https://github.com/peopleforrester/claude-dotfiles --skill accessibility-checker-peopleforrester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to systematically identify and remediate accessibility issues on web content, ensuring inclusive experiences for all users.

Core Features & Use Cases

  • WCAG checks: assess conformance to WCAG 2.1 AA criteria across pages and components.
  • Issue remediation guidance: provide clear steps to fix color contrast, keyboard navigation, semantic markup, and ARIA usage.
  • Use Case: Audit a marketing landing page to surface missing alt text, insufficient contrast, and inaccessible form controls, then produce an actionable remediation plan.

Quick Start

Launch the accessibility-checker against a target page (e.g., https://example.com) and review a prioritized list of fixes.

Frequently Asked Questions about accessibility-checker

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

FAQPage Schema
How do I audit a web page for WCAG 2.1 AA compliance?

WCAG compliance checks assess web pages against WCAG 2.1 AA criteria to identify color contrast, keyboard navigation, semantic markup, and ARIA issues. The audit outputs a prioritized remediation report guiding immediate fixes.

What's the best way to fix color contrast and ARIA issues on a landing page?

Fixing color contrast and ARIA issues requires running an accessibility audit on the target page. The checker surfaces inaccessible form controls and missing alt text, providing clear, prioritized remediation steps to update semantic markup and ARIA usage.

Can I check keyboard navigation across multiple UI components and forms?

Yes, you can check keyboard navigation across multiple UI components, pages, and forms. The accessibility audit systematically identifies keyboard navigation barriers and other WCAG 2.1 AA issues across your entire project.

Does this accessibility audit require any external dependencies or browser extensions?

No external dependencies are required to run the audit. You can launch the checker directly against a target page URL to evaluate WCAG 2.1 AA criteria and generate an actionable remediation plan without additional setup.

Why does my web audit only flag some elements and not all accessibility issues?

A web audit focuses on identifying WCAG 2.1 AA criteria violations, specifically targeting color contrast, keyboard navigation, semantic markup, and ARIA issues. It prioritizes these concrete fixes to produce an actionable remediation report.