skills.rest
LuisSambrano
LuisSambranoCOMMUNITY
Explore all skills by this author →
𝕏@luissambrano_uxGitHub

accessibility

Audit web accessibility with Lighthouse and axe-core for WCAG 2.1 compliance.

7|2|Updated Jan 28, 2026
Search Tags:#accessibility#a11y#screen reader#web development#keyboard navigation#WCAG
One-click install
npx skills add https://github.com/LuisSambrano/antigravity-config --skill accessibility-luissambrano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/LuisSambrano/antigravity-config/tree/main/skills/3-web/wq-accessibility
Command: npx skills add https://github.com/LuisSambrano/antigravity-config --skill accessibility-luissambrano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web content usable by everyone, including individuals with disabilities, by adhering to established accessibility standards.

Core Features & Use Cases

  • WCAG 2.1 Compliance: Provides guidelines and code examples for meeting Perceivable, Operable, Understandable, and Robust (POUR) principles.
  • Automated & Manual Testing: Includes commands for automated audits (Lighthouse, axe-core) and a checklist for manual verification.
  • Use Case: A development team needs to ensure their new web application meets legal accessibility requirements. They use this Skill to audit their existing components and implement necessary fixes for color contrast, keyboard navigation, and screen reader compatibility.

Quick Start

Run a Lighthouse accessibility audit on the provided URL.

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 application for WCAG 2.1 compliance?▼

To audit web accessibility for WCAG 2.1 compliance, you can run automated tests using Lighthouse or axe-core, and perform manual checks for keyboard navigation, screen reader compatibility, and color contrast.

How do I fix keyboard navigation and focus visibility issues in web development?▼

Fixing keyboard accessibility and focus visibility involves auditing your web components with axe-core and applying WCAG 2.1 Operable principle guidelines to ensure all interactive elements are reachable and visible via keyboard.

What is the best way to test screen reader compatibility and ARIA usage?▼

Testing screen reader compatibility and ARIA usage requires manual verification alongside automated Lighthouse audits to ensure correct implementation of WCAG 2.1 Robust and Perceivable principles for assistive technologies.

Does this accessibility approach work with existing web development components?▼

Yes, this accessibility auditing approach works with existing web development components by evaluating text alternatives, form labels, and ARIA usage against WCAG 2.1 guidelines to identify and implement necessary fixes.

Why do I need both automated testing and manual checks for web accessibility?▼

Automated testing with Lighthouse and axe-core catches baseline accessibility issues, but manual checks are required to verify keyboard navigation, screen reader compatibility, and color contrast for full WCAG 2.1 compliance.

When should I not rely solely on automated accessibility audits?▼

You should not rely solely on automated accessibility audits because tools like Lighthouse cannot fully evaluate manual checks such as keyboard navigation flow, screen reader compatibility, and contextual ARIA usage.

Related Skills

Explore More Software Engineering Skills→
williamzujkowskiwilliamzujkowski
6

Frontend Accessibility Validator

Run automated WCAG 2.2 accessibility checks with axe-core, Pa11y, and Lighthouse.

Community
Advanced
gsd-buildgsd-build
7.8k

accessibility

Audit web projects for WCAG 2.1 accessibility issues and generate remediation plans.

Official
Advanced
V4-CompanyV4-Company
2

marsai:dev-frontend-accessibility

Run axe-core accessibility scans on React/TypeScript UI components.

Official
Intermediate
bdbchbdbch
2

accessibility-review

Audit web applications for WCAG 2.1/2.2 accessibility compliance in Chrome.

Community
Advanced