accessibility

Audit web accessibility against WCAG 2.1 using Lighthouse and axe-core.

1|2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/ihmorol/unsw-nb15-handling-binary-multiclass-ids --skill accessibility-ihmorol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/ihmorol/unsw-nb15-handling-binary-multiclass-ids/tree/main/.opencode/skills/accessibility
Command: npx skills add https://github.com/ihmorol/unsw-nb15-handling-binary-multiclass-ids --skill accessibility-ihmorol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make digital content usable by everyone, including people with disabilities, by auditing and improving web accessibility based on established guidelines.

Core Features & Use Cases

  • WCAG 2.1 Compliance: Provides guidance and checks against Perceivable, Operable, Understandable, and Robust (POUR) principles.
  • Automated Testing Integration: Includes commands for running automated accessibility audits using tools like Lighthouse and axe-core.
  • Manual Testing Checklist: Offers a comprehensive checklist for manual verification, including keyboard navigation and screen reader testing.
  • Use Case: A web development team needs to ensure their new website meets accessibility standards before launch. They can use this Skill to audit their pages, identify issues like poor color contrast or missing alt text, and receive actionable recommendations for fixes.

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

You can audit web accessibility by running automated tools like Lighthouse and axe-core, which check against WCAG 2.1 guidelines across Perceivable, Operable, Understandable, and Robust principles.

What is the difference between automated and manual screen reader testing?

Automated testing uses tools like axe-core to detect code-level issues like missing alt text, while manual screen reader testing verifies actual user navigation, focusing on operability and understandability.

How do I check keyboard navigation for web accessibility?

You check keyboard navigation by following a manual testing checklist that verifies users can access all interactive elements without a mouse, ensuring compliance with WCAG operable principles.

Can I use Lighthouse to fix poor color contrast and missing alt text?

Yes, you can use Lighthouse to identify accessibility issues like poor color contrast and missing alt text, providing actionable recommendations to fix these specific web standards violations.

What WCAG principles are covered by web accessibility audits?

Web accessibility audits cover the four WCAG 2.1 principles: Perceivable, Operable, Understandable, and Robust, ensuring digital content is usable by people with diverse disabilities.

Does axe-core support automated testing for all WCAG 2.1 guidelines?

axe-core supports automated testing for many WCAG 2.1 guidelines, but manual testing checklists are required for aspects like screen reader compatibility and keyboard navigation.