accessibility

Audit web content for WCAG 2.1 accessibility issues.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/workleap/wl-agents-code-review-poc --skill accessibility-workleap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/workleap/wl-agents-code-review-poc/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/workleap/wl-agents-code-review-poc --skill accessibility-workleap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skill helps teams identify and remediate accessibility issues in web content to meet WCAG 2.1 guidelines, improving usability for users with disabilities and reducing compliance risk.

Core Features & Use Cases

  • WCAG-aligned audits: Reference POUR principles to assess perceivable, operable, understandable, and robust content.
  • Guidance and examples: Provide practical remediation steps for common issues like color contrast, keyboard navigation, and ARIA usage.
  • Use Case: When auditing a new product page, run checks and produce a prioritized remediation plan for designers and developers.

Quick Start

Start by requesting an accessibility audit for a specific URL or HTML snippet and receive a prioritized checklist with remediation examples.

Frequently Asked Questions about accessibility

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

FAQPage Schema
What is the process for generating an accessibility remediation plan for a new product page?

The process involves running an accessibility audit on the new product page, which checks for WCAG 2.1 violations and outputs a prioritized remediation plan with actionable guidelines and examples for the design and development team.

How do I audit my web page for WCAG 2.1 accessibility issues?

You can audit web content for WCAG 2.1 accessibility issues by providing a URL or HTML snippet to receive a prioritized remediation checklist covering POUR principles, color contrast, keyboard navigation, and ARIA usage.

What is the best way to check if my UI components meet screen reader and keyboard navigation requirements?

The best way to verify screen reader and keyboard navigation support is to evaluate UI components against WCAG 2.1 guidelines, generating actionable examples and remediation steps to improve operability and robustness.

Can I use this to get remediation examples for ARIA usage and color contrast failures?

Yes, you can request an accessibility audit to identify specific ARIA usage and color contrast failures, receiving practical remediation examples and a prioritized action plan for designers and developers.

Does this accessibility audit evaluate content based on all four POUR principles?

Yes, this accessibility audit evaluates web content against all four POUR principles—perceivable, operable, understandable, and robust—to ensure comprehensive WCAG 2.1 compliance and reduce usability barriers for people with disabilities.

What is the process for generating an accessibility remediation plan for a new product page?

The process involves running an accessibility audit on the new product page, which checks for WCAG 2.1 violations and outputs a prioritized remediation plan with actionable guidelines and examples for the design and development team.