accessibility

Audit web projects for WCAG 2.2 accessibility compliance.

16|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Jannael/Glinter --skill accessibility-jannael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Jannael/Glinter/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/Jannael/Glinter --skill accessibility-jannael

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Auditing and improving web accessibility to meet WCAG 2.2 guidelines, ensuring content is usable by people with disabilities.

Core Features & Use Cases

  • Comprehensive WCAG 2.2 guidance and Lighthouse accessibility audits to identify and remedy accessibility gaps.
  • POUR-based recommendations with practical patterns and examples to improve perceivable, operable, understandable, and robust content.
  • Use Case: Evaluate a product's UI to ensure keyboard navigation, screen reader compatibility, color contrast, and semantic markup.

Quick Start

Run an accessibility audit against your web pages and apply WCAG 2.2 patterns to achieve compliant interfaces.

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?

WCAG 2.2 compliance audits evaluate your web pages against POUR principles to identify gaps in keyboard navigation, screen reader compatibility, color contrast, and semantic markup, providing actionable remediation steps.

What is the best way to check keyboard navigation and screen reader compatibility?

Checking keyboard navigation and screen reader compatibility involves evaluating your product's UI using Lighthouse accessibility audits and POUR-based patterns to ensure operable and robust content for assistive technologies.

How do I fix color contrast issues to meet web accessibility standards?

Fixing color contrast for web accessibility standards requires auditing your interfaces against WCAG 2.2 guidelines to identify perceivable content failures and applying structured remediation patterns to achieve compliant contrast ratios.

Can I use this approach to audit accessibility for both websites and web apps?

Yes, you can audit accessibility for both sites and apps by running evaluations against WCAG 2.2 standards to ensure usable interfaces across diverse web projects, applying POUR-based recommendations for remediation.

What are the limitations of automated Lighthouse accessibility audits?

Automated Lighthouse accessibility audits identify structural gaps in semantic markup and color contrast, but achieving full WCAG 2.2 conformance requires manual POUR-based evaluation for keyboard navigation and screen reader compatibility.