skills.rest
Khrees2412
Khrees2412COMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web content against WCAG 2.1 and Lighthouse accessibility guidelines.

Updated Dec 28, 2025
Search Tags:#accessibility#a11y#ARIA#WCAG#lighthouse#web-a11y
One-click install
npx skills add https://github.com/Khrees2412/grepbase --skill accessibility-khrees2412
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Khrees2412/grepbase/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/Khrees2412/grepbase --skill accessibility-khrees2412

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility issues block users with disabilities from accessing content; this Skill provides comprehensive WCAG-guided guidelines, practical examples, and hands-on strategies to improve inclusive web experiences.

Core Features & Use Cases

  • WCAG 2.1 and POUR-based guidelines and Lighthouse accessibility audits to evaluate and improve content accessibility.
  • ARIA patterns, keyboard accessibility, focus management, skip links, and semantic HTML guidance to ensure operability and understandability.
  • Use cases include auditing new web pages, retrofitting existing sites for accessibility compliance, and producing remediation checklists for development teams.

Quick Start

Audit a web page for accessibility against WCAG 2.1 and Lighthouse guidelines and generate a prioritized remediation plan.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a web page for WCAG 2.1 compliance?▼

To audit web accessibility, apply WCAG 2.1 guidelines and Lighthouse audits to evaluate content against POUR principles. This process identifies issues across perceivable, operable, understandable, and robust categories, generating a prioritized remediation plan for developers.

What is the best way to fix ARIA patterns and keyboard navigation issues?▼

Fixing ARIA patterns and keyboard navigation requires applying semantic HTML, managing focus states, and implementing skip links. This ensures operability and understandability for dynamic web content, aligning with WCAG 2.1 standards for keyboard accessibility.

Can I use Lighthouse and axe to validate web accessibility automatically?▼

Yes, you can validate web accessibility using automated tests like Lighthouse and axe. These tools evaluate content against WCAG 2.1 guidelines to detect structural and labeling issues, providing actionable remediation guidance for QA teams.

Does this approach handle both static and dynamic web content accessibility?▼

Yes, this accessibility approach handles both static and dynamic contexts. By applying ARIA patterns, keyboard navigation standards, and POUR principles, it structures and tests content to ensure inclusive design across various web page types.

When do I need to apply POUR principles for web accessibility?▼

Apply POUR principles when auditing new web pages or retrofitting existing sites for accessibility compliance. These perceivable, operable, understandable, and robust guidelines structure content evaluation and produce remediation checklists for development teams.

Related Skills

Explore More Design & Creative Skills→
RB-chrismandichRB-chrismandich
1

a11y-audit

Audit web projects for WCAG 2.2 AA accessibility issues with ARIA and semantic HTML checks.

Community
Advanced
wredziowredzio

accessibility

Identify and remediate WCAG 2.1 AA accessibility issues in web pages.

Community
Advanced
nanorepublicananorepublica
61

Frontend Accessibility

Enforce frontend accessibility compliance in HTML, CSS, and JavaScript components.

Community
Basic
CENKSSSCENKSSS

accessibility-testing

Validate web application accessibility against WCAG 2.2 standards.

Community
Advanced