accessibility

Audit web content for WCAG 2.2 conformance and accessibility gaps.

Updated Apr 6, 2025
One-click install
npx skills add https://github.com/Monosen/golink --skill accessibility-monosen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Monosen/golink/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/Monosen/golink --skill accessibility-monosen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility by applying WCAG 2.2 guidelines and Lighthouse audits to identify and remediate accessibility gaps across modern web content.

Core Features & Use Cases

  • Comprehensive auditing patterns for POUR, perceivable, operable, understandable, and robust criteria.
  • Guidance for remediation with WCAG-aligned patterns and Lighthouse-inspired checks.
  • Use cases include audits of landing pages, dashboards, forms, and SPA components, with concrete remediation steps.

Quick Start

Run a quick accessibility scan on a page or app and implement the top 3 fixes recommended by the audit.

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 project for WCAG 2.2 compliance?

To audit web accessibility for WCAG 2.2 compliance, apply comprehensive auditing patterns against POUR criteria and Lighthouse-inspired checks to identify gaps across landing pages, dashboards, forms, and SPA components.

What is the best way to fix keyboard and screen reader accessibility gaps?

The best way to fix keyboard and screen reader accessibility gaps is by applying WCAG-aligned remediation patterns and ARIA patterns to dynamic interfaces, ensuring operable and robust web content for assistive technologies.

How do I remediate color-contrast issues in web components?

Remediate color-contrast issues by applying WCAG 2.2 perceivable criteria and Lighthouse audits to web components, implementing actionable remediation patterns to satisfy automated checks for inclusive design.

Does this approach work for auditing single-page application components?

Yes, this accessibility auditing approach works for single-page application components by applying WCAG guidelines and Lighthouse audits to dynamic interfaces, providing concrete remediation steps for SPA accessibility gaps.

Why do automated accessibility checks fail on my dynamic web interfaces?

Automated accessibility checks fail on dynamic web interfaces when they lack proper ARIA patterns and keyboard support, requiring WCAG 2.2 aligned remediation patterns to satisfy robust and operable conformance criteria.