accessibility

Identify WCAG 2.1 accessibility issues and provide remediation guidance.

77|3|Updated Mar 24, 2026

Search Tags:#accessibility #a11y #wcag #lighthouse #color-contrast #aria #keyboard-navigation

Ready to run

npx skills add https://github.com/FlorianBruniaux/starmapper --skill accessibility-florianbruniaux

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/FlorianBruniaux/starmapper/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/FlorianBruniaux/starmapper --skill accessibility-florianbruniaux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This comprehensive guide provides WCAG 2.1 and Lighthouse-based accessibility heuristics to help teams make web content usable by everyone, including people with disabilities.

Core Features & Use Cases

WCAG 2.1, POUR principles, keyboard-navigation, color-contrast, ARIA usage, skip links, and motion preferences guidance.
Auditing websites, apps, and components; providing concrete remediation steps and testing guidance; integrating accessibility checks into development workflows.
Use case: run an accessibility audit on a product page, apply fixes, and verify improvements with automated checks and screen reader considerations.

Quick Start

Run a quick accessibility review on your web page and implement the recommended WCAG 2.1 improvements.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I run a WCAG 2.1 accessibility audit on a web page?▼

Run a WCAG 2.1 accessibility audit by evaluating web content against POUR principles, color contrast, ARIA usage, keyboard navigation, and skip links to identify actionable issues and remediation steps.

What is the best way to fix Lighthouse color-contrast accessibility failures?▼

Fix Lighthouse color-contrast failures by applying WCAG 2.1 contrast ratio guidance to your web components, ensuring text remains readable and compliant for users with visual impairments.

How does ARIA usage affect keyboard navigation compliance?▼

Proper ARIA usage affects keyboard navigation by defining roles and states that assistive technologies rely on, ensuring interactive elements remain operable without a mouse.

Can I integrate accessibility checks into existing development workflows?▼

Yes, you can integrate accessibility checks into development workflows by applying Lighthouse audit findings and WCAG criteria across websites and components during the build process.

Why do skip links matter for web accessibility compliance?▼

Skip links matter for accessibility because they let keyboard and screen reader users bypass repetitive navigation, directly fulfilling WCAG operable requirements and improving user experience.

What are the limitations of automated Lighthouse accessibility audits?▼

Automated Lighthouse audits detect structural issues like missing ARIA or contrast failures, but manual screen reader testing remains necessary to verify actual usability and POUR compliance.